mirror/Meshtastic-Android
1
0
Fork 0
mirror of https://github.com/meshtastic/Meshtastic-Android.git synced 2026-07-10 21:36:00 -04:00
Code Issues Packages Projects Releases Wiki Activity

chore: Scheduled updates (Firmware, Hardware, Translations, Graphs) (#5465)

Browse Source
This commit is contained in:
James Rich
2026-05-19 10:12:04 -05:00
committed by GitHub
parent a141df4372
commit 83bb1a31f7
743 changed files with 89519 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
androidApp/README.md
View File

@@ -49,6 +49,7 @@ graph TB
:androidApp -.-> :feature:map
:androidApp -.-> :feature:node
:androidApp -.-> :feature:settings
:androidApp -.-> :feature:docs
:androidApp -.-> :feature:firmware
:androidApp -.-> :feature:wifi-provision
:androidApp -.-> :feature:widget

15
androidApp/src/main/assets/device_hardware.json
View File

@@ -1398,5 +1398,20 @@
"images": [
"mini-epaper-s3.svg"
]
},
{
"hwModel": 127,
"hwModelSlug": "HELTEC_MESH_NODE_T096",
"platformioTarget": "heltec-mesh-node-t096",
"architecture": "nrf52840",
"activelySupported": false,
"supportLevel": 1,
"displayName": "Heltec Mesh Node 096",
"tags": [
"Heltec"
],
"images": [
"heltec-mesh-node-t096.svg"
]
}
]

2
core/resources/src/commonMain/composeResources/values-ar/strings.xml generated
View File

@@ -70,6 +70,8 @@
<string name="display">إعدادات الشاشة</string>
<!-- DISTANCE -->
<string name="distance">المسافة</string>
<!-- DOC -->
<string name="doc_title_mqtt">MQTT</string>
<string name="edit">تعديل</string>
<string name="eight_hours">8 ساعات</string>
<!-- ENCRYPTION -->

3
core/resources/src/commonMain/composeResources/values-be/strings.xml generated
View File

@@ -85,6 +85,9 @@
<string name="display">Экран</string>
<!-- DISTANCE -->
<string name="distance">Адлегласць</string>
<!-- DOC -->
<string name="doc_title_mqtt">MQTT</string>
<string name="doc_title_onboarding">Начало работы</string>
<string name="download">Сцягнуць</string>
<string name="edit">Змяніць</string>
<string name="eight_hours">8 Гадзін</string>

7
core/resources/src/commonMain/composeResources/values-bg/strings.xml generated
View File

@@ -262,6 +262,13 @@
<string name="distance_measurements">Измервания на разстояния</string>
<string name="distance_measurements_description">Показване на разстоянието между вашия телефон и други възли на Meshtastic с позиции.</string>
<string name="dns">DNS</string>
<!-- DOC -->
<string name="doc_clear_search">Изчистване на търсенето</string>
<string name="doc_title_connections">Връзки</string>
<string name="doc_title_discovery">Откриване</string>
<string name="doc_title_mqtt">MQTT</string>
<string name="doc_title_nodes">Възли</string>
<string name="doc_title_onboarding">Първи стъпки</string>
<string name="done">Готово</string>
<string name="dont_show_again_for_device">Да не се показва отново за това устройство</string>
<string name="downlink_enabled">Downlink активиран</string>

1
core/resources/src/commonMain/composeResources/values-ca/strings.xml generated
View File

@@ -63,6 +63,7 @@
<!-- DISPLAY -->
<!-- DISTANCE -->
<string name="distance">Distància</string>
<!-- DOC -->
<string name="edit">Editar</string>
<string name="eight_hours">8 Hores</string>
<!-- ENCRYPTION -->

6
core/resources/src/commonMain/composeResources/values-cs/strings.xml generated
View File

@@ -287,6 +287,12 @@
<string name="distance_filters_description">Filtrovat seznam uzlů a mesh mapu podle vzdálenosti od vašeho telefonu.</string>
<string name="distance_measurements">Měření vzdálenosti</string>
<string name="distance_measurements_description">Zobrazí vzdálenost mezi vaším telefonem a ostatními uzly Meshtastic s určenou polohou.</string>
<!-- DOC -->
<string name="doc_clear_search">Vymazat hledání</string>
<string name="doc_title_connections">Připojení</string>
<string name="doc_title_discovery">Objevujte</string>
<string name="doc_title_mqtt">MQTT</string>
<string name="doc_title_nodes">Uzly</string>
<string name="done">Hotovo</string>
<string name="double_tap_as_button_press">Dvojité klepnutí jako stisk tlačítka</string>
<string name="downlink_enabled">Stahování povoleno</string>

23
core/resources/src/commonMain/composeResources/values-de/strings.xml generated
View File

@@ -324,6 +324,14 @@
<string name="distance_measurements">Entfernungsmessungen</string>
<string name="distance_measurements_description">Zeigt den Abstand zwischen Ihrem Telefon und anderen Meshtastic Knoten mit einem Standort an.</string>
<string name="dns">DNS</string>
<!-- DOC -->
<string name="doc_clear_search">Neue Suche</string>
<string name="doc_title_connections">Verbindungen</string>
<string name="doc_title_discovery">Entdecken</string>
<string name="doc_title_firmware">Firmwareaktualisierungen</string>
<string name="doc_title_mqtt">MQTT</string>
<string name="doc_title_nodes">Knoten</string>
<string name="doc_title_onboarding">Erste Schritte</string>
<string name="done">Fertig</string>
<string name="dont_show_again_for_device">Für dieses Gerät nicht erneut anzeigen</string>
<string name="double_tap_as_button_press">Doppelklick als Taste</string>
@@ -731,6 +739,7 @@
<string name="mute_always">Immer</string>
<string name="mute_notifications">Benachrichtigungen stummschalten</string>
<string name="mute_remove">Benachrichtigungen für '%1$s ' einschalten?</string>
<string name="mute_selected">Auswahl stumm schalten</string>
<string name="mute_status_always">Immer stumm</string>
<string name="mute_status_muted_for_days">Stumm für %1$d Tage, %2$s Stunden</string>
<string name="mute_status_muted_for_hours">Stumm für %1$s Stunden</string>
@@ -1135,6 +1144,7 @@
<string name="store_forward_config">Speichern &amp; Weiterleiten Einstellungen</string>
<string name="store_forward_enabled">Speichern &amp; Weiterleiten aktiviert</string>
<string name="subnet">Subnet</string>
<string name="success">Erfolgreich</string>
<string name="super_deep_sleep_duration_seconds">Dauer Supertiefschlaf</string>
<string name="supported">Unterstützt</string>
<string name="supported_by_community">Unterstützt von der Meshtastic Gemeinschaft</string>
@@ -1153,8 +1163,19 @@
<string name="tak_role_teamlead">Teamleiter</string>
<string name="tak_role_teammember">Teammitglied</string>
<string name="tak_role_unspecified">Unspecified</string>
<string name="tak_server">TAK Server</string>
<string name="tak_server_enabled">Lokalen TAK Server aktivieren</string>
<string name="tak_server_enabled_desc">Startet einen lokalen TLS-Server auf Port 8089 für ATAK/iTAK Verbindungen</string>
<string name="tak_server_export_data_package_desc">Erstelle .zip für ATAK/iTAK um sich mit diesem Server zu verbinden</string>
<string name="tak_server_loading">…</string>
<string name="tak_server_section">Server</string>
<string name="tak_server_test_card_title">TAK Mesh Test (Debug)</string>
<string name="tak_server_test_idle">Alle %1$d Tests an das Netz senden</string>
<string name="tak_server_test_result_bytes">%1$dB ✓</string>
<string name="tak_server_test_result_unknown_error">✗</string>
<string name="tak_server_test_results">%1$d bestanden, %2$d fehlgeschlagen von %3$d/%4$d</string>
<string name="tak_server_test_run">Ausführen</string>
<string name="tak_server_test_running">Ausführen: %1$s</string>
<string name="tak_team">Teamfarbe</string>
<string name="tak_team_blue">Blau</string>
<string name="tak_team_brown">Braun</string>
@@ -1247,6 +1268,7 @@
<string name="unmessageable">Nicht erreichbar</string>
<string name="unmonitored_or_infrastructure">Unbeaufsichtigt oder Infrastruktur</string>
<string name="unmute">Stummschaltung aufheben</string>
<string name="unmute_selected">Auswahl aktivieren</string>
<string name="unrecognized">Unbekannt</string>
<string name="unset">Nicht gesetzt - 0</string>
<string name="up_down_select_input_enabled">Up/Down/Select Eingang aktiviert</string>
@@ -1302,6 +1324,7 @@
<string name="wifi_provision_description">Stellen Sie Ihrem mPWRD-OS Gerät WLAN Zugangsdaten über Bluetooth zur Verfügung.</string>
<string name="wifi_provision_device_found">Gerät gefunden</string>
<string name="wifi_provision_device_found_detail">Bereit zur Suche nach WLAN Netzwerken.</string>
<string name="wifi_provision_hidden_network">Verstecktes Netzwerk</string>
<string name="wifi_provision_mpwrd_disclaimer">Erfahren Sie mehr über das mPWRD-OS Projekt\nhttps://github.com/mPWRD-OS</string>
<string name="wifi_provision_no_networks">Keine Netzwerke gefunden</string>
<string name="wifi_provision_scan_failed">Suche nach WLAN Netzwerken fehlgeschlagen: %1$s</string>

2
core/resources/src/commonMain/composeResources/values-el/strings.xml generated
View File

@@ -81,6 +81,8 @@
<string name="display">Οθόνη</string>
<!-- DISTANCE -->
<string name="distance">Απόσταση</string>
<!-- DOC -->
<string name="doc_title_mqtt">MQTT</string>
<string name="edit">Επεξεργασία</string>
<string name="eight_hours">8 Ώρες</string>
<!-- ENCRYPTION -->

6
core/resources/src/commonMain/composeResources/values-es/strings.xml generated
View File

@@ -250,6 +250,12 @@
<string name="distance_measurements">Mediciones de Distancia</string>
<string name="distance_measurements_description">Muestra la distancia entre tu teléfono y otros nodos Meshtastic posicionados.</string>
<string name="dns">DNS</string>
<!-- DOC -->
<string name="doc_clear_search">Borrar búsqueda</string>
<string name="doc_title_connections">Conexiones</string>
<string name="doc_title_mqtt">MQTT</string>
<string name="doc_title_nodes">Nodos</string>
<string name="doc_title_onboarding">Primeros Pasos</string>
<string name="done">Hecho</string>
<string name="double_tap_as_button_press">Doble pulsación como botón</string>
<string name="downlink_enabled">Baja de Paquetes Permitida</string>

21
core/resources/src/commonMain/composeResources/values-et/strings.xml generated
View File

@@ -324,6 +324,12 @@
<string name="distance_measurements">Kauguse mõõtmised</string>
<string name="distance_measurements_description">Kuva telefoni ja teiste Meshtastic sõlmede asukoha vaheline kaugus.</string>
<string name="dns">DNS</string>
<!-- DOC -->
<string name="doc_clear_search">Puhasta otsing</string>
<string name="doc_title_connections">Ühendus</string>
<string name="doc_title_discovery">Avastamine</string>
<string name="doc_title_mqtt">MQTT</string>
<string name="doc_title_nodes">Sõlmed</string>
<string name="done">Valmis</string>
<string name="dont_show_again_for_device">Ära selle seadme puhul enam kuva</string>
<string name="double_tap_as_button_press">Topeltpuudutus nupuna</string>
@@ -731,6 +737,7 @@
<string name="mute_always">Alati</string>
<string name="mute_notifications">Vaigista teatised</string>
<string name="mute_remove">Tühistada '%1$s' teadete vaigistus?</string>
<string name="mute_selected">Vaigista valitud</string>
<string name="mute_status_always">Alati vaigistatud</string>
<string name="mute_status_muted_for_days">Vaigistatud %1$d päeva, %2$s tundi</string>
<string name="mute_status_muted_for_hours">Vaigistatud %1$s tundi</string>
@@ -1135,6 +1142,7 @@
<string name="store_forward_config">Salvesta &amp; edasta sätted</string>
<string name="store_forward_enabled">Salvesta &amp; edastamine lubatud</string>
<string name="subnet">Alamvõrk</string>
<string name="success">Edukas</string>
<string name="super_deep_sleep_duration_seconds">Super sügava une kestus</string>
<string name="supported">Toetatud</string>
<string name="supported_by_community">Toetatud Meshtastic kommuuni poolt</string>
@@ -1153,8 +1161,19 @@
<string name="tak_role_teamlead">Meeskonna ülem</string>
<string name="tak_role_teammember">Meeskonnaliige</string>
<string name="tak_role_unspecified">Määramata</string>
<string name="tak_server">TAK server</string>
<string name="tak_server_enabled">Kohaliku TAK-serveri lubamine</string>
<string name="tak_server_enabled_desc">Käivitab ATAK/iTAK-ühenduste jaoks kohaliku TLS serveri, pordil 8089</string>
<string name="tak_server_export_data_package_desc">Genereeri selle serveriga ühendumiseks ATAK/iTAK-il .zip fail</string>
<string name="tak_server_loading">…</string>
<string name="tak_server_section">Server</string>
<string name="tak_server_test_card_title">TAK kärgvõrgu test (silu)</string>
<string name="tak_server_test_idle">Saada kõik %1$d testkinnitust kärgvõrku</string>
<string name="tak_server_test_result_bytes">%1$dB ✓</string>
<string name="tak_server_test_result_unknown_error">✗</string>
<string name="tak_server_test_results">%1$d läbitud, %2$d ebaõnnestunud %3$d/%4$d</string>
<string name="tak_server_test_run">Käivita</string>
<string name="tak_server_test_running">Töötav: %1$s</string>
<string name="tak_team">Meeskonna värv</string>
<string name="tak_team_blue">Sinine</string>
<string name="tak_team_brown">Pruun</string>
@@ -1247,6 +1266,7 @@
<string name="unmessageable">Ei võta sõnumeid vastu</string>
<string name="unmonitored_or_infrastructure">Jälgimata või infrastruktuuripõhine</string>
<string name="unmute">Eemalda vaigistus</string>
<string name="unmute_selected">Lõpeta valitud vaigistus</string>
<string name="unrecognized">Tundmatu</string>
<string name="unset">Tühistatud - 0</string>
<string name="up_down_select_input_enabled">Üles/Alla/Vali sisend lubatud</string>
@@ -1302,6 +1322,7 @@
<string name="wifi_provision_description">Anna mPWRD-OS-seadmele Sinihamba kaudu WiFi mandaadid.</string>
<string name="wifi_provision_device_found">Seade leitud</string>
<string name="wifi_provision_device_found_detail">Valmis WiFi võrkude otsimiseks.</string>
<string name="wifi_provision_hidden_network">Peidetud võrk</string>
<string name="wifi_provision_mpwrd_disclaimer">Lisateavet mPWRD-OS projekti kohta leiate aadressilt\nhttps://github.com/mPWRD-OS</string>
<string name="wifi_provision_no_networks">Võrke ei leitud</string>
<string name="wifi_provision_scan_failed">WiFi võrkude leidmine ebaõnnestus %1$s</string>

6
core/resources/src/commonMain/composeResources/values-fi/strings.xml generated
View File

@@ -324,6 +324,12 @@
<string name="distance_measurements">Etäisyyden mittaukset</string>
<string name="distance_measurements_description">Näytä etäisyys puhelimen ja muiden sijainnin jakavien Meshtastic laitteiden välillä.</string>
<string name="dns">DNS</string>
<!-- DOC -->
<string name="doc_clear_search">Tyhjennä haku</string>
<string name="doc_title_connections">Yhteydet</string>
<string name="doc_title_discovery">Haku</string>
<string name="doc_title_mqtt">MQTT</string>
<string name="doc_title_nodes">Laitteet</string>
<string name="done">Valmis</string>
<string name="dont_show_again_for_device">Älä näytä enää tälle laitteelle</string>
<string name="double_tap_as_button_press">Kaksoisnapautus painikkeena</string>

6
core/resources/src/commonMain/composeResources/values-fr/strings.xml generated
View File

@@ -321,6 +321,12 @@
<string name="distance_measurements">Mesures de distance</string>
<string name="distance_measurements_description">Afficher la distance entre votre téléphone et les autres nœuds Meshtastic avec des positions.</string>
<string name="dns">DNS</string>
<!-- DOC -->
<string name="doc_clear_search">Effacer la recherche</string>
<string name="doc_title_connections">Connexions</string>
<string name="doc_title_discovery">Découverte</string>
<string name="doc_title_mqtt">MQTT</string>
<string name="doc_title_nodes">Nœuds</string>
<string name="done">Terminé</string>
<string name="dont_show_again_for_device">Ne plus afficher pour cet appareil</string>
<string name="double_tap_as_button_press">Double clic comme appui sur le bouton</string>

1
core/resources/src/commonMain/composeResources/values-ga/strings.xml generated
View File

@@ -71,6 +71,7 @@
<!-- DISPLAY -->
<!-- DISTANCE -->
<string name="distance">Sáth</string>
<!-- DOC -->
<string name="edit">Cuir in eagar</string>
<string name="eight_hours">8 Uair an chloig</string>
<!-- ENCRYPTION -->

1
core/resources/src/commonMain/composeResources/values-gl/strings.xml generated
View File

@@ -65,6 +65,7 @@
<!-- DISPLAY -->
<!-- DISTANCE -->
<string name="distance">Distancia</string>
<!-- DOC -->
<string name="edit">Editar</string>
<string name="eight_hours">8 Horas</string>
<!-- ENCRYPTION -->

1
core/resources/src/commonMain/composeResources/values-he/strings.xml generated
View File

@@ -64,6 +64,7 @@
<!-- DISPLAY -->
<!-- DISTANCE -->
<string name="distance">מרחק</string>
<!-- DOC -->
<!-- ENCRYPTION -->
<!-- ENVIRONMENT -->
<string name="error">שגיאה</string>

1
core/resources/src/commonMain/composeResources/values-hr/strings.xml generated
View File

@@ -69,6 +69,7 @@
<!-- DISPLAY -->
<!-- DISTANCE -->
<string name="distance">Udaljenost</string>
<!-- DOC -->
<string name="edit">Uredi</string>
<string name="eight_hours">8 Sati</string>
<!-- ENCRYPTION -->

1
core/resources/src/commonMain/composeResources/values-ht/strings.xml generated
View File

@@ -68,6 +68,7 @@
<!-- DISPLAY -->
<!-- DISTANCE -->
<string name="distance">Distans</string>
<!-- DOC -->
<string name="edit">Modifye</string>
<string name="eight_hours">8 Èdtan</string>
<!-- ENCRYPTION -->

4
core/resources/src/commonMain/composeResources/values-hu/strings.xml generated
View File

@@ -254,6 +254,10 @@
<string name="distance_filters_description">Szűrd a csomópont-listát és a mesh térképet a telefon közelsége alapján.</string>
<string name="distance_measurements">Távolságmérés</string>
<string name="distance_measurements_description">Megjeleníti a távolságot a telefonod és más, pozícióval rendelkező Meshtastic csomópontok között.</string>
<!-- DOC -->
<string name="doc_clear_search">Keresés törlése</string>
<string name="doc_title_mqtt">MQTT</string>
<string name="doc_title_nodes">Csomópontok</string>
<string name="double_tap_as_button_press">Dupla koppintás mint gomb</string>
<string name="downlink_enabled">Letöltés engedélyezve</string>
<string name="downlink_feature_description">A nyilvános internetes átjáróból érkező üzenetek továbbításra kerülnek a helyi mesh hálózatra. A zéró-ugrási szabály miatt az alapértelmezett MQTT szerver forgalma nem terjed tovább ennél az eszköznél.</string>

1
core/resources/src/commonMain/composeResources/values-is/strings.xml generated
View File

@@ -58,6 +58,7 @@
<string name="disconnected">Aftengd</string>
<!-- DISPLAY -->
<!-- DISTANCE -->
<!-- DOC -->
<!-- ENCRYPTION -->
<!-- ENVIRONMENT -->
<string name="error_duty_cycle">Hámarsksendingartíma náð. Ekki hægt að senda skilaboð, vinsamlegast reynið aftur síðar.</string>

6
core/resources/src/commonMain/composeResources/values-it/strings.xml generated
View File

@@ -276,6 +276,12 @@
<string name="distance_measurements">Misure di distanza</string>
<string name="distance_measurements_description">Visualizza la distanza tra il telefono e gli altri nodi Meshtastic con posizione attiva.</string>
<string name="dns">DNS</string>
<!-- DOC -->
<string name="doc_clear_search">Azzera ricerca</string>
<string name="doc_title_connections">Connessioni</string>
<string name="doc_title_mqtt">MQTT</string>
<string name="doc_title_nodes">Nodi</string>
<string name="doc_title_onboarding">Come iniziare</string>
<string name="done">Fatto</string>
<string name="double_tap_as_button_press">Doppio tocco come pressione pulsante</string>
<string name="downlink_enabled">Downlink attivato</string>

6
core/resources/src/commonMain/composeResources/values-ja/strings.xml generated
View File

@@ -192,6 +192,12 @@
<string name="display_units">表示単位</string>
<!-- DISTANCE -->
<string name="distance">距離</string>
<!-- DOC -->
<string name="doc_clear_search">検索をクリア</string>
<string name="doc_title_connections">コネクション</string>
<string name="doc_title_discovery">ディスカバリー</string>
<string name="doc_title_mqtt">MQTT</string>
<string name="doc_title_nodes">ノード</string>
<string name="downlink_enabled">ダウンリンクの有効化</string>
<string name="dynamic">動的</string>
<string name="echo_enabled">Echoを有効化</string>

3
core/resources/src/commonMain/composeResources/values-ko/strings.xml generated
View File

@@ -148,6 +148,9 @@
<!-- DISTANCE -->
<string name="distance">거리</string>
<string name="dns">DNS</string>
<!-- DOC -->
<string name="doc_title_mqtt">MQTT</string>
<string name="doc_title_nodes">노드</string>
<string name="downlink_enabled">다운링크 활성화</string>
<string name="download">다운로드</string>
<string name="echo_enabled">에코 활성화</string>

1
core/resources/src/commonMain/composeResources/values-lt/strings.xml generated
View File

@@ -72,6 +72,7 @@
<!-- DISPLAY -->
<!-- DISTANCE -->
<string name="distance">Atstumas</string>
<!-- DOC -->
<string name="edit">Redaguoti</string>
<string name="eight_hours">8 Valandos</string>
<!-- ENCRYPTION -->

2
core/resources/src/commonMain/composeResources/values-nl/strings.xml generated
View File

@@ -120,6 +120,8 @@
<string name="display_units">Geef eenheden weer</string>
<!-- DISTANCE -->
<string name="distance">Afstand</string>
<!-- DOC -->
<string name="doc_title_mqtt">MQTT</string>
<string name="downlink_enabled">Downlink ingeschakeld</string>
<string name="dynamic">Dynamisch</string>
<string name="echo_enabled">Echo ingeschakeld</string>

1
core/resources/src/commonMain/composeResources/values-no/strings.xml generated
View File

@@ -73,6 +73,7 @@
<!-- DISPLAY -->
<!-- DISTANCE -->
<string name="distance">Distanse</string>
<!-- DOC -->
<string name="edit">Rediger</string>
<string name="eight_hours">8 Timer</string>
<!-- ENCRYPTION -->

4
core/resources/src/commonMain/composeResources/values-pl/strings.xml generated
View File

@@ -226,6 +226,10 @@
<!-- DISTANCE -->
<string name="distance">Odległość</string>
<string name="dns">DNS</string>
<!-- DOC -->
<string name="doc_clear_search">Wyczyść wyszukiwanie</string>
<string name="doc_title_mqtt">MQTT</string>
<string name="doc_title_nodes">Węzły</string>
<string name="done">Wykonano</string>
<string name="double_tap_as_button_press">Podwójne dotknięcie jako naciśnięcie przycisku</string>
<string name="downlink_enabled">Odbiór włączony</string>

5
core/resources/src/commonMain/composeResources/values-pt-rBR/strings.xml generated
View File

@@ -186,6 +186,11 @@
<string name="distance_filters_description">Filtre a lista de nós e o mapa da malha baseado na proximidade do seu telefone.</string>
<string name="distance_measurements">Medição de Distâncias</string>
<string name="distance_measurements_description">Exiba a distância entre o telefone e outros nós do Meshtastic com posições.</string>
<!-- DOC -->
<string name="doc_clear_search">Limpar busca</string>
<string name="doc_title_connections">Conexões</string>
<string name="doc_title_mqtt">MQTT</string>
<string name="doc_title_nodes">Nós</string>
<string name="done">Concluído</string>
<string name="downlink_enabled">Downlink ativado</string>
<string name="download">Baixar</string>

4
core/resources/src/commonMain/composeResources/values-pt/strings.xml generated
View File

@@ -150,6 +150,10 @@
<string name="display_units">Unidade de visualização</string>
<!-- DISTANCE -->
<string name="distance">Distância</string>
<!-- DOC -->
<string name="doc_title_connections">Ligações</string>
<string name="doc_title_mqtt">MQTT</string>
<string name="doc_title_nodes">Nodes</string>
<string name="downlink_enabled">Downlink ativado</string>
<string name="dynamic">Dinâmico</string>
<string name="echo_enabled">Eco ativado</string>

5
core/resources/src/commonMain/composeResources/values-ro/strings.xml generated
View File

@@ -300,6 +300,11 @@
<string name="distance_measurements">Măsurătorile distanței</string>
<string name="distance_measurements_description">Afișează distanța dintre telefonul dvs. și alte noduri Meshtastice cu poziții.</string>
<string name="dns">DNS</string>
<!-- DOC -->
<string name="doc_clear_search">Ștergeți căutarea</string>
<string name="doc_title_discovery">Descoperiți</string>
<string name="doc_title_mqtt">MQTT</string>
<string name="doc_title_nodes">Noduri</string>
<string name="done">Gata</string>
<string name="double_tap_as_button_press">Apăsare dublă ca buton</string>
<string name="downlink_enabled">Downlink activat</string>

55
core/resources/src/commonMain/composeResources/values-ru/strings.xml generated
View File

@@ -326,6 +326,47 @@
<string name="distance_measurements">Измерения расстояния</string>
<string name="distance_measurements_description">Показать расстояния между вашим телефоном и другими нодами Meshstatic с позициями.</string>
<string name="dns">Служба доменных имен (DNS)</string>
<!-- DOC -->
<string name="doc_clear_search">Очистить условия поиска</string>
<string name="doc_keywords_connections">bluetooth,usb,tcp,pairing,serial,wifi</string>
<string name="doc_keywords_desktop">desktop,linux,macos,windows,serial</string>
<string name="doc_keywords_discovery">discovery,topology,network,scan,neighbor</string>
<string name="doc_keywords_firmware">firmware,update,ota,flash,version,recovery</string>
<string name="doc_keywords_map">map,waypoint,gps,position,location,marker</string>
<string name="doc_keywords_measurement">formatter,metric,number,locale,temperature,conversion,api</string>
<string name="doc_keywords_messages">message,channel,encryption,direct,broadcast,quick-chat</string>
<string name="doc_keywords_mqtt">mqtt,broker,internet,bridge,uplink,downlink</string>
<string name="doc_keywords_node_metrics">metrics,telemetry,signal,snr,rssi,battery,traceroute</string>
<string name="doc_keywords_nodes">node,mesh,list,role,status,favorite,filter</string>
<string name="doc_keywords_onboarding">setup,welcome,permissions,first-launch</string>
<string name="doc_keywords_settings_module">module,serial,telemetry,canned,store-forward,administration</string>
<string name="doc_keywords_settings_radio">settings,radio,lora,region,modem,device,power,security</string>
<string name="doc_keywords_signal_meter">signal,rssi,snr,bars,quality,lora,noise,meter</string>
<string name="doc_keywords_tak">tak,atak,cursor-on-target,team-awareness</string>
<string name="doc_keywords_telemetry">telemetry,sensor,temperature,humidity,pressure,power</string>
<string name="doc_keywords_translate">translate,crowdin,localization,language,i18n,contribute</string>
<string name="doc_keywords_units">units,locale,metric,imperial,temperature,distance</string>
<string name="doc_search_placeholder">Поиск по документации…</string>
<string name="doc_section_developer">Руководство разработчика</string>
<string name="doc_section_user">Руководство пользователя</string>
<string name="doc_title_connections">Соединения</string>
<string name="doc_title_desktop">Десктопное приложение</string>
<string name="doc_title_discovery">Обнаружение</string>
<string name="doc_title_firmware">Обновления прошивки</string>
<string name="doc_title_map">Карта и путевые точки</string>
<string name="doc_title_measurement">Измерение и форматирование</string>
<string name="doc_title_messages">Сообщения и каналы</string>
<string name="doc_title_mqtt">MQTT</string>
<string name="doc_title_node_metrics">Метрики ноды</string>
<string name="doc_title_nodes">Ноды</string>
<string name="doc_title_onboarding">Начало работы</string>
<string name="doc_title_settings_module">Настройки - Модули и администрирование</string>
<string name="doc_title_settings_radio">Настройки - Радио и пользователь</string>
<string name="doc_title_signal_meter">Измеритель сигнала</string>
<string name="doc_title_tak">Интеграция TAK</string>
<string name="doc_title_telemetry">Телеметрия и датчики</string>
<string name="doc_title_translate">Перевести приложение</string>
<string name="doc_title_units">Ед.изм. и локализация</string>
<string name="done">Готово</string>
<string name="dont_show_again_for_device">Больше не показывать для этого устройства</string>
<string name="double_tap_as_button_press">Двойное нажатие как кнопка</string>
@@ -503,6 +544,7 @@
<string name="hardware_model">Модель оборудования</string>
<string name="heading">Курс</string>
<string name="heartbeat">Heartbeat</string>
<string name="help_and_documentation">Справка и документация</string>
<string name="hide_layer">Скрыть слой</string>
<string name="hide_password">Скрыть пароль</string>
<string name="history_return_max">Макс возврат истории</string>
@@ -1168,8 +1210,19 @@
<string name="tak_role_teamlead">Руководитель команды</string>
<string name="tak_role_teammember">Участник команды</string>
<string name="tak_role_unspecified">Не определена</string>
<string name="tak_server">Сервер TAK</string>
<string name="tak_server_enabled">Включить локальный сервер TAK</string>
<string name="tak_server_enabled_desc">Запускает локальный TLS-сервер на порту 8089 для подключений ATAK/iTAK</string>
<string name="tak_server_export_data_package_desc">Создайте .zip для ATAK/iTAK, чтобы подключиться к этому серверу</string>
<string name="tak_server_loading">...</string>
<string name="tak_server_section">Сервер</string>
<string name="tak_server_test_card_title">Сетевой тест TAK (Отладка)</string>
<string name="tak_server_test_idle">Отправить все %1$d тестовых приспособлений в сеть</string>
<string name="tak_server_test_result_bytes">%1$dБ ✓</string>
<string name="tak_server_test_result_unknown_error">✗</string>
<string name="tak_server_test_results">%1$d пройдено, %2$d неудачно из %3$d/%4$d</string>
<string name="tak_server_test_run">Запустить</string>
<string name="tak_server_test_running">Запущено: %1$s</string>
<string name="tak_team">Цвет команды</string>
<string name="tak_team_blue">Синий</string>
<string name="tak_team_brown">Коричневый</string>
@@ -1239,7 +1292,7 @@
<string name="traffic_management_rate_limit_enabled">Ограничение скорости</string>
<string name="traffic_management_rate_limit_max_packets">Макс пакетов в окне</string>
<string name="traffic_management_rate_limit_window">Окно ограничения скорости (сек.)</string>
<string name="traffic_management_router_preserve_hops">Сохраняить хопы маршрутизатора</string>
<string name="traffic_management_router_preserve_hops">Сохранять хопы маршрутизатора</string>
<string name="traffic_management_unknown_packet_threshold">Порог передач неизвестных пакетов</string>
<string name="transmit_over_lora">Передать через LoRa</string>
<string name="transport_ble">BLE</string>

3
core/resources/src/commonMain/composeResources/values-sk/strings.xml generated
View File

@@ -130,6 +130,9 @@
<string name="display">Obrazovka</string>
<!-- DISTANCE -->
<string name="distance">Vzdialenosť</string>
<!-- DOC -->
<string name="doc_clear_search">Vymazať vyhľadávanie</string>
<string name="doc_title_mqtt">MQTT</string>
<string name="edit">Upraviť</string>
<string name="eight_hours">8 Hodín</string>
<!-- ENCRYPTION -->

1
core/resources/src/commonMain/composeResources/values-sl/strings.xml generated
View File

@@ -75,6 +75,7 @@
<!-- DISPLAY -->
<!-- DISTANCE -->
<string name="distance">Razdalja</string>
<!-- DOC -->
<string name="edit">Uredi</string>
<string name="eight_hours">8 Ur</string>
<!-- ENCRYPTION -->

1
core/resources/src/commonMain/composeResources/values-sq/strings.xml generated
View File

@@ -68,6 +68,7 @@
<!-- DISPLAY -->
<!-- DISTANCE -->
<string name="distance">Distanca</string>
<!-- DOC -->
<string name="edit">Redakto</string>
<string name="eight_hours">8 Orë</string>
<!-- ENCRYPTION -->

3
core/resources/src/commonMain/composeResources/values-sr/strings.xml generated
View File

@@ -142,6 +142,9 @@
<string name="display">Приказ</string>
<!-- DISTANCE -->
<string name="distance">Udaljenost</string>
<!-- DOC -->
<string name="doc_title_firmware">Ажурирања фирмвера</string>
<string name="doc_title_nodes">Чворови</string>
<string name="double_tap_as_button_press">Двоструки додир као дугме</string>
<string name="edit">Измени</string>
<string name="eight_hours">8 Сати</string>

3
core/resources/src/commonMain/composeResources/values-srp/strings.xml generated
View File

@@ -142,6 +142,9 @@
<string name="display">Приказ</string>
<!-- DISTANCE -->
<string name="distance">Раздаљина</string>
<!-- DOC -->
<string name="doc_title_firmware">Ажурирања фирмвера</string>
<string name="doc_title_nodes">Чворови</string>
<string name="double_tap_as_button_press">Двоструки додир као дугме</string>
<string name="edit">Измени</string>
<string name="eight_hours">8 Сати</string>

6
core/resources/src/commonMain/composeResources/values-sv/strings.xml generated
View File

@@ -303,6 +303,12 @@
<string name="distance_measurements">Avståndsmätning</string>
<string name="distance_measurements_description">Visa avståndet mellan din telefon och andra Meshtastic noder med kända positioner.</string>
<string name="dns">DNS</string>
<!-- DOC -->
<string name="doc_clear_search">Rensa sökning</string>
<string name="doc_title_discovery">Upptäckt</string>
<string name="doc_title_mqtt">MQTT</string>
<string name="doc_title_nodes">Noder</string>
<string name="doc_title_onboarding">Kom igång</string>
<string name="done">Klart</string>
<string name="dont_show_again_for_device">Visa inte igen för denna enhet</string>
<string name="double_tap_as_button_press">Dubbeltryck som knapptryck</string>

5
core/resources/src/commonMain/composeResources/values-tr/strings.xml generated
View File

@@ -159,6 +159,11 @@
<string name="distance_filters">Mesafe Filtresi</string>
<string name="distance_measurements">Uzaklık Ölçüsü</string>
<string name="dns">DNS</string>
<!-- DOC -->
<string name="doc_clear_search">Aramayı sil</string>
<string name="doc_title_connections">Bağlantılar</string>
<string name="doc_title_mqtt">MQTT</string>
<string name="doc_title_nodes">Nodelar</string>
<string name="downlink_enabled">Aşağı bağlantı etkinleştirildi</string>
<string name="download">İndir</string>
<string name="dynamic">Dinamik</string>

4
core/resources/src/commonMain/composeResources/values-uk/strings.xml generated
View File

@@ -287,6 +287,10 @@
<string name="distance_filters">Фільтри відстані</string>
<string name="distance_measurements">Вимірювання відстані</string>
<string name="dns">DNS</string>
<!-- DOC -->
<string name="doc_clear_search">Очистити пошук</string>
<string name="doc_title_mqtt">MQTT</string>
<string name="doc_title_nodes">Вузли</string>
<string name="done">Готово</string>
<string name="double_tap_as_button_press">Подвійний дотик як натискання кнопки</string>
<string name="downlink_enabled">Прийом увімкнений</string>

7
core/resources/src/commonMain/composeResources/values-zh-rCN/strings.xml generated
View File

@@ -302,6 +302,13 @@
<string name="distance_measurements">距离测量</string>
<string name="distance_measurements_description">显示您的手机和其他带有位置的 Meshtastic 节点之间的距离。</string>
<string name="dns">DNS</string>
<!-- DOC -->
<string name="doc_clear_search">清除搜索</string>
<string name="doc_title_connections">连接数</string>
<string name="doc_title_discovery">发现</string>
<string name="doc_title_firmware">固件升级</string>
<string name="doc_title_mqtt">MQTT</string>
<string name="doc_title_nodes">节点</string>
<string name="done">完成</string>
<string name="double_tap_as_button_press">双击作为按钮</string>
<string name="downlink_enabled">启用下行</string>

7
core/resources/src/commonMain/composeResources/values-zh-rTW/strings.xml generated
View File

@@ -319,6 +319,13 @@
<string name="distance_measurements">距離量測</string>
<string name="distance_measurements_description">顯示您手機與其他有定位資訊的 Meshtastic 節點之間的距離。</string>
<string name="dns">DNS</string>
<!-- DOC -->
<string name="doc_clear_search">清除搜尋結果</string>
<string name="doc_title_connections">連線</string>
<string name="doc_title_discovery">尋找</string>
<string name="doc_title_mqtt">MQTT</string>
<string name="doc_title_nodes">節點</string>
<string name="doc_title_onboarding"># 入門指南</string>
<string name="done">完成</string>
<string name="double_tap_as_button_press">雙擊觸發按鈕功能</string>
<string name="downlink_enabled">已啓用下行</string>

30
docs/ar-rSA/index.md Normal file
View File

@@ -0,0 +1,30 @@
---
title: Home
layout: default
nav_order: 0
---
# Meshtastic Android App Documentation
User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform).
Use the sidebar navigation to browse the **User Guide** for app features and the **Developer Guide** for contributing to the project.
---
## Quick Links
| Guide | الوصف |
| --------------------------------------------------------------------- | -------------------------------------------------------------- |
| [Getting Started](user/onboarding) | Connect your first radio and send a message |
| [Messages & Channels](user/messages-and-channels) | Channel broadcasts, direct messages, reactions, and encryption |
| [Nodes](user/nodes) | Understanding the mesh network node list |
| [Signal Meter](user/signal-meter) | How the LoRa signal quality meter works |
| [Units & Locale](user/units-and-locale) | How temperatures, distances, and times adapt to your region |
| [Desktop App](user/desktop) | Linux, macOS, and Windows desktop usage |
| [Architecture](developer/architecture) | App architecture overview for contributors |
| [Contributing](developer/contributing) | Branch naming, PR workflow, and verification commands |
---
> This documentation is served from the same markdown source that powers the in-app **Help & Documentation** browser.

125
docs/ar-rSA/user/connections.md Normal file
View File

@@ -0,0 +1,125 @@
---
title: Connections
nav_order: 2
last_updated: 2026-05-13
description: Connect your phone or desktop to a Meshtastic radio via Bluetooth, USB, or TCP/IP.
aliases:
- bluetooth
- usb
- tcp
- pairing
---
# Connections
Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node.
## Bluetooth (BLE)
Bluetooth Low Energy is the default and most common connection method on Android.
### Pairing a Device
1. Ensure your Meshtastic radio is powered on and in pairing mode.
2. Open the app and navigate to **Connections**.
3. Tap **Scan for Devices** — nearby Meshtastic radios will appear.
4. Select your device from the list.
5. Accept the Bluetooth pairing prompt if shown.
![Device list item](/assets/screenshots/connections_bluetooth_scan.png)
You can filter devices by transport type using the filter chips at the top:
![Transport filter chips](/assets/screenshots/connections_transport_filters.png)
> 💡 **Tip:** If your device doesn't appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device.
### Connection Status
| Icon | State | الوصف |
| ---- | -------------- | ----------------------------- |
| 🟢 | Connected | Active radio link established |
| 🟡 | Connecting | Handshake in progress |
| 🔴 | انقطع الاتصال | No active connection |
| ⚪ | Not configured | No device selected |
When connecting, a status indicator shows the current connection state:
![Connecting status](/assets/screenshots/connections_connecting.png)
If no devices are found, the app shows an empty state with instructions:
![No devices found](/assets/screenshots/connections_empty_state.png)
### Troubleshooting Bluetooth
- **Device not found:** Toggle Bluetooth off/on, ensure location is enabled.
- **Connection drops:** Move closer to the radio; check for interference.
- **Pairing rejected:** Forget the device in Android Bluetooth settings and retry.
## USB Serial
USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable.
### Setup
1. Connect your radio via USB cable to your device.
2. The app will prompt for USB permission — tap **Allow**.
3. The connection is established automatically.
> ⚠️ **Note:** USB connections require OTG support on Android devices.
## TCP/IP (WiFi)
Some Meshtastic radios support WiFi connectivity, allowing TCP-based connections.
### Configuration
1. Connect your radio to a WiFi network via the radio's web interface or settings.
2. In the app, go to **Connections → TCP**.
3. Enter the radio's IP address and port (default: 4403).
4. Tap **Connect**.
![WiFi scanning for devices](/assets/screenshots/connections_wifi_scanning.png)
When a device is found, it appears in the connection list:
![WiFi device found](/assets/screenshots/connections_wifi_device_found.png)
A successful connection is confirmed with a status indicator:
![WiFi connection success](/assets/screenshots/connections_wifi_success.png)
### When to Use TCP
- Radio is on the same local network
- Testing with a simulated radio
- Environments where Bluetooth has interference issues
## Reconnection Behavior
The app reconnects to the **last selected device** on startup. You can manually switch transports from the connections screen at any time.
To disconnect from a radio, use the disconnect button on the connections screen:
![Disconnect from radio](/assets/screenshots/connections_disconnect.png)
## Desktop Connections
On Desktop (Linux/macOS/Windows), the app supports:
- **Bluetooth (BLE)** — via the Kable library; works on macOS, Linux, and Windows
- **USB Serial** — primary wired connection method
- **TCP/IP** — for network-connected radios
See [Desktop App](desktop) for platform-specific details and keyboard shortcuts.
## Related Topics
- [Getting Started](onboarding) — first-launch setup and permissions
- [Settings — Radio & User](settings-radio-user) — Bluetooth and network configuration
- [Desktop App](desktop) — desktop-specific connection details
- [Supported devices](https://meshtastic.org/docs/hardware/devices) — full list of compatible radios on meshtastic.org
---

147
docs/ar-rSA/user/desktop.md Normal file
View File

@@ -0,0 +1,147 @@
---
title: Desktop App
nav_order: 14
last_updated: 2026-05-13
description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts.
aliases:
- desktop
- linux
- macos
- windows
- jvm
---
# Desktop App
The Meshtastic Desktop application provides the same mesh communication features on Linux, macOS, and Windows.
## Overview
The Desktop app shares its core codebase with the Android app through Kotlin Multiplatform (KMP). Most features work identically across platforms.
## Installation
### Linux
- Download the `.deb` or `.AppImage` package from the releases page
- Or build from source using `./gradlew :desktopApp:run`
### macOS
- Download the `.dmg` package from releases
- Or build from source
### Windows
- Download the `.msi` installer from releases
- Or build from source
## Connecting Your Radio
### USB Serial (Primary)
The most reliable connection method on Desktop:
1. Connect your Meshtastic radio via USB cable.
2. The app should detect the serial port automatically.
3. If not detected, select the correct serial port from the connections menu.
### TCP/IP
For network-connected radios:
1. Enter the radio's IP address and port (default: 4403).
2. Click **Connect**.
### Bluetooth (BLE)
Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/JuulLabs/kable) library:
1. Ensure your system has a Bluetooth adapter.
2. The app scans for nearby Meshtastic radios automatically.
3. Select your device from the connections screen.
## Feature Parity
| Feature | Android | Desktop | Notes |
| ---------------------------------------- | ------- | ------- | -------------------------- |
| Messaging | ✓ | ✓ | Full parity |
| Node List | ✓ | ✓ | Full parity |
| الخريطة | ✓ | ✓ | Full parity |
| الإعدادات | ✓ | ✓ | Full parity |
| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop |
| Firmware Update OTA | ✓ | ✗ | Use web flasher |
| Notifications | ✓ | ✓ | Native OS notifications |
| Widgets | ✓ | ✗ | Android-only |
| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only |
\*Chirpy AI requires Android 14+ on Google flavor builds with supported hardware.
## UI Differences
The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction.
### Keyboard Shortcuts
| Shortcut | Action |
| ------------------- | --------------------------- |
| **⌘Q** / **Ctrl+Q** | Quit the application |
| **⌘,** / **Ctrl+,** | Open Settings |
| **⌘1** / **Ctrl+1** | Switch to Conversations tab |
| **⌘2** / **Ctrl+2** | Switch to Nodes tab |
| **⌘3** / **Ctrl+3** | Switch to Map tab |
| **⌘4** / **Ctrl+4** | Switch to Connections tab |
### Window & System Tray
- **Window resizing** — responsive layout adapts to window dimensions
- **System tray** — minimize to system tray for background mesh operation
- **Tray menu** — right-click the tray icon to show window or quit
- **Mouse interaction** — hover states and standard desktop navigation
### Notification Preferences
The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from **Settings → Notifications** within the app.
## Built-in Documentation Browser
The Desktop app includes a built-in documentation browser for quick access to help content without leaving the application.
![Docs browser with table of contents](/assets/screenshots/docs-browser_toc.png)
The browser supports full-text search across all documentation:
![Searching the docs browser](/assets/screenshots/docs-browser_search.png)
Individual doc pages render with full formatting:
![A documentation page](/assets/screenshots/docs-browser_page.png)
## Building from Source
```bash
git clone https://github.com/meshtastic/Meshtastic-Android.git
cd Meshtastic-Android
git submodule update --init
./gradlew :desktopApp:run
```
Requirements:
- JDK 21
- No Android SDK required for desktop-only builds
## Known Limitations
- No OTA firmware updates (use web flasher)
- Some Android-specific features (widgets, specific notification channels) are unavailable
- Performance may vary on low-spec hardware running Compose Desktop
- BLE bonding is not yet supported on desktop (pairing works without bonding)
## Related Topics
- [Connections](connections) — connection methods overview
- [Firmware Updates](firmware) — use the [Web Flasher](https://flasher.meshtastic.org) for desktop firmware updates
---

114
docs/ar-rSA/user/discovery.md Normal file
View File

@@ -0,0 +1,114 @@
---
title: Discovery
nav_order: 12
last_updated: 2026-05-13
description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools.
aliases:
- mesh-discovery
- local-discovery
- network-scan
- traceroute
- neighbor-info
---
# Discovery
Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist.
> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens.
---
## Traceroute
Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It's the single most useful tool for debugging connectivity problems.
### Running a Traceroute
1. Navigate to **Nodes** and tap the node you want to trace.
2. On the node detail screen, tap **Traceroute**.
3. The app sends a traceroute request and waits for the response.
4. Results display each hop in order, with signal quality at every step.
### Reading the Results
A traceroute result looks like this:
```
You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target
```
Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment.
| What to look for | What it means |
| -------------------------------------------------------------------------- | --------------------------------------------------------------------------- |
| All hops show Good SNR (> 5 dB) | Healthy path — messages flow reliably |
| One hop shows Bad SNR (< 0 dB) | Weak link — this relay segment is fragile |
| Many hops (4+) | Long path — consider repositioning a node to shorten it |
| Different path on retry | Mesh is adapting — multiple routes exist (this is good!) |
> 💡 **Tip:** Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.
### Troubleshooting with Traceroute
- **"No route found"** — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
- **Traceroute times out** — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in **Settings → LoRa Config**.
- **Asymmetric paths** — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric.
---
## Neighbor Info
The Neighbor Info module lets each node broadcast a list of the nodes it can **directly hear** (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.
### Enabling Neighbor Info
1. Navigate to **Settings → Module Config → Neighbor Info**.
2. Enable the module.
3. Set the broadcast interval (default: 900 seconds / 15 minutes).
Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same.
### Viewing Neighbor Data
- Open any node's detail screen and look for the **Neighbors** section.
- Each neighbor entry shows the node that was directly heard and its signal quality.
- Combine neighbor data from multiple nodes to understand the full mesh topology.
> ⚠️ **Note:** Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion.
---
## Node List as a Discovery Tool
The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.
### Finding New Nodes
- Sort by **Last heard** to see the most recently active nodes at the top.
- Enable **Include unknown** to see nodes that have appeared on the mesh but haven't sent user info yet — these are often newly powered-on devices.
### Assessing Connectivity
- Sort by **Hops away** to see which nodes are directly reachable (0 hops) versus relayed.
- Sort by **Distance** to find nearby nodes and verify they're reachable.
- Use **Exclude MQTT** to focus on nodes reachable over radio (not via internet bridge).
### Infrastructure Audit
- Disable **Exclude infrastructure** to see Router, Repeater, Router Late, and Client Base nodes.
- Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.
See [Nodes](nodes) for full details on filtering and sorting options.
---
## Tips for Mesh Exploration
- **Start with traceroute** — it gives you immediate, actionable information about a specific path.
- **Enable Neighbor Info on key nodes** — especially routers and repeaters, to build a picture of the backbone.
- **Check the map** — node positions on the [Map](map-and-waypoints) combined with signal data help you understand why some links are strong and others are weak.
- **Compare signal over time** — use the [Signal Meter](signal-meter) guide to interpret SNR and RSSI values correctly.
---

114
docs/ar-rSA/user/firmware.md Normal file
View File

@@ -0,0 +1,114 @@
---
title: Firmware Updates
nav_order: 13
last_updated: 2026-05-13
description: Update your radio firmware over Bluetooth — OTA process, version channels, pre-flight checks, and recovery.
aliases:
- firmware
- update
- ota
- flash
---
# Firmware Updates
Keep your Meshtastic radio up to date with the latest firmware for new features, bug fixes, and security improvements.
## Checking for Updates
1. Navigate to **Settings → Firmware Update** or tap the firmware notification if shown.
2. The app checks for available firmware versions.
3. Available updates show the version number and changelog summary.
## Update Methods
### OTA (Over-The-Air) via Bluetooth
The most common update method for Android users:
1. Ensure your radio is connected via Bluetooth.
2. Navigate to the Firmware Update screen.
3. Select the desired firmware version.
4. Tap **Update** to begin the OTA process.
5. Wait for the update to complete — **do not disconnect** during the update.
![Firmware checking for updates](/assets/screenshots/firmware_checking.png)
> ⚠️ **Warning:** Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process.
![Firmware disclaimer](/assets/screenshots/firmware_disclaimer.png)
### USB Flashing
For recovery or when OTA is unavailable:
- Use the [Meshtastic Web Flasher](https://flasher.meshtastic.org)
- Or the [Meshtastic CLI tool](https://meshtastic.org/docs/getting-started/flashing-firmware) on desktop
## Version Channels
| عربي | الوصف |
| ------ | ------------------------------------------- |
| Stable | Recommended for most users; tested releases |
| Alpha | Preview releases; may contain bugs |
## Pre-Update Checklist
Before updating:
- [ ] Battery > 50%
- [ ] Stable Bluetooth connection
- [ ] Note your current settings (they may reset on major version changes)
- [ ] Check the release notes for breaking changes
## Post-Update
After a successful update:
- The radio will reboot automatically
- Bluetooth connection will re-establish
- Verify your settings are intact
- Check the firmware version in **Settings → About**
![Firmware update success](/assets/screenshots/firmware_success.png)
## Troubleshooting
### Update Stuck
If the update appears frozen:
- Wait at least 5 minutes before intervening
- If truly stuck, power-cycle the radio
- Attempt the update again
![Firmware update error](/assets/screenshots/firmware_error.png)
### Device Won't Boot After Update
If your device fails to boot:
1. Try connecting via USB to a computer
2. Use the web flasher in recovery/DFU mode
3. Flash a known-good firmware version
4. Check the Meshtastic Discord for device-specific recovery steps
### Compatibility Warnings
The app may show warnings when:
- Connected radio firmware is below minimum supported version
- Major version mismatch between app and firmware
- Deprecated features need migration
> ⚠️ **Important:** Always update the Meshtastic app before or alongside firmware updates to ensure compatibility.
## Related Topics
- [Connections](connections) — reconnecting after a firmware update
- [Flashing firmware guide](https://meshtastic.org/docs/getting-started/flashing-firmware) — full firmware flashing walkthrough on meshtastic.org
- [Supported devices](https://meshtastic.org/docs/hardware/devices) — check firmware compatibility by device
- [FAQ](https://meshtastic.org/docs/about/faq) — common questions on meshtastic.org
---

116
docs/ar-rSA/user/map-and-waypoints.md Normal file
View File

@@ -0,0 +1,116 @@
---
title: Map & Waypoints
nav_order: 6
last_updated: 2026-05-13
description: View node positions on the map, create and share waypoints, and manage position sharing and privacy.
aliases:
- map
- waypoints
- gps
- location
---
# Map & Waypoints
The Map screen shows the geographic positions of nodes on your mesh, along with shared waypoints.
## Map View
The map displays:
- **Node positions** — colored markers for each node reporting location
- **Waypoints** — shared points of interest
- **Your position** — your current GPS location
### Node Markers
Node markers on the map indicate:
| Color | Meaning |
| ------ | ---------------------------------------------- |
| Green | Online (heard recently) |
| Yellow | Away (heard within 2 hours) |
| Gray | Offline (stale position) |
| Blue | Your own node |
### Map Controls
- **Zoom** — pinch or use +/- buttons
- **Pan** — drag to explore
- **Center** — select the location button to center on your position
- **Node tap** — tap a node marker to view details
The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position.
![Map controls overlay](/assets/screenshots/map_controls_overlay.png)
## Waypoints
Waypoints are shared geographic points of interest that all mesh members can see.
### Creating a Waypoint
1. Long-press on the map at the desired location.
2. Enter a name and optional description.
3. Choose an icon/emoji for the waypoint.
4. Tap **Send** to share with the mesh.
### Waypoint Properties
| Property | الوصف |
| ---------- | ------------------------------------------------------- |
| الاسم | Short identifier (max 30 characters) |
| الوصف | Optional longer description |
| Icon | Visual marker emoji on the map |
| مقفل | If locked, only the creator can edit or delete |
| Expiration | Optional auto-remove time |
### Waypoint Expiration
Waypoints can be set to expire automatically:
- **Never** (default) — waypoint remains until manually deleted
- **Timed** — waypoint is automatically removed after the specified duration (e.g., "remove after 2 hours"). Useful for temporary markers like rally points, hazards, or meeting locations.
Expired waypoints are automatically hidden from the map so they don't clutter the display. The expiration countdown begins when the waypoint is created, not when other nodes receive it.
### Managing Waypoints
- Tap a waypoint on the map to view its details and coordinates
- Edit or delete waypoints you created
- **Locked waypoints** cannot be modified or deleted by other nodes — only the original creator can change them
- Unlocked waypoints can be edited by any mesh member
## Position Sharing
### Enabling Position Sharing
Your node shares its GPS position based on:
- **Fixed interval** — broadcast position at regular intervals
- **Smart position** — broadcast when movement exceeds a threshold
- **Manual** — only share when explicitly requested
Configure position behavior in **Settings → Position**.
### Privacy Considerations
> 🔒 **Privacy:** Position data is broadcast to all nodes on your channel. If you don't want your location shared, disable GPS position in settings or use a fixed/fake position.
## Map Sources
The app supports multiple map tile sources:
- OpenStreetMap (default)
- Satellite imagery (where available)
- Offline tiles (download map areas for offline use)
## Related Topics
- [Nodes](nodes) — view and filter your node list
- [Node Metrics](node-metrics) — signal quality and position history for individual nodes
- [Discovery](discovery) — traceroute and neighbor info for understanding mesh topology
- [Units & Locale](units-and-locale) — distance and coordinate display formats
---

159
docs/ar-rSA/user/messages-and-channels.md Normal file
View File

@@ -0,0 +1,159 @@
---
title: Messages & Channels
nav_order: 3
last_updated: 2026-05-13
description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions.
aliases:
- channels
- direct-messages
- messaging
- conversations
---
# Messages & Channels
Meshtastic supports two communication modes: **channel broadcasts** and **direct messages**.
## القنوات
Channels are shared communication groups. All nodes configured with the same channel key can read and send messages on that channel.
### Default Channel
Every Meshtastic device comes with a default **LongFast** channel. This is an unencrypted channel used for general mesh communication.
### Channel Security
Channels support multiple encryption levels:
| Icon | Security Level | الوصف |
| ---- | ------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------- |
| 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. |
| 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. |
| 🔓 | Default / Open | Uses the well-known default key. **Any Meshtastic device** on the same preset can read these messages. |
| ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. |
> 🔒 **Security Tip:** Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive.
### Adding a Channel
1. Navigate to **Settings → Channels**.
2. Tap **Add Channel** or scan a QR code.
3. Configure the channel name and encryption key.
4. Share the channel URL/QR code with others who need access.
Tapping a channel shows its details and sharing options.
## Direct Messages
Direct messages (DMs) are point-to-point encrypted communications between two specific nodes.
### Sending a Direct Message
1. Open the **Messages** tab.
2. Select a node from your contacts list or tap a node in the node list.
3. Type your message and tap **Send**.
### Message States
| State | Icon | Meaning |
| --------------------------------- | ---- | ----------------------------------------------------------------------------------------------------------------- |
| Queued | ⏳ | Message waiting to be sent |
| En route | ✓ | Delivered to the radio, awaiting acknowledgment |
| Delivered | ✓✓ | Acknowledgment received from recipient |
| Received | ✓ | Message received from the mesh (incoming) |
| S&F Routing | 🔗 | Store & Forward: message being routed through an S&F node |
| S&F Confirmed | 🔗 | Store & Forward: delivery confirmed via S&F node |
| غلط | ✗ | Delivery failed after retries |
### Delivery Errors
When a message fails to deliver, the error indicator shows what went wrong:
| غلط | Meaning | What to Do |
| ---------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
| استغرق وقت طويل | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
| لم يجد وسيط | No radio interface available to send | Check that your radio is connected and the channel is configured. |
| Max Retransmit | All retry attempts exhausted | The mesh path is unreliable. Try a different channel or wait for conditions to improve. |
| لا يوجد قناه | The destination channel doesn't exist | Verify both nodes share the same channel configuration. |
| Too Large | Message exceeds maximum payload size | Shorten your message (max ~230 characters). |
| No Response | Node received message but didn't respond | The recipient's radio may be busy or in low-power sleep mode. |
| Duty Cycle Limit | Regional airtime limit reached | Your radio has used its allowed transmit time. Wait for the duty cycle window to reset (typically 1 hour in EU regions). |
| طلب غير جيد | Malformed or invalid message | This usually indicates a software bug. Try restarting the app. |
> 💡 **Tip:** Most delivery errors resolve themselves. If a node is intermittently reachable, the mesh will retry. For persistent "No Route" errors, check that intermediate Router nodes are online.
## Message Features
### Quick Chat
Pre-configured messages for rapid communication:
- Access via the Quick Chat button in the message input area
- Choose from built-in phrases or custom messages
- Customize quick chat messages in **Settings → Quick Chat**
- Useful when typing is impractical (gloves, small screen, urgent)
![Quick chat option](/assets/screenshots/messages_quick_chat.png)
The channel list shows each channel with its latest message preview.
### Message Bubbles
Messages appear as chat bubbles — sent messages on the right, received messages on the left. Each bubble shows the sender, timestamp, and delivery status. Messages with replies include a quoted preview of the original message above the response.
### Reactions
React to messages with emoji:
- **Long-press** a message to open the actions menu
- Tap **Add Reaction** to choose an emoji
- Reactions appear below the message bubble
- Multiple users can react to the same message
- React to your own messages or others' messages
![Emoji reaction badges displayed beneath a message](/assets/screenshots/messages_reaction.png)
> 💡 **Tip:** Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages.
### Message Actions
Long-press any message to access:
- **Copy** — copy message text to clipboard
- **Reply** — quote the message in your response
- **React** — add an emoji reaction
- **Delete** — remove a message you sent (local deletion)
### Message Priority
Messages are queued and transmitted based on priority:
1. Emergency/alert messages (highest)
2. Direct messages
3. Channel broadcasts (lowest)
### Message Limits
- **Maximum length:** 237 bytes (approximately 230 characters for ASCII text)
- **Rate limiting:** The mesh enforces airtime fairness; heavy message volume may be throttled
- **Delivery:** Messages are retried automatically if no acknowledgment is received
## Best Practices
- Use channels for group coordination
- Use direct messages for private person-to-person communication
- Keep messages short — mesh bandwidth is limited
- Configure encryption for sensitive communications
## Related Topics
- [Nodes](nodes) — tap a node to start a direct message
- [Settings — Radio & User](settings-radio-user) — configure channel encryption and presets
- [MQTT](mqtt) — bridge channel messages to the internet
- [Channel configuration](https://meshtastic.org/docs/configuration/radio/channels) — detailed channel settings on meshtastic.org
---

137
docs/ar-rSA/user/mqtt.md Normal file
View File

@@ -0,0 +1,137 @@
---
title: MQTT
nav_order: 11
last_updated: 2026-05-13
description: Bridge your mesh to the internet — MQTT broker setup, encryption layers, and map reporting.
aliases:
- mqtt
- internet-bridge
- broker
---
# MQTT
MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range.
## Overview
The MQTT module connects your node to an MQTT broker, allowing:
- Messages to reach nodes on different physical meshes via the internet
- Integration with home automation and monitoring systems
- Publishing node positions to the public Meshtastic map
- Custom data pipelines for logging and alerting
## How It Works
```
[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
```
A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.
## Configuration
### Enabling MQTT
1. Navigate to **Settings → Module Config → MQTT**.
2. Enable the MQTT module.
3. Configure the broker connection:
![MQTT toggle switch](/assets/screenshots/settings_switch.png)
| Setting | الوصف | Default |
| --------------- | --------------------------------------------------------------------------------------------- | --------------------------------------------------- |
| Server Address | MQTT broker hostname | mqtt.meshtastic.org |
| Username | Broker authentication | meshdev |
| Password | Broker authentication | large4cats |
| Root Topic | Base topic for messages | msh |
| Encryption | Encrypt MQTT payload | Enabled |
| ~~JSON Output~~ | ⚠️ **Deprecated** — JSON packet support has been removed from firmware; this field is ignored | Disabled |
| TLS | Secure connection to broker | Disabled |
| Map Reporting | Report position to public map | Disabled |
### Default Meshtastic Broker
The community maintains a public broker at `mqtt.meshtastic.org`. This is intended for general use and testing.
> 🔒 **Privacy:** Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.
### Private Broker
For better privacy and control, you can run your own MQTT broker:
- Mosquitto (lightweight, open-source)
- HiveMQ
- EMQX
Configure your node to point to your private broker with appropriate credentials.
## Map Reporting
When Map Reporting is enabled, your node publishes its position to the Meshtastic community map:
- Visible at [meshmap.net](https://meshmap.net) and similar community map services
- Only position and node info are shared
- Disable this if you don't want your location publicly visible
## Uplink vs Downlink
| Direction | الوصف |
| ------------ | -------------------------------- |
| **Uplink** | Messages from mesh → MQTT broker |
| **Downlink** | Messages from MQTT broker → mesh |
Configure per-channel which directions are active to control message flow and airtime usage.
## Message Formats
MQTT uses protobuf message format:
| Format | الوصف | Use case |
| ------------ | ----------------------------------- | -------------------------- |
| **Protobuf** | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging |
> ⚠️ **Note:** JSON output support was removed from firmware. The `json_enabled` setting is still visible in the app for legacy compatibility but has no effect on current firmware versions.
## Encryption & Privacy
Understanding the layered encryption model:
1. **Channel encryption** happens on the mesh _before_ MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
2. **MQTT encryption** (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information.
3. **TLS** encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.
> 🔒 **Important:** The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively **unencrypted** — anyone can decode them. Always use a custom PSK for private communications.
## Best Practices
- Use channel-level encryption (PSK) on channels that bridge to MQTT
- Don't enable MQTT on nodes without internet access (it will buffer and waste memory)
- Use a private broker for sensitive deployments
- Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
- Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back
## Troubleshooting
### MQTT Not Connecting
- **Check WiFi** — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself.
- **Verify credentials** — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces.
- **Firewall** — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports.
- **DNS resolution** — if using a custom broker hostname, verify the node can resolve it. Try the broker's IP address directly.
### Messages Not Bridging
- **Check uplink/downlink settings** — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
- **Channel mismatch** — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
- **Topic mismatch** — ensure both gateways use the same root topic. The default `msh` works for the public broker.
## Related Topics
- [Settings — Modules & Admin](settings-module-admin) — MQTT module configuration reference
- [Messages & Channels](messages-and-channels) — channel encryption and PSK setup
- [MQTT integration guide](https://meshtastic.org/docs/software/integrations/mqtt) — detailed MQTT documentation on meshtastic.org
---

130
docs/ar-rSA/user/node-metrics.md Normal file
View File

@@ -0,0 +1,130 @@
---
title: Node Metrics
nav_order: 5
last_updated: 2026-05-13
description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history.
aliases:
- metrics
- telemetry
- device-metrics
- signal
---
# Node Metrics
The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.
## Device Metrics
Basic operating information reported by each node:
| Metric | الوصف |
| -------------- | ----------------------------------- |
| Battery Level | Current battery percentage |
| شدة التيار | Battery voltage reading |
| استخدام القناة | Percentage of airtime consumed |
| Airtime | Transmission time used by this node |
| Uptime | Time since last reboot |
Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time.
> 💡 **Tip:** Tap any metric card to expand it into a full chart with historical data points. 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 |
| Gas Resistance | BME680 |
| IAQ (Air Quality) | BME680 |
Environment metrics are charted over time for easy trend analysis — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.
> 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors.
## Signal Metrics
Radio signal quality information:
| Metric | الوصف |
| ------------------ | ----------------------------------------------------------------------------- |
| SNR | Signal-to-Noise Ratio (higher is better) |
| مؤشر القوة النسبية | Received Signal Strength Indicator (closer to 0 is better) |
| Hop Count | Number of mesh hops for last message |
### Signal Quality Reference
| SNR Range | Quality |
| --------------------------------- | --------- |
| > 10 dB | Excellent |
| 0 to 10 dB | جيد |
| -10 to 0 dB | مناسب |
| < -10 dB | Poor |
## Power Metrics
Power management telemetry (requires INA sensor or compatible hardware):
| Metric | الوصف |
| ----------- | ----------------------- |
| Bus Voltage | Supply voltage |
| الحالي | Power draw in milliamps |
| Power | Calculated wattage |
## Traceroute
Traceroute shows the path a message takes through the mesh:
1. From the node detail screen, tap **Traceroute**.
2. The app sends a traceroute request to the target node.
3. Results show each hop with SNR/RSSI values.
### Reading Traceroute Results
```
You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target
```
Each hop represents a relay node that forwarded the message.
## سجل الموقع
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.
## Viewing Metrics
1. Navigate to **Nodes**.
2. Tap the node you want to inspect.
3. Select the metric category from the detail tabs.
![Node detail — local device](/assets/screenshots/nodes_detail_local.png)
The position tab shows location data for nodes that share GPS:
![Position inline content](/assets/screenshots/nodes_position.png)
> ⚠️ **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.
## Related Topics
- [Nodes](nodes) — node list, filtering, and sorting
- [Telemetry & Sensors](telemetry-and-sensors) — supported sensors and configuration
- [Signal Meter](signal-meter) — how signal quality is calculated from SNR and RSSI
- [Discovery](discovery) — traceroute details and neighbor info
- [Units & Locale](units-and-locale) — temperature, distance, and speed display formats
---

152
docs/ar-rSA/user/nodes.md Normal file
View File

@@ -0,0 +1,152 @@
---
title: Nodes
nav_order: 4
last_updated: 2026-05-13
description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions.
aliases:
- node-list
- mesh-nodes
- peers
---
# Nodes
The Nodes screen displays all devices visible on your mesh network.
## 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** — last heard signal strength
- **Last heard** — time since last communication
- **Distance** — estimated distance (if positions are shared)
- **Battery** — remote node battery level (if telemetry is enabled)
### Node Status Indicators
| Badge | Meaning |
| ---------- | ------------------------------------- |
| 🟢 Online | Node heard within the last 15 minutes |
| 🟡 Away | Node heard within the last 2 hours |
| 🔴 Offline | Node not heard for over 2 hours |
| ⭐ Favorite | Node marked as favorite by the user |
### Node Roles
Nodes can be configured with different roles that affect their mesh behavior:
| Role | الوصف |
| -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Client | Standard end-user device |
| 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 & Found | Continuous position beacon for recovery |
### 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 devices.
- **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 devices or to reduce congestion in dense areas.
- **Tracker** — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
- **Sensor** — An unattended device 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](tak) for details.
> 💡 **Tip:** The mesh works best when most nodes are **Client** or **Router**. Too many Mute nodes reduces 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 | Communication uses shared channel PSK — encrypted but identity not individually verified |
| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) |
> 💡 **Tip:** PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised.
## Quick Actions
From the node list, you can:
- **Tap** a node to view its detail page
- **Long-press** for quick actions:
- Send a direct message
- View on map
- Request position
- Mark as favorite
- Traceroute
## Filtering & Sorting
### Text Search
Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.
### Filter Toggles
| عربي | الوصف |
| -------------------------- | ---------------------------------------------------------------------------------------------- |
| **Only online** | Show only nodes heard within the last 15 minutes |
| **Only direct** | Show only nodes with direct (non-relayed) connections |
| **Include unknown** | Show nodes that haven't sent user info yet |
| **Exclude infrastructure** | Hide infrastructure-role nodes (Router, Repeater, Router Late, Client Base) |
| **Exclude MQTT** | Hide nodes heard only via MQTT internet bridge |
| **Show ignored** | Show nodes you've previously dismissed or muted |
### Sort Options
| Sort | الوصف |
| ------------------------------------------- | ------------------------------------------------------------------ |
| **Last heard** (default) | Most recently heard nodes first |
| **Alphabetical** | 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 |
| **Favorites** | Favorited nodes first |
## Node Detail
Tapping a node opens the detail view with comprehensive information. See [Node Metrics](node-metrics) for full details on metrics and telemetry.
![Node detail view](/assets/screenshots/nodes_node_list.png)
The detail screen includes device info, position, and action buttons:
![Node detail section](/assets/screenshots/nodes_detail_section.png)
Inline status indicators show key metrics at a glance:
| Indicator | Screenshot |
| -------------- | -------------------------------------------------------- |
| Signal quality | ![Signal](/assets/screenshots/nodes_signal_info.png) |
| Battery level | ![Battery](/assets/screenshots/nodes_battery_info.png) |
| Hop count | ![Hops](/assets/screenshots/nodes_hops_info.png) |
| آخر ظهور | ![Last heard](/assets/screenshots/nodes_last_heard.png) |
| المسافة | ![Distance](/assets/screenshots/nodes_distance_info.png) |
## Related Topics
- [Node Metrics](node-metrics) — detailed telemetry dashboards for each node
- [Messages & Channels](messages-and-channels) — send a direct message to a node
- [Map & Waypoints](map-and-waypoints) — view node positions geographically
- [Discovery](discovery) — traceroute and neighbor info for topology exploration
- [Signal Meter](signal-meter) — understand what the signal bars mean
---

99
docs/ar-rSA/user/onboarding.md Normal file
View File

@@ -0,0 +1,99 @@
---
title: Getting Started
nav_order: 1
last_updated: 2026-05-13
description: First-launch setup — permissions, onboarding flow, and next steps after connecting your radio.
aliases:
- first-launch
- setup
- intro
---
# Getting Started
Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app.
## First Launch
When you open the app for the first time, you'll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings.
### Welcome Screen
The welcome screen introduces Meshtastic and its core capabilities:
- Off-grid mesh communication
- No cellular or internet required
- End-to-end encrypted messaging
Tap **Get Started** to proceed through the setup flow.
![Welcome screen](/assets/screenshots/onboarding_welcome.png)
## Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
### Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio:
- **Bluetooth scanning** — discover nearby Meshtastic radios
- **Bluetooth connect** — establish and maintain connections with paired radios
Grant both permissions when prompted. Without Bluetooth, you'll need to use USB or TCP connections instead.
### Location Permission
> ⚠️ **Why is location required for Bluetooth?** Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice.
Meshtastic also uses your location for:
- Showing your position on the mesh map
- Calculating distances to other nodes
- Sharing your GPS coordinates with other mesh members (if enabled)
Grant **"While using the app"** or **"Always"** depending on your preference:
- **While using the app** — position updates only when the app is open
- **Always** — enables background position updates for always-on mesh presence
If denied, Bluetooth scanning will not function and your node will not report a position.
### Notifications Permission
Notifications alert you to:
- Incoming messages from channels and direct messages
- Connection status changes (connected, disconnected, reconnecting)
- Firmware update availability
> 💡 **Tip:** You can fine-tune notification preferences later in Android system settings. The app creates separate notification channels for messages, connection events, and background service status.
### Critical Alerts Permission
On supported devices, the app may request permission for critical alerts:
- These are high-priority notifications that can break through Do Not Disturb mode
- Useful for emergency mesh alerts or urgent messages
- You can **skip** this step if you don't need breakthrough notifications
- Configure or revoke later in Android notification settings
## After Setup
Once permissions are granted, the app transitions to the main interface. Your first action should be connecting to a Meshtastic radio — see [Connections](connections) for detailed instructions.
> 💡 **Tip:** If you skipped any permissions during setup, you can grant them later through **Android Settings → Apps → Meshtastic → Permissions**. The app will prompt you again if a missing permission blocks a feature you try to use.
## What's Next?
Once connected to a radio, explore:
- [Connections](connections) — pair your first radio device
- [Messages & Channels](messages-and-channels) — send your first message
- [Nodes](nodes) — see who's on your mesh
- [Map & Waypoints](map-and-waypoints) — view node positions
- [Settings](settings-radio-user) — configure your radio and user profile
New to Meshtastic? The [getting started guide](https://meshtastic.org/docs/getting-started) on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
---

246
docs/ar-rSA/user/settings-module-admin.md Normal file
View File

@@ -0,0 +1,246 @@
---
title: Settings — Modules & Admin
nav_order: 8
last_updated: 2026-05-13
description: Configure optional feature modules (MQTT, telemetry, canned messages, TAK, and more) and perform device administration.
aliases:
- modules
- module-config
- administration
---
# Settings — Modules & Admin
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
> 💡 **Tip:** You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
![Toggle switch](/assets/screenshots/settings_switch.png)
![Dropdown selector](/assets/screenshots/settings_dropdown.png)
![Text field](/assets/screenshots/settings_text_field.png)
![Settings card layout](/assets/screenshots/settings_titled_card.png)
## Module Configuration
### MQTT Module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems.
| Setting | الوصف |
| --------------- | ------------------------------------------------------------------------ |
| Enabled | Toggle MQTT bridge |
| Server | MQTT broker address |
| Username | Authentication username |
| Password | Authentication password |
| Encryption | Encrypt MQTT payloads |
| ~~JSON Output~~ | ⚠️ **Deprecated** — JSON support removed from firmware; field is ignored |
| TLS | Use secure connection |
| Root Topic | Base MQTT topic path |
| Map Report | Publish position for public map |
See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup.
### Serial Module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node's serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
| Setting | الوصف |
| ---------- | ------------------------------- |
| Enabled | Activate serial communication |
| Echo | Echo received serial data back |
| Mode | Text, Protobuf, or NMEA output |
| RX/TX Pins | GPIO pins for serial connection |
| Baud Rate | Serial communication speed |
### External Notification Module
Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
| Setting | الوصف |
| -------------------------------- | --------------------------- |
| Enabled | Activate notifications |
| Alert Message | Notify on incoming messages |
| Alert Message Buzzer | Use buzzer for messages |
| Alert Message Vibra | Use vibration for messages |
| Alert Bell | Notify on bell character |
| Output (GPIO) | Pin for notification output |
| Active | High or Low active |
| Duration (ms) | Notification length |
| Use I2S as Buzzer | Use I2S audio output |
### Store & Forward Module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren't lost during brief disconnections.
| Setting | الوصف |
| ------------------------------------------ | -------------------------- |
| Enabled | Activate store and forward |
| Heartbeat (s) | Announcement interval |
| Records | Maximum stored messages |
| History Return (max) | Max messages to replay |
| History Return (window) | Time window for replay |
> 💡 **Tip:** Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they're typically always-on.
### Range Test Module
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
| Setting | الوصف |
| -------------------------------------- | --------------------------------- |
| Enabled | Activate range testing |
| Sender Interval (s) | Time between test transmissions |
| Save CSV | Log received test data to SD card |
### Telemetry Module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
| Setting | الوصف |
| ---------------------------- | --------------------------------------- |
| Device Metrics Interval | How often to report device metrics |
| Environment Metrics Interval | How often to report environment sensors |
| Air Quality Enabled | Report particulate sensor data |
| Power Metrics Enabled | Report power usage |
See [Telemetry & Sensors](telemetry-and-sensors) for supported sensors and configuration recommendations.
### Canned Message Module
Pre-configured messages accessible from the device's physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
| Setting | الوصف |
| ------------------ | ----------------------------------------------------------- |
| ~~Enabled~~ | ⚠️ **Deprecated** — current firmware may ignore this toggle |
| الرسائل | Newline-separated list of messages |
| Send Bell | Play bell sound on send |
| Rotary Encoder | Enable rotary encoder input |
| Up/Down/Press Pins | GPIO pin assignments for input |
### Audio Module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an **experimental** feature that encodes voice into very small data packets using the Codec2 codec.
| Setting | الوصف |
| --------------- | -------------------------------- |
| Enabled | Activate audio module |
| Codec2 Rate | Audio quality/bandwidth tradeoff |
| I2S Word Select | GPIO pin for I2S WS |
| I2S Data In | GPIO pin for I2S DIN |
| I2S Data Out | GPIO pin for I2S DOUT |
> ⚠️ **Note:** Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think "understandable radio voice," not phone-call quality.
### Remote Hardware Module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
| Setting | الوصف |
| -------------------- | --------------------------------------------------------------- |
| Enabled | Activate remote GPIO access |
| Allow Undefined Pins | Allow access to any GPIO pin (security risk) |
> ⚠️ **Warning:** Enabling "Allow Undefined Pins" gives remote nodes access to all GPIO pins, which could interfere with the radio's own hardware. Only enable on dedicated GPIO nodes.
### Neighbor Info Module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
| Setting | الوصف |
| -------------------------------------- | ------------------------------------ |
| Enabled | Activate neighbor broadcasting |
| Update Interval (s) | How often to broadcast neighbor list |
See [Discovery](discovery) for how to use neighbor data for mesh topology exploration.
### Ambient Lighting Module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
| Setting | الوصف |
| ------------------ | ---------------------------------------------------------- |
| Enabled | Activate LED control |
| LED State | On, Off, or set specific color |
| Red / Green / Blue | Individual color channel values (0–255) |
### Detection Sensor Module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
| Setting | الوصف |
| ---------------------------------------- | ----------------------------------------------------------------------- |
| Enabled | Activate detection sensor |
| Monitor Pin | GPIO pin connected to sensor |
| Detection Triggered High | Trigger when pin goes high (vs. low) |
| Minimum Broadcast (s) | Minimum time between alert broadcasts |
| State Broadcast (s) | Periodic state broadcast interval |
| Send Bell | Include bell character in alerts |
| Friendly Name | Custom name for this sensor |
### Paxcounter Module
People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
| Setting | الوصف |
| -------------------------------------- | -------------------------- |
| Enabled | Activate people counting |
| Update Interval (s) | How often to report counts |
> 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
### TAK Module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. See [TAK Integration](tak) for detailed setup and usage.
## الإدارة
### Remote Administration
Remotely configure nodes that share your admin key:
1. Select the target node in the node list.
2. Navigate to **Settings** for that node.
3. Modify configuration.
4. Tap **Save** — changes are sent over the mesh.
> ⚠️ **Requires:** Admin key configured on both your node and the target node.
### Clean Node Database
Removes stale nodes from your local database that haven't been heard in a configurable time window.
### Factory Reset
Resets all settings to factory defaults. **This cannot be undone.**
### إعادة التشغيل
Remotely reboot a connected or administered node.
### Debug Panel
View detailed diagnostic information:
- Protocol buffers debug output
- Mesh packet log
- Connection state details
### Troubleshooting Remote Admin
- **"No response from target node"** — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
- **Changes not applying** — some settings require a reboot to take effect. Try the Reboot action after saving.
- **Can't see remote settings** — ensure your node has the admin key for the target node and that Admin Channel is enabled in Security Config.
## Related Topics
- [Settings — Radio & User](settings-radio-user) — core radio and user profile settings
- [Module configuration reference](https://meshtastic.org/docs/configuration/module) — detailed module docs on meshtastic.org
- [FAQ](https://meshtastic.org/docs/about/faq) — common questions on meshtastic.org
---

173
docs/ar-rSA/user/settings-radio-user.md Normal file
View File

@@ -0,0 +1,173 @@
---
title: Settings — Radio & User
nav_order: 7
last_updated: 2026-05-13
description: Configure your radio hardware, LoRa presets, user profile, position sharing, power management, and security.
aliases:
- الإعدادات
- radio-config
- user-config
- lora
---
# Settings — Radio & User
Configure your radio hardware and user identity parameters.
## User Settings
### User Profile
| Setting | الوصف |
| ----------------- | ------------------------------------------------------------------------------------- |
| Long Name | Your display name (up to 39 characters) |
| Short Name | 4-character abbreviated name |
| Licensed Operator | Enable if you hold an amateur radio license (enables higher power) |
### Applying Changes
After modifying settings, tap **Save** to write the configuration to your radio. The device may reboot to apply changes.
## Radio Configuration
### Device Config
| Setting | الوصف | Default |
| ------------------------------------------ | ----------------------------------------------------------------------- | -------- |
| Role | Node behavior (Client, Router, etc.) | Client |
| Rebroadcast Mode | How the node retransmits messages | All |
| Node Info Broadcast (s) | Interval for broadcasting node info | 10800 |
| Double-tap Button | Action for double-tap button press | Disabled |
### LoRa Config
| Setting | الوصف | Default |
| ----------------- | ----------------------------------------------------------------------- | ----------------------------------------- |
| الجهة | Regulatory region for frequency bands | Unset (must configure) |
| Modem Preset | Speed/range tradeoff | LongFast |
| Hop Limit | Maximum retransmit hops | 3 |
| TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) |
| Frequency Offset | Fine-tune frequency (MHz) | 0 |
| Channel Bandwidth | Bandwidth setting | Default for preset |
> ⚠️ **Important:** You **must** set your region before transmitting. Operating without the correct region may violate local radio regulations. See the [region configuration guide](https://meshtastic.org/docs/getting-started/initial-config) on meshtastic.org for details.
### Modem Presets
| Preset | Range | Speed | SNR Limit | Best For |
| ------------------ | ----------------------- | ------------------------- | ------------------------ | -------------------------------------------------------------------------------------------------------- |
| Short Turbo | ~1 km | 21.9 kbps | −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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density |
| Medium Fast | ~5 km | 5.5 kbps | −10 dB | Suburban areas; moderate building density |
| Medium Slow | ~8 km | 1.1 kbps | −12.5 dB | Suburban/rural; moderate range with slower speed |
| Long Turbo | ~10 km | 4.4 kbps | −10 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput |
| Long Fast | ~10 km | 1.1 kbps | −12.5 dB | **General use (default)** — balanced range and speed |
| Long Moderate | ~20 km | 0.34 kbps | −15 dB | Rural with some terrain; occasional use |
| Lite Fast | ~5 km | 5.5 kbps | −10 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast |
| Lite Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast |
| Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices |
| Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast |
| ~~Long Slow~~ | ~30 km | 0.18 kbps | −17.5 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 |
#### 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.
> ⚠️ **Important:** 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.
> 💡 **Tip:** The range estimates above 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
| Setting | الوصف |
| ------------------- | ------------------------------------------------------------------------------------ |
| Screen Timeout | Time before display sleeps |
| Display Units | Metric or Imperial |
| OLED Type | Auto, SSD1306, SH1106, SH1107 |
| Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) |
| ~~Compass North~~ | ⚠️ **Deprecated** — replaced by Compass Orientation; still visible in older firmware |
### Position Config
| Setting | الوصف |
| ----------------------------------------- | ---------------------------------- |
| GPS Enabled | Enable/disable GPS |
| GPS Update Interval | How often to acquire GPS fix |
| Position Broadcast (s) | How often to share position |
| Smart Position | Enable movement-based broadcasting |
| Fixed Position | Use a manually set position |
### Power Config
| Setting | الوصف |
| --------------------------------------- | --------------------------------------- |
| Power Saving | Enable low-power sleep mode |
| Shutdown After (s) | Auto-shutdown idle timer |
| ADC Multiplier | Battery voltage calibration factor |
| Wait Bluetooth (s) | Time to wait for BLE connection at boot |
| Mesh SDS Timeout (s) | Super-deep-sleep timeout |
### Network Config
| Setting | الوصف |
| ------------- | ---------------------------------------------------- |
| WiFi Enabled | Enable WiFi radio (ESP32 devices) |
| WiFi SSID | Network name to connect to |
| WiFi PSK | Network password |
| NTP Server | Time synchronization server |
| Syslog Server | Remote logging server |
![IP address field](/assets/screenshots/settings_ipv4_field.png)
### Bluetooth Config
| Setting | الوصف |
| ----------------- | ------------------------------------------------------------------------- |
| Bluetooth Enabled | Enable/disable BLE radio |
| Pairing Mode | Fixed PIN, Random PIN, or No PIN |
| Fixed PIN | PIN code for pairing (default: 123456) |
### Security Config
| Setting | الوصف |
| --------------------- | -------------------------------------------------------------------------- |
| Public Key | Your node's public key (read-only) |
| Admin Key | Key for remote administration |
| Private Key | Your node's private key (handle securely) |
| Admin Channel Enabled | Allow admin commands via channel |
| Debug Log | Output live debug logging over serial/bluetooth |
| Serial Enabled | Enable serial console access (moved from Device Config) |
| Managed Mode | Restrict non-admin channel changes |
![Password field](/assets/screenshots/settings_password_field.png)
Settings use standard preference controls — dropdowns, toggles, and sliders:
| Control | Screenshot |
| -------- | ------------------------------------------------------ |
| Dropdown | ![Dropdown](/assets/screenshots/settings_dropdown.png) |
| Toggle | ![Toggle](/assets/screenshots/settings_switch.png) |
| Slider | ![Slider](/assets/screenshots/settings_slider.png) |
## Related Topics
- [Settings — Modules & Admin](settings-module-admin) — optional feature modules and device administration
- [Signal Meter](signal-meter) — how modem presets affect signal quality thresholds
- [LoRa configuration](https://meshtastic.org/docs/configuration/radio/lora) — detailed LoRa settings reference on meshtastic.org
- [Initial configuration](https://meshtastic.org/docs/getting-started/initial-config) — region setup guide on meshtastic.org
---

81
docs/ar-rSA/user/signal-meter.md Normal file
View File

@@ -0,0 +1,81 @@
---
title: How the Meshtastic Signal Meter Works
nav_order: 15
last_updated: 2026-05-13
description: How the signal meter calculates quality from RSSI and SNR — LoRa spread spectrum, presets, and what the bars really mean.
aliases:
- signal
- signal-meter
- snr
- rssi
---
# How the Meshtastic Signal Meter Works
The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the "bars" on a traditional cell phone or Wi-Fi router.
Most consumer devices simply measure how "loud" a signal is. However, because Meshtastic uses **LoRa (Long Range)** technology, its signal meter measures how **clear** the signal is, relative to the specific settings your mesh is using.
---
## 1. The Two Metrics: "Loudness" vs. "Clarity"
Every time the LoRa radio chip receives a message, it reports two measurements:
- **RSSI (Received Signal Strength Indicator):** The **loudness** of the raw power hitting your antenna.
- **SNR (Signal-to-Noise Ratio):** The **clarity** of the signal compared to the background static.
> **Tip — The Analogy:** Imagine you are trying to hear a friend talking to you.
>
> - **RSSI** is how loud their voice is.
> - **The Noise Floor** is the background noise in the room (air conditioning, other people talking, traffic).
> - **SNR** is how easily you can distinguish your friend's voice from the background noise.
If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can't understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR).
---
## 2. The Magic of LoRa: Hearing "Below the Noise Floor"
For standard radios (like FM or Wi-Fi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static.
LoRa is special. It uses **"Spread Spectrum"** modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep _underneath_ the background noise. This is why you will frequently see **negative SNR numbers** in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static).
Depending on which Meshtastic preset you are using (e.g., `LongFast` vs. `ShortFast`), the radio has a specific **SNR Limit** — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static.
---
## 3. How the Signal Meter Calculates Quality
The Meshtastic apps take both RSSI and SNR and run them through a specific formula to assign your signal a quality rating (None, Bad, Fair, or Good). It specifically scales these values based on the physical limits of the radio preset you are using.
Here is exactly how the app decides how many bars (or what color) to show you:
| Level | Bars | Criteria | Meaning |
| ------- | ---- | ----------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- |
| جيد | 3 | RSSI better than `-115 dBm` **AND** SNR better than `-7 dB` | Signal is both loud and clear — healthy connection. |
| مناسب | 2 | RSSI better than `-126 dBm` with good SNR, **OR** SNR better than `-15 dB` with good RSSI | Signal getting quieter or noisier, but still decodable. |
| سيئ | 1 | Falls between Fair and None thresholds | At the edge of range or experiencing interference. |
| لا يوجد | 0 | RSSI worse than `-126 dBm` **AND** SNR worse than `-15 dB` | Transmission completely buried in noise. |
---
## 4. What This Means for You
Because Meshtastic's meter acts as a **"Clarity Meter"**, it behaves differently than what most people expect:
> **Tip — Don't panic over low RSSI:** You might see a seemingly terrible RSSI value like `-118 dBm`. On a cell phone, you would have zero bars. But if you have an SNR of `+2 dB`, Meshtastic will still show a strong signal! _The library is quiet, so the whisper is heard perfectly._
> **Warning — Watch out for local noise:** If you hook up a massive antenna and see a great RSSI (e.g., `-90 dBm`) but your signal meter is only showing **1 Bar (Bad)**, you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh.
## Where Signal Information Appears
In the app, signal data is shown in several places:
- **Node list** — signal bars icon next to each node
- **Node detail** — SNR, RSSI, and signal quality in the device metrics section
- **Traceroute** — per-hop signal quality for each relay node
- **Signal metrics** — historical SNR and RSSI data in the metrics charts
![Node entry showing SNR, RSSI values and colored signal bars](/assets/screenshots/nodes_signal_info.png)

126
docs/ar-rSA/user/tak.md Normal file
View File

@@ -0,0 +1,126 @@
---
title: TAK Integration
nav_order: 10
last_updated: 2026-05-13
description: Interoperate with ATAK and WinTAK — CoT position sharing, TAK roles, and plugin setup.
aliases:
- tak
- atak
- team-awareness-kit
---
# TAK Integration
Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK.
## Overview
The TAK module allows Meshtastic nodes to:
- Share position data in TAK-compatible CoT (Cursor on Target) format
- Appear as team members on TAK map displays
- Receive TAK PLI (Position Location Information) messages
## Setup
### Prerequisites
- ATAK (Android Team Awareness Kit) or WinTAK installed
- Meshtastic ATAK Plugin installed
- TAK module enabled on your Meshtastic radio
### Configuration
1. Navigate to **Settings → Module Config → TAK**.
2. Enable the TAK module.
3. Configure the TAK team/group settings:
![Module toggle switch](/assets/screenshots/settings_switch.png)
| Setting | الوصف |
| ------- | -------------------------- |
| Enabled | Activate TAK interop |
| Mode | TAK-compatible output mode |
### ATAK Plugin Setup
1. Install the Meshtastic ATAK Plugin from the plugin repository.
2. Open ATAK and enable the Meshtastic plugin.
3. The plugin bridges messages between ATAK and your mesh network.
## TAK Roles
Nodes configured with TAK-related roles behave differently from standard clients:
| Role | الوصف |
| --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **TAK** | Full TAK interoperability — sends and receives CoT data, chat messages, and PLI updates. Functions as a standard client plus TAK bridge. |
| **TAK Tracker** | Position-only TAK output — automatically broadcasts PLI at regular intervals without user interaction. Optimized for unattended position beacons (vehicles, equipment, waypoints). Does not relay chat messages. |
> 💡 **Tip:** Use **TAK Tracker** for devices that only need to report position (e.g., a radio mounted in a vehicle). Use **TAK** for devices where users actively participate in TAK operations.
### CoT (Cursor on Target) Format
TAK messages use the Cursor on Target XML format — a military standard for sharing situational awareness data. Meshtastic converts its internal protobuf messages to CoT format when bridging to TAK systems, so no manual format conversion is needed.
## TAK Identity
When using TAK roles, your node broadcasts identity information that appears on TAK maps:
| Setting | الوصف |
| -------- | ---------------------------------------------------------------------------------------------------------------- |
| Team | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) |
| Role | Your operational role (Team Member, Team Lead, HQ, Medic, RTO, etc.) |
| Callsign | Your TAK callsign (defaults to your Meshtastic long name) |
These settings appear in **Settings → Module Config → TAK** when the TAK module is enabled.
> 💡 **Tip:** Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments.
## Wire Format (V1 / V2)
Meshtastic supports two TAK wire formats:
| Format | Compatibility | Features |
| ------------------------------- | --------------------------------------------------------------- | --------------------------------------------------------- |
| V1 (Legacy) | ATAK Plugin v1.x, older firmware | Basic CoT position sharing only |
| V2 (Current) | ATAK Plugin v2.x, firmware 2.3+ | Full CoT support including chat, routes, zstd compression |
The app automatically selects V2 when both sides support it. No manual configuration needed — the TAK module negotiates format based on firmware capabilities.
## Usage with ATAK
Once configured:
- Meshtastic nodes appear as markers on the ATAK map with callsign labels
- Chat messages can bridge between mesh and TAK networks
- Position updates flow bidirectionally between Meshtastic and TAK
- TAK Tracker nodes broadcast PLI automatically — their positions appear on ATAK maps without any ATAK-side configuration
> ⚠️ **Note:** TAK integration requires specific node roles and module configuration. Standard client nodes don't automatically participate in TAK operations.
## Troubleshooting
| Problem | Cause | Solution |
| -------------------------------- | ------------------------------------- | ----------------------------------------------------------------------- |
| Node doesn't appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker |
| Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config |
| ATAK plugin shows "disconnected" | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin |
| Chat messages not bridging | V1 format doesn't support chat | Ensure both nodes run firmware 2.3+ for V2 wire format |
| CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption |
## Security Considerations
- TAK data shares your position and callsign information
- Ensure your channel encryption is configured when using TAK in sensitive environments
- The TAK module respects the same channel encryption as other Meshtastic messages
## Related Topics
- [Settings — Modules & Admin](settings-module-admin) — TAK module configuration
- [Nodes](nodes) — TAK and TAK Tracker roles in the node list
- [Map & Waypoints](map-and-waypoints) — node positions on the map
- [ATAK plugin guide](https://meshtastic.org/docs/software/integrations/atak-plugin) — detailed ATAK setup on meshtastic.org
---

118
docs/ar-rSA/user/telemetry-and-sensors.md Normal file
View File

@@ -0,0 +1,118 @@
---
title: Telemetry & Sensors
nav_order: 9
last_updated: 2026-05-13
description: Sensor data on the mesh — supported environment, air quality, and power sensors, plus configuration and viewing guides.
aliases:
- sensors
- environment
- weather
- power-metrics
---
# Telemetry & Sensors
Meshtastic nodes can collect and share sensor data across the mesh network.
## Overview
Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time.
## Device Telemetry
All Meshtastic nodes report basic device telemetry:
| Metric | الوصف | Typical Range |
| ------------------ | ------------------------------ | ------------------------------------------------------------------ |
| Battery Level | Charge percentage | 0–100% |
| شدة التيار | Battery voltage | 3.0–4.2V (LiPo) |
| استخدام القناة | % of airtime used locally | 0–100% |
| Air Utilization TX | % of airtime used by this node | 0–100% |
| Uptime | Seconds since last boot | Varies |
## Environment Sensors
Supported environmental sensors:
### Temperature & Humidity
| Sensor | الحرارة | الرطوبة | Pressure | Notes |
| ------- | ------- | ------- | -------- | ----------------------- |
| BME280 | ✓ | ✓ | ✓ | Recommended all-in-one |
| BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ |
| SHT31 | ✓ | ✓ | — | High accuracy |
| MCP9808 | ✓ | — | — | Precision temperature |
| LPS22 | — | — | ✓ | Pressure only |
### Air Quality
| Sensor | Metric | Notes |
| -------- | -------------------------------------------------- | -------------------------- |
| BME680 | Gas Resistance / IAQ | Volatile organic compounds |
| PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter |
| SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor |
### Light & UV
| Sensor | Metric |
| -------- | -------------------------------------- |
| OPT3001 | Ambient light (lux) |
| VEML7700 | Ambient light (lux) |
| LTR390 | UV index |
## Power Metrics
Nodes with INA-series power sensors can report:
| Metric | الوصف |
| ----------- | ----------------------------------------- |
| Bus Voltage | Supply rail voltage |
| الحالي | Power consumption (mA) |
| Power | Calculated power (mW) |
Useful for monitoring solar charging or battery health on remote nodes.
## Configuring Telemetry
1. Navigate to **Settings → Module Config → Telemetry**.
2. Set reporting intervals:
- **Device Metrics Interval** — how often to broadcast device metrics
- **Environment Metrics Interval** — how often to broadcast sensor data
3. Enable specific sensor types as needed.
### Recommended Intervals
| Use Case | Device (s) | Environment (s) |
| ------------------------------------------ | ----------------------------- | ---------------------------------- |
| Urban mesh (many nodes) | 3600 | 3600 |
| Rural mesh (few nodes) | 900 | 900 |
| Weather station | 900 | 300 |
| Battery conservation | 7200 | 7200 |
> ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh.
## Viewing Telemetry
1. Navigate to **Nodes** and select a node.
2. Telemetry sections show on the detail screen:
- Device Metrics (always available)
- Environment Metrics (if sensors present)
- Power Metrics (if INA sensor present)
3. Historical graphs show trends over time.
![Telemetry actions](/assets/screenshots/node-metrics_telemetric_actions.png)
## Troubleshooting
- **No environment data showing?** The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware.
- **Stale readings?** Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online.
- **Sensor conflict on I2C bus?** Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio's serial debug output.
## Related Topics
- [Node Metrics](node-metrics) — view telemetry data on the node detail screen
- [Settings — Modules & Admin](settings-module-admin) — telemetry module configuration
- [Units & Locale](units-and-locale) — temperature and pressure display units
---

97
docs/ar-rSA/user/translate.md Normal file
View File

@@ -0,0 +1,97 @@
---
title: Translate the App
parent: User Guide
nav_order: 17
last_updated: 2026-05-13
aliases:
- translate
- crowdin
- localization
---
# Translate the App
Contributing translations helps make Meshtastic accessible to a wider audience. The app uses [Crowdin](https://crowdin.com/) to manage community translations for both the user interface and in-app documentation.
---
## What Gets Translated
| Resource | Source Location | Notes |
| ----------------- | ------------------------------------- | ---------------------------------------------------------------------- |
| UI strings | `composeResources/values/strings.xml` | Buttons, labels, messages, and all user-visible text |
| User Guide pages | `docs/user/*.md` | In-app documentation shown in Help & Documentation |
| Fastlane metadata | `fastlane/metadata/android/en-US/` | App Store listing title, description, and changelogs |
> **Note — Developer Guide pages are English-only.** Code-focused documentation targeting contributors is not translated.
---
## How to Contribute
1. **Visit the Crowdin project.** Open the [Meshtastic Android Crowdin project](https://crowdin.com/project/meshtastic-android) and sign in or create a free account.
2. **Choose your language.** Select an existing language or request a new one by opening a [GitHub issue](https://github.com/meshtastic/Meshtastic-Android/issues/new).
3. **Translate strings.** Crowdin shows the English source on the left and your translation on the right. Translate each string and save.
4. **Review context.** Many strings include screenshots or context comments — check these to understand where the text appears in the app.
5. **Submit.** Approved translations are automatically merged into the next release.
> **Tip — Keep translations short.** UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear.
---
## Adding a New Language
If your language is not yet listed on Crowdin:
1. Open an issue on [GitHub](https://github.com/meshtastic/Meshtastic-Android/issues/new) requesting the new locale.
2. A maintainer will add the language to Crowdin and configure `crowdin.yml`.
3. Once added, you can begin translating immediately.
---
## How Translations Are Organized
The Android app uses **Compose Multiplatform resources** for all user-visible strings:
```
core/resources/src/commonMain/composeResources/
├── values/ ← English (default)
│ └── strings.xml
├── values-de/ ← German
│ └── strings.xml
├── values-fr/ ← French
│ └── strings.xml
└── ...
```
In-app documentation follows a similar pattern under `docs/`:
```
docs/
├── user/ ← English source (default)
│ ├── onboarding.md
│ └── ...
├── fr/user/ ← French translations
│ ├── onboarding.md
│ └── ...
└── ...
```
The app automatically selects the correct locale based on your device's **Language & Region** settings.
---
## Translation Guidelines
- **Do not translate** technical terms like "LoRa", "MQTT", "BLE", "TAK", "SNR", or "RSSI" — these are universal.
- **Keep placeholders intact.** Strings like `%1$s` or `%d` are filled in at runtime. Do not remove or reorder them unless the grammar of your language requires it.
- **Match tone.** The app uses a friendly, direct voice. Avoid overly formal language.
- **Test if possible.** Switch your device language and open the app to see how translations look in context.
---
## Questions?
If you have questions about a specific string's context or need help getting started, open a discussion on the [Meshtastic GitHub Discussions](https://github.com/meshtastic/Meshtastic-Android/discussions) page.
Thank you for helping expand the reach of Meshtastic!

118
docs/ar-rSA/user/units-and-locale.md Normal file
View File

@@ -0,0 +1,118 @@
---
title: Units, Measurement & Locale
parent: User Guide
nav_order: 16
last_updated: 2026-05-12
---
# Units, Measurement & Locale
The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use — no settings to change inside the app.
---
## How It Works
Meshtastic radios always transmit data in **metric units** (meters, °C, km/h, hPa, etc.). When the app receives this data, it uses the `MetricFormatter` utility to convert and display values in whatever unit system your device's locale specifies.
On Android, your measurement preferences are determined by your system **Language & Region** settings. On Desktop (JVM), the app uses the JVM's default `Locale`.
> **Tip — You never need to toggle units inside the app.** Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more.
---
## الحرارة
Temperature values from environment sensors are transmitted as **°C** and displayed based on your device's temperature unit preference.
![Environment metrics with temperature](/assets/screenshots/nodes_environment_metrics.png)
| Your Setting | You See |
| ------------ | ------- |
| Celsius | 22°C |
| Fahrenheit | 72°F |
This affects all temperature displays throughout the app: node environment telemetry, soil temperature, dew point, and telemetry chart axes.
## Distance & Altitude
Distances between nodes and GPS altitudes are transmitted as **meters** and automatically scaled and converted.
![Distance info display](/assets/screenshots/nodes_distance_info.png)
| Your Setting | Small Distance | Large Distance | Altitude |
| -------------------------------- | -------------- | ---------------------- | -------- |
| Metric | 350 m | 2.5 km | 1,200 m |
| Imperial (US) | 1,148 ft | 1.6 mi | 3,937 ft |
The app uses natural scaling — short distances stay in meters or feet, while longer distances switch to kilometres or miles automatically.
### Where these appear
- **Node list** — distance and bearing to each node
- **Node detail** — altitude, distance from your position
- **Map** — waypoint distances, traceroute hop distances
- **Compass** — distance to selected node
## Speed
GPS ground speed is displayed in your locale's preferred speed unit.
| Your Setting | You See |
| -------------------------------- | ------- |
| Metric | 12 km/h |
| Imperial (US) | 7 mph |
## Wind
Wind speed and gust data from environment sensors are transmitted as **m/s** and converted for display.
| Your Setting | You See |
| -------------------------------- | ------- |
| Metric | 5 m/s |
| Imperial (US) | 11 mph |
Wind readings appear in the **Node Detail** environment section and the **Environment Telemetry** charts.
## Rainfall
Rainfall measurements (1-hour and 24-hour totals) are transmitted as **mm** and converted for display.
| Your Setting | You See |
| -------------------------------- | ---------------------- |
| Metric | 12 mm |
| Imperial (US) | 0.5 in |
## Units That Never Change
Some units are international standards and are displayed the same way regardless of your locale:
| Measurement | Unit | Why |
| -------------------------------- | ------------------------------ | ------------------------------------- |
| Barometric pressure | hPa | International meteorological standard |
| Heading / bearing | ° (degrees) | Universal navigation convention |
| Radiation | μR/hr | Standard dosimetry unit |
| GPS coordinates | decimal degrees | Universal geographic standard |
| Humidity, battery, soil moisture | % | Universal |
## Date & Time
All timestamps throughout the app — last heard, message times, telemetry logs, chart axes — follow your device's date and time preferences.
| Setting | What It Controls | Example |
| ---------------- | ---------------- | ------------------------------------------------ |
| **24-Hour Time** | Clock format | 14:30 vs 2:30 PM |
| **Date Format** | Date ordering | 09/05/2026 vs 05/09/2026 |
The app also uses **relative time** where it makes sense — for example, "5 min ago" or "2 hours ago" in the node list — which is automatically localised into your device language.
## Changing Your Measurement System (Android)
On Android, your measurement system (metric vs imperial) is tied to your region setting:
1. Open **Android Settings → System → Language & Region**
2. Change your **Region** or **Measurement units** preference
3. Return to Meshtastic — values update immediately
> **Tip — The app uses `MetricFormatter` from `core:common`.** All measurement formatting is handled by a shared KMP utility that respects your platform's locale. Developers adding new measurement displays should use `MetricFormatter` rather than hard-coding unit conversions.

30
docs/be-rBY/index.md Normal file
View File

@@ -0,0 +1,30 @@
---
title: Home
layout: default
nav_order: 0
---
# Meshtastic Android App Documentation
User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform).
Use the sidebar navigation to browse the **User Guide** for app features and the **Developer Guide** for contributing to the project.
---
## Quick Links
| Guide | Апісанне |
| --------------------------------------------------------------------- | -------------------------------------------------------------- |
| [Getting Started](user/onboarding) | Connect your first radio and send a message |
| [Messages & Channels](user/messages-and-channels) | Channel broadcasts, direct messages, reactions, and encryption |
| [Nodes](user/nodes) | Understanding the mesh network node list |
| [Signal Meter](user/signal-meter) | How the LoRa signal quality meter works |
| [Units & Locale](user/units-and-locale) | How temperatures, distances, and times adapt to your region |
| [Desktop App](user/desktop) | Linux, macOS, and Windows desktop usage |
| [Architecture](developer/architecture) | App architecture overview for contributors |
| [Contributing](developer/contributing) | Branch naming, PR workflow, and verification commands |
---
> This documentation is served from the same markdown source that powers the in-app **Help & Documentation** browser.

125
docs/be-rBY/user/connections.md Normal file
View File

@@ -0,0 +1,125 @@
---
title: Connections
nav_order: 2
last_updated: 2026-05-13
description: Connect your phone or desktop to a Meshtastic radio via Bluetooth, USB, or TCP/IP.
aliases:
- bluetooth
- usb
- tcp
- pairing
---
# Connections
Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node.
## Bluetooth (BLE)
Bluetooth Low Energy is the default and most common connection method on Android.
### Pairing a Device
1. Ensure your Meshtastic radio is powered on and in pairing mode.
2. Open the app and navigate to **Connections**.
3. Tap **Scan for Devices** — nearby Meshtastic radios will appear.
4. Select your device from the list.
5. Accept the Bluetooth pairing prompt if shown.
![Device list item](/assets/screenshots/connections_bluetooth_scan.png)
You can filter devices by transport type using the filter chips at the top:
![Transport filter chips](/assets/screenshots/connections_transport_filters.png)
> 💡 **Tip:** If your device doesn't appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device.
### Connection Status
| Icon | State | Апісанне |
| ---- | -------------- | ----------------------------- |
| 🟢 | Злучаны | Active radio link established |
| 🟡 | Злучаемся | Handshake in progress |
| 🔴 | Адлучана | No active connection |
| ⚪ | Not configured | No device selected |
When connecting, a status indicator shows the current connection state:
![Connecting status](/assets/screenshots/connections_connecting.png)
If no devices are found, the app shows an empty state with instructions:
![No devices found](/assets/screenshots/connections_empty_state.png)
### Troubleshooting Bluetooth
- **Device not found:** Toggle Bluetooth off/on, ensure location is enabled.
- **Connection drops:** Move closer to the radio; check for interference.
- **Pairing rejected:** Forget the device in Android Bluetooth settings and retry.
## USB Serial
USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable.
### Setup
1. Connect your radio via USB cable to your device.
2. The app will prompt for USB permission — tap **Allow**.
3. The connection is established automatically.
> ⚠️ **Note:** USB connections require OTG support on Android devices.
## TCP/IP (WiFi)
Some Meshtastic radios support WiFi connectivity, allowing TCP-based connections.
### Конфигурация
1. Connect your radio to a WiFi network via the radio's web interface or settings.
2. In the app, go to **Connections → TCP**.
3. Enter the radio's IP address and port (default: 4403).
4. Tap **Connect**.
![WiFi scanning for devices](/assets/screenshots/connections_wifi_scanning.png)
When a device is found, it appears in the connection list:
![WiFi device found](/assets/screenshots/connections_wifi_device_found.png)
A successful connection is confirmed with a status indicator:
![WiFi connection success](/assets/screenshots/connections_wifi_success.png)
### When to Use TCP
- Radio is on the same local network
- Testing with a simulated radio
- Environments where Bluetooth has interference issues
## Reconnection Behavior
The app reconnects to the **last selected device** on startup. You can manually switch transports from the connections screen at any time.
To disconnect from a radio, use the disconnect button on the connections screen:
![Disconnect from radio](/assets/screenshots/connections_disconnect.png)
## Desktop Connections
On Desktop (Linux/macOS/Windows), the app supports:
- **Bluetooth (BLE)** — via the Kable library; works on macOS, Linux, and Windows
- **USB Serial** — primary wired connection method
- **TCP/IP** — for network-connected radios
See [Desktop App](desktop) for platform-specific details and keyboard shortcuts.
## Related Topics
- [Getting Started](onboarding) — first-launch setup and permissions
- [Settings — Radio & User](settings-radio-user) — Bluetooth and network configuration
- [Desktop App](desktop) — desktop-specific connection details
- [Supported devices](https://meshtastic.org/docs/hardware/devices) — full list of compatible radios on meshtastic.org
---

147
docs/be-rBY/user/desktop.md Normal file
View File

@@ -0,0 +1,147 @@
---
title: Desktop App
nav_order: 14
last_updated: 2026-05-13
description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts.
aliases:
- desktop
- linux
- macos
- windows
- jvm
---
# Desktop App
The Meshtastic Desktop application provides the same mesh communication features on Linux, macOS, and Windows.
## Абзор
The Desktop app shares its core codebase with the Android app through Kotlin Multiplatform (KMP). Most features work identically across platforms.
## Установка
### Linux
- Download the `.deb` or `.AppImage` package from the releases page
- Or build from source using `./gradlew :desktopApp:run`
### macOS
- Download the `.dmg` package from releases
- Or build from source
### Windows
- Download the `.msi` installer from releases
- Or build from source
## Connecting Your Radio
### USB Serial (Primary)
The most reliable connection method on Desktop:
1. Connect your Meshtastic radio via USB cable.
2. The app should detect the serial port automatically.
3. If not detected, select the correct serial port from the connections menu.
### TCP/IP
For network-connected radios:
1. Enter the radio's IP address and port (default: 4403).
2. Click **Connect**.
### Bluetooth (BLE)
Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/JuulLabs/kable) library:
1. Ensure your system has a Bluetooth adapter.
2. The app scans for nearby Meshtastic radios automatically.
3. Select your device from the connections screen.
## Feature Parity
| Feature | Android | Desktop | Notes |
| ---------------------------------------- | ------- | ------- | -------------------------- |
| Messaging | ✓ | ✓ | Full parity |
| Node List | ✓ | ✓ | Full parity |
| Map | ✓ | ✓ | Full parity |
| Налады | ✓ | ✓ | Full parity |
| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop |
| Firmware Update OTA | ✓ | ✗ | Use web flasher |
| Notifications | ✓ | ✓ | Native OS notifications |
| Widgets | ✓ | ✗ | Android-only |
| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only |
\*Chirpy AI requires Android 14+ on Google flavor builds with supported hardware.
## UI Differences
The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction.
### Keyboard Shortcuts
| Shortcut | Action |
| ------------------- | --------------------------- |
| **⌘Q** / **Ctrl+Q** | Quit the application |
| **⌘,** / **Ctrl+,** | Open Settings |
| **⌘1** / **Ctrl+1** | Switch to Conversations tab |
| **⌘2** / **Ctrl+2** | Switch to Nodes tab |
| **⌘3** / **Ctrl+3** | Switch to Map tab |
| **⌘4** / **Ctrl+4** | Switch to Connections tab |
### Window & System Tray
- **Window resizing** — responsive layout adapts to window dimensions
- **System tray** — minimize to system tray for background mesh operation
- **Tray menu** — right-click the tray icon to show window or quit
- **Mouse interaction** — hover states and standard desktop navigation
### Notification Preferences
The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from **Settings → Notifications** within the app.
## Built-in Documentation Browser
The Desktop app includes a built-in documentation browser for quick access to help content without leaving the application.
![Docs browser with table of contents](/assets/screenshots/docs-browser_toc.png)
The browser supports full-text search across all documentation:
![Searching the docs browser](/assets/screenshots/docs-browser_search.png)
Individual doc pages render with full formatting:
![A documentation page](/assets/screenshots/docs-browser_page.png)
## Building from Source
```bash
git clone https://github.com/meshtastic/Meshtastic-Android.git
cd Meshtastic-Android
git submodule update --init
./gradlew :desktopApp:run
```
Requirements:
- JDK 21
- No Android SDK required for desktop-only builds
## Known Limitations
- No OTA firmware updates (use web flasher)
- Some Android-specific features (widgets, specific notification channels) are unavailable
- Performance may vary on low-spec hardware running Compose Desktop
- BLE bonding is not yet supported on desktop (pairing works without bonding)
## Related Topics
- [Connections](connections) — connection methods overview
- [Firmware Updates](firmware) — use the [Web Flasher](https://flasher.meshtastic.org) for desktop firmware updates
---

114
docs/be-rBY/user/discovery.md Normal file
View File

@@ -0,0 +1,114 @@
---
title: Discovery
nav_order: 12
last_updated: 2026-05-13
description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools.
aliases:
- mesh-discovery
- local-discovery
- network-scan
- traceroute
- neighbor-info
---
# Discovery
Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist.
> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens.
---
## Traceroute
Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It's the single most useful tool for debugging connectivity problems.
### Running a Traceroute
1. Navigate to **Nodes** and tap the node you want to trace.
2. On the node detail screen, tap **Traceroute**.
3. The app sends a traceroute request and waits for the response.
4. Results display each hop in order, with signal quality at every step.
### Reading the Results
A traceroute result looks like this:
```
You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target
```
Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment.
| What to look for | What it means |
| -------------------------------------------------------------------------- | --------------------------------------------------------------------------- |
| All hops show Good SNR (> 5 dB) | Healthy path — messages flow reliably |
| One hop shows Bad SNR (< 0 dB) | Weak link — this relay segment is fragile |
| Many hops (4+) | Long path — consider repositioning a node to shorten it |
| Different path on retry | Mesh is adapting — multiple routes exist (this is good!) |
> 💡 **Tip:** Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.
### Troubleshooting with Traceroute
- **"No route found"** — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
- **Traceroute times out** — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in **Settings → LoRa Config**.
- **Asymmetric paths** — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric.
---
## Neighbor Info
The Neighbor Info module lets each node broadcast a list of the nodes it can **directly hear** (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.
### Enabling Neighbor Info
1. Navigate to **Settings → Module Config → Neighbor Info**.
2. Enable the module.
3. Set the broadcast interval (default: 900 seconds / 15 minutes).
Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same.
### Viewing Neighbor Data
- Open any node's detail screen and look for the **Neighbors** section.
- Each neighbor entry shows the node that was directly heard and its signal quality.
- Combine neighbor data from multiple nodes to understand the full mesh topology.
> ⚠️ **Note:** Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion.
---
## Node List as a Discovery Tool
The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.
### Finding New Nodes
- Sort by **Last heard** to see the most recently active nodes at the top.
- Enable **Include unknown** to see nodes that have appeared on the mesh but haven't sent user info yet — these are often newly powered-on devices.
### Assessing Connectivity
- Sort by **Hops away** to see which nodes are directly reachable (0 hops) versus relayed.
- Sort by **Distance** to find nearby nodes and verify they're reachable.
- Use **Exclude MQTT** to focus on nodes reachable over radio (not via internet bridge).
### Infrastructure Audit
- Disable **Exclude infrastructure** to see Router, Repeater, Router Late, and Client Base nodes.
- Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.
See [Nodes](nodes) for full details on filtering and sorting options.
---
## Tips for Mesh Exploration
- **Start with traceroute** — it gives you immediate, actionable information about a specific path.
- **Enable Neighbor Info on key nodes** — especially routers and repeaters, to build a picture of the backbone.
- **Check the map** — node positions on the [Map](map-and-waypoints) combined with signal data help you understand why some links are strong and others are weak.
- **Compare signal over time** — use the [Signal Meter](signal-meter) guide to interpret SNR and RSSI values correctly.
---

114
docs/be-rBY/user/firmware.md Normal file
View File

@@ -0,0 +1,114 @@
---
title: Firmware Updates
nav_order: 13
last_updated: 2026-05-13
description: Update your radio firmware over Bluetooth — OTA process, version channels, pre-flight checks, and recovery.
aliases:
- firmware
- update
- ota
- flash
---
# Firmware Updates
Keep your Meshtastic radio up to date with the latest firmware for new features, bug fixes, and security improvements.
## Checking for Updates
1. Navigate to **Settings → Firmware Update** or tap the firmware notification if shown.
2. The app checks for available firmware versions.
3. Available updates show the version number and changelog summary.
## Update Methods
### OTA (Over-The-Air) via Bluetooth
The most common update method for Android users:
1. Ensure your radio is connected via Bluetooth.
2. Navigate to the Firmware Update screen.
3. Select the desired firmware version.
4. Tap **Update** to begin the OTA process.
5. Wait for the update to complete — **do not disconnect** during the update.
![Firmware checking for updates](/assets/screenshots/firmware_checking.png)
> ⚠️ **Warning:** Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process.
![Firmware disclaimer](/assets/screenshots/firmware_disclaimer.png)
### USB Flashing
For recovery or when OTA is unavailable:
- Use the [Meshtastic Web Flasher](https://flasher.meshtastic.org)
- Or the [Meshtastic CLI tool](https://meshtastic.org/docs/getting-started/flashing-firmware) on desktop
## Version Channels
| Канал | Апісанне |
| ------ | ------------------------------------------- |
| Stable | Recommended for most users; tested releases |
| Alpha | Preview releases; may contain bugs |
## Pre-Update Checklist
Before updating:
- [ ] Battery > 50%
- [ ] Stable Bluetooth connection
- [ ] Note your current settings (they may reset on major version changes)
- [ ] Check the release notes for breaking changes
## Post-Update
After a successful update:
- The radio will reboot automatically
- Bluetooth connection will re-establish
- Verify your settings are intact
- Check the firmware version in **Settings → About**
![Firmware update success](/assets/screenshots/firmware_success.png)
## Troubleshooting
### Update Stuck
If the update appears frozen:
- Wait at least 5 minutes before intervening
- If truly stuck, power-cycle the radio
- Attempt the update again
![Firmware update error](/assets/screenshots/firmware_error.png)
### Device Won't Boot After Update
If your device fails to boot:
1. Try connecting via USB to a computer
2. Use the web flasher in recovery/DFU mode
3. Flash a known-good firmware version
4. Check the Meshtastic Discord for device-specific recovery steps
### Compatibility Warnings
The app may show warnings when:
- Connected radio firmware is below minimum supported version
- Major version mismatch between app and firmware
- Deprecated features need migration
> ⚠️ **Important:** Always update the Meshtastic app before or alongside firmware updates to ensure compatibility.
## Related Topics
- [Connections](connections) — reconnecting after a firmware update
- [Flashing firmware guide](https://meshtastic.org/docs/getting-started/flashing-firmware) — full firmware flashing walkthrough on meshtastic.org
- [Supported devices](https://meshtastic.org/docs/hardware/devices) — check firmware compatibility by device
- [FAQ](https://meshtastic.org/docs/about/faq) — common questions on meshtastic.org
---

116
docs/be-rBY/user/map-and-waypoints.md Normal file
View File

@@ -0,0 +1,116 @@
---
title: Map & Waypoints
nav_order: 6
last_updated: 2026-05-13
description: View node positions on the map, create and share waypoints, and manage position sharing and privacy.
aliases:
- map
- waypoints
- gps
- location
---
# Map & Waypoints
The Map screen shows the geographic positions of nodes on your mesh, along with shared waypoints.
## Map View
The map displays:
- **Node positions** — colored markers for each node reporting location
- **Waypoints** — shared points of interest
- **Your position** — your current GPS location
### Node Markers
Node markers on the map indicate:
| Color | Meaning |
| ------ | ---------------------------------------------- |
| Зялёны | Online (heard recently) |
| Yellow | Away (heard within 2 hours) |
| Gray | Offline (stale position) |
| Сіні | Your own node |
### Map Controls
- **Zoom** — pinch or use +/- buttons
- **Pan** — drag to explore
- **Center** — select the location button to center on your position
- **Node tap** — tap a node marker to view details
The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position.
![Map controls overlay](/assets/screenshots/map_controls_overlay.png)
## Waypoints
Waypoints are shared geographic points of interest that all mesh members can see.
### Creating a Waypoint
1. Long-press on the map at the desired location.
2. Enter a name and optional description.
3. Choose an icon/emoji for the waypoint.
4. Tap **Send** to share with the mesh.
### Waypoint Properties
| Property | Апісанне |
| ---------- | ------------------------------------------------------- |
| Назва | Short identifier (max 30 characters) |
| Апісанне | Optional longer description |
| Icon | Visual marker emoji on the map |
| Locked | If locked, only the creator can edit or delete |
| Expiration | Optional auto-remove time |
### Waypoint Expiration
Waypoints can be set to expire automatically:
- **Never** (default) — waypoint remains until manually deleted
- **Timed** — waypoint is automatically removed after the specified duration (e.g., "remove after 2 hours"). Useful for temporary markers like rally points, hazards, or meeting locations.
Expired waypoints are automatically hidden from the map so they don't clutter the display. The expiration countdown begins when the waypoint is created, not when other nodes receive it.
### Managing Waypoints
- Tap a waypoint on the map to view its details and coordinates
- Edit or delete waypoints you created
- **Locked waypoints** cannot be modified or deleted by other nodes — only the original creator can change them
- Unlocked waypoints can be edited by any mesh member
## Position Sharing
### Enabling Position Sharing
Your node shares its GPS position based on:
- **Fixed interval** — broadcast position at regular intervals
- **Smart position** — broadcast when movement exceeds a threshold
- **Manual** — only share when explicitly requested
Configure position behavior in **Settings → Position**.
### Privacy Considerations
> 🔒 **Privacy:** Position data is broadcast to all nodes on your channel. If you don't want your location shared, disable GPS position in settings or use a fixed/fake position.
## Map Sources
The app supports multiple map tile sources:
- OpenStreetMap (default)
- Satellite imagery (where available)
- Offline tiles (download map areas for offline use)
## Related Topics
- [Nodes](nodes) — view and filter your node list
- [Node Metrics](node-metrics) — signal quality and position history for individual nodes
- [Discovery](discovery) — traceroute and neighbor info for understanding mesh topology
- [Units & Locale](units-and-locale) — distance and coordinate display formats
---

159
docs/be-rBY/user/messages-and-channels.md Normal file
View File

@@ -0,0 +1,159 @@
---
title: Messages & Channels
nav_order: 3
last_updated: 2026-05-13
description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions.
aliases:
- channels
- direct-messages
- messaging
- conversations
---
# Messages & Channels
Meshtastic supports two communication modes: **channel broadcasts** and **direct messages**.
## Каналы
Channels are shared communication groups. All nodes configured with the same channel key can read and send messages on that channel.
### Default Channel
Every Meshtastic device comes with a default **LongFast** channel. This is an unencrypted channel used for general mesh communication.
### Channel Security
Channels support multiple encryption levels:
| Icon | Security Level | Апісанне |
| ---- | ------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------- |
| 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. |
| 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. |
| 🔓 | Default / Open | Uses the well-known default key. **Any Meshtastic device** on the same preset can read these messages. |
| ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. |
> 🔒 **Security Tip:** Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive.
### Adding a Channel
1. Navigate to **Settings → Channels**.
2. Tap **Add Channel** or scan a QR code.
3. Configure the channel name and encryption key.
4. Share the channel URL/QR code with others who need access.
Tapping a channel shows its details and sharing options.
## Direct Messages
Direct messages (DMs) are point-to-point encrypted communications between two specific nodes.
### Sending a Direct Message
1. Open the **Messages** tab.
2. Select a node from your contacts list or tap a node in the node list.
3. Type your message and tap **Send**.
### Message States
| State | Icon | Meaning |
| --------------------------------- | ---- | ----------------------------------------------------------------------------------------------------------------- |
| Queued | ⏳ | Message waiting to be sent |
| En route | ✓ | Delivered to the radio, awaiting acknowledgment |
| Delivered | ✓✓ | Acknowledgment received from recipient |
| Received | ✓ | Message received from the mesh (incoming) |
| S&F Routing | 🔗 | Store & Forward: message being routed through an S&F node |
| S&F Confirmed | 🔗 | Store & Forward: delivery confirmed via S&F node |
| Памылка | ✗ | Delivery failed after retries |
### Delivery Errors
When a message fails to deliver, the error indicator shows what went wrong:
| Памылка | Meaning | What to Do |
| --------------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
| Скончыўся час чакання | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
| Няма інтэрфейсу | No radio interface available to send | Check that your radio is connected and the channel is configured. |
| Max Retransmit | All retry attempts exhausted | The mesh path is unreliable. Try a different channel or wait for conditions to improve. |
| Няма канала | The destination channel doesn't exist | Verify both nodes share the same channel configuration. |
| Too Large | Message exceeds maximum payload size | Shorten your message (max ~230 characters). |
| No Response | Node received message but didn't respond | The recipient's radio may be busy or in low-power sleep mode. |
| Duty Cycle Limit | Regional airtime limit reached | Your radio has used its allowed transmit time. Wait for the duty cycle window to reset (typically 1 hour in EU regions). |
| Няправільны запыт | Malformed or invalid message | This usually indicates a software bug. Try restarting the app. |
> 💡 **Tip:** Most delivery errors resolve themselves. If a node is intermittently reachable, the mesh will retry. For persistent "No Route" errors, check that intermediate Router nodes are online.
## Message Features
### Quick Chat
Pre-configured messages for rapid communication:
- Access via the Quick Chat button in the message input area
- Choose from built-in phrases or custom messages
- Customize quick chat messages in **Settings → Quick Chat**
- Useful when typing is impractical (gloves, small screen, urgent)
![Quick chat option](/assets/screenshots/messages_quick_chat.png)
The channel list shows each channel with its latest message preview.
### Message Bubbles
Messages appear as chat bubbles — sent messages on the right, received messages on the left. Each bubble shows the sender, timestamp, and delivery status. Messages with replies include a quoted preview of the original message above the response.
### Reactions
React to messages with emoji:
- **Long-press** a message to open the actions menu
- Tap **Add Reaction** to choose an emoji
- Reactions appear below the message bubble
- Multiple users can react to the same message
- React to your own messages or others' messages
![Emoji reaction badges displayed beneath a message](/assets/screenshots/messages_reaction.png)
> 💡 **Tip:** Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages.
### Message Actions
Long-press any message to access:
- **Copy** — copy message text to clipboard
- **Reply** — quote the message in your response
- **React** — add an emoji reaction
- **Delete** — remove a message you sent (local deletion)
### Message Priority
Messages are queued and transmitted based on priority:
1. Emergency/alert messages (highest)
2. Direct messages
3. Channel broadcasts (lowest)
### Message Limits
- **Maximum length:** 237 bytes (approximately 230 characters for ASCII text)
- **Rate limiting:** The mesh enforces airtime fairness; heavy message volume may be throttled
- **Delivery:** Messages are retried automatically if no acknowledgment is received
## Best Practices
- Use channels for group coordination
- Use direct messages for private person-to-person communication
- Keep messages short — mesh bandwidth is limited
- Configure encryption for sensitive communications
## Related Topics
- [Nodes](nodes) — tap a node to start a direct message
- [Settings — Radio & User](settings-radio-user) — configure channel encryption and presets
- [MQTT](mqtt) — bridge channel messages to the internet
- [Channel configuration](https://meshtastic.org/docs/configuration/radio/channels) — detailed channel settings on meshtastic.org
---

137
docs/be-rBY/user/mqtt.md Normal file
View File

@@ -0,0 +1,137 @@
---
title: MQTT
nav_order: 11
last_updated: 2026-05-13
description: Bridge your mesh to the internet — MQTT broker setup, encryption layers, and map reporting.
aliases:
- mqtt
- internet-bridge
- broker
---
# MQTT
MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range.
## Абзор
The MQTT module connects your node to an MQTT broker, allowing:
- Messages to reach nodes on different physical meshes via the internet
- Integration with home automation and monitoring systems
- Publishing node positions to the public Meshtastic map
- Custom data pipelines for logging and alerting
## How It Works
```
[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
```
A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.
## Конфигурация
### Enabling MQTT
1. Navigate to **Settings → Module Config → MQTT**.
2. Enable the MQTT module.
3. Configure the broker connection:
![MQTT toggle switch](/assets/screenshots/settings_switch.png)
| Setting | Апісанне | Default |
| ----------------- | --------------------------------------------------------------------------------------------- | --------------------------------------------------- |
| Server Address | MQTT broker hostname | mqtt.meshtastic.org |
| Імя карыстальніка | Broker authentication | meshdev |
| Пароль | Broker authentication | large4cats |
| Root Topic | Base topic for messages | msh |
| Шифравание | Encrypt MQTT payload | Уключана |
| ~~JSON Output~~ | ⚠️ **Deprecated** — JSON packet support has been removed from firmware; this field is ignored | Disabled |
| TLS | Secure connection to broker | Disabled |
| Map Reporting | Report position to public map | Disabled |
### Default Meshtastic Broker
The community maintains a public broker at `mqtt.meshtastic.org`. This is intended for general use and testing.
> 🔒 **Privacy:** Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.
### Private Broker
For better privacy and control, you can run your own MQTT broker:
- Mosquitto (lightweight, open-source)
- HiveMQ
- EMQX
Configure your node to point to your private broker with appropriate credentials.
## Map Reporting
When Map Reporting is enabled, your node publishes its position to the Meshtastic community map:
- Visible at [meshmap.net](https://meshmap.net) and similar community map services
- Only position and node info are shared
- Disable this if you don't want your location publicly visible
## Uplink vs Downlink
| Direction | Апісанне |
| ------------ | -------------------------------- |
| **Uplink** | Messages from mesh → MQTT broker |
| **Downlink** | Messages from MQTT broker → mesh |
Configure per-channel which directions are active to control message flow and airtime usage.
## Message Formats
MQTT uses protobuf message format:
| Format | Апісанне | Use case |
| ------------ | ----------------------------------- | -------------------------- |
| **Protobuf** | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging |
> ⚠️ **Note:** JSON output support was removed from firmware. The `json_enabled` setting is still visible in the app for legacy compatibility but has no effect on current firmware versions.
## Encryption & Privacy
Understanding the layered encryption model:
1. **Channel encryption** happens on the mesh _before_ MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
2. **MQTT encryption** (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information.
3. **TLS** encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.
> 🔒 **Important:** The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively **unencrypted** — anyone can decode them. Always use a custom PSK for private communications.
## Best Practices
- Use channel-level encryption (PSK) on channels that bridge to MQTT
- Don't enable MQTT on nodes without internet access (it will buffer and waste memory)
- Use a private broker for sensitive deployments
- Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
- Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back
## Troubleshooting
### MQTT Not Connecting
- **Check WiFi** — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself.
- **Verify credentials** — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces.
- **Firewall** — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports.
- **DNS resolution** — if using a custom broker hostname, verify the node can resolve it. Try the broker's IP address directly.
### Messages Not Bridging
- **Check uplink/downlink settings** — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
- **Channel mismatch** — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
- **Topic mismatch** — ensure both gateways use the same root topic. The default `msh` works for the public broker.
## Related Topics
- [Settings — Modules & Admin](settings-module-admin) — MQTT module configuration reference
- [Messages & Channels](messages-and-channels) — channel encryption and PSK setup
- [MQTT integration guide](https://meshtastic.org/docs/software/integrations/mqtt) — detailed MQTT documentation on meshtastic.org
---

130
docs/be-rBY/user/node-metrics.md Normal file
View File

@@ -0,0 +1,130 @@
---
title: Node Metrics
nav_order: 5
last_updated: 2026-05-13
description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history.
aliases:
- metrics
- telemetry
- device-metrics
- signal
---
# Node Metrics
The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.
## Device Metrics
Basic operating information reported by each node:
| Metric | Апісанне |
| ------------------- | ----------------------------------- |
| Battery Level | Current battery percentage |
| Voltage | Battery voltage reading |
| Channel Utilization | Percentage of airtime consumed |
| Airtime | Transmission time used by this node |
| Uptime | Time since last reboot |
Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time.
> 💡 **Tip:** Tap any metric card to expand it into a full chart with historical data points. Pinch to zoom the time axis.
## Environment Metrics
Environmental sensor data (requires compatible hardware):
| Metric | Sensor Examples |
| ------------------------------------ | --------------------- |
| Тэмпература | BME280, BME680, SHT31 |
| Вільготнасць | BME280, BME680, SHT31 |
| Barometric Pressure | BME280, BMP280 |
| Gas Resistance | BME680 |
| IAQ (Air Quality) | BME680 |
Environment metrics are charted over time for easy trend analysis — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.
> 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors.
## Signal Metrics
Radio signal quality information:
| Metric | Апісанне |
| ------------------- | ----------------------------------------------------------------------------- |
| сігнал-шум | Signal-to-Noise Ratio (higher is better) |
| адносная магутнасць | Received Signal Strength Indicator (closer to 0 is better) |
| Hop Count | Number of mesh hops for last message |
### Signal Quality Reference
| SNR Range | Quality |
| --------------------------------- | --------- |
| > 10 dB | Excellent |
| 0 to 10 dB | Good |
| -10 to 0 dB | Fair |
| < -10 dB | Poor |
## Power Metrics
Power management telemetry (requires INA sensor or compatible hardware):
| Metric | Апісанне |
| ----------- | ----------------------- |
| Bus Voltage | Supply voltage |
| 3 | Power draw in milliamps |
| Power | Calculated wattage |
## Traceroute
Traceroute shows the path a message takes through the mesh:
1. From the node detail screen, tap **Traceroute**.
2. The app sends a traceroute request to the target node.
3. Results show each hop with SNR/RSSI values.
### Reading Traceroute Results
```
You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target
```
Each hop represents a relay node that forwarded the message.
## Гісторыя месцазнаходжання
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.
## Viewing Metrics
1. Navigate to **Nodes**.
2. Tap the node you want to inspect.
3. Select the metric category from the detail tabs.
![Node detail — local device](/assets/screenshots/nodes_detail_local.png)
The position tab shows location data for nodes that share GPS:
![Position inline content](/assets/screenshots/nodes_position.png)
> ⚠️ **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.
## Related Topics
- [Nodes](nodes) — node list, filtering, and sorting
- [Telemetry & Sensors](telemetry-and-sensors) — supported sensors and configuration
- [Signal Meter](signal-meter) — how signal quality is calculated from SNR and RSSI
- [Discovery](discovery) — traceroute details and neighbor info
- [Units & Locale](units-and-locale) — temperature, distance, and speed display formats
---

152
docs/be-rBY/user/nodes.md Normal file
View File

@@ -0,0 +1,152 @@
---
title: Nodes
nav_order: 4
last_updated: 2026-05-13
description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions.
aliases:
- node-list
- mesh-nodes
- peers
---
# Nodes
The Nodes screen displays all devices visible on your mesh network.
## 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** — last heard signal strength
- **Last heard** — time since last communication
- **Distance** — estimated distance (if positions are shared)
- **Battery** — remote node battery level (if telemetry is enabled)
### Node Status Indicators
| Badge | Meaning |
| ---------- | ------------------------------------- |
| 🟢 Online | Node heard within the last 15 minutes |
| 🟡 Away | Node heard within the last 2 hours |
| 🔴 Offline | Node not heard for over 2 hours |
| ⭐ Favorite | Node marked as favorite by the user |
### Node Roles
Nodes can be configured with different roles that affect their mesh behavior:
| Role | Апісанне |
| -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| CLIENT | Standard end-user device |
| 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 & Found | Continuous position beacon for recovery |
### 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 devices.
- **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 devices or to reduce congestion in dense areas.
- **Tracker** — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
- **Sensor** — An unattended device 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](tak) for details.
> 💡 **Tip:** The mesh works best when most nodes are **Client** or **Router**. Too many Mute nodes reduces 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 | Communication uses shared channel PSK — encrypted but identity not individually verified |
| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) |
> 💡 **Tip:** PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised.
## Quick Actions
From the node list, you can:
- **Tap** a node to view its detail page
- **Long-press** for quick actions:
- Send a direct message
- View on map
- Request position
- Mark as favorite
- Traceroute
## Filtering & Sorting
### Text Search
Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.
### Filter Toggles
| Фільтраваць | Апісанне |
| -------------------------- | ---------------------------------------------------------------------------------------------- |
| **Only online** | Show only nodes heard within the last 15 minutes |
| **Only direct** | Show only nodes with direct (non-relayed) connections |
| **Include unknown** | Show nodes that haven't sent user info yet |
| **Exclude infrastructure** | Hide infrastructure-role nodes (Router, Repeater, Router Late, Client Base) |
| **Exclude MQTT** | Hide nodes heard only via MQTT internet bridge |
| **Show ignored** | Show nodes you've previously dismissed or muted |
### Sort Options
| Sort | Апісанне |
| ------------------------------------------- | ------------------------------------------------------------------ |
| **Last heard** (default) | Most recently heard nodes first |
| **Alphabetical** | 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 |
| **Favorites** | Favorited nodes first |
## Node Detail
Tapping a node opens the detail view with comprehensive information. See [Node Metrics](node-metrics) for full details on metrics and telemetry.
![Node detail view](/assets/screenshots/nodes_node_list.png)
The detail screen includes device info, position, and action buttons:
![Node detail section](/assets/screenshots/nodes_detail_section.png)
Inline status indicators show key metrics at a glance:
| Indicator | Screenshot |
| ----------------- | -------------------------------------------------------- |
| Signal quality | ![Signal](/assets/screenshots/nodes_signal_info.png) |
| Battery level | ![Battery](/assets/screenshots/nodes_battery_info.png) |
| Hop count | ![Hops](/assets/screenshots/nodes_hops_info.png) |
| Апошні раз пачуты | ![Last heard](/assets/screenshots/nodes_last_heard.png) |
| Адлегласць | ![Distance](/assets/screenshots/nodes_distance_info.png) |
## Related Topics
- [Node Metrics](node-metrics) — detailed telemetry dashboards for each node
- [Messages & Channels](messages-and-channels) — send a direct message to a node
- [Map & Waypoints](map-and-waypoints) — view node positions geographically
- [Discovery](discovery) — traceroute and neighbor info for topology exploration
- [Signal Meter](signal-meter) — understand what the signal bars mean
---

99
docs/be-rBY/user/onboarding.md Normal file
View File

@@ -0,0 +1,99 @@
---
title: Начало работы
nav_order: 1
last_updated: 2026-05-13
description: First-launch setup — permissions, onboarding flow, and next steps after connecting your radio.
aliases:
- first-launch
- setup
- intro
---
# Начало работы
Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app.
## First Launch
When you open the app for the first time, you'll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings.
### Welcome Screen
The welcome screen introduces Meshtastic and its core capabilities:
- Off-grid mesh communication
- No cellular or internet required
- End-to-end encrypted messaging
Tap **Get Started** to proceed through the setup flow.
![Welcome screen](/assets/screenshots/onboarding_welcome.png)
## Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
### Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio:
- **Bluetooth scanning** — discover nearby Meshtastic radios
- **Bluetooth connect** — establish and maintain connections with paired radios
Grant both permissions when prompted. Without Bluetooth, you'll need to use USB or TCP connections instead.
### Location Permission
> ⚠️ **Why is location required for Bluetooth?** Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice.
Meshtastic also uses your location for:
- Showing your position on the mesh map
- Calculating distances to other nodes
- Sharing your GPS coordinates with other mesh members (if enabled)
Grant **"While using the app"** or **"Always"** depending on your preference:
- **While using the app** — position updates only when the app is open
- **Always** — enables background position updates for always-on mesh presence
If denied, Bluetooth scanning will not function and your node will not report a position.
### Notifications Permission
Notifications alert you to:
- Incoming messages from channels and direct messages
- Connection status changes (connected, disconnected, reconnecting)
- Firmware update availability
> 💡 **Tip:** You can fine-tune notification preferences later in Android system settings. The app creates separate notification channels for messages, connection events, and background service status.
### Critical Alerts Permission
On supported devices, the app may request permission for critical alerts:
- These are high-priority notifications that can break through Do Not Disturb mode
- Useful for emergency mesh alerts or urgent messages
- You can **skip** this step if you don't need breakthrough notifications
- Configure or revoke later in Android notification settings
## After Setup
Once permissions are granted, the app transitions to the main interface. Your first action should be connecting to a Meshtastic radio — see [Connections](connections) for detailed instructions.
> 💡 **Tip:** If you skipped any permissions during setup, you can grant them later through **Android Settings → Apps → Meshtastic → Permissions**. The app will prompt you again if a missing permission blocks a feature you try to use.
## What's Next?
Once connected to a radio, explore:
- [Connections](connections) — pair your first radio device
- [Messages & Channels](messages-and-channels) — send your first message
- [Nodes](nodes) — see who's on your mesh
- [Map & Waypoints](map-and-waypoints) — view node positions
- [Settings](settings-radio-user) — configure your radio and user profile
New to Meshtastic? The [getting started guide](https://meshtastic.org/docs/getting-started) on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
---

246
docs/be-rBY/user/settings-module-admin.md Normal file
View File

@@ -0,0 +1,246 @@
---
title: Settings — Modules & Admin
nav_order: 8
last_updated: 2026-05-13
description: Configure optional feature modules (MQTT, telemetry, canned messages, TAK, and more) and perform device administration.
aliases:
- modules
- module-config
- administration
---
# Settings — Modules & Admin
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
> 💡 **Tip:** You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
![Toggle switch](/assets/screenshots/settings_switch.png)
![Dropdown selector](/assets/screenshots/settings_dropdown.png)
![Text field](/assets/screenshots/settings_text_field.png)
![Settings card layout](/assets/screenshots/settings_titled_card.png)
## Module Configuration
### MQTT Module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems.
| Setting | Апісанне |
| ----------------- | ------------------------------------------------------------------------ |
| Уключана | Toggle MQTT bridge |
| Сервер | MQTT broker address |
| Імя карыстальніка | Authentication username |
| Пароль | Authentication password |
| Шифравание | Encrypt MQTT payloads |
| ~~JSON Output~~ | ⚠️ **Deprecated** — JSON support removed from firmware; field is ignored |
| TLS | Use secure connection |
| Root Topic | Base MQTT topic path |
| Map Report | Publish position for public map |
See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup.
### Serial Module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node's serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
| Setting | Апісанне |
| ---------- | ------------------------------- |
| Уключана | Activate serial communication |
| Echo | Echo received serial data back |
| Mode | Text, Protobuf, or NMEA output |
| RX/TX Pins | GPIO pins for serial connection |
| Baud Rate | Serial communication speed |
### External Notification Module
Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
| Setting | Апісанне |
| -------------------------------- | --------------------------- |
| Уключана | Activate notifications |
| Alert Message | Notify on incoming messages |
| Alert Message Buzzer | Use buzzer for messages |
| Alert Message Vibra | Use vibration for messages |
| Alert Bell | Notify on bell character |
| Output (GPIO) | Pin for notification output |
| Active | High or Low active |
| Duration (ms) | Notification length |
| Use I2S as Buzzer | Use I2S audio output |
### Store & Forward Module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren't lost during brief disconnections.
| Setting | Апісанне |
| ------------------------------------------ | -------------------------- |
| Уключана | Activate store and forward |
| Heartbeat (s) | Announcement interval |
| Records | Maximum stored messages |
| History Return (max) | Max messages to replay |
| History Return (window) | Time window for replay |
> 💡 **Tip:** Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they're typically always-on.
### Range Test Module
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
| Setting | Апісанне |
| -------------------------------------- | --------------------------------- |
| Уключана | Activate range testing |
| Sender Interval (s) | Time between test transmissions |
| Save CSV | Log received test data to SD card |
### Telemetry Module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
| Setting | Апісанне |
| ---------------------------- | --------------------------------------- |
| Device Metrics Interval | How often to report device metrics |
| Environment Metrics Interval | How often to report environment sensors |
| Air Quality Enabled | Report particulate sensor data |
| Power Metrics Enabled | Report power usage |
See [Telemetry & Sensors](telemetry-and-sensors) for supported sensors and configuration recommendations.
### Canned Message Module
Pre-configured messages accessible from the device's physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
| Setting | Апісанне |
| ------------------ | ----------------------------------------------------------- |
| ~~Enabled~~ | ⚠️ **Deprecated** — current firmware may ignore this toggle |
| Паведамленні | Newline-separated list of messages |
| Send Bell | Play bell sound on send |
| Rotary Encoder | Enable rotary encoder input |
| Up/Down/Press Pins | GPIO pin assignments for input |
### Audio Module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an **experimental** feature that encodes voice into very small data packets using the Codec2 codec.
| Setting | Апісанне |
| --------------- | -------------------------------- |
| Уключана | Activate audio module |
| Codec2 Rate | Audio quality/bandwidth tradeoff |
| I2S Word Select | GPIO pin for I2S WS |
| I2S Data In | GPIO pin for I2S DIN |
| I2S Data Out | GPIO pin for I2S DOUT |
> ⚠️ **Note:** Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think "understandable radio voice," not phone-call quality.
### Remote Hardware Module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
| Setting | Апісанне |
| -------------------- | --------------------------------------------------------------- |
| Уключана | Activate remote GPIO access |
| Allow Undefined Pins | Allow access to any GPIO pin (security risk) |
> ⚠️ **Warning:** Enabling "Allow Undefined Pins" gives remote nodes access to all GPIO pins, which could interfere with the radio's own hardware. Only enable on dedicated GPIO nodes.
### Neighbor Info Module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
| Setting | Апісанне |
| -------------------------------------- | ------------------------------------ |
| Уключана | Activate neighbor broadcasting |
| Update Interval (s) | How often to broadcast neighbor list |
See [Discovery](discovery) for how to use neighbor data for mesh topology exploration.
### Ambient Lighting Module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
| Setting | Апісанне |
| ------------------ | ---------------------------------------------------------- |
| Уключана | Activate LED control |
| LED State | On, Off, or set specific color |
| Red / Green / Blue | Individual color channel values (0–255) |
### Detection Sensor Module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
| Setting | Апісанне |
| ---------------------------------------- | ----------------------------------------------------------------------- |
| Уключана | Activate detection sensor |
| Monitor Pin | GPIO pin connected to sensor |
| Detection Triggered High | Trigger when pin goes high (vs. low) |
| Minimum Broadcast (s) | Minimum time between alert broadcasts |
| State Broadcast (s) | Periodic state broadcast interval |
| Send Bell | Include bell character in alerts |
| Friendly Name | Custom name for this sensor |
### Paxcounter Module
People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
| Setting | Апісанне |
| -------------------------------------- | -------------------------- |
| Уключана | Activate people counting |
| Update Interval (s) | How often to report counts |
> 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
### TAK Module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. See [TAK Integration](tak) for detailed setup and usage.
## Administration
### Remote Administration
Remotely configure nodes that share your admin key:
1. Select the target node in the node list.
2. Navigate to **Settings** for that node.
3. Modify configuration.
4. Tap **Save** — changes are sent over the mesh.
> ⚠️ **Requires:** Admin key configured on both your node and the target node.
### Clean Node Database
Removes stale nodes from your local database that haven't been heard in a configurable time window.
### Factory Reset
Resets all settings to factory defaults. **This cannot be undone.**
### Перазагрузіць
Remotely reboot a connected or administered node.
### Панэль адладкі
View detailed diagnostic information:
- Protocol buffers debug output
- Mesh packet log
- Connection state details
### Troubleshooting Remote Admin
- **"No response from target node"** — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
- **Changes not applying** — some settings require a reboot to take effect. Try the Reboot action after saving.
- **Can't see remote settings** — ensure your node has the admin key for the target node and that Admin Channel is enabled in Security Config.
## Related Topics
- [Settings — Radio & User](settings-radio-user) — core radio and user profile settings
- [Module configuration reference](https://meshtastic.org/docs/configuration/module) — detailed module docs on meshtastic.org
- [FAQ](https://meshtastic.org/docs/about/faq) — common questions on meshtastic.org
---

173
docs/be-rBY/user/settings-radio-user.md Normal file
View File

@@ -0,0 +1,173 @@
---
title: Settings — Radio & User
nav_order: 7
last_updated: 2026-05-13
description: Configure your radio hardware, LoRa presets, user profile, position sharing, power management, and security.
aliases:
- settings
- radio-config
- user-config
- lora
---
# Settings — Radio & User
Configure your radio hardware and user identity parameters.
## User Settings
### User Profile
| Setting | Апісанне |
| ----------------- | ------------------------------------------------------------------------------------- |
| Long Name | Your display name (up to 39 characters) |
| Short Name | 4-character abbreviated name |
| Licensed Operator | Enable if you hold an amateur radio license (enables higher power) |
### Applying Changes
After modifying settings, tap **Save** to write the configuration to your radio. The device may reboot to apply changes.
## Radio Configuration
### Device Config
| Setting | Апісанне | Default |
| ------------------------------------------ | ----------------------------------------------------------------------- | -------- |
| Role | Node behavior (Client, Router, etc.) | CLIENT |
| Rebroadcast Mode | How the node retransmits messages | Усе |
| Node Info Broadcast (s) | Interval for broadcasting node info | 10800 |
| Double-tap Button | Action for double-tap button press | Disabled |
### LoRa Config
| Setting | Апісанне | Default |
| ----------------- | ----------------------------------------------------------------------- | ----------------------------------------- |
| Рэгіён | Regulatory region for frequency bands | Unset (must configure) |
| Modem Preset | Speed/range tradeoff | LongFast |
| Hop Limit | Maximum retransmit hops | 3 |
| TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) |
| Frequency Offset | Fine-tune frequency (MHz) | 0 |
| Channel Bandwidth | Bandwidth setting | Default for preset |
> ⚠️ **Important:** You **must** set your region before transmitting. Operating without the correct region may violate local radio regulations. See the [region configuration guide](https://meshtastic.org/docs/getting-started/initial-config) on meshtastic.org for details.
### Modem Presets
| Preset | Range | Хуткасць | SNR Limit | Best For |
| ------------------ | ----------------------- | ------------------------- | ------------------------ | -------------------------------------------------------------------------------------------------------- |
| Short Turbo | ~1 km | 21.9 kbps | −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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density |
| Medium Fast | ~5 km | 5.5 kbps | −10 dB | Suburban areas; moderate building density |
| Medium Slow | ~8 km | 1.1 kbps | −12.5 dB | Suburban/rural; moderate range with slower speed |
| Long Turbo | ~10 km | 4.4 kbps | −10 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput |
| Long Fast | ~10 km | 1.1 kbps | −12.5 dB | **General use (default)** — balanced range and speed |
| Long Moderate | ~20 km | 0.34 kbps | −15 dB | Rural with some terrain; occasional use |
| Lite Fast | ~5 km | 5.5 kbps | −10 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast |
| Lite Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast |
| Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices |
| Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast |
| ~~Long Slow~~ | ~30 km | 0.18 kbps | −17.5 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 |
#### 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.
> ⚠️ **Important:** 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.
> 💡 **Tip:** The range estimates above 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
| Setting | Апісанне |
| ------------------- | ------------------------------------------------------------------------------------ |
| Screen Timeout | Time before display sleeps |
| Display Units | Metric or Imperial |
| OLED Type | Auto, SSD1306, SH1106, SH1107 |
| Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) |
| ~~Compass North~~ | ⚠️ **Deprecated** — replaced by Compass Orientation; still visible in older firmware |
### Position Config
| Setting | Апісанне |
| ----------------------------------------- | ---------------------------------- |
| GPS Enabled | Enable/disable GPS |
| GPS Update Interval | How often to acquire GPS fix |
| Position Broadcast (s) | How often to share position |
| Smart Position | Enable movement-based broadcasting |
| Fixed Position | Use a manually set position |
### Power Config
| Setting | Апісанне |
| --------------------------------------- | --------------------------------------- |
| | Enable low-power sleep mode |
| Shutdown After (s) | Auto-shutdown idle timer |
| ADC Multiplier | Battery voltage calibration factor |
| Wait Bluetooth (s) | Time to wait for BLE connection at boot |
| Mesh SDS Timeout (s) | Super-deep-sleep timeout |
### Network Config
| Setting | Апісанне |
| ------------- | ---------------------------------------------------- |
| WiFi Enabled | Enable WiFi radio (ESP32 devices) |
| WiFi SSID | Network name to connect to |
| WiFi PSK | Network password |
| NTP Server | Time synchronization server |
| Syslog Server | Remote logging server |
![IP address field](/assets/screenshots/settings_ipv4_field.png)
### Bluetooth Config
| Setting | Апісанне |
| ----------------- | ------------------------------------------------------------------------- |
| Bluetooth Enabled | Enable/disable BLE radio |
| Pairing Mode | Fixed PIN, Random PIN, or No PIN |
| Fixed PIN | PIN code for pairing (default: 123456) |
### Security Config
| Setting | Апісанне |
| --------------------- | -------------------------------------------------------------------------- |
| Public Key | Your node's public key (read-only) |
| Admin Key | Key for remote administration |
| Прыватны ключ | Your node's private key (handle securely) |
| Admin Channel Enabled | Allow admin commands via channel |
| Debug Log | Output live debug logging over serial/bluetooth |
| Serial Enabled | Enable serial console access (moved from Device Config) |
| Managed Mode | Restrict non-admin channel changes |
![Password field](/assets/screenshots/settings_password_field.png)
Settings use standard preference controls — dropdowns, toggles, and sliders:
| Control | Screenshot |
| -------- | ------------------------------------------------------ |
| Dropdown | ![Dropdown](/assets/screenshots/settings_dropdown.png) |
| Toggle | ![Toggle](/assets/screenshots/settings_switch.png) |
| Slider | ![Slider](/assets/screenshots/settings_slider.png) |
## Related Topics
- [Settings — Modules & Admin](settings-module-admin) — optional feature modules and device administration
- [Signal Meter](signal-meter) — how modem presets affect signal quality thresholds
- [LoRa configuration](https://meshtastic.org/docs/configuration/radio/lora) — detailed LoRa settings reference on meshtastic.org
- [Initial configuration](https://meshtastic.org/docs/getting-started/initial-config) — region setup guide on meshtastic.org
---

81
docs/be-rBY/user/signal-meter.md Normal file
View File

@@ -0,0 +1,81 @@
---
title: How the Meshtastic Signal Meter Works
nav_order: 15
last_updated: 2026-05-13
description: How the signal meter calculates quality from RSSI and SNR — LoRa spread spectrum, presets, and what the bars really mean.
aliases:
- signal
- signal-meter
- snr
- rssi
---
# How the Meshtastic Signal Meter Works
The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the "bars" on a traditional cell phone or Wi-Fi router.
Most consumer devices simply measure how "loud" a signal is. However, because Meshtastic uses **LoRa (Long Range)** technology, its signal meter measures how **clear** the signal is, relative to the specific settings your mesh is using.
---
## 1. The Two Metrics: "Loudness" vs. "Clarity"
Every time the LoRa radio chip receives a message, it reports two measurements:
- **RSSI (Received Signal Strength Indicator):** The **loudness** of the raw power hitting your antenna.
- **SNR (Signal-to-Noise Ratio):** The **clarity** of the signal compared to the background static.
> **Tip — The Analogy:** Imagine you are trying to hear a friend talking to you.
>
> - **RSSI** is how loud their voice is.
> - **The Noise Floor** is the background noise in the room (air conditioning, other people talking, traffic).
> - **SNR** is how easily you can distinguish your friend's voice from the background noise.
If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can't understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR).
---
## 2. The Magic of LoRa: Hearing "Below the Noise Floor"
For standard radios (like FM or Wi-Fi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static.
LoRa is special. It uses **"Spread Spectrum"** modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep _underneath_ the background noise. This is why you will frequently see **negative SNR numbers** in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static).
Depending on which Meshtastic preset you are using (e.g., `LongFast` vs. `ShortFast`), the radio has a specific **SNR Limit** — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static.
---
## 3. How the Signal Meter Calculates Quality
The Meshtastic apps take both RSSI and SNR and run them through a specific formula to assign your signal a quality rating (None, Bad, Fair, or Good). It specifically scales these values based on the physical limits of the radio preset you are using.
Here is exactly how the app decides how many bars (or what color) to show you:
| Level | Bars | Criteria | Meaning |
| ------ | ---- | ----------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- |
| Good | 3 | RSSI better than `-115 dBm` **AND** SNR better than `-7 dB` | Signal is both loud and clear — healthy connection. |
| Fair | 2 | RSSI better than `-126 dBm` with good SNR, **OR** SNR better than `-15 dB` with good RSSI | Signal getting quieter or noisier, but still decodable. |
| Bad | 1 | Falls between Fair and None thresholds | At the edge of range or experiencing interference. |
| Нічога | 0 | RSSI worse than `-126 dBm` **AND** SNR worse than `-15 dB` | Transmission completely buried in noise. |
---
## 4. What This Means for You
Because Meshtastic's meter acts as a **"Clarity Meter"**, it behaves differently than what most people expect:
> **Tip — Don't panic over low RSSI:** You might see a seemingly terrible RSSI value like `-118 dBm`. On a cell phone, you would have zero bars. But if you have an SNR of `+2 dB`, Meshtastic will still show a strong signal! _The library is quiet, so the whisper is heard perfectly._
> **Warning — Watch out for local noise:** If you hook up a massive antenna and see a great RSSI (e.g., `-90 dBm`) but your signal meter is only showing **1 Bar (Bad)**, you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh.
## Where Signal Information Appears
In the app, signal data is shown in several places:
- **Node list** — signal bars icon next to each node
- **Node detail** — SNR, RSSI, and signal quality in the device metrics section
- **Traceroute** — per-hop signal quality for each relay node
- **Signal metrics** — historical SNR and RSSI data in the metrics charts
![Node entry showing SNR, RSSI values and colored signal bars](/assets/screenshots/nodes_signal_info.png)

126
docs/be-rBY/user/tak.md Normal file
View File

@@ -0,0 +1,126 @@
---
title: TAK Integration
nav_order: 10
last_updated: 2026-05-13
description: Interoperate with ATAK and WinTAK — CoT position sharing, TAK roles, and plugin setup.
aliases:
- tak
- atak
- team-awareness-kit
---
# TAK Integration
Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK.
## Абзор
The TAK module allows Meshtastic nodes to:
- Share position data in TAK-compatible CoT (Cursor on Target) format
- Appear as team members on TAK map displays
- Receive TAK PLI (Position Location Information) messages
## Setup
### Prerequisites
- ATAK (Android Team Awareness Kit) or WinTAK installed
- Meshtastic ATAK Plugin installed
- TAK module enabled on your Meshtastic radio
### Конфигурация
1. Navigate to **Settings → Module Config → TAK**.
2. Enable the TAK module.
3. Configure the TAK team/group settings:
![Module toggle switch](/assets/screenshots/settings_switch.png)
| Setting | Апісанне |
| -------- | -------------------------- |
| Уключана | Activate TAK interop |
| Mode | TAK-compatible output mode |
### ATAK Plugin Setup
1. Install the Meshtastic ATAK Plugin from the plugin repository.
2. Open ATAK and enable the Meshtastic plugin.
3. The plugin bridges messages between ATAK and your mesh network.
## TAK Roles
Nodes configured with TAK-related roles behave differently from standard clients:
| Role | Апісанне |
| --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **TAK** | Full TAK interoperability — sends and receives CoT data, chat messages, and PLI updates. Functions as a standard client plus TAK bridge. |
| **TAK Tracker** | Position-only TAK output — automatically broadcasts PLI at regular intervals without user interaction. Optimized for unattended position beacons (vehicles, equipment, waypoints). Does not relay chat messages. |
> 💡 **Tip:** Use **TAK Tracker** for devices that only need to report position (e.g., a radio mounted in a vehicle). Use **TAK** for devices where users actively participate in TAK operations.
### CoT (Cursor on Target) Format
TAK messages use the Cursor on Target XML format — a military standard for sharing situational awareness data. Meshtastic converts its internal protobuf messages to CoT format when bridging to TAK systems, so no manual format conversion is needed.
## TAK Identity
When using TAK roles, your node broadcasts identity information that appears on TAK maps:
| Setting | Апісанне |
| -------- | ---------------------------------------------------------------------------------------------------------------- |
| Team | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) |
| Role | Your operational role (Team Member, Team Lead, HQ, Medic, RTO, etc.) |
| Callsign | Your TAK callsign (defaults to your Meshtastic long name) |
These settings appear in **Settings → Module Config → TAK** when the TAK module is enabled.
> 💡 **Tip:** Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments.
## Wire Format (V1 / V2)
Meshtastic supports two TAK wire formats:
| Format | Compatibility | Функцианал |
| ------------------------------- | --------------------------------------------------------------- | --------------------------------------------------------- |
| V1 (Legacy) | ATAK Plugin v1.x, older firmware | Basic CoT position sharing only |
| V2 (Current) | ATAK Plugin v2.x, firmware 2.3+ | Full CoT support including chat, routes, zstd compression |
The app automatically selects V2 when both sides support it. No manual configuration needed — the TAK module negotiates format based on firmware capabilities.
## Usage with ATAK
Once configured:
- Meshtastic nodes appear as markers on the ATAK map with callsign labels
- Chat messages can bridge between mesh and TAK networks
- Position updates flow bidirectionally between Meshtastic and TAK
- TAK Tracker nodes broadcast PLI automatically — their positions appear on ATAK maps without any ATAK-side configuration
> ⚠️ **Note:** TAK integration requires specific node roles and module configuration. Standard client nodes don't automatically participate in TAK operations.
## Troubleshooting
| Problem | Cause | Solution |
| -------------------------------- | ------------------------------------- | ----------------------------------------------------------------------- |
| Node doesn't appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker |
| Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config |
| ATAK plugin shows "disconnected" | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin |
| Chat messages not bridging | V1 format doesn't support chat | Ensure both nodes run firmware 2.3+ for V2 wire format |
| CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption |
## Security Considerations
- TAK data shares your position and callsign information
- Ensure your channel encryption is configured when using TAK in sensitive environments
- The TAK module respects the same channel encryption as other Meshtastic messages
## Related Topics
- [Settings — Modules & Admin](settings-module-admin) — TAK module configuration
- [Nodes](nodes) — TAK and TAK Tracker roles in the node list
- [Map & Waypoints](map-and-waypoints) — node positions on the map
- [ATAK plugin guide](https://meshtastic.org/docs/software/integrations/atak-plugin) — detailed ATAK setup on meshtastic.org
---

118
docs/be-rBY/user/telemetry-and-sensors.md Normal file
View File

@@ -0,0 +1,118 @@
---
title: Telemetry & Sensors
nav_order: 9
last_updated: 2026-05-13
description: Sensor data on the mesh — supported environment, air quality, and power sensors, plus configuration and viewing guides.
aliases:
- sensors
- environment
- weather
- power-metrics
---
# Telemetry & Sensors
Meshtastic nodes can collect and share sensor data across the mesh network.
## Абзор
Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time.
## Device Telemetry
All Meshtastic nodes report basic device telemetry:
| Metric | Апісанне | Typical Range |
| ------------------- | ------------------------------ | ------------------------------------------------------------------ |
| Battery Level | Charge percentage | 0–100% |
| Voltage | Battery voltage | 3.0–4.2V (LiPo) |
| Channel Utilization | % of airtime used locally | 0–100% |
| Air Utilization TX | % of airtime used by this node | 0–100% |
| Uptime | Seconds since last boot | Varies |
## Environment Sensors
Supported environmental sensors:
### Temperature & Humidity
| SENSOR | Тэмпература | Вільготнасць | Pressure | Notes |
| ------- | ----------- | ------------ | -------- | ----------------------- |
| BME280 | ✓ | ✓ | ✓ | Recommended all-in-one |
| BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ |
| SHT31 | ✓ | ✓ | — | High accuracy |
| MCP9808 | ✓ | — | — | Precision temperature |
| LPS22 | — | — | ✓ | Pressure only |
### Air Quality
| SENSOR | Metric | Notes |
| -------- | -------------------------------------------------- | -------------------------- |
| BME680 | Gas Resistance / IAQ | Volatile organic compounds |
| PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter |
| SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor |
### Light & UV
| SENSOR | Metric |
| -------- | -------------------------------------- |
| OPT3001 | Ambient light (lux) |
| VEML7700 | Ambient light (lux) |
| LTR390 | UV index |
## Power Metrics
Nodes with INA-series power sensors can report:
| Metric | Апісанне |
| ----------- | ----------------------------------------- |
| Bus Voltage | Supply rail voltage |
| 3 | Power consumption (mA) |
| Power | Calculated power (mW) |
Useful for monitoring solar charging or battery health on remote nodes.
## Configuring Telemetry
1. Navigate to **Settings → Module Config → Telemetry**.
2. Set reporting intervals:
- **Device Metrics Interval** — how often to broadcast device metrics
- **Environment Metrics Interval** — how often to broadcast sensor data
3. Enable specific sensor types as needed.
### Recommended Intervals
| Use Case | Device (s) | Environment (s) |
| ------------------------------------------ | ----------------------------- | ---------------------------------- |
| Urban mesh (many nodes) | 3600 | 3600 |
| Rural mesh (few nodes) | 900 | 900 |
| Weather station | 900 | 300 |
| Battery conservation | 7200 | 7200 |
> ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh.
## Viewing Telemetry
1. Navigate to **Nodes** and select a node.
2. Telemetry sections show on the detail screen:
- Device Metrics (always available)
- Environment Metrics (if sensors present)
- Power Metrics (if INA sensor present)
3. Historical graphs show trends over time.
![Telemetry actions](/assets/screenshots/node-metrics_telemetric_actions.png)
## Troubleshooting
- **No environment data showing?** The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware.
- **Stale readings?** Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online.
- **Sensor conflict on I2C bus?** Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio's serial debug output.
## Related Topics
- [Node Metrics](node-metrics) — view telemetry data on the node detail screen
- [Settings — Modules & Admin](settings-module-admin) — telemetry module configuration
- [Units & Locale](units-and-locale) — temperature and pressure display units
---

97
docs/be-rBY/user/translate.md Normal file
View File

@@ -0,0 +1,97 @@
---
title: Translate the App
parent: User Guide
nav_order: 17
last_updated: 2026-05-13
aliases:
- translate
- crowdin
- localization
---
# Translate the App
Contributing translations helps make Meshtastic accessible to a wider audience. The app uses [Crowdin](https://crowdin.com/) to manage community translations for both the user interface and in-app documentation.
---
## What Gets Translated
| Resource | Source Location | Notes |
| ----------------- | ------------------------------------- | ---------------------------------------------------------------------- |
| UI strings | `composeResources/values/strings.xml` | Buttons, labels, messages, and all user-visible text |
| User Guide pages | `docs/user/*.md` | In-app documentation shown in Help & Documentation |
| Fastlane metadata | `fastlane/metadata/android/en-US/` | App Store listing title, description, and changelogs |
> **Note — Developer Guide pages are English-only.** Code-focused documentation targeting contributors is not translated.
---
## How to Contribute
1. **Visit the Crowdin project.** Open the [Meshtastic Android Crowdin project](https://crowdin.com/project/meshtastic-android) and sign in or create a free account.
2. **Choose your language.** Select an existing language or request a new one by opening a [GitHub issue](https://github.com/meshtastic/Meshtastic-Android/issues/new).
3. **Translate strings.** Crowdin shows the English source on the left and your translation on the right. Translate each string and save.
4. **Review context.** Many strings include screenshots or context comments — check these to understand where the text appears in the app.
5. **Submit.** Approved translations are automatically merged into the next release.
> **Tip — Keep translations short.** UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear.
---
## Adding a New Language
If your language is not yet listed on Crowdin:
1. Open an issue on [GitHub](https://github.com/meshtastic/Meshtastic-Android/issues/new) requesting the new locale.
2. A maintainer will add the language to Crowdin and configure `crowdin.yml`.
3. Once added, you can begin translating immediately.
---
## How Translations Are Organized
The Android app uses **Compose Multiplatform resources** for all user-visible strings:
```
core/resources/src/commonMain/composeResources/
├── values/ ← English (default)
│ └── strings.xml
├── values-de/ ← German
│ └── strings.xml
├── values-fr/ ← French
│ └── strings.xml
└── ...
```
In-app documentation follows a similar pattern under `docs/`:
```
docs/
├── user/ ← English source (default)
│ ├── onboarding.md
│ └── ...
├── fr/user/ ← French translations
│ ├── onboarding.md
│ └── ...
└── ...
```
The app automatically selects the correct locale based on your device's **Language & Region** settings.
---
## Translation Guidelines
- **Do not translate** technical terms like "LoRa", "MQTT", "BLE", "TAK", "SNR", or "RSSI" — these are universal.
- **Keep placeholders intact.** Strings like `%1$s` or `%d` are filled in at runtime. Do not remove or reorder them unless the grammar of your language requires it.
- **Match tone.** The app uses a friendly, direct voice. Avoid overly formal language.
- **Test if possible.** Switch your device language and open the app to see how translations look in context.
---
## Questions?
If you have questions about a specific string's context or need help getting started, open a discussion on the [Meshtastic GitHub Discussions](https://github.com/meshtastic/Meshtastic-Android/discussions) page.
Thank you for helping expand the reach of Meshtastic!

118
docs/be-rBY/user/units-and-locale.md Normal file
View File

@@ -0,0 +1,118 @@
---
title: Units, Measurement & Locale
parent: User Guide
nav_order: 16
last_updated: 2026-05-12
---
# Units, Measurement & Locale
The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use — no settings to change inside the app.
---
## How It Works
Meshtastic radios always transmit data in **metric units** (meters, °C, km/h, hPa, etc.). When the app receives this data, it uses the `MetricFormatter` utility to convert and display values in whatever unit system your device's locale specifies.
On Android, your measurement preferences are determined by your system **Language & Region** settings. On Desktop (JVM), the app uses the JVM's default `Locale`.
> **Tip — You never need to toggle units inside the app.** Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more.
---
## Тэмпература
Temperature values from environment sensors are transmitted as **°C** and displayed based on your device's temperature unit preference.
![Environment metrics with temperature](/assets/screenshots/nodes_environment_metrics.png)
| Your Setting | You See |
| ------------ | ------- |
| Celsius | 22°C |
| Fahrenheit | 72°F |
This affects all temperature displays throughout the app: node environment telemetry, soil temperature, dew point, and telemetry chart axes.
## Distance & Altitude
Distances between nodes and GPS altitudes are transmitted as **meters** and automatically scaled and converted.
![Distance info display](/assets/screenshots/nodes_distance_info.png)
| Your Setting | Small Distance | Large Distance | Altitude |
| -------------------------------- | -------------- | ---------------------- | -------- |
| Metric | 350 m | 2.5 km | 1,200 m |
| Imperial (US) | 1,148 ft | 1.6 mi | 3,937 ft |
The app uses natural scaling — short distances stay in meters or feet, while longer distances switch to kilometres or miles automatically.
### Where these appear
- **Node list** — distance and bearing to each node
- **Node detail** — altitude, distance from your position
- **Map** — waypoint distances, traceroute hop distances
- **Compass** — distance to selected node
## Хуткасць
GPS ground speed is displayed in your locale's preferred speed unit.
| Your Setting | You See |
| -------------------------------- | ------- |
| Metric | 12 km/h |
| Imperial (US) | 7 mph |
## Wind
Wind speed and gust data from environment sensors are transmitted as **m/s** and converted for display.
| Your Setting | You See |
| -------------------------------- | ------- |
| Metric | 5 m/s |
| Imperial (US) | 11 mph |
Wind readings appear in the **Node Detail** environment section and the **Environment Telemetry** charts.
## Rainfall
Rainfall measurements (1-hour and 24-hour totals) are transmitted as **mm** and converted for display.
| Your Setting | You See |
| -------------------------------- | ---------------------- |
| Metric | 12 mm |
| Imperial (US) | 0.5 in |
## Units That Never Change
Some units are international standards and are displayed the same way regardless of your locale:
| Measurement | Unit | Why |
| -------------------------------- | ------------------------------ | ------------------------------------- |
| Barometric pressure | hPa | International meteorological standard |
| Heading / bearing | ° (degrees) | Universal navigation convention |
| Radiation | μR/hr | Standard dosimetry unit |
| GPS coordinates | decimal degrees | Universal geographic standard |
| Humidity, battery, soil moisture | % | Universal |
## Date & Time
All timestamps throughout the app — last heard, message times, telemetry logs, chart axes — follow your device's date and time preferences.
| Setting | What It Controls | Example |
| ---------------- | ---------------- | ------------------------------------------------ |
| **24-Hour Time** | Clock format | 14:30 vs 2:30 PM |
| **Date Format** | Date ordering | 09/05/2026 vs 05/09/2026 |
The app also uses **relative time** where it makes sense — for example, "5 min ago" or "2 hours ago" in the node list — which is automatically localised into your device language.
## Changing Your Measurement System (Android)
On Android, your measurement system (metric vs imperial) is tied to your region setting:
1. Open **Android Settings → System → Language & Region**
2. Change your **Region** or **Measurement units** preference
3. Return to Meshtastic — values update immediately
> **Tip — The app uses `MetricFormatter` from `core:common`.** All measurement formatting is handled by a shared KMP utility that respects your platform's locale. Developers adding new measurement displays should use `MetricFormatter` rather than hard-coding unit conversions.

30
docs/bg-rBG/index.md Normal file
View File

@@ -0,0 +1,30 @@
---
title: Home
layout: default
nav_order: 0
---
# Meshtastic Android App Documentation
User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform).
Use the sidebar navigation to browse the **User Guide** for app features and the **Developer Guide** for contributing to the project.
---
## Quick Links
| Guide | Описание |
| --------------------------------------------------------------------- | -------------------------------------------------------------- |
| [Getting Started](user/onboarding) | Connect your first radio and send a message |
| [Messages & Channels](user/messages-and-channels) | Channel broadcasts, direct messages, reactions, and encryption |
| [Nodes](user/nodes) | Understanding the mesh network node list |
| [Signal Meter](user/signal-meter) | How the LoRa signal quality meter works |
| [Units & Locale](user/units-and-locale) | How temperatures, distances, and times adapt to your region |
| [Desktop App](user/desktop) | Linux, macOS, and Windows desktop usage |
| [Architecture](developer/architecture) | App architecture overview for contributors |
| [Contributing](developer/contributing) | Branch naming, PR workflow, and verification commands |
---
> This documentation is served from the same markdown source that powers the in-app **Help & Documentation** browser.

125
docs/bg-rBG/user/connections.md Normal file
View File

@@ -0,0 +1,125 @@
---
title: Връзки
nav_order: 2
last_updated: 2026-05-13
description: Connect your phone or desktop to a Meshtastic radio via Bluetooth, USB, or TCP/IP.
aliases:
- bluetooth
- usb
- tcp
- pairing
---
# Връзки
Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node.
## Bluetooth (BLE)
Bluetooth Low Energy is the default and most common connection method on Android.
### Pairing a Device
1. Ensure your Meshtastic radio is powered on and in pairing mode.
2. Open the app and navigate to **Connections**.
3. Tap **Scan for Devices** — nearby Meshtastic radios will appear.
4. Select your device from the list.
5. Accept the Bluetooth pairing prompt if shown.
![Device list item](/assets/screenshots/connections_bluetooth_scan.png)
You can filter devices by transport type using the filter chips at the top:
![Transport filter chips](/assets/screenshots/connections_transport_filters.png)
> 💡 **Tip:** If your device doesn't appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device.
### Connection Status
| Icon | State | Описание |
| ---- | ----------------- | ----------------------------- |
| 🟢 | Свързано | Active radio link established |
| 🟡 | Свързване | Handshake in progress |
| 🔴 | Прекъсната връзка | No active connection |
| ⚪ | Not configured | Няма избрано устройство |
When connecting, a status indicator shows the current connection state:
![Connecting status](/assets/screenshots/connections_connecting.png)
If no devices are found, the app shows an empty state with instructions:
![No devices found](/assets/screenshots/connections_empty_state.png)
### Troubleshooting Bluetooth
- **Device not found:** Toggle Bluetooth off/on, ensure location is enabled.
- **Connection drops:** Move closer to the radio; check for interference.
- **Pairing rejected:** Forget the device in Android Bluetooth settings and retry.
## USB Serial
USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable.
### Setup
1. Connect your radio via USB cable to your device.
2. The app will prompt for USB permission — tap **Allow**.
3. The connection is established automatically.
> ⚠️ **Note:** USB connections require OTG support on Android devices.
## TCP/IP (WiFi)
Some Meshtastic radios support WiFi connectivity, allowing TCP-based connections.
### Конфигурация
1. Connect your radio to a WiFi network via the radio's web interface or settings.
2. In the app, go to **Connections → TCP**.
3. Enter the radio's IP address and port (default: 4403).
4. Tap **Connect**.
![WiFi scanning for devices](/assets/screenshots/connections_wifi_scanning.png)
When a device is found, it appears in the connection list:
![WiFi device found](/assets/screenshots/connections_wifi_device_found.png)
A successful connection is confirmed with a status indicator:
![WiFi connection success](/assets/screenshots/connections_wifi_success.png)
### When to Use TCP
- Radio is on the same local network
- Testing with a simulated radio
- Environments where Bluetooth has interference issues
## Reconnection Behavior
The app reconnects to the **last selected device** on startup. You can manually switch transports from the connections screen at any time.
To disconnect from a radio, use the disconnect button on the connections screen:
![Disconnect from radio](/assets/screenshots/connections_disconnect.png)
## Desktop Connections
On Desktop (Linux/macOS/Windows), the app supports:
- **Bluetooth (BLE)** — via the Kable library; works on macOS, Linux, and Windows
- **USB Serial** — primary wired connection method
- **TCP/IP** — for network-connected radios
See [Desktop App](desktop) for platform-specific details and keyboard shortcuts.
## Related Topics
- [Getting Started](onboarding) — first-launch setup and permissions
- [Settings — Radio & User](settings-radio-user) — Bluetooth and network configuration
- [Desktop App](desktop) — desktop-specific connection details
- [Supported devices](https://meshtastic.org/docs/hardware/devices) — full list of compatible radios on meshtastic.org
---

147
docs/bg-rBG/user/desktop.md Normal file
View File

@@ -0,0 +1,147 @@
---
title: Desktop App
nav_order: 14
last_updated: 2026-05-13
description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts.
aliases:
- desktop
- linux
- macos
- windows
- jvm
---
# Desktop App
The Meshtastic Desktop application provides the same mesh communication features on Linux, macOS, and Windows.
## Преглед
The Desktop app shares its core codebase with the Android app through Kotlin Multiplatform (KMP). Most features work identically across platforms.
## Инсталация
### Linux
- Download the `.deb` or `.AppImage` package from the releases page
- Or build from source using `./gradlew :desktopApp:run`
### macOS
- Download the `.dmg` package from releases
- Or build from source
### Windows
- Download the `.msi` installer from releases
- Or build from source
## Connecting Your Radio
### USB Serial (Primary)
The most reliable connection method on Desktop:
1. Connect your Meshtastic radio via USB cable.
2. The app should detect the serial port automatically.
3. If not detected, select the correct serial port from the connections menu.
### TCP/IP
For network-connected radios:
1. Enter the radio's IP address and port (default: 4403).
2. Click **Connect**.
### Bluetooth (BLE)
Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/JuulLabs/kable) library:
1. Ensure your system has a Bluetooth adapter.
2. The app scans for nearby Meshtastic radios automatically.
3. Select your device from the connections screen.
## Feature Parity
| Feature | Android | Desktop | Бележки |
| ---------------------------------------- | ------- | ------- | -------------------------- |
| Messaging | ✓ | ✓ | Full parity |
| Node List | ✓ | ✓ | Full parity |
| Карта | ✓ | ✓ | Full parity |
| Настройки | ✓ | ✓ | Full parity |
| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop |
| Firmware Update OTA | ✓ | ✗ | Use web flasher |
| Известия | ✓ | ✓ | Native OS notifications |
| Widgets | ✓ | ✗ | Android-only |
| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only |
\*Chirpy AI requires Android 14+ on Google flavor builds with supported hardware.
## UI Differences
The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction.
### Keyboard Shortcuts
| Shortcut | Action |
| ------------------- | --------------------------- |
| **⌘Q** / **Ctrl+Q** | Quit the application |
| **⌘,** / **Ctrl+,** | Open Settings |
| **⌘1** / **Ctrl+1** | Switch to Conversations tab |
| **⌘2** / **Ctrl+2** | Switch to Nodes tab |
| **⌘3** / **Ctrl+3** | Switch to Map tab |
| **⌘4** / **Ctrl+4** | Switch to Connections tab |
### Window & System Tray
- **Window resizing** — responsive layout adapts to window dimensions
- **System tray** — minimize to system tray for background mesh operation
- **Tray menu** — right-click the tray icon to show window or quit
- **Mouse interaction** — hover states and standard desktop navigation
### Notification Preferences
The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from **Settings → Notifications** within the app.
## Built-in Documentation Browser
The Desktop app includes a built-in documentation browser for quick access to help content without leaving the application.
![Docs browser with table of contents](/assets/screenshots/docs-browser_toc.png)
The browser supports full-text search across all documentation:
![Searching the docs browser](/assets/screenshots/docs-browser_search.png)
Individual doc pages render with full formatting:
![A documentation page](/assets/screenshots/docs-browser_page.png)
## Building from Source
```bash
git clone https://github.com/meshtastic/Meshtastic-Android.git
cd Meshtastic-Android
git submodule update --init
./gradlew :desktopApp:run
```
Requirements:
- JDK 21
- No Android SDK required for desktop-only builds
## Known Limitations
- No OTA firmware updates (use web flasher)
- Some Android-specific features (widgets, specific notification channels) are unavailable
- Performance may vary on low-spec hardware running Compose Desktop
- BLE bonding is not yet supported on desktop (pairing works without bonding)
## Related Topics
- [Connections](connections) — connection methods overview
- [Firmware Updates](firmware) — use the [Web Flasher](https://flasher.meshtastic.org) for desktop firmware updates
---

114
docs/bg-rBG/user/discovery.md Normal file
View File

@@ -0,0 +1,114 @@
---
title: Откриване
nav_order: 12
last_updated: 2026-05-13
description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools.
aliases:
- mesh-discovery
- local-discovery
- network-scan
- traceroute
- neighbor-info
---
# Откриване
Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist.
> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens.
---
## Трасиране на маршрут
Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It's the single most useful tool for debugging connectivity problems.
### Running a Traceroute
1. Navigate to **Nodes** and tap the node you want to trace.
2. On the node detail screen, tap **Traceroute**.
3. The app sends a traceroute request and waits for the response.
4. Results display each hop in order, with signal quality at every step.
### Reading the Results
A traceroute result looks like this:
```
You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target
```
Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment.
| What to look for | What it means |
| -------------------------------------------------------------------------- | --------------------------------------------------------------------------- |
| All hops show Good SNR (> 5 dB) | Healthy path — messages flow reliably |
| One hop shows Bad SNR (< 0 dB) | Weak link — this relay segment is fragile |
| Many hops (4+) | Long path — consider repositioning a node to shorten it |
| Different path on retry | Mesh is adapting — multiple routes exist (this is good!) |
> 💡 **Tip:** Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.
### Troubleshooting with Traceroute
- **"No route found"** — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
- **Traceroute times out** — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in **Settings → LoRa Config**.
- **Asymmetric paths** — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric.
---
## Neighbor Info
The Neighbor Info module lets each node broadcast a list of the nodes it can **directly hear** (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.
### Enabling Neighbor Info
1. Navigate to **Settings → Module Config → Neighbor Info**.
2. Enable the module.
3. Set the broadcast interval (default: 900 seconds / 15 minutes).
Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same.
### Viewing Neighbor Data
- Open any node's detail screen and look for the **Neighbors** section.
- Each neighbor entry shows the node that was directly heard and its signal quality.
- Combine neighbor data from multiple nodes to understand the full mesh topology.
> ⚠️ **Note:** Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion.
---
## Node List as a Discovery Tool
The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.
### Finding New Nodes
- Sort by **Last heard** to see the most recently active nodes at the top.
- Enable **Include unknown** to see nodes that have appeared on the mesh but haven't sent user info yet — these are often newly powered-on devices.
### Assessing Connectivity
- Sort by **Hops away** to see which nodes are directly reachable (0 hops) versus relayed.
- Sort by **Distance** to find nearby nodes and verify they're reachable.
- Use **Exclude MQTT** to focus on nodes reachable over radio (not via internet bridge).
### Infrastructure Audit
- Disable **Exclude infrastructure** to see Router, Repeater, Router Late, and Client Base nodes.
- Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.
See [Nodes](nodes) for full details on filtering and sorting options.
---
## Tips for Mesh Exploration
- **Start with traceroute** — it gives you immediate, actionable information about a specific path.
- **Enable Neighbor Info on key nodes** — especially routers and repeaters, to build a picture of the backbone.
- **Check the map** — node positions on the [Map](map-and-waypoints) combined with signal data help you understand why some links are strong and others are weak.
- **Compare signal over time** — use the [Signal Meter](signal-meter) guide to interpret SNR and RSSI values correctly.
---

114
docs/bg-rBG/user/firmware.md Normal file
View File

@@ -0,0 +1,114 @@
---
title: Firmware Updates
nav_order: 13
last_updated: 2026-05-13
description: Update your radio firmware over Bluetooth — OTA process, version channels, pre-flight checks, and recovery.
aliases:
- firmware
- update
- ota
- flash
---
# Firmware Updates
Keep your Meshtastic radio up to date with the latest firmware for new features, bug fixes, and security improvements.
## Checking for Updates
1. Navigate to **Settings → Firmware Update** or tap the firmware notification if shown.
2. The app checks for available firmware versions.
3. Available updates show the version number and changelog summary.
## Update Methods
### OTA (Over-The-Air) via Bluetooth
The most common update method for Android users:
1. Ensure your radio is connected via Bluetooth.
2. Navigate to the Firmware Update screen.
3. Select the desired firmware version.
4. Tap **Update** to begin the OTA process.
5. Wait for the update to complete — **do not disconnect** during the update.
![Firmware checking for updates](/assets/screenshots/firmware_checking.png)
> ⚠️ **Warning:** Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process.
![Firmware disclaimer](/assets/screenshots/firmware_disclaimer.png)
### USB Flashing
For recovery or when OTA is unavailable:
- Use the [Meshtastic Web Flasher](https://flasher.meshtastic.org)
- Or the [Meshtastic CLI tool](https://meshtastic.org/docs/getting-started/flashing-firmware) on desktop
## Version Channels
| Канал | Описание |
| -------- | ------------------------------------------- |
| Стабилен | Recommended for most users; tested releases |
| Алфа | Preview releases; may contain bugs |
## Pre-Update Checklist
Before updating:
- [ ] Battery > 50%
- [ ] Stable Bluetooth connection
- [ ] Note your current settings (they may reset on major version changes)
- [ ] Check the release notes for breaking changes
## Post-Update
After a successful update:
- The radio will reboot automatically
- Bluetooth connection will re-establish
- Verify your settings are intact
- Check the firmware version in **Settings → About**
![Firmware update success](/assets/screenshots/firmware_success.png)
## Отстраняване на неизправности
### Update Stuck
If the update appears frozen:
- Wait at least 5 minutes before intervening
- If truly stuck, power-cycle the radio
- Attempt the update again
![Firmware update error](/assets/screenshots/firmware_error.png)
### Device Won't Boot After Update
If your device fails to boot:
1. Try connecting via USB to a computer
2. Use the web flasher in recovery/DFU mode
3. Flash a known-good firmware version
4. Check the Meshtastic Discord for device-specific recovery steps
### Compatibility Warnings
The app may show warnings when:
- Connected radio firmware is below minimum supported version
- Major version mismatch between app and firmware
- Deprecated features need migration
> ⚠️ **Important:** Always update the Meshtastic app before or alongside firmware updates to ensure compatibility.
## Related Topics
- [Connections](connections) — reconnecting after a firmware update
- [Flashing firmware guide](https://meshtastic.org/docs/getting-started/flashing-firmware) — full firmware flashing walkthrough on meshtastic.org
- [Supported devices](https://meshtastic.org/docs/hardware/devices) — check firmware compatibility by device
- [FAQ](https://meshtastic.org/docs/about/faq) — common questions on meshtastic.org
---

116
docs/bg-rBG/user/map-and-waypoints.md Normal file
View File

@@ -0,0 +1,116 @@
---
title: Map & Waypoints
nav_order: 6
last_updated: 2026-05-13
description: View node positions on the map, create and share waypoints, and manage position sharing and privacy.
aliases:
- map
- waypoints
- gps
- location
---
# Map & Waypoints
The Map screen shows the geographic positions of nodes on your mesh, along with shared waypoints.
## Map View
The map displays:
- **Node positions** — colored markers for each node reporting location
- **Waypoints** — shared points of interest
- **Your position** — your current GPS location
### Node Markers
Node markers on the map indicate:
| Color | Meaning |
| ----- | ---------------------------------------------- |
| Зелен | Online (heard recently) |
| Жълт | Away (heard within 2 hours) |
| Gray | Offline (stale position) |
| Син | Your own node |
### Map Controls
- **Zoom** — pinch or use +/- buttons
- **Pan** — drag to explore
- **Center** — select the location button to center on your position
- **Node tap** — tap a node marker to view details
The floating toolbar provides quick access to compass, layer switching, node filters, refresh, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position.
![Map controls overlay](/assets/screenshots/map_controls_overlay.png)
## Waypoints
Waypoints are shared geographic points of interest that all mesh members can see.
### Creating a Waypoint
1. Long-press on the map at the desired location.
2. Enter a name and optional description.
3. Choose an icon/emoji for the waypoint.
4. Tap **Send** to share with the mesh.
### Waypoint Properties
| Property | Описание |
| ---------- | ------------------------------------------------------- |
| Име | Short identifier (max 30 characters) |
| Описание | Optional longer description |
| Icon | Visual marker emoji on the map |
| Заключен | If locked, only the creator can edit or delete |
| Expiration | Optional auto-remove time |
### Waypoint Expiration
Waypoints can be set to expire automatically:
- **Never** (default) — waypoint remains until manually deleted
- **Timed** — waypoint is automatically removed after the specified duration (e.g., "remove after 2 hours"). Useful for temporary markers like rally points, hazards, or meeting locations.
Expired waypoints are automatically hidden from the map so they don't clutter the display. The expiration countdown begins when the waypoint is created, not when other nodes receive it.
### Managing Waypoints
- Tap a waypoint on the map to view its details and coordinates
- Edit or delete waypoints you created
- **Locked waypoints** cannot be modified or deleted by other nodes — only the original creator can change them
- Unlocked waypoints can be edited by any mesh member
## Position Sharing
### Enabling Position Sharing
Your node shares its GPS position based on:
- **Fixed interval** — broadcast position at regular intervals
- **Smart position** — broadcast when movement exceeds a threshold
- **Manual** — only share when explicitly requested
Configure position behavior in **Settings → Position**.
### Privacy Considerations
> 🔒 **Privacy:** Position data is broadcast to all nodes on your channel. If you don't want your location shared, disable GPS position in settings or use a fixed/fake position.
## Map Sources
The app supports multiple map tile sources:
- OpenStreetMap (default)
- Satellite imagery (where available)
- Offline tiles (download map areas for offline use)
## Related Topics
- [Nodes](nodes) — view and filter your node list
- [Node Metrics](node-metrics) — signal quality and position history for individual nodes
- [Discovery](discovery) — traceroute and neighbor info for understanding mesh topology
- [Units & Locale](units-and-locale) — distance and coordinate display formats
---

159
docs/bg-rBG/user/messages-and-channels.md Normal file
View File

@@ -0,0 +1,159 @@
---
title: Messages & Channels
nav_order: 3
last_updated: 2026-05-13
description: Send and receive messages, manage channels, configure encryption, and use quick chat, reactions, and message actions.
aliases:
- канали
- direct-messages
- messaging
- conversations
---
# Messages & Channels
Meshtastic supports two communication modes: **channel broadcasts** and **direct messages**.
## Канали
Channels are shared communication groups. All nodes configured with the same channel key can read and send messages on that channel.
### Default Channel
Every Meshtastic device comes with a default **LongFast** channel. This is an unencrypted channel used for general mesh communication.
### Сигурност на канала
Channels support multiple encryption levels:
| Icon | Security Level | Описание |
| ---- | ------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------- |
| 🔒 | PSK (256-bit AES) | Fully encrypted with a strong pre-shared key. Only nodes with the matching key can read messages. |
| 🔐 | PSK (128-bit AES) | Encrypted with a shorter key. Secure for most uses but 256-bit is preferred for sensitive data. |
| 🔓 | Default / Open | Uses the well-known default key. **Any Meshtastic device** on the same preset can read these messages. |
| ⚠️ | Insecure + Position | Open channel that also broadcasts your GPS position. Use with caution in public meshes. |
> 🔒 **Security Tip:** Always configure a unique PSK for private communications. The default channel is intentionally open so new users can discover the mesh — but you should create a separate encrypted channel for anything sensitive.
### Adding a Channel
1. Navigate to **Settings → Channels**.
2. Tap **Add Channel** or scan a QR code.
3. Configure the channel name and encryption key.
4. Share the channel URL/QR code with others who need access.
Tapping a channel shows its details and sharing options.
## Директни съобщения
Direct messages (DMs) are point-to-point encrypted communications between two specific nodes.
### Sending a Direct Message
1. Open the **Messages** tab.
2. Select a node from your contacts list or tap a node in the node list.
3. Type your message and tap **Send**.
### Message States
| State | Icon | Meaning |
| --------------------------------- | ---- | ----------------------------------------------------------------------------------------------------------------- |
| Queued | ⏳ | Message waiting to be sent |
| En route | ✓ | Delivered to the radio, awaiting acknowledgment |
| Доставено | ✓✓ | Acknowledgment received from recipient |
| Received | ✓ | Message received from the mesh (incoming) |
| S&F Routing | 🔗 | Store & Forward: message being routed through an S&F node |
| S&F Confirmed | 🔗 | Store & Forward: delivery confirmed via S&F node |
| Грешка | ✗ | Delivery failed after retries |
### Delivery Errors
When a message fails to deliver, the error indicator shows what went wrong:
| Грешка | Meaning | What to Do |
| ---------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| No Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. |
| Got NAK | The next-hop node refused to relay | The relay node may be congested. Wait and retry. |
| Timeout | No acknowledgment within retry window | The recipient may be just out of range. Try increasing hop limit or moving to a better position. |
| Няма интерфейс | No radio interface available to send | Check that your radio is connected and the channel is configured. |
| Max Retransmit | All retry attempts exhausted | The mesh path is unreliable. Try a different channel or wait for conditions to improve. |
| Няма канал | The destination channel doesn't exist | Verify both nodes share the same channel configuration. |
| Too Large | Message exceeds maximum payload size | Shorten your message (max ~230 characters). |
| Няма отговор | Node received message but didn't respond | The recipient's radio may be busy or in low-power sleep mode. |
| Duty Cycle Limit | Regional airtime limit reached | Your radio has used its allowed transmit time. Wait for the duty cycle window to reset (typically 1 hour in EU regions). |
| Невалидна заявка | Malformed or invalid message | This usually indicates a software bug. Try restarting the app. |
> 💡 **Tip:** Most delivery errors resolve themselves. If a node is intermittently reachable, the mesh will retry. For persistent "No Route" errors, check that intermediate Router nodes are online.
## Message Features
### Quick Chat
Pre-configured messages for rapid communication:
- Access via the Quick Chat button in the message input area
- Choose from built-in phrases or custom messages
- Customize quick chat messages in **Settings → Quick Chat**
- Useful when typing is impractical (gloves, small screen, urgent)
![Quick chat option](/assets/screenshots/messages_quick_chat.png)
The channel list shows each channel with its latest message preview.
### Message Bubbles
Messages appear as chat bubbles — sent messages on the right, received messages on the left. Each bubble shows the sender, timestamp, and delivery status. Messages with replies include a quoted preview of the original message above the response.
### Reactions
React to messages with emoji:
- **Long-press** a message to open the actions menu
- Tap **Add Reaction** to choose an emoji
- Reactions appear below the message bubble
- Multiple users can react to the same message
- React to your own messages or others' messages
![Emoji reaction badges displayed beneath a message](/assets/screenshots/messages_reaction.png)
> 💡 **Tip:** Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages.
### Message Actions
Long-press any message to access:
- **Copy** — copy message text to clipboard
- **Reply** — quote the message in your response
- **React** — add an emoji reaction
- **Delete** — remove a message you sent (local deletion)
### Message Priority
Messages are queued and transmitted based on priority:
1. Emergency/alert messages (highest)
2. Direct messages
3. Channel broadcasts (lowest)
### Message Limits
- **Maximum length:** 237 bytes (approximately 230 characters for ASCII text)
- **Rate limiting:** The mesh enforces airtime fairness; heavy message volume may be throttled
- **Delivery:** Messages are retried automatically if no acknowledgment is received
## Най-добри практики
- Use channels for group coordination
- Use direct messages for private person-to-person communication
- Keep messages short — mesh bandwidth is limited
- Configure encryption for sensitive communications
## Related Topics
- [Nodes](nodes) — tap a node to start a direct message
- [Settings — Radio & User](settings-radio-user) — configure channel encryption and presets
- [MQTT](mqtt) — bridge channel messages to the internet
- [Channel configuration](https://meshtastic.org/docs/configuration/radio/channels) — detailed channel settings on meshtastic.org
---

137
docs/bg-rBG/user/mqtt.md Normal file
View File

@@ -0,0 +1,137 @@
---
title: MQTT
nav_order: 11
last_updated: 2026-05-13
description: Bridge your mesh to the internet — MQTT broker setup, encryption layers, and map reporting.
aliases:
- mqtt
- internet-bridge
- broker
---
# MQTT
MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range.
## Преглед
The MQTT module connects your node to an MQTT broker, allowing:
- Messages to reach nodes on different physical meshes via the internet
- Integration with home automation and monitoring systems
- Publishing node positions to the public Meshtastic map
- Custom data pipelines for logging and alerting
## Как работи
```
[Your Node] → Radio → [Gateway Node with WiFi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node]
```
A gateway node with internet access (WiFi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh.
## Конфигурация
### Enabling MQTT
1. Navigate to **Settings → Module Config → MQTT**.
2. Enable the MQTT module.
3. Configure the broker connection:
![MQTT toggle switch](/assets/screenshots/settings_switch.png)
| Настройка | Описание | По подразбиране |
| ----------------- | --------------------------------------------------------------------------------------------- | --------------------------------------------------- |
| Адрес на сървъра | MQTT broker hostname | mqtt.meshtastic.org |
| Потребителско име | Broker authentication | meshdev |
| Парола | Broker authentication | large4cats |
| Root Topic | Base topic for messages | msh |
| Криптиране | Encrypt MQTT payload | Активиран |
| ~~JSON Output~~ | ⚠️ **Deprecated** — JSON packet support has been removed from firmware; this field is ignored | Disabled |
| TLS | Secure connection to broker | Disabled |
| Map Reporting | Report position to public map | Disabled |
### Default Meshtastic Broker
The community maintains a public broker at `mqtt.meshtastic.org`. This is intended for general use and testing.
> 🔒 **Privacy:** Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications.
### Private Broker
For better privacy and control, you can run your own MQTT broker:
- Mosquitto (lightweight, open-source)
- HiveMQ
- EMQX
Configure your node to point to your private broker with appropriate credentials.
## Map Reporting
When Map Reporting is enabled, your node publishes its position to the Meshtastic community map:
- Visible at [meshmap.net](https://meshmap.net) and similar community map services
- Only position and node info are shared
- Disable this if you don't want your location publicly visible
## Uplink vs Downlink
| Direction | Описание |
| ------------ | -------------------------------- |
| **Uplink** | Messages from mesh → MQTT broker |
| **Downlink** | Messages from MQTT broker → mesh |
Configure per-channel which directions are active to control message flow and airtime usage.
## Message Formats
MQTT uses protobuf message format:
| Format | Описание | Use case |
| ------------ | ----------------------------------- | -------------------------- |
| **Protobuf** | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging |
> ⚠️ **Note:** JSON output support was removed from firmware. The `json_enabled` setting is still visible in the app for legacy compatibility but has no effect on current firmware versions.
## Encryption & Privacy
Understanding the layered encryption model:
1. **Channel encryption** happens on the mesh _before_ MQTT. If your channel has a PSK, the MQTT payload is already encrypted — the broker and any subscribers see only the ciphertext.
2. **MQTT encryption** (the module setting) adds an additional encryption layer for transit to the broker. This protects metadata and routing information.
3. **TLS** encrypts the TCP connection to the broker itself, preventing network-level eavesdropping.
> 🔒 **Important:** The default public channel has a well-known key. Messages on the default channel sent via MQTT are effectively **unencrypted** — anyone can decode them. Always use a custom PSK for private communications.
## Най-добри практики
- Use channel-level encryption (PSK) on channels that bridge to MQTT
- Don't enable MQTT on nodes without internet access (it will buffer and waste memory)
- Use a private broker for sensitive deployments
- Be mindful of airtime when downlinking messages from busy MQTT topics — every downlinked message consumes radio airtime on your local mesh
- Consider enabling uplink-only if you only need to monitor your mesh remotely without injecting messages back
## Отстраняване на неизправности
### MQTT Not Connecting
- **Check WiFi** — the gateway node must have an active internet connection (WiFi or Ethernet). MQTT does not work over the LoRa radio link itself.
- **Verify credentials** — incorrect username or password will silently fail on most brokers. Double-check for trailing spaces.
- **Firewall** — port 1883 (MQTT) or 8883 (MQTT+TLS) must be open. Some networks block non-standard ports.
- **DNS resolution** — if using a custom broker hostname, verify the node can resolve it. Try the broker's IP address directly.
### Messages Not Bridging
- **Check uplink/downlink settings** — if only uplink is enabled, messages flow from mesh to MQTT but not back. Enable downlink on the receiving gateway.
- **Channel mismatch** — both gateways must share the same channel with the same PSK. A mismatch means messages are encrypted with different keys and appear as garbage.
- **Topic mismatch** — ensure both gateways use the same root topic. The default `msh` works for the public broker.
## Related Topics
- [Settings — Modules & Admin](settings-module-admin) — MQTT module configuration reference
- [Messages & Channels](messages-and-channels) — channel encryption and PSK setup
- [MQTT integration guide](https://meshtastic.org/docs/software/integrations/mqtt) — detailed MQTT documentation on meshtastic.org
---

130
docs/bg-rBG/user/node-metrics.md Normal file
View File

@@ -0,0 +1,130 @@
---
title: Node Metrics
nav_order: 5
last_updated: 2026-05-13
description: Telemetry dashboards for each mesh node — device health, environment sensors, signal quality, power, traceroute, and position history.
aliases:
- metrics
- telemetry
- device-metrics
- signal
---
# Node Metrics
The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.
## Метрики на устройството
Basic operating information reported by each node:
| Метрични | Описание |
| -------------------- | ----------------------------------- |
| Battery Level | Current battery percentage |
| Напрежение | Battery voltage reading |
| Използване на канала | Percentage of airtime consumed |
| Airtime | Transmission time used by this node |
| Време на работа | Time since last reboot |
Device metrics are displayed as individual cards with trend sparklines showing battery level, voltage, channel utilization, airtime, and uptime over time.
> 💡 **Tip:** Tap any metric card to expand it into a full chart with historical data points. 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 for easy trend analysis — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.
> 💡 **Tip:** Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See [Telemetry & Sensors](telemetry-and-sensors) for a full list of supported sensors.
## Signal Metrics
Radio signal quality information:
| Метрични | Описание |
| --------- | ----------------------------------------------------------------------------- |
| SNR | Signal-to-Noise Ratio (higher is better) |
| RSSI | Received Signal Strength Indicator (closer to 0 is better) |
| Hop Count | Number of mesh hops for last message |
### Signal Quality Reference
| SNR Range | Quality |
| --------------------------------- | ------------- |
| > 10 dB | Excellent |
| 0 to 10 dB | Добър |
| -10 to 0 dB | Задоволителен |
| < -10 dB | Poor |
## Показатели на мощност
Power management telemetry (requires INA sensor or compatible hardware):
| Метрични | Описание |
| ----------- | ----------------------- |
| Bus Voltage | Supply voltage |
| Текущ | Power draw in milliamps |
| Захранване | Calculated wattage |
## Трасиране на маршрут
Traceroute shows the path a message takes through the mesh:
1. From the node detail screen, tap **Traceroute**.
2. The app sends a traceroute request to the target node.
3. Results show each hop with SNR/RSSI values.
### Reading Traceroute Results
```
You → Node A (SNR: 8.5) → Node B (SNR: 5.2) → Target
```
Each hop represents a relay node that forwarded the message.
## Журнал на позициите
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.
## Viewing Metrics
1. Navigate to **Nodes**.
2. Tap the node you want to inspect.
3. Select the metric category from the detail tabs.
![Node detail — local device](/assets/screenshots/nodes_detail_local.png)
The position tab shows location data for nodes that share GPS:
![Position inline content](/assets/screenshots/nodes_position.png)
> ⚠️ **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.
## Related Topics
- [Nodes](nodes) — node list, filtering, and sorting
- [Telemetry & Sensors](telemetry-and-sensors) — supported sensors and configuration
- [Signal Meter](signal-meter) — how signal quality is calculated from SNR and RSSI
- [Discovery](discovery) — traceroute details and neighbor info
- [Units & Locale](units-and-locale) — temperature, distance, and speed display formats
---

152
docs/bg-rBG/user/nodes.md Normal file
View File

@@ -0,0 +1,152 @@
---
title: Възли
nav_order: 4
last_updated: 2026-05-13
description: Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions.
aliases:
- node-list
- mesh-nodes
- peers
---
# Възли
The Nodes screen displays all devices visible on your mesh network.
## 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** — last heard signal strength
- **Last heard** — time since last communication
- **Distance** — estimated distance (if positions are shared)
- **Battery** — remote node battery level (if telemetry is enabled)
### Node Status Indicators
| Badge | Meaning |
| ---------- | ------------------------------------- |
| 🟢 Online | Node heard within the last 15 minutes |
| 🟡 Away | Node heard within the last 2 hours |
| 🔴 Offline | Node not heard for over 2 hours |
| ⭐ Favorite | Node marked as favorite by the user |
### Node Roles
Nodes can be configured with different roles that affect their mesh behavior:
| Роля | Описание |
| -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Клиент | Standard end-user device |
| Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client |
| Client Mute | Receives but doesn't retransmit |
| Скрит клиент | Like Client Mute, plus hides from node list |
| Рутер | 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 |
| TAK | Interoperates with TAK systems (sends/receives CoT) |
| TAK Tracker | TAK position reporting only |
| Lost & Found | Continuous position beacon for recovery |
### 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 devices.
- **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 devices or to reduce congestion in dense areas.
- **Tracker** — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
- **Sensor** — An unattended device 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](tak) for details.
> 💡 **Tip:** The mesh works best when most nodes are **Client** or **Router**. Too many Mute nodes reduces 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 | Communication uses shared channel PSK — encrypted but identity not individually verified |
| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) |
> 💡 **Tip:** PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised.
## Quick Actions
From the node list, you can:
- **Tap** a node to view its detail page
- **Long-press** for quick actions:
- Send a direct message
- Вижте на картата
- Поискване на позиция
- Mark as favorite
- Трасиране на маршрут
## Filtering & Sorting
### Text Search
Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.
### Filter Toggles
| Филтър | Описание |
| -------------------------- | ---------------------------------------------------------------------------------------------- |
| **Only online** | Show only nodes heard within the last 15 minutes |
| **Only direct** | Show only nodes with direct (non-relayed) connections |
| **Include unknown** | Show nodes that haven't sent user info yet |
| **Exclude infrastructure** | Hide infrastructure-role nodes (Router, Repeater, Router Late, Client Base) |
| **Exclude MQTT** | Hide nodes heard only via MQTT internet bridge |
| **Show ignored** | Show nodes you've previously dismissed or muted |
### Sort Options
| Sort | Описание |
| ------------------------------------------- | ------------------------------------------------------------------ |
| **Last heard** (default) | Most recently heard nodes first |
| **Alphabetical** | 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 |
| **Favorites** | Favorited nodes first |
## Node Detail
Tapping a node opens the detail view with comprehensive information. See [Node Metrics](node-metrics) for full details on metrics and telemetry.
![Node detail view](/assets/screenshots/nodes_node_list.png)
The detail screen includes device info, position, and action buttons:
![Node detail section](/assets/screenshots/nodes_detail_section.png)
Inline status indicators show key metrics at a glance:
| Indicator | Екранна снимка |
| ----------------- | -------------------------------------------------------- |
| Signal quality | ![Signal](/assets/screenshots/nodes_signal_info.png) |
| Ниво на батерията | ![Battery](/assets/screenshots/nodes_battery_info.png) |
| Hop count | ![Hops](/assets/screenshots/nodes_hops_info.png) |
| Последно чут | ![Last heard](/assets/screenshots/nodes_last_heard.png) |
| Разстояние | ![Distance](/assets/screenshots/nodes_distance_info.png) |
## Related Topics
- [Node Metrics](node-metrics) — detailed telemetry dashboards for each node
- [Messages & Channels](messages-and-channels) — send a direct message to a node
- [Map & Waypoints](map-and-waypoints) — view node positions geographically
- [Discovery](discovery) — traceroute and neighbor info for topology exploration
- [Signal Meter](signal-meter) — understand what the signal bars mean
---

99
docs/bg-rBG/user/onboarding.md Normal file
View File

@@ -0,0 +1,99 @@
---
title: Първи стъпки
nav_order: 1
last_updated: 2026-05-13
description: First-launch setup — permissions, onboarding flow, and next steps after connecting your radio.
aliases:
- first-launch
- setup
- intro
---
# Първи стъпки
Welcome to Meshtastic! This guide walks you through the initial setup of the Meshtastic Android app.
## First Launch
When you open the app for the first time, you'll be guided through an introductory flow that helps configure essential permissions and settings. Each step can be completed in order, or you can skip and configure permissions later in Android settings.
### Welcome Screen
The welcome screen introduces Meshtastic and its core capabilities:
- Off-grid mesh communication
- No cellular or internet required
- End-to-end encrypted messaging
Tap **Get Started** to proceed through the setup flow.
![Welcome screen](/assets/screenshots/onboarding_welcome.png)
## Permissions
The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality.
### Bluetooth Permission
Bluetooth is the primary connection method between your phone and Meshtastic radio:
- **Bluetooth scanning** — discover nearby Meshtastic radios
- **Bluetooth connect** — establish and maintain connections with paired radios
Grant both permissions when prompted. Without Bluetooth, you'll need to use USB or TCP connections instead.
### Location Permission
> ⚠️ **Why is location required for Bluetooth?** Android requires location permission to discover nearby Bluetooth Low Energy devices. This is an Android system requirement, not a Meshtastic-specific choice.
Meshtastic also uses your location for:
- Showing your position on the mesh map
- Calculating distances to other nodes
- Sharing your GPS coordinates with other mesh members (if enabled)
Grant **"While using the app"** or **"Always"** depending on your preference:
- **While using the app** — position updates only when the app is open
- **Always** — enables background position updates for always-on mesh presence
If denied, Bluetooth scanning will not function and your node will not report a position.
### Notifications Permission
Notifications alert you to:
- Incoming messages from channels and direct messages
- Connection status changes (connected, disconnected, reconnecting)
- Firmware update availability
> 💡 **Tip:** You can fine-tune notification preferences later in Android system settings. The app creates separate notification channels for messages, connection events, and background service status.
### Critical Alerts Permission
On supported devices, the app may request permission for critical alerts:
- These are high-priority notifications that can break through Do Not Disturb mode
- Useful for emergency mesh alerts or urgent messages
- You can **skip** this step if you don't need breakthrough notifications
- Configure or revoke later in Android notification settings
## After Setup
Once permissions are granted, the app transitions to the main interface. Your first action should be connecting to a Meshtastic radio — see [Connections](connections) for detailed instructions.
> 💡 **Tip:** If you skipped any permissions during setup, you can grant them later through **Android Settings → Apps → Meshtastic → Permissions**. The app will prompt you again if a missing permission blocks a feature you try to use.
## What's Next?
Once connected to a radio, explore:
- [Connections](connections) — pair your first radio device
- [Messages & Channels](messages-and-channels) — send your first message
- [Nodes](nodes) — see who's on your mesh
- [Map & Waypoints](map-and-waypoints) — view node positions
- [Settings](settings-radio-user) — configure your radio and user profile
New to Meshtastic? The [getting started guide](https://meshtastic.org/docs/getting-started) on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup.
---

246
docs/bg-rBG/user/settings-module-admin.md Normal file
View File

@@ -0,0 +1,246 @@
---
title: Settings — Modules & Admin
nav_order: 8
last_updated: 2026-05-13
description: Configure optional feature modules (MQTT, telemetry, canned messages, TAK, and more) and perform device administration.
aliases:
- modules
- module-config
- administration
---
# Settings — Modules & Admin
Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.
> 💡 **Tip:** You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration.
Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:
![Toggle switch](/assets/screenshots/settings_switch.png)
![Dropdown selector](/assets/screenshots/settings_dropdown.png)
![Text field](/assets/screenshots/settings_text_field.png)
![Settings card layout](/assets/screenshots/settings_titled_card.png)
## Конфигурация на модулите
### MQTT Module
Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems.
| Настройка | Описание |
| ----------------- | ------------------------------------------------------------------------ |
| Активиран | Toggle MQTT bridge |
| Сървър | MQTT broker address |
| Потребителско име | Authentication username |
| Парола | Authentication password |
| Криптиране | Encrypt MQTT payloads |
| ~~JSON Output~~ | ⚠️ **Deprecated** — JSON support removed from firmware; field is ignored |
| TLS | Use secure connection |
| Root Topic | Base MQTT topic path |
| Map Report | Publish position for public map |
See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup.
### Serial Module
Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node's serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.
| Настройка | Описание |
| ---------- | ------------------------------- |
| Активиран | Activate serial communication |
| Ехо | Echo received serial data back |
| Режим | Text, Protobuf, or NMEA output |
| RX/TX Pins | GPIO pins for serial connection |
| Baud Rate | Serial communication speed |
### External Notification Module
Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.
| Настройка | Описание |
| -------------------------------- | --------------------------- |
| Активиран | Activate notifications |
| Предупредително съобщение | Notify on incoming messages |
| Alert Message Buzzer | Use buzzer for messages |
| Alert Message Vibra | Use vibration for messages |
| Alert Bell | Notify on bell character |
| Output (GPIO) | Pin for notification output |
| Активно | High or Low active |
| Duration (ms) | Notification length |
| Use I2S as Buzzer | Use I2S audio output |
### Store & Forward Module
Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren't lost during brief disconnections.
| Настройка | Описание |
| ------------------------------------------ | -------------------------- |
| Активиран | Activate store and forward |
| Heartbeat (s) | Announcement interval |
| Записи | Maximum stored messages |
| History Return (max) | Max messages to replay |
| History Return (window) | Time window for replay |
> 💡 **Tip:** Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they're typically always-on.
### Range Test Module
Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.
| Настройка | Описание |
| -------------------------------------- | --------------------------------- |
| Активиран | Activate range testing |
| Sender Interval (s) | Time between test transmissions |
| Save CSV | Log received test data to SD card |
### Telemetry Module
Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).
| Настройка | Описание |
| -------------------------------- | --------------------------------------- |
| Device Metrics Interval | How often to report device metrics |
| Environment Metrics Interval | How often to report environment sensors |
| Качество на въздуха е активирано | Report particulate sensor data |
| Power Metrics Enabled | Report power usage |
See [Telemetry & Sensors](telemetry-and-sensors) for supported sensors and configuration recommendations.
### Canned Message Module
Pre-configured messages accessible from the device's physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.
| Настройка | Описание |
| ------------------ | ----------------------------------------------------------- |
| ~~Enabled~~ | ⚠️ **Deprecated** — current firmware may ignore this toggle |
| Съобщения | Newline-separated list of messages |
| Send Bell | Play bell sound on send |
| Rotary Encoder | Enable rotary encoder input |
| Up/Down/Press Pins | GPIO pin assignments for input |
### Audio Module
Codec2 audio support for low-bandwidth voice communication over the mesh. This is an **experimental** feature that encodes voice into very small data packets using the Codec2 codec.
| Настройка | Описание |
| --------------- | -------------------------------- |
| Активиран | Activate audio module |
| Codec2 Rate | Audio quality/bandwidth tradeoff |
| I2S Word Select | GPIO pin for I2S WS |
| I2S Data In | GPIO pin for I2S DIN |
| I2S Data Out | GPIO pin for I2S DOUT |
> ⚠️ **Note:** Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think "understandable radio voice," not phone-call quality.
### Remote Hardware Module
GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.
| Настройка | Описание |
| -------------------- | --------------------------------------------------------------- |
| Активиран | Activate remote GPIO access |
| Allow Undefined Pins | Allow access to any GPIO pin (security risk) |
> ⚠️ **Warning:** Enabling "Allow Undefined Pins" gives remote nodes access to all GPIO pins, which could interfere with the radio's own hardware. Only enable on dedicated GPIO nodes.
### Neighbor Info Module
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
| Настройка | Описание |
| -------------------------------------- | ------------------------------------ |
| Активиран | Activate neighbor broadcasting |
| Update Interval (s) | How often to broadcast neighbor list |
See [Discovery](discovery) for how to use neighbor data for mesh topology exploration.
### Ambient Lighting Module
Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.
| Настройка | Описание |
| ------------------ | ---------------------------------------------------------- |
| Активиран | Activate LED control |
| LED State | On, Off, or set specific color |
| Red / Green / Blue | Individual color channel values (0–255) |
### Detection Sensor Module
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
| Настройка | Описание |
| ---------------------------------------- | ----------------------------------------------------------------------- |
| Активиран | Activate detection sensor |
| Monitor Pin | GPIO pin connected to sensor |
| Detection Triggered High | Trigger when pin goes high (vs. low) |
| Minimum Broadcast (s) | Minimum time between alert broadcasts |
| State Broadcast (s) | Periodic state broadcast interval |
| Send Bell | Include bell character in alerts |
| Приятелско име | Custom name for this sensor |
### Paxcounter Module
People counter using WiFi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
| Настройка | Описание |
| -------------------------------------- | -------------------------- |
| Активиран | Activate people counting |
| Update Interval (s) | How often to report counts |
> 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
### TAK Module
Team Awareness Kit integration for interoperability with ATAK and WinTAK. See [TAK Integration](tak) for detailed setup and usage.
## Администриране
### Отдалечено администриране
Remotely configure nodes that share your admin key:
1. Select the target node in the node list.
2. Navigate to **Settings** for that node.
3. Modify configuration.
4. Tap **Save** — changes are sent over the mesh.
> ⚠️ **Requires:** Admin key configured on both your node and the target node.
### Почистване на базата данни с възлите
Removes stale nodes from your local database that haven't been heard in a configurable time window.
### Factory Reset
Resets all settings to factory defaults. **This cannot be undone.**
### Рестартиране
Remotely reboot a connected or administered node.
### Панел за отстраняване на грешки
View detailed diagnostic information:
- Protocol buffers debug output
- Mesh packet log
- Connection state details
### Troubleshooting Remote Admin
- **"No response from target node"** — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
- **Changes not applying** — some settings require a reboot to take effect. Try the Reboot action after saving.
- **Can't see remote settings** — ensure your node has the admin key for the target node and that Admin Channel is enabled in Security Config.
## Related Topics
- [Settings — Radio & User](settings-radio-user) — core radio and user profile settings
- [Module configuration reference](https://meshtastic.org/docs/configuration/module) — detailed module docs on meshtastic.org
- [FAQ](https://meshtastic.org/docs/about/faq) — common questions on meshtastic.org
---

173
docs/bg-rBG/user/settings-radio-user.md Normal file
View File

@@ -0,0 +1,173 @@
---
title: Settings — Radio & User
nav_order: 7
last_updated: 2026-05-13
description: Configure your radio hardware, LoRa presets, user profile, position sharing, power management, and security.
aliases:
- настройки
- radio-config
- user-config
- lora
---
# Settings — Radio & User
Configure your radio hardware and user identity parameters.
## Потребителски настройки
### User Profile
| Настройка | Описание |
| ----------------- | ------------------------------------------------------------------------------------- |
| Дълго име | Your display name (up to 39 characters) |
| Кратко име | 4-character abbreviated name |
| Licensed Operator | Enable if you hold an amateur radio license (enables higher power) |
### Applying Changes
After modifying settings, tap **Save** to write the configuration to your radio. The device may reboot to apply changes.
## Конфигурация на радиото
### Конфигуриране на устройството
| Настройка | Описание | По подразбиране |
| ------------------------------------------ | ----------------------------------------------------------------------- | --------------- |
| Роля | Node behavior (Client, Router, etc.) | Клиент |
| Режим на препредаване | How the node retransmits messages | Всички |
| Node Info Broadcast (s) | Interval for broadcasting node info | 10800 |
| Double-tap Button | Action for double-tap button press | Disabled |
### Конфигуриране на LoRa
| Настройка | Описание | По подразбиране |
| ---------------------------- | ----------------------------------------------------------------------- | ----------------------------------------- |
| Регион | Regulatory region for frequency bands | Unset (must configure) |
| Предварително настроен модем | Speed/range tradeoff | LongFast |
| Лимит на отскоци | Maximum retransmit hops | 3 |
| TX Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) |
| Отместване на честотата | Fine-tune frequency (MHz) | 0 |
| Channel Bandwidth | Bandwidth setting | Default for preset |
> ⚠️ **Important:** You **must** set your region before transmitting. Operating without the correct region may violate local radio regulations. See the [region configuration guide](https://meshtastic.org/docs/getting-started/initial-config) on meshtastic.org for details.
### Modem Presets
| Preset | Диапазон | Скорост | SNR Limit | Best For |
| ------------------ | ----------------------- | ------------------------- | ------------------------ | -------------------------------------------------------------------------------------------------------- |
| Short Turbo | ~1 km | 21.9 kbps | −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 | 5.5 kbps | −10 dB | Suburban short-range; moderate building density |
| Medium Fast | ~5 km | 5.5 kbps | −10 dB | Suburban areas; moderate building density |
| Medium Slow | ~8 km | 1.1 kbps | −12.5 dB | Suburban/rural; moderate range with slower speed |
| Long Turbo | ~10 km | 4.4 kbps | −10 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput |
| Long Fast | ~10 km | 1.1 kbps | −12.5 dB | **General use (default)** — balanced range and speed |
| Long Moderate | ~20 km | 0.34 kbps | −15 dB | Rural with some terrain; occasional use |
| Lite Fast | ~5 km | 5.5 kbps | −10 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast |
| Lite Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast |
| Narrow Fast | ~5 km | 2.7 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices |
| Narrow Slow | ~10 km | 1.1 kbps | −12.5 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast |
| ~~Long Slow~~ | ~30 km | 0.18 kbps | −17.5 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 |
#### 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.
> ⚠️ **Important:** 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.
> 💡 **Tip:** The range estimates above 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.
### Конфигуриране на дисплея
| Настройка | Описание |
| ------------------- | ------------------------------------------------------------------------------------ |
| Screen Timeout | Time before display sleeps |
| Display Units | Metric or Imperial |
| Тип OLED | Auto, SSD1306, SH1106, SH1107 |
| Compass Orientation | Rotation offset for compass display (0°, 90°, 180°, 270°) |
| ~~Compass North~~ | ⚠️ **Deprecated** — replaced by Compass Orientation; still visible in older firmware |
### Конфигуриране на позицията
| Настройка | Описание |
| ----------------------------------------- | ---------------------------------- |
| GPS Enabled | Enable/disable GPS |
| Интервал на актуализиране на GPS | How often to acquire GPS fix |
| Position Broadcast (s) | How often to share position |
| Интелигентна позиция | Enable movement-based broadcasting |
| Фиксирана позиция | Use a manually set position |
### Конфигуриране на захранването
| Настройка | Описание |
| --------------------------------------- | --------------------------------------- |
| Power Saving | Enable low-power sleep mode |
| Shutdown After (s) | Auto-shutdown idle timer |
| ADC Multiplier | Battery voltage calibration factor |
| Wait Bluetooth (s) | Time to wait for BLE connection at boot |
| Mesh SDS Timeout (s) | Super-deep-sleep timeout |
### Конфигуриране на мрежата
| Настройка | Описание |
| ------------- | ---------------------------------------------------- |
| WiFi Enabled | Enable WiFi radio (ESP32 devices) |
| WiFi SSID | Network name to connect to |
| WiFi PSK | Парола за мрежата |
| NTP сървър | Time synchronization server |
| Syslog Server | Remote logging server |
![IP address field](/assets/screenshots/settings_ipv4_field.png)
### Конфигуриране на Bluetooth
| Настройка | Описание |
| ------------------ | ------------------------------------------------------------------------- |
| Bluetooth Enabled | Enable/disable BLE radio |
| Режим на сдвояване | Fixed PIN, Random PIN, or No PIN |
| Фиксиран ПИН | PIN code for pairing (default: 123456) |
### Конфигуриране на сигурността
| Настройка | Описание |
| --------------------- | -------------------------------------------------------------------------- |
| Публичен ключ | Your node's public key (read-only) |
| Администраторски ключ | Key for remote administration |
| Частен ключ | Your node's private key (handle securely) |
| Admin Channel Enabled | Allow admin commands via channel |
| Debug Log | Output live debug logging over serial/bluetooth |
| Serial Enabled | Enable serial console access (moved from Device Config) |
| Управляем режим | Restrict non-admin channel changes |
![Password field](/assets/screenshots/settings_password_field.png)
Settings use standard preference controls — dropdowns, toggles, and sliders:
| Control | Екранна снимка |
| -------- | ------------------------------------------------------ |
| Dropdown | ![Dropdown](/assets/screenshots/settings_dropdown.png) |
| Toggle | ![Toggle](/assets/screenshots/settings_switch.png) |
| Slider | ![Slider](/assets/screenshots/settings_slider.png) |
## Related Topics
- [Settings — Modules & Admin](settings-module-admin) — optional feature modules and device administration
- [Signal Meter](signal-meter) — how modem presets affect signal quality thresholds
- [LoRa configuration](https://meshtastic.org/docs/configuration/radio/lora) — detailed LoRa settings reference on meshtastic.org
- [Initial configuration](https://meshtastic.org/docs/getting-started/initial-config) — region setup guide on meshtastic.org
---

81
docs/bg-rBG/user/signal-meter.md Normal file
View File

@@ -0,0 +1,81 @@
---
title: How the Meshtastic Signal Meter Works
nav_order: 15
last_updated: 2026-05-13
description: How the signal meter calculates quality from RSSI and SNR — LoRa spread spectrum, presets, and what the bars really mean.
aliases:
- signal
- signal-meter
- snr
- rssi
---
# How the Meshtastic Signal Meter Works
The Meshtastic signal meter — the familiar bars or status color in the app — is calculated very differently than the "bars" on a traditional cell phone or Wi-Fi router.
Most consumer devices simply measure how "loud" a signal is. However, because Meshtastic uses **LoRa (Long Range)** technology, its signal meter measures how **clear** the signal is, relative to the specific settings your mesh is using.
---
## 1. The Two Metrics: "Loudness" vs. "Clarity"
Every time the LoRa radio chip receives a message, it reports two measurements:
- **RSSI (Received Signal Strength Indicator):** The **loudness** of the raw power hitting your antenna.
- **SNR (Signal-to-Noise Ratio):** The **clarity** of the signal compared to the background static.
> **Tip — The Analogy:** Imagine you are trying to hear a friend talking to you.
>
> - **RSSI** is how loud their voice is.
> - **The Noise Floor** is the background noise in the room (air conditioning, other people talking, traffic).
> - **SNR** is how easily you can distinguish your friend's voice from the background noise.
If your friend shouts at you at a deafening rock concert, the signal is incredibly loud (High RSSI), but you still can't understand them because the background noise is louder (Bad SNR). Conversely, if your friend whispers to you in a dead-silent library, the signal is very weak (Low RSSI), but you can understand them perfectly (Great SNR).
---
## 2. The Magic of LoRa: Hearing "Below the Noise Floor"
For standard radios (like FM or Wi-Fi), if the background noise is louder than the signal (a negative SNR), the receiver just hears static.
LoRa is special. It uses **"Spread Spectrum"** modulation, which allows the radio to mathematically pull a signal out of the air even when it is buried deep _underneath_ the background noise. This is why you will frequently see **negative SNR numbers** in Meshtastic (e.g., -10 dB, which means the signal is 10 decibels weaker than the background static).
Depending on which Meshtastic preset you are using (e.g., `LongFast` vs. `ShortFast`), the radio has a specific **SNR Limit** — the absolute maximum amount of noise it can tolerate before the message is completely lost to the static.
---
## 3. How the Signal Meter Calculates Quality
The Meshtastic apps take both RSSI and SNR and run them through a specific formula to assign your signal a quality rating (None, Bad, Fair, or Good). It specifically scales these values based on the physical limits of the radio preset you are using.
Here is exactly how the app decides how many bars (or what color) to show you:
| Level | Bars | Criteria | Meaning |
| ------------- | ---- | ----------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- |
| Добър | 3 | RSSI better than `-115 dBm` **AND** SNR better than `-7 dB` | Signal is both loud and clear — healthy connection. |
| Задоволителен | 2 | RSSI better than `-126 dBm` with good SNR, **OR** SNR better than `-15 dB` with good RSSI | Signal getting quieter or noisier, but still decodable. |
| Лош | 1 | Falls between Fair and None thresholds | At the edge of range or experiencing interference. |
| Няма | 0 | RSSI worse than `-126 dBm` **AND** SNR worse than `-15 dB` | Transmission completely buried in noise. |
---
## 4. What This Means for You
Because Meshtastic's meter acts as a **"Clarity Meter"**, it behaves differently than what most people expect:
> **Tip — Don't panic over low RSSI:** You might see a seemingly terrible RSSI value like `-118 dBm`. On a cell phone, you would have zero bars. But if you have an SNR of `+2 dB`, Meshtastic will still show a strong signal! _The library is quiet, so the whisper is heard perfectly._
> **Warning — Watch out for local noise:** If you hook up a massive antenna and see a great RSSI (e.g., `-90 dBm`) but your signal meter is only showing **1 Bar (Bad)**, you have a problem. It means you have local interference — perhaps a cheap power supply, a noisy computer, or a nearby radio tower — creating so much static that it is drowning out your mesh.
## Where Signal Information Appears
In the app, signal data is shown in several places:
- **Node list** — signal bars icon next to each node
- **Node detail** — SNR, RSSI, and signal quality in the device metrics section
- **Traceroute** — per-hop signal quality for each relay node
- **Signal metrics** — historical SNR and RSSI data in the metrics charts
![Node entry showing SNR, RSSI values and colored signal bars](/assets/screenshots/nodes_signal_info.png)

126
docs/bg-rBG/user/tak.md Normal file
View File

@@ -0,0 +1,126 @@
---
title: TAK Integration
nav_order: 10
last_updated: 2026-05-13
description: Interoperate with ATAK and WinTAK — CoT position sharing, TAK roles, and plugin setup.
aliases:
- tak
- atak
- team-awareness-kit
---
# TAK Integration
Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic mesh devices and TAK applications like ATAK and WinTAK.
## Преглед
The TAK module allows Meshtastic nodes to:
- Share position data in TAK-compatible CoT (Cursor on Target) format
- Appear as team members on TAK map displays
- Receive TAK PLI (Position Location Information) messages
## Setup
### Prerequisites
- ATAK (Android Team Awareness Kit) or WinTAK installed
- Meshtastic ATAK Plugin installed
- TAK module enabled on your Meshtastic radio
### Конфигурация
1. Navigate to **Settings → Module Config → TAK**.
2. Enable the TAK module.
3. Configure the TAK team/group settings:
![Module toggle switch](/assets/screenshots/settings_switch.png)
| Настройка | Описание |
| --------- | -------------------------- |
| Активиран | Activate TAK interop |
| Режим | TAK-compatible output mode |
### ATAK Plugin Setup
1. Install the Meshtastic ATAK Plugin from the plugin repository.
2. Open ATAK and enable the Meshtastic plugin.
3. The plugin bridges messages between ATAK and your mesh network.
## TAK Roles
Nodes configured with TAK-related roles behave differently from standard clients:
| Роля | Описание |
| --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **TAK** | Full TAK interoperability — sends and receives CoT data, chat messages, and PLI updates. Functions as a standard client plus TAK bridge. |
| **TAK Tracker** | Position-only TAK output — automatically broadcasts PLI at regular intervals without user interaction. Optimized for unattended position beacons (vehicles, equipment, waypoints). Does not relay chat messages. |
> 💡 **Tip:** Use **TAK Tracker** for devices that only need to report position (e.g., a radio mounted in a vehicle). Use **TAK** for devices where users actively participate in TAK operations.
### CoT (Cursor on Target) Format
TAK messages use the Cursor on Target XML format — a military standard for sharing situational awareness data. Meshtastic converts its internal protobuf messages to CoT format when bridging to TAK systems, so no manual format conversion is needed.
## TAK Identity
When using TAK roles, your node broadcasts identity information that appears on TAK maps:
| Настройка | Описание |
| --------- | ---------------------------------------------------------------------------------------------------------------- |
| Team | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) |
| Роля | Your operational role (Team Member, Team Lead, HQ, Medic, RTO, etc.) |
| Callsign | Your TAK callsign (defaults to your Meshtastic long name) |
These settings appear in **Settings → Module Config → TAK** when the TAK module is enabled.
> 💡 **Tip:** Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments.
## Wire Format (V1 / V2)
Meshtastic supports two TAK wire formats:
| Format | Съвместимост | Характеристики |
| ------------------------------- | --------------------------------------------------------------- | --------------------------------------------------------- |
| V1 (Legacy) | ATAK Plugin v1.x, older firmware | Basic CoT position sharing only |
| V2 (Current) | ATAK Plugin v2.x, firmware 2.3+ | Full CoT support including chat, routes, zstd compression |
The app automatically selects V2 when both sides support it. No manual configuration needed — the TAK module negotiates format based on firmware capabilities.
## Usage with ATAK
Once configured:
- Meshtastic nodes appear as markers on the ATAK map with callsign labels
- Chat messages can bridge between mesh and TAK networks
- Position updates flow bidirectionally between Meshtastic and TAK
- TAK Tracker nodes broadcast PLI automatically — their positions appear on ATAK maps without any ATAK-side configuration
> ⚠️ **Note:** TAK integration requires specific node roles and module configuration. Standard client nodes don't automatically participate in TAK operations.
## Отстраняване на неизправности
| Problem | Cause | Solution |
| -------------------------------- | ------------------------------------- | ----------------------------------------------------------------------- |
| Node doesn't appear on ATAK map | TAK module disabled or wrong role | Verify TAK module is enabled and node role is TAK or TAK Tracker |
| Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config |
| ATAK plugin shows "disconnected" | BLE connection lost or plugin crashed | Reconnect Bluetooth in Meshtastic app, then restart ATAK plugin |
| Chat messages not bridging | V1 format doesn't support chat | Ensure both nodes run firmware 2.3+ for V2 wire format |
| CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption |
## Security Considerations
- TAK data shares your position and callsign information
- Ensure your channel encryption is configured when using TAK in sensitive environments
- The TAK module respects the same channel encryption as other Meshtastic messages
## Related Topics
- [Settings — Modules & Admin](settings-module-admin) — TAK module configuration
- [Nodes](nodes) — TAK and TAK Tracker roles in the node list
- [Map & Waypoints](map-and-waypoints) — node positions on the map
- [ATAK plugin guide](https://meshtastic.org/docs/software/integrations/atak-plugin) — detailed ATAK setup on meshtastic.org
---

118
docs/bg-rBG/user/telemetry-and-sensors.md Normal file
View File

@@ -0,0 +1,118 @@
---
title: Telemetry & Sensors
nav_order: 9
last_updated: 2026-05-13
description: Sensor data on the mesh — supported environment, air quality, and power sensors, plus configuration and viewing guides.
aliases:
- sensors
- environment
- weather
- power-metrics
---
# Telemetry & Sensors
Meshtastic nodes can collect and share sensor data across the mesh network.
## Преглед
Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time.
## Device Telemetry
All Meshtastic nodes report basic device telemetry:
| Метрични | Описание | Typical Range |
| -------------------- | ------------------------------ | ------------------------------------------------------------------ |
| Battery Level | Charge percentage | 0–100% |
| Напрежение | Battery voltage | 3.0–4.2V (LiPo) |
| Използване на канала | % of airtime used locally | 0–100% |
| Air Utilization TX | % of airtime used by this node | 0–100% |
| Време на работа | Seconds since last boot | Varies |
## Environment Sensors
Supported environmental sensors:
### Temperature & Humidity
| Сензор | Температура | Влажност | Налягане | Бележки |
| ------- | ----------- | -------- | -------- | ----------------------- |
| BME280 | ✓ | ✓ | ✓ | Recommended all-in-one |
| BME680 | ✓ | ✓ | ✓ | Adds gas resistance/IAQ |
| SHT31 | ✓ | ✓ | — | High accuracy |
| MCP9808 | ✓ | — | — | Precision temperature |
| LPS22 | — | — | ✓ | Pressure only |
### Air Quality
| Сензор | Метрични | Бележки |
| -------- | -------------------------------------------------- | -------------------------- |
| BME680 | Gas Resistance / IAQ | Volatile organic compounds |
| PMSA003I | PM1.0, PM2.5, PM10 | Particulate matter |
| SEN55 | PM, NOx, VOC, Temp, Humidity | Multi-sensor |
### Light & UV
| Сензор | Метрични |
| -------- | -------------------------------------- |
| OPT3001 | Ambient light (lux) |
| VEML7700 | Ambient light (lux) |
| LTR390 | UV index |
## Показатели на мощност
Nodes with INA-series power sensors can report:
| Метрични | Описание |
| ----------- | ----------------------------------------- |
| Bus Voltage | Supply rail voltage |
| Текущ | Power consumption (mA) |
| Захранване | Calculated power (mW) |
Useful for monitoring solar charging or battery health on remote nodes.
## Configuring Telemetry
1. Navigate to **Settings → Module Config → Telemetry**.
2. Set reporting intervals:
- **Device Metrics Interval** — how often to broadcast device metrics
- **Environment Metrics Interval** — how often to broadcast sensor data
3. Enable specific sensor types as needed.
### Recommended Intervals
| Use Case | Device (s) | Environment (s) |
| ------------------------------------------ | ----------------------------- | ---------------------------------- |
| Urban mesh (many nodes) | 3600 | 3600 |
| Rural mesh (few nodes) | 900 | 900 |
| Weather station | 900 | 300 |
| Battery conservation | 7200 | 7200 |
> ⚠️ **Note:** Shorter intervals increase airtime usage and battery drain across the mesh.
## Viewing Telemetry
1. Navigate to **Nodes** and select a node.
2. Telemetry sections show on the detail screen:
- Device Metrics (always available)
- Environment Metrics (if sensors present)
- Power Metrics (if INA sensor present)
3. Historical graphs show trends over time.
![Telemetry actions](/assets/screenshots/node-metrics_telemetric_actions.png)
## Отстраняване на неизправности
- **No environment data showing?** The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware.
- **Stale readings?** Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online.
- **Sensor conflict on I2C bus?** Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio's serial debug output.
## Related Topics
- [Node Metrics](node-metrics) — view telemetry data on the node detail screen
- [Settings — Modules & Admin](settings-module-admin) — telemetry module configuration
- [Units & Locale](units-and-locale) — temperature and pressure display units
---

97
docs/bg-rBG/user/translate.md Normal file
View File

@@ -0,0 +1,97 @@
---
title: Translate the App
parent: User Guide
nav_order: 17
last_updated: 2026-05-13
aliases:
- translate
- crowdin
- localization
---
# Translate the App
Contributing translations helps make Meshtastic accessible to a wider audience. The app uses [Crowdin](https://crowdin.com/) to manage community translations for both the user interface and in-app documentation.
---
## What Gets Translated
| Resource | Source Location | Бележки |
| ----------------- | ------------------------------------- | ---------------------------------------------------------------------- |
| UI strings | `composeResources/values/strings.xml` | Buttons, labels, messages, and all user-visible text |
| User Guide pages | `docs/user/*.md` | In-app documentation shown in Help & Documentation |
| Fastlane metadata | `fastlane/metadata/android/en-US/` | App Store listing title, description, and changelogs |
> **Note — Developer Guide pages are English-only.** Code-focused documentation targeting contributors is not translated.
---
## Как да допринесете
1. **Visit the Crowdin project.** Open the [Meshtastic Android Crowdin project](https://crowdin.com/project/meshtastic-android) and sign in or create a free account.
2. **Choose your language.** Select an existing language or request a new one by opening a [GitHub issue](https://github.com/meshtastic/Meshtastic-Android/issues/new).
3. **Translate strings.** Crowdin shows the English source on the left and your translation on the right. Translate each string and save.
4. **Review context.** Many strings include screenshots or context comments — check these to understand where the text appears in the app.
5. **Submit.** Approved translations are automatically merged into the next release.
> **Tip — Keep translations short.** UI strings often appear in buttons, chips, or narrow columns. If a translation is significantly longer than the English original, consider abbreviating where the meaning stays clear.
---
## Adding a New Language
If your language is not yet listed on Crowdin:
1. Open an issue on [GitHub](https://github.com/meshtastic/Meshtastic-Android/issues/new) requesting the new locale.
2. A maintainer will add the language to Crowdin and configure `crowdin.yml`.
3. Once added, you can begin translating immediately.
---
## How Translations Are Organized
The Android app uses **Compose Multiplatform resources** for all user-visible strings:
```
core/resources/src/commonMain/composeResources/
├── values/ ← English (default)
│ └── strings.xml
├── values-de/ ← German
│ └── strings.xml
├── values-fr/ ← French
│ └── strings.xml
└── ...
```
In-app documentation follows a similar pattern under `docs/`:
```
docs/
├── user/ ← English source (default)
│ ├── onboarding.md
│ └── ...
├── fr/user/ ← French translations
│ ├── onboarding.md
│ └── ...
└── ...
```
The app automatically selects the correct locale based on your device's **Language & Region** settings.
---
## Translation Guidelines
- **Do not translate** technical terms like "LoRa", "MQTT", "BLE", "TAK", "SNR", or "RSSI" — these are universal.
- **Keep placeholders intact.** Strings like `%1$s` or `%d` are filled in at runtime. Do not remove or reorder them unless the grammar of your language requires it.
- **Match tone.** The app uses a friendly, direct voice. Avoid overly formal language.
- **Test if possible.** Switch your device language and open the app to see how translations look in context.
---
## Questions?
If you have questions about a specific string's context or need help getting started, open a discussion on the [Meshtastic GitHub Discussions](https://github.com/meshtastic/Meshtastic-Android/discussions) page.
Благодарим ви, че помогнахте за разширяването на обхвата на Meshtastic!

118
docs/bg-rBG/user/units-and-locale.md Normal file
View File

@@ -0,0 +1,118 @@
---
title: Units, Measurement & Locale
parent: User Guide
nav_order: 16
last_updated: 2026-05-12
---
# Units, Measurement & Locale
The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use — no settings to change inside the app.
---
## Как работи
Meshtastic radios always transmit data in **metric units** (meters, °C, km/h, hPa, etc.). When the app receives this data, it uses the `MetricFormatter` utility to convert and display values in whatever unit system your device's locale specifies.
On Android, your measurement preferences are determined by your system **Language & Region** settings. On Desktop (JVM), the app uses the JVM's default `Locale`.
> **Tip — You never need to toggle units inside the app.** Change your system measurement preferences and every screen in Meshtastic updates automatically — node details, telemetry charts, weather, altitude, and more.
---
## Температура
Temperature values from environment sensors are transmitted as **°C** and displayed based on your device's temperature unit preference.
![Environment metrics with temperature](/assets/screenshots/nodes_environment_metrics.png)
| Your Setting | You See |
| ------------ | ------- |
| Celsius | 22°C |
| Fahrenheit | 72°F |
This affects all temperature displays throughout the app: node environment telemetry, soil temperature, dew point, and telemetry chart axes.
## Distance & Altitude
Distances between nodes and GPS altitudes are transmitted as **meters** and automatically scaled and converted.
![Distance info display](/assets/screenshots/nodes_distance_info.png)
| Your Setting | Small Distance | Large Distance | Надморска височина |
| -------------------------------- | -------------- | ---------------------- | ------------------ |
| Метрични | 350 m | 2.5 km | 1,200 m |
| Imperial (US) | 1,148 ft | 1.6 mi | 3,937 ft |
The app uses natural scaling — short distances stay in meters or feet, while longer distances switch to kilometres or miles automatically.
### Where these appear
- **Node list** — distance and bearing to each node
- **Node detail** — altitude, distance from your position
- **Map** — waypoint distances, traceroute hop distances
- **Compass** — distance to selected node
## Скорост
GPS ground speed is displayed in your locale's preferred speed unit.
| Your Setting | You See |
| -------------------------------- | ------- |
| Метрични | 12 km/h |
| Imperial (US) | 7 mph |
## Вятър
Wind speed and gust data from environment sensors are transmitted as **m/s** and converted for display.
| Your Setting | You See |
| -------------------------------- | ------- |
| Метрични | 5 m/s |
| Imperial (US) | 11 mph |
Wind readings appear in the **Node Detail** environment section and the **Environment Telemetry** charts.
## Rainfall
Rainfall measurements (1-hour and 24-hour totals) are transmitted as **mm** and converted for display.
| Your Setting | You See |
| -------------------------------- | ---------------------- |
| Метрични | 12 mm |
| Imperial (US) | 0.5 in |
## Units That Never Change
Some units are international standards and are displayed the same way regardless of your locale:
| Measurement | Unit | Why |
| -------------------------------- | ------------------------------ | ------------------------------------- |
| Barometric pressure | hPa | International meteorological standard |
| Heading / bearing | ° (degrees) | Universal navigation convention |
| Радиация | μR/hr | Standard dosimetry unit |
| GPS coordinates | decimal degrees | Universal geographic standard |
| Humidity, battery, soil moisture | % | Universal |
## Date & Time
All timestamps throughout the app — last heard, message times, telemetry logs, chart axes — follow your device's date and time preferences.
| Настройка | What It Controls | Пример |
| ---------------- | ---------------- | ------------------------------------------------ |
| **24-Hour Time** | Clock format | 14:30 vs 2:30 PM |
| **Date Format** | Date ordering | 09/05/2026 vs 05/09/2026 |
The app also uses **relative time** where it makes sense — for example, "5 min ago" or "2 hours ago" in the node list — which is automatically localised into your device language.
## Changing Your Measurement System (Android)
On Android, your measurement system (metric vs imperial) is tied to your region setting:
1. Open **Android Settings → System → Language & Region**
2. Change your **Region** or **Measurement units** preference
3. Return to Meshtastic — values update immediately
> **Tip — The app uses `MetricFormatter` from `core:common`.** All measurement formatting is handled by a shared KMP utility that respects your platform's locale. Developers adding new measurement displays should use `MetricFormatter` rather than hard-coding unit conversions.

30
docs/ca-rES/index.md Normal file
View File

@@ -0,0 +1,30 @@
---
title: Home
layout: default
nav_order: 0
---
# Meshtastic Android App Documentation
User and developer documentation for the Meshtastic Android, Desktop, and iOS applications powered by KMP (Kotlin Multiplatform).
Use the sidebar navigation to browse the **User Guide** for app features and the **Developer Guide** for contributing to the project.
---
## Quick Links
| Guide | Descripció |
| --------------------------------------------------------------------- | -------------------------------------------------------------- |
| [Getting Started](user/onboarding) | Connect your first radio and send a message |
| [Messages & Channels](user/messages-and-channels) | Channel broadcasts, direct messages, reactions, and encryption |
| [Nodes](user/nodes) | Understanding the mesh network node list |
| [Signal Meter](user/signal-meter) | How the LoRa signal quality meter works |
| [Units & Locale](user/units-and-locale) | How temperatures, distances, and times adapt to your region |
| [Desktop App](user/desktop) | Linux, macOS, and Windows desktop usage |
| [Architecture](developer/architecture) | App architecture overview for contributors |
| [Contributing](developer/contributing) | Branch naming, PR workflow, and verification commands |
---
> This documentation is served from the same markdown source that powers the in-app **Help & Documentation** browser.

125
docs/ca-rES/user/connections.md Normal file
View File

@@ -0,0 +1,125 @@
---
title: Connections
nav_order: 2
last_updated: 2026-05-13
description: Connect your phone or desktop to a Meshtastic radio via Bluetooth, USB, or TCP/IP.
aliases:
- bluetooth
- usb
- tcp
- pairing
---
# Connections
Meshtastic supports multiple transport methods to communicate between your phone/desktop and a radio node.
## Bluetooth (BLE)
Bluetooth Low Energy is the default and most common connection method on Android.
### Pairing a Device
1. Ensure your Meshtastic radio is powered on and in pairing mode.
2. Open the app and navigate to **Connections**.
3. Tap **Scan for Devices** — nearby Meshtastic radios will appear.
4. Select your device from the list.
5. Accept the Bluetooth pairing prompt if shown.
![Device list item](/assets/screenshots/connections_bluetooth_scan.png)
You can filter devices by transport type using the filter chips at the top:
![Transport filter chips](/assets/screenshots/connections_transport_filters.png)
> 💡 **Tip:** If your device doesn't appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device.
### Connection Status
| Icon | State | Descripció |
| ---- | -------------- | ----------------------------- |
| 🟢 | Connected | Active radio link established |
| 🟡 | Connecting | Handshake in progress |
| 🔴 | Desconnectat | No active connection |
| ⚪ | Not configured | No device selected |
When connecting, a status indicator shows the current connection state:
![Connecting status](/assets/screenshots/connections_connecting.png)
If no devices are found, the app shows an empty state with instructions:
![No devices found](/assets/screenshots/connections_empty_state.png)
### Troubleshooting Bluetooth
- **Device not found:** Toggle Bluetooth off/on, ensure location is enabled.
- **Connection drops:** Move closer to the radio; check for interference.
- **Pairing rejected:** Forget the device in Android Bluetooth settings and retry.
## USB Serial
USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable.
### Setup
1. Connect your radio via USB cable to your device.
2. The app will prompt for USB permission — tap **Allow**.
3. The connection is established automatically.
> ⚠️ **Note:** USB connections require OTG support on Android devices.
## TCP/IP (WiFi)
Some Meshtastic radios support WiFi connectivity, allowing TCP-based connections.
### Configuration
1. Connect your radio to a WiFi network via the radio's web interface or settings.
2. In the app, go to **Connections → TCP**.
3. Enter the radio's IP address and port (default: 4403).
4. Tap **Connect**.
![WiFi scanning for devices](/assets/screenshots/connections_wifi_scanning.png)
When a device is found, it appears in the connection list:
![WiFi device found](/assets/screenshots/connections_wifi_device_found.png)
A successful connection is confirmed with a status indicator:
![WiFi connection success](/assets/screenshots/connections_wifi_success.png)
### When to Use TCP
- Radio is on the same local network
- Testing with a simulated radio
- Environments where Bluetooth has interference issues
## Reconnection Behavior
The app reconnects to the **last selected device** on startup. You can manually switch transports from the connections screen at any time.
To disconnect from a radio, use the disconnect button on the connections screen:
![Disconnect from radio](/assets/screenshots/connections_disconnect.png)
## Desktop Connections
On Desktop (Linux/macOS/Windows), the app supports:
- **Bluetooth (BLE)** — via the Kable library; works on macOS, Linux, and Windows
- **USB Serial** — primary wired connection method
- **TCP/IP** — for network-connected radios
See [Desktop App](desktop) for platform-specific details and keyboard shortcuts.
## Related Topics
- [Getting Started](onboarding) — first-launch setup and permissions
- [Settings — Radio & User](settings-radio-user) — Bluetooth and network configuration
- [Desktop App](desktop) — desktop-specific connection details
- [Supported devices](https://meshtastic.org/docs/hardware/devices) — full list of compatible radios on meshtastic.org
---

147
docs/ca-rES/user/desktop.md Normal file
View File

@@ -0,0 +1,147 @@
---
title: Desktop App
nav_order: 14
last_updated: 2026-05-13
description: Install and use the Meshtastic Desktop app on Linux, macOS, and Windows — connections, feature parity, and keyboard shortcuts.
aliases:
- desktop
- linux
- macos
- windows
- jvm
---
# Desktop App
The Meshtastic Desktop application provides the same mesh communication features on Linux, macOS, and Windows.
## Overview
The Desktop app shares its core codebase with the Android app through Kotlin Multiplatform (KMP). Most features work identically across platforms.
## Installation
### Linux
- Download the `.deb` or `.AppImage` package from the releases page
- Or build from source using `./gradlew :desktopApp:run`
### macOS
- Download the `.dmg` package from releases
- Or build from source
### Windows
- Download the `.msi` installer from releases
- Or build from source
## Connecting Your Radio
### USB Serial (Primary)
The most reliable connection method on Desktop:
1. Connect your Meshtastic radio via USB cable.
2. The app should detect the serial port automatically.
3. If not detected, select the correct serial port from the connections menu.
### TCP/IP
For network-connected radios:
1. Enter the radio's IP address and port (default: 4403).
2. Click **Connect**.
### Bluetooth (BLE)
Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/JuulLabs/kable) library:
1. Ensure your system has a Bluetooth adapter.
2. The app scans for nearby Meshtastic radios automatically.
3. Select your device from the connections screen.
## Feature Parity
| Feature | Android | Desktop | Notes |
| ---------------------------------------- | ------- | ------- | -------------------------- |
| Messaging | ✓ | ✓ | Full parity |
| Node List | ✓ | ✓ | Full parity |
| Map | ✓ | ✓ | Full parity |
| Settings | ✓ | ✓ | Full parity |
| Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop |
| Firmware Update OTA | ✓ | ✗ | Use web flasher |
| Notifications | ✓ | ✓ | Native OS notifications |
| Widgets | ✓ | ✗ | Android-only |
| AI Assistant (Chirpy) | ✓\* | ✗ | Google flavor Android only |
\*Chirpy AI requires Android 14+ on Google flavor builds with supported hardware.
## UI Differences
The Desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction.
### Keyboard Shortcuts
| Shortcut | Action |
| ------------------- | --------------------------- |
| **⌘Q** / **Ctrl+Q** | Quit the application |
| **⌘,** / **Ctrl+,** | Open Settings |
| **⌘1** / **Ctrl+1** | Switch to Conversations tab |
| **⌘2** / **Ctrl+2** | Switch to Nodes tab |
| **⌘3** / **Ctrl+3** | Switch to Map tab |
| **⌘4** / **Ctrl+4** | Switch to Connections tab |
### Window & System Tray
- **Window resizing** — responsive layout adapts to window dimensions
- **System tray** — minimize to system tray for background mesh operation
- **Tray menu** — right-click the tray icon to show window or quit
- **Mouse interaction** — hover states and standard desktop navigation
### Notification Preferences
The Desktop app provides in-app toggles for controlling which notifications are shown — messages, new nodes, and low battery alerts. Access these from **Settings → Notifications** within the app.
## Built-in Documentation Browser
The Desktop app includes a built-in documentation browser for quick access to help content without leaving the application.
![Docs browser with table of contents](/assets/screenshots/docs-browser_toc.png)
The browser supports full-text search across all documentation:
![Searching the docs browser](/assets/screenshots/docs-browser_search.png)
Individual doc pages render with full formatting:
![A documentation page](/assets/screenshots/docs-browser_page.png)
## Building from Source
```bash
git clone https://github.com/meshtastic/Meshtastic-Android.git
cd Meshtastic-Android
git submodule update --init
./gradlew :desktopApp:run
```
Requirements:
- JDK 21
- No Android SDK required for desktop-only builds
## Known Limitations
- No OTA firmware updates (use web flasher)
- Some Android-specific features (widgets, specific notification channels) are unavailable
- Performance may vary on low-spec hardware running Compose Desktop
- BLE bonding is not yet supported on desktop (pairing works without bonding)
## Related Topics
- [Connections](connections) — connection methods overview
- [Firmware Updates](firmware) — use the [Web Flasher](https://flasher.meshtastic.org) for desktop firmware updates
---

114
docs/ca-rES/user/discovery.md Normal file
View File

@@ -0,0 +1,114 @@
---
title: Discovery
nav_order: 12
last_updated: 2026-05-13
description: Explore your mesh network — traceroute paths, neighbor maps, and node discovery tools.
aliases:
- mesh-discovery
- local-discovery
- network-scan
- traceroute
- neighbor-info
---
# Discovery
Discovery tools help you understand **how** your mesh network is connected — which nodes can hear each other, what paths messages take, and where bottlenecks or weak links exist.
> 💡 **Tip:** You don't need a dedicated "discovery mode" to start exploring your mesh. The tools below are available right now from the node list and node detail screens.
---
## Traçar ruta
Traceroute reveals the exact path a message takes from your node to any other node on the mesh. It's the single most useful tool for debugging connectivity problems.
### Running a Traceroute
1. Navigate to **Nodes** and tap the node you want to trace.
2. On the node detail screen, tap **Traceroute**.
3. The app sends a traceroute request and waits for the response.
4. Results display each hop in order, with signal quality at every step.
### Reading the Results
A traceroute result looks like this:
```
You → Node A (SNR: 8.5, RSSI: -95) → Node B (SNR: 5.2, RSSI: -108) → Target
```
Each hop represents a relay node that forwarded the message. The SNR and RSSI values at each hop tell you about the link quality on that specific segment.
| What to look for | What it means |
| -------------------------------------------------------------------------- | --------------------------------------------------------------------------- |
| All hops show Good SNR (> 5 dB) | Healthy path — messages flow reliably |
| One hop shows Bad SNR (< 0 dB) | Weak link — this relay segment is fragile |
| Many hops (4+) | Long path — consider repositioning a node to shorten it |
| Different path on retry | Mesh is adapting — multiple routes exist (this is good!) |
> 💡 **Tip:** Run traceroute several times over a few minutes. If the path changes, your mesh has redundant routes — a sign of a well-connected network.
### Troubleshooting with Traceroute
- **"No route found"** — The target node may be offline, out of range, or on a different channel. Check that both nodes share at least one channel with the same encryption key.
- **Traceroute times out** — The path may be too long (exceeds hop limit) or a relay node is congested. Try increasing the hop limit in **Settings → LoRa Config**.
- **Asymmetric paths** — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation is not always symmetric.
---
## Neighbor Info
The Neighbor Info module lets each node broadcast a list of the nodes it can **directly hear** (single-hop). When multiple nodes share their neighbor lists, you can piece together a topology map of the entire mesh.
### Enabling Neighbor Info
1. Navigate to **Settings → Module Config → Neighbor Info**.
2. Enable the module.
3. Set the broadcast interval (default: 900 seconds / 15 minutes).
Once enabled, your node periodically broadcasts its neighbor table. Other nodes with Neighbor Info enabled do the same.
### Viewing Neighbor Data
- Open any node's detail screen and look for the **Neighbors** section.
- Each neighbor entry shows the node that was directly heard and its signal quality.
- Combine neighbor data from multiple nodes to understand the full mesh topology.
> ⚠️ **Note:** Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. On busy meshes with many nodes, consider longer broadcast intervals (3600 seconds or more) to avoid congestion.
---
## Node List as a Discovery Tool
The node list itself is a powerful discovery tool when you use its filtering and sorting features effectively.
### Finding New Nodes
- Sort by **Last heard** to see the most recently active nodes at the top.
- Enable **Include unknown** to see nodes that have appeared on the mesh but haven't sent user info yet — these are often newly powered-on devices.
### Assessing Connectivity
- Sort by **Hops away** to see which nodes are directly reachable (0 hops) versus relayed.
- Sort by **Distance** to find nearby nodes and verify they're reachable.
- Use **Exclude MQTT** to focus on nodes reachable over radio (not via internet bridge).
### Infrastructure Audit
- Disable **Exclude infrastructure** to see Router, Repeater, Router Late, and Client Base nodes.
- Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.
See [Nodes](nodes) for full details on filtering and sorting options.
---
## Tips for Mesh Exploration
- **Start with traceroute** — it gives you immediate, actionable information about a specific path.
- **Enable Neighbor Info on key nodes** — especially routers and repeaters, to build a picture of the backbone.
- **Check the map** — node positions on the [Map](map-and-waypoints) combined with signal data help you understand why some links are strong and others are weak.
- **Compare signal over time** — use the [Signal Meter](signal-meter) guide to interpret SNR and RSSI values correctly.
---

114
docs/ca-rES/user/firmware.md Normal file
View File

@@ -0,0 +1,114 @@
---
title: Firmware Updates
nav_order: 13
last_updated: 2026-05-13
description: Update your radio firmware over Bluetooth — OTA process, version channels, pre-flight checks, and recovery.
aliases:
- firmware
- update
- ota
- flash
---
# Firmware Updates
Keep your Meshtastic radio up to date with the latest firmware for new features, bug fixes, and security improvements.
## Checking for Updates
1. Navigate to **Settings → Firmware Update** or tap the firmware notification if shown.
2. The app checks for available firmware versions.
3. Available updates show the version number and changelog summary.
## Update Methods
### OTA (Over-The-Air) via Bluetooth
The most common update method for Android users:
1. Ensure your radio is connected via Bluetooth.
2. Navigate to the Firmware Update screen.
3. Select the desired firmware version.
4. Tap **Update** to begin the OTA process.
5. Wait for the update to complete — **do not disconnect** during the update.
![Firmware checking for updates](/assets/screenshots/firmware_checking.png)
> ⚠️ **Warning:** Interrupting a firmware update can brick your device. Ensure your radio has sufficient battery (>50% recommended) and maintain Bluetooth proximity during the entire process.
![Firmware disclaimer](/assets/screenshots/firmware_disclaimer.png)
### USB Flashing
For recovery or when OTA is unavailable:
- Use the [Meshtastic Web Flasher](https://flasher.meshtastic.org)
- Or the [Meshtastic CLI tool](https://meshtastic.org/docs/getting-started/flashing-firmware) on desktop
## Version Channels
| Canal | Descripció |
| ------ | ------------------------------------------- |
| Stable | Recommended for most users; tested releases |
| Alpha | Preview releases; may contain bugs |
## Pre-Update Checklist
Before updating:
- [ ] Battery > 50%
- [ ] Stable Bluetooth connection
- [ ] Note your current settings (they may reset on major version changes)
- [ ] Check the release notes for breaking changes
## Post-Update
After a successful update:
- The radio will reboot automatically
- Bluetooth connection will re-establish
- Verify your settings are intact
- Check the firmware version in **Settings → About**
![Firmware update success](/assets/screenshots/firmware_success.png)
## Troubleshooting
### Update Stuck
If the update appears frozen:
- Wait at least 5 minutes before intervening
- If truly stuck, power-cycle the radio
- Attempt the update again
![Firmware update error](/assets/screenshots/firmware_error.png)
### Device Won't Boot After Update
If your device fails to boot:
1. Try connecting via USB to a computer
2. Use the web flasher in recovery/DFU mode
3. Flash a known-good firmware version
4. Check the Meshtastic Discord for device-specific recovery steps
### Compatibility Warnings
The app may show warnings when:
- Connected radio firmware is below minimum supported version
- Major version mismatch between app and firmware
- Deprecated features need migration
> ⚠️ **Important:** Always update the Meshtastic app before or alongside firmware updates to ensure compatibility.
## Related Topics
- [Connections](connections) — reconnecting after a firmware update
- [Flashing firmware guide](https://meshtastic.org/docs/getting-started/flashing-firmware) — full firmware flashing walkthrough on meshtastic.org
- [Supported devices](https://meshtastic.org/docs/hardware/devices) — check firmware compatibility by device
- [FAQ](https://meshtastic.org/docs/about/faq) — common questions on meshtastic.org
---

Some files were not shown because too many files have changed in this diff Show More