{"0": {
    "doc": "Adding a Feature Module",
    "title": "Adding a Feature Module",
    "content": "Step-by-step guide for creating a new KMP feature module in the Meshtastic project. ",
    "url": "/Meshtastic-Android/main/en/developer/adding-a-feature-module.html",
    
    "relUrl": "/en/developer/adding-a-feature-module.html"
  },"1": {
    "doc": "Adding a Feature Module",
    "title": "Create the Module Directory",
    "content": "mkdir -p feature/my-feature/src/{commonMain,commonTest,androidMain,jvmMain,iosMain}/kotlin/org/meshtastic/feature/myfeature . ",
    "url": "/Meshtastic-Android/main/en/developer/adding-a-feature-module.html#create-the-module-directory",
    
    "relUrl": "/en/developer/adding-a-feature-module.html#create-the-module-directory"
  },"2": {
    "doc": "Adding a Feature Module",
    "title": "Create build.gradle.kts",
    "content": "plugins { alias(libs.plugins.meshtastic.kmp.feature) } kotlin { android { withHostTest { isIncludeAndroidResources = true } } sourceSets { commonMain.dependencies { implementation(projects.core.common) implementation(projects.core.navigation) implementation(projects.core.resources) implementation(projects.core.ui) implementation(projects.core.di) } commonTest.dependencies { implementation(libs.compose.multiplatform.ui.test) } jvmTest.dependencies { implementation(compose.desktop.currentOs) } } } . ",
    "url": "/Meshtastic-Android/main/en/developer/adding-a-feature-module.html#create-buildgradlekts",
    
    "relUrl": "/en/developer/adding-a-feature-module.html#create-buildgradlekts"
  },"3": {
    "doc": "Adding a Feature Module",
    "title": "Register in settings.gradle.kts",
    "content": "Add your module to the main include() block: . include( // ...existing modules... \":feature:my-feature\", ) . ",
    "url": "/Meshtastic-Android/main/en/developer/adding-a-feature-module.html#register-in-settingsgradlekts",
    
    "relUrl": "/en/developer/adding-a-feature-module.html#register-in-settingsgradlekts"
  },"4": {
    "doc": "Adding a Feature Module",
    "title": "Create the DI Module",
    "content": "src/commonMain/kotlin/org/meshtastic/feature/myfeature/di/FeatureMyFeatureModule.kt: . package org.meshtastic.feature.myfeature.di import org.koin.core.annotation.ComponentScan import org.koin.core.annotation.Module @Module @ComponentScan(\"org.meshtastic.feature.myfeature\") class FeatureMyFeatureModule . ",
    "url": "/Meshtastic-Android/main/en/developer/adding-a-feature-module.html#create-the-di-module",
    
    "relUrl": "/en/developer/adding-a-feature-module.html#create-the-di-module"
  },"5": {
    "doc": "Adding a Feature Module",
    "title": "Register DI in App/Desktop",
    "content": "Add your module to: . | androidApp/src/main/kotlin/org/meshtastic/app/di/AppKoinModule.kt | desktopApp/src/main/kotlin/org/meshtastic/desktop/di/DesktopKoinModule.kt | . ",
    "url": "/Meshtastic-Android/main/en/developer/adding-a-feature-module.html#register-di-in-appdesktop",
    
    "relUrl": "/en/developer/adding-a-feature-module.html#register-di-in-appdesktop"
  },"6": {
    "doc": "Adding a Feature Module",
    "title": "Add Navigation Routes",
    "content": "In core/navigation/src/commonMain/kotlin/org/meshtastic/core/navigation/Routes.kt: . @Serializable sealed interface MyFeatureRoute : Route { @Serializable data object MyFeatureGraph : MyFeatureRoute, Graph @Serializable data object MyFeatureHome : MyFeatureRoute } . ",
    "url": "/Meshtastic-Android/main/en/developer/adding-a-feature-module.html#add-navigation-routes",
    
    "relUrl": "/en/developer/adding-a-feature-module.html#add-navigation-routes"
  },"7": {
    "doc": "Adding a Feature Module",
    "title": "Create Navigation Entries",
    "content": "src/commonMain/kotlin/org/meshtastic/feature/myfeature/navigation/MyFeatureNavigation.kt: . package org.meshtastic.feature.myfeature.navigation import androidx.navigation3.runtime.EntryProviderScope import androidx.navigation3.runtime.NavBackStack import androidx.navigation3.runtime.NavKey import org.meshtastic.core.navigation.MyFeatureRoute fun EntryProviderScope<NavKey>.myFeatureGraph(backStack: NavBackStack<NavKey>) { entry<MyFeatureRoute.MyFeatureGraph> { MyFeatureScreen(onNavigateUp = { backStack.removeLastOrNull() }) } entry<MyFeatureRoute.MyFeatureHome> { MyFeatureScreen(onNavigateUp = { backStack.removeLastOrNull() }) } } . Both the graph sentinel (MyFeatureRoute.MyFeatureGraph) and the primary screen (MyFeatureRoute.MyFeatureHome) navigate to the same composable, so the feature is reachable via either a top-level push or a deep-link graph push — the same pattern feature:wifi-provision and feature:firmware use. Then wire it up: call myFeatureGraph(backStack) from the shared entryProvider<NavKey> { } block in androidApp’s Main.kt and desktopApp’s DesktopNavigation.kt, alongside the other features’ entries functions. See Navigation Entry Registration. ",
    "url": "/Meshtastic-Android/main/en/developer/adding-a-feature-module.html#create-navigation-entries",
    
    "relUrl": "/en/developer/adding-a-feature-module.html#create-navigation-entries"
  },"8": {
    "doc": "Adding a Feature Module",
    "title": "Source Set Guidelines",
    "content": "| Source Set | Contains | . | commonMain | Models, ViewModels, shared UI, DI module, navigation | . | androidMain | Android-specific implementations (e.g., platform APIs) | . | jvmMain | Desktop-specific implementations | . | iosMain | iOS-specific implementations | . | commonTest | Shared unit tests | . ",
    "url": "/Meshtastic-Android/main/en/developer/adding-a-feature-module.html#source-set-guidelines",
    
    "relUrl": "/en/developer/adding-a-feature-module.html#source-set-guidelines"
  },"9": {
    "doc": "Adding a Feature Module",
    "title": "Testing Expectations",
    "content": "Every feature module should have: . | Unit tests in commonTest for business logic | UI tests using compose-multiplatform-ui-test where appropriate | No test dependency on other feature modules | . ",
    "url": "/Meshtastic-Android/main/en/developer/adding-a-feature-module.html#testing-expectations",
    
    "relUrl": "/en/developer/adding-a-feature-module.html#testing-expectations"
  },"10": {
    "doc": "Adding a Feature Module",
    "title": "Checklist",
    "content": ". | Module directory created | build.gradle.kts with correct plugins and dependencies | Added to settings.gradle.kts | DI module created with @ComponentScan | DI module registered in app and desktop roots | Routes added to Routes.kt | Navigation entries registered | ./gradlew kmpSmokeCompile passes | ./gradlew :feature:my-feature:allTests passes | . ",
    "url": "/Meshtastic-Android/main/en/developer/adding-a-feature-module.html#checklist",
    
    "relUrl": "/en/developer/adding-a-feature-module.html#checklist"
  },"11": {
    "doc": "App Functions",
    "title": "App Functions",
    "content": "App Functions expose Meshtastic capabilities to the Android system and to on-device AI assistants (such as Gemini) through the Android App Functions API. With them enabled, an assistant can discover and trigger mesh workflows for you — for example sending a message or checking your mesh status — without you opening the app. App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. App Functions let the system AI assistant act on your mesh; Chirpy is a conversational assistant inside the Meshtastic app itself. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/app-functions.html",
    
    "relUrl": "/sk-rSK/user/app-functions.html"
  },"12": {
    "doc": "App Functions",
    "title": "Enabling App Functions",
    "content": "Control App Functions from Settings → System AI. The screen has: . | A master toggle labeled “Allow AI access”, with the subtitle “Let system AI assistants (e.g. Gemini) discover and use mesh functions”. When off, no functions are exposed to the system. | An individual toggle for each function, so you can expose only the capabilities you want. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. The functions are grouped into a Write section (functions that change something or send data to your mesh) and a Read section (functions that only return information). The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Write Functions . | Function | What it does | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Read Functions . | Function | What it returns | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | The list of nodes on your mesh. | . | Get channel info | Information about your channels. | . | Get device status | Status of your connected radio. | . | Get node details | Detailed information about a specific node. | . | Get mesh metrics | Telemetry and metrics from your mesh. | . | Get recent messages | Recent messages from your conversations. | . | Get unread summary | A summary of unread messages. | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/app-functions.html#enabling-app-functions",
    
    "relUrl": "/sk-rSK/user/app-functions.html#enabling-app-functions"
  },"13": {
    "doc": "App Functions",
    "title": "Privacy",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/app-functions.html#privacy",
    
    "relUrl": "/sk-rSK/user/app-functions.html#privacy"
  },"14": {
    "doc": "App Functions",
    "title": "Related Topics",
    "content": ". | Messages & Channels — sending messages directly in the app | Nodes — the node list the read functions draw from | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/app-functions.html#related-topics",
    
    "relUrl": "/sk-rSK/user/app-functions.html#related-topics"
  },"15": {
    "doc": "App Functions",
    "title": "App Functions",
    "content": "App Functions expose Meshtastic capabilities to the Android system and to on-device AI assistants (such as Gemini) through the Android App Functions API. With them enabled, an assistant can discover and trigger mesh workflows for you — for example sending a message or checking your mesh status — without you opening the app. App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. App Functions let the system AI assistant act on your mesh; Chirpy is a conversational assistant inside the Meshtastic app itself. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/app-functions.html",
    
    "relUrl": "/be-rBY/user/app-functions.html"
  },"16": {
    "doc": "App Functions",
    "title": "Enabling App Functions",
    "content": "Control App Functions from Settings → System AI. The screen has: . | A master toggle labeled “Allow AI access”, with the subtitle “Let system AI assistants (e.g. Gemini) discover and use mesh functions”. When off, no functions are exposed to the system. | An individual toggle for each function, so you can expose only the capabilities you want. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. The functions are grouped into a Write section (functions that change something or send data to your mesh) and a Read section (functions that only return information). The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Write Functions . | Function | What it does | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Read Functions . | Function | What it returns | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | The list of nodes on your mesh. | . | Get channel info | Information about your channels. | . | Get device status | Status of your connected radio. | . | Get node details | Detailed information about a specific node. | . | Get mesh metrics | Telemetry and metrics from your mesh. | . | Get recent messages | Recent messages from your conversations. | . | Get unread summary | A summary of unread messages. | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/app-functions.html#enabling-app-functions",
    
    "relUrl": "/be-rBY/user/app-functions.html#enabling-app-functions"
  },"17": {
    "doc": "App Functions",
    "title": "Privacy",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/app-functions.html#privacy",
    
    "relUrl": "/be-rBY/user/app-functions.html#privacy"
  },"18": {
    "doc": "App Functions",
    "title": "Related Topics",
    "content": ". | Messages & Channels — sending messages directly in the app | Nodes — the node list the read functions draw from | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/app-functions.html#related-topics",
    
    "relUrl": "/be-rBY/user/app-functions.html#related-topics"
  },"19": {
    "doc": "App Functions",
    "title": "App Functions",
    "content": "App Functions expose Meshtastic capabilities to the Android system and to on-device AI assistants (such as Gemini) through the Android App Functions API. With them enabled, an assistant can discover and trigger mesh workflows for you — for example sending a message or checking your mesh status — without you opening the app. App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. App Functions let the system AI assistant act on your mesh; Chirpy is a conversational assistant inside the Meshtastic app itself. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/app-functions.html",
    
    "relUrl": "/it-rIT/user/app-functions.html"
  },"20": {
    "doc": "App Functions",
    "title": "Enabling App Functions",
    "content": "Control App Functions from Settings → System AI. The screen has: . | A master toggle labeled “Allow AI access”, with the subtitle “Let system AI assistants (e.g. Gemini) discover and use mesh functions”. When off, no functions are exposed to the system. | An individual toggle for each function, so you can expose only the capabilities you want. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. The functions are grouped into a Write section (functions that change something or send data to your mesh) and a Read section (functions that only return information). The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Write Functions . | Function | What it does | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Read Functions . | Function | What it returns | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | The list of nodes on your mesh. | . | Get channel info | Information about your channels. | . | Get device status | Status of your connected radio. | . | Get node details | Detailed information about a specific node. | . | Get mesh metrics | Telemetry and metrics from your mesh. | . | Get recent messages | Recent messages from your conversations. | . | Get unread summary | A summary of unread messages. | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/app-functions.html#enabling-app-functions",
    
    "relUrl": "/it-rIT/user/app-functions.html#enabling-app-functions"
  },"21": {
    "doc": "App Functions",
    "title": "Privacy",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/app-functions.html#privacy",
    
    "relUrl": "/it-rIT/user/app-functions.html#privacy"
  },"22": {
    "doc": "App Functions",
    "title": "Related Topics",
    "content": ". | Messages & Channels — sending messages directly in the app | Nodes — the node list the read functions draw from | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/app-functions.html#related-topics",
    
    "relUrl": "/it-rIT/user/app-functions.html#related-topics"
  },"23": {
    "doc": "App Functions",
    "title": "App Functions",
    "content": "App Functions expose Meshtastic capabilities to the Android system and to on-device AI assistants (such as Gemini) through the Android App Functions API. With them enabled, an assistant can discover and trigger mesh workflows for you — for example sending a message or checking your mesh status — without you opening the app. App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. App Functions let the system AI assistant act on your mesh; Chirpy is a conversational assistant inside the Meshtastic app itself. ",
    "url": "/Meshtastic-Android/main/es-rES/user/app-functions.html",
    
    "relUrl": "/es-rES/user/app-functions.html"
  },"24": {
    "doc": "App Functions",
    "title": "Enabling App Functions",
    "content": "Control App Functions from Settings → System AI. The screen has: . | A master toggle labeled “Allow AI access”, with the subtitle “Let system AI assistants (e.g. Gemini) discover and use mesh functions”. When off, no functions are exposed to the system. | An individual toggle for each function, so you can expose only the capabilities you want. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. The functions are grouped into a Write section (functions that change something or send data to your mesh) and a Read section (functions that only return information). The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Write Functions . | Function | What it does | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Read Functions . | Function | What it returns | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | The list of nodes on your mesh. | . | Get channel info | Information about your channels. | . | Get device status | Status of your connected radio. | . | Get node details | Detailed information about a specific node. | . | Get mesh metrics | Telemetry and metrics from your mesh. | . | Get recent messages | Recent messages from your conversations. | . | Get unread summary | A summary of unread messages. | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/app-functions.html#enabling-app-functions",
    
    "relUrl": "/es-rES/user/app-functions.html#enabling-app-functions"
  },"25": {
    "doc": "App Functions",
    "title": "Privacy",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/es-rES/user/app-functions.html#privacy",
    
    "relUrl": "/es-rES/user/app-functions.html#privacy"
  },"26": {
    "doc": "App Functions",
    "title": "Related Topics",
    "content": ". | Messages & Channels — sending messages directly in the app | Nodes — the node list the read functions draw from | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/app-functions.html#related-topics",
    
    "relUrl": "/es-rES/user/app-functions.html#related-topics"
  },"27": {
    "doc": "App Functions",
    "title": "App Functions",
    "content": "App Functions expose Meshtastic capabilities to the Android system and to on-device AI assistants (such as Gemini) through the Android App Functions API. With them enabled, an assistant can discover and trigger mesh workflows for you — for example sending a message or checking your mesh status — without you opening the app. App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. App Functions let the system AI assistant act on your mesh; Chirpy is a conversational assistant inside the Meshtastic app itself. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/app-functions.html",
    
    "relUrl": "/sl-rSI/user/app-functions.html"
  },"28": {
    "doc": "App Functions",
    "title": "Enabling App Functions",
    "content": "Control App Functions from Settings → System AI. The screen has: . | A master toggle labeled “Allow AI access”, with the subtitle “Let system AI assistants (e.g. Gemini) discover and use mesh functions”. When off, no functions are exposed to the system. | An individual toggle for each function, so you can expose only the capabilities you want. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. The functions are grouped into a Write section (functions that change something or send data to your mesh) and a Read section (functions that only return information). The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Write Functions . | Function | What it does | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Read Functions . | Function | What it returns | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | The list of nodes on your mesh. | . | Get channel info | Information about your channels. | . | Get device status | Status of your connected radio. | . | Get node details | Detailed information about a specific node. | . | Get mesh metrics | Telemetry and metrics from your mesh. | . | Get recent messages | Recent messages from your conversations. | . | Get unread summary | A summary of unread messages. | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/app-functions.html#enabling-app-functions",
    
    "relUrl": "/sl-rSI/user/app-functions.html#enabling-app-functions"
  },"29": {
    "doc": "App Functions",
    "title": "Privacy",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/app-functions.html#privacy",
    
    "relUrl": "/sl-rSI/user/app-functions.html#privacy"
  },"30": {
    "doc": "App Functions",
    "title": "Related Topics",
    "content": ". | Messages & Channels — sending messages directly in the app | Nodes — the node list the read functions draw from | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/app-functions.html#related-topics",
    
    "relUrl": "/sl-rSI/user/app-functions.html#related-topics"
  },"31": {
    "doc": "App Functions",
    "title": "App Functions",
    "content": "App Functions expose Meshtastic capabilities to the Android system and to on-device AI assistants (such as Gemini) through the Android App Functions API. With them enabled, an assistant can discover and trigger mesh workflows for you — for example sending a message or checking your mesh status — without you opening the app. App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. App Functions let the system AI assistant act on your mesh; Chirpy is a conversational assistant inside the Meshtastic app itself. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/app-functions.html",
    
    "relUrl": "/no-rNO/user/app-functions.html"
  },"32": {
    "doc": "App Functions",
    "title": "Enabling App Functions",
    "content": "Control App Functions from Settings → System AI. The screen has: . | A master toggle labeled “Allow AI access”, with the subtitle “Let system AI assistants (e.g. Gemini) discover and use mesh functions”. When off, no functions are exposed to the system. | An individual toggle for each function, so you can expose only the capabilities you want. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. The functions are grouped into a Write section (functions that change something or send data to your mesh) and a Read section (functions that only return information). The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Write Functions . | Function | What it does | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Read Functions . | Function | What it returns | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | The list of nodes on your mesh. | . | Get channel info | Information about your channels. | . | Get device status | Status of your connected radio. | . | Get node details | Detailed information about a specific node. | . | Get mesh metrics | Telemetry and metrics from your mesh. | . | Get recent messages | Recent messages from your conversations. | . | Get unread summary | A summary of unread messages. | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/app-functions.html#enabling-app-functions",
    
    "relUrl": "/no-rNO/user/app-functions.html#enabling-app-functions"
  },"33": {
    "doc": "App Functions",
    "title": "Privacy",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/app-functions.html#privacy",
    
    "relUrl": "/no-rNO/user/app-functions.html#privacy"
  },"34": {
    "doc": "App Functions",
    "title": "Related Topics",
    "content": ". | Messages & Channels — sending messages directly in the app | Nodes — the node list the read functions draw from | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/app-functions.html#related-topics",
    
    "relUrl": "/no-rNO/user/app-functions.html#related-topics"
  },"35": {
    "doc": "App Functions",
    "title": "App Functions",
    "content": "App Functions expose Meshtastic capabilities to the Android system and to on-device AI assistants (such as Gemini) through the Android App Functions API. With them enabled, an assistant can discover and trigger mesh workflows for you — for example sending a message or checking your mesh status — without you opening the app. App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. App Functions let the system AI assistant act on your mesh; Chirpy is a conversational assistant inside the Meshtastic app itself. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/app-functions.html",
    
    "relUrl": "/hu-rHU/user/app-functions.html"
  },"36": {
    "doc": "App Functions",
    "title": "Enabling App Functions",
    "content": "Control App Functions from Settings → System AI. The screen has: . | A master toggle labeled “Allow AI access”, with the subtitle “Let system AI assistants (e.g. Gemini) discover and use mesh functions”. When off, no functions are exposed to the system. | An individual toggle for each function, so you can expose only the capabilities you want. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. The functions are grouped into a Write section (functions that change something or send data to your mesh) and a Read section (functions that only return information). The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Write Functions . | Function | What it does | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Read Functions . | Function | What it returns | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | The list of nodes on your mesh. | . | Get channel info | Information about your channels. | . | Get device status | Status of your connected radio. | . | Get node details | Detailed information about a specific node. | . | Get mesh metrics | Telemetry and metrics from your mesh. | . | Get recent messages | Recent messages from your conversations. | . | Get unread summary | A summary of unread messages. | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/app-functions.html#enabling-app-functions",
    
    "relUrl": "/hu-rHU/user/app-functions.html#enabling-app-functions"
  },"37": {
    "doc": "App Functions",
    "title": "Privacy",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/app-functions.html#privacy",
    
    "relUrl": "/hu-rHU/user/app-functions.html#privacy"
  },"38": {
    "doc": "App Functions",
    "title": "Related Topics",
    "content": ". | Messages & Channels — sending messages directly in the app | Nodes — the node list the read functions draw from | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/app-functions.html#related-topics",
    
    "relUrl": "/hu-rHU/user/app-functions.html#related-topics"
  },"39": {
    "doc": "Функции приложения",
    "title": "Функции приложения",
    "content": "Функции приложения предоставляют возможности Meshtastic системе Android и встроенным AI-помощникам (таким как Gemini) через API функций приложения Android. С их включением помощник может находить и запускать сетевые рабочие процессы за тебя — например, отправлять сообщение или проверять статус сети — не утруждая тебя открытием приложения. App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. Функции приложения позволяют системному AI-помощнику действовать с вашей сетью; Chirpy — это голосовой помощник прямо внутри приложения Meshtastic. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/app-functions.html",
    
    "relUrl": "/ru-rRU/user/app-functions.html"
  },"40": {
    "doc": "Функции приложения",
    "title": "Включение функций приложения",
    "content": "Control App Functions from Settings → System AI. Экран содержит: . | Главный переключатель с надписью “Разрешить доступ ИИ” и подзаголовком “Позволь системным ИИ-ассистентам (например, Gemini) обнаруживать и использовать функции сети”. Когда выключено, системе не доступны никакие функции. | Отдельный переключатель для каждой функции, чтобы включать только те возможности, которые хочешь. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. Функции разделены на секцию Запись (функции, которые что-то меняют или отправляют данные в сеть) и Чтение (только возвращают информацию). The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Функции записи . | Функция | Что она делает | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Функции записи . | Функция | Что она возвращает | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | Список узлов в твоей сети. | . | Get channel info | Информация о твоих каналах. | . | Get device status | Состояние подключенного радиоустройства. | . | Get node details | Подробная информация о конкретной ноде. | . | Get mesh metrics | Телеметрия и метрики твоей сети. | . | Get recent messages | Последние сообщения из твоих разговоров. | . | Get unread summary | Сводка непрочитанных сообщений. | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/app-functions.html#%D0%B2%D0%BA%D0%BB%D1%8E%D1%87%D0%B5%D0%BD%D0%B8%D0%B5-%D1%84%D1%83%D0%BD%D0%BA%D1%86%D0%B8%D0%B9-%D0%BF%D1%80%D0%B8%D0%BB%D0%BE%D0%B6%D0%B5%D0%BD%D0%B8%D1%8F",
    
    "relUrl": "/ru-rRU/user/app-functions.html#включение-функций-приложения"
  },"41": {
    "doc": "Функции приложения",
    "title": "Приватность",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/app-functions.html#%D0%BF%D1%80%D0%B8%D0%B2%D0%B0%D1%82%D0%BD%D0%BE%D1%81%D1%82%D1%8C",
    
    "relUrl": "/ru-rRU/user/app-functions.html#приватность"
  },"42": {
    "doc": "Функции приложения",
    "title": "Связанные темы",
    "content": ". | Сообщения и каналы — отправка сообщений прямо в приложении | Ноды — список нод, из которого берут данные функции чтения | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/app-functions.html#%D1%81%D0%B2%D1%8F%D0%B7%D0%B0%D0%BD%D0%BD%D1%8B%D0%B5-%D1%82%D0%B5%D0%BC%D1%8B",
    
    "relUrl": "/ru-rRU/user/app-functions.html#связанные-темы"
  },"43": {
    "doc": "Funkce aplikace",
    "title": "Funkce aplikace",
    "content": "App Functions expose Meshtastic capabilities to the Android system and to on-device AI assistants (such as Gemini) through the Android App Functions API. With them enabled, an assistant can discover and trigger mesh workflows for you — for example sending a message or checking your mesh status — without you opening the app. App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. App Functions let the system AI assistant act on your mesh; Chirpy is a conversational assistant inside the Meshtastic app itself. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/app-functions.html",
    
    "relUrl": "/cs-rCZ/user/app-functions.html"
  },"44": {
    "doc": "Funkce aplikace",
    "title": "Enabling App Functions",
    "content": "Control App Functions from Settings → System AI. The screen has: . | A master toggle labeled “Allow AI access”, with the subtitle “Let system AI assistants (e.g. Gemini) discover and use mesh functions”. When off, no functions are exposed to the system. | An individual toggle for each function, so you can expose only the capabilities you want. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. The functions are grouped into a Write section (functions that change something or send data to your mesh) and a Read section (functions that only return information). The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Write Functions . | Function | What it does | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Read Functions . | Function | What it returns | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | The list of nodes on your mesh. | . | Get channel info | Information about your channels. | . | Get device status | Status of your connected radio. | . | Get node details | Detailed information about a specific node. | . | Get mesh metrics | Telemetry and metrics from your mesh. | . | Get recent messages | Recent messages from your conversations. | . | Get unread summary | A summary of unread messages. | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/app-functions.html#enabling-app-functions",
    
    "relUrl": "/cs-rCZ/user/app-functions.html#enabling-app-functions"
  },"45": {
    "doc": "Funkce aplikace",
    "title": "Privacy",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/app-functions.html#privacy",
    
    "relUrl": "/cs-rCZ/user/app-functions.html#privacy"
  },"46": {
    "doc": "Funkce aplikace",
    "title": "Související témata",
    "content": ". | Messages & Channels — sending messages directly in the app | Nodes — the node list the read functions draw from | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/app-functions.html#souvisej%C3%ADc%C3%AD-t%C3%A9mata",
    
    "relUrl": "/cs-rCZ/user/app-functions.html#související-témata"
  },"47": {
    "doc": "App Functions",
    "title": "App Functions",
    "content": "App Functions expose Meshtastic capabilities to the Android system and to on-device AI assistants (such as Gemini) through the Android App Functions API. With them enabled, an assistant can discover and trigger mesh workflows for you — for example sending a message or checking your mesh status — without you opening the app. App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. App Functions let the system AI assistant act on your mesh; Chirpy is a conversational assistant inside the Meshtastic app itself. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/app-functions.html",
    
    "relUrl": "/bg-rBG/user/app-functions.html"
  },"48": {
    "doc": "App Functions",
    "title": "Enabling App Functions",
    "content": "Control App Functions from Settings → System AI. The screen has: . | A master toggle labeled “Allow AI access”, with the subtitle “Let system AI assistants (e.g. Gemini) discover and use mesh functions”. When off, no functions are exposed to the system. | An individual toggle for each function, so you can expose only the capabilities you want. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. The functions are grouped into a Write section (functions that change something or send data to your mesh) and a Read section (functions that only return information). The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Write Functions . | Функция | Какво прави | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Read Functions . | Функция | What it returns | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | The list of nodes on your mesh. | . | Get channel info | Information about your channels. | . | Get device status | Status of your connected radio. | . | Get node details | Detailed information about a specific node. | . | Get mesh metrics | Telemetry and metrics from your mesh. | . | Get recent messages | Recent messages from your conversations. | . | Get unread summary | A summary of unread messages. | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/app-functions.html#enabling-app-functions",
    
    "relUrl": "/bg-rBG/user/app-functions.html#enabling-app-functions"
  },"49": {
    "doc": "App Functions",
    "title": "Поверителност",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/app-functions.html#%D0%BF%D0%BE%D0%B2%D0%B5%D1%80%D0%B8%D1%82%D0%B5%D0%BB%D0%BD%D0%BE%D1%81%D1%82",
    
    "relUrl": "/bg-rBG/user/app-functions.html#поверителност"
  },"50": {
    "doc": "App Functions",
    "title": "Свързани теми",
    "content": ". | Messages & Channels — sending messages directly in the app | Nodes — the node list the read functions draw from | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/app-functions.html#%D1%81%D0%B2%D1%8A%D1%80%D0%B7%D0%B0%D0%BD%D0%B8-%D1%82%D0%B5%D0%BC%D0%B8",
    
    "relUrl": "/bg-rBG/user/app-functions.html#свързани-теми"
  },"51": {
    "doc": "App Functions",
    "title": "App Functions",
    "content": "App Functions expose Meshtastic capabilities to the Android system and to on-device AI assistants (such as Gemini) through the Android App Functions API. With them enabled, an assistant can discover and trigger mesh workflows for you — for example sending a message or checking your mesh status — without you opening the app. App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. App Functions let the system AI assistant act on your mesh; Chirpy is a conversational assistant inside the Meshtastic app itself. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/app-functions.html",
    
    "relUrl": "/ga-rIE/user/app-functions.html"
  },"52": {
    "doc": "App Functions",
    "title": "Enabling App Functions",
    "content": "Control App Functions from Settings → System AI. The screen has: . | A master toggle labeled “Allow AI access”, with the subtitle “Let system AI assistants (e.g. Gemini) discover and use mesh functions”. When off, no functions are exposed to the system. | An individual toggle for each function, so you can expose only the capabilities you want. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. The functions are grouped into a Write section (functions that change something or send data to your mesh) and a Read section (functions that only return information). The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Write Functions . | Function | What it does | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Read Functions . | Function | What it returns | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | The list of nodes on your mesh. | . | Get channel info | Information about your channels. | . | Get device status | Status of your connected radio. | . | Get node details | Detailed information about a specific node. | . | Get mesh metrics | Telemetry and metrics from your mesh. | . | Get recent messages | Recent messages from your conversations. | . | Get unread summary | A summary of unread messages. | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/app-functions.html#enabling-app-functions",
    
    "relUrl": "/ga-rIE/user/app-functions.html#enabling-app-functions"
  },"53": {
    "doc": "App Functions",
    "title": "Privacy",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/app-functions.html#privacy",
    
    "relUrl": "/ga-rIE/user/app-functions.html#privacy"
  },"54": {
    "doc": "App Functions",
    "title": "Related Topics",
    "content": ". | Messages & Channels — sending messages directly in the app | Nodes — the node list the read functions draw from | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/app-functions.html#related-topics",
    
    "relUrl": "/ga-rIE/user/app-functions.html#related-topics"
  },"55": {
    "doc": "App Functions",
    "title": "App Functions",
    "content": "App Functions expose Meshtastic capabilities to the Android system and to on-device AI assistants (such as Gemini) through the Android App Functions API. With them enabled, an assistant can discover and trigger mesh workflows for you — for example sending a message or checking your mesh status — without you opening the app. App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. App Functions let the system AI assistant act on your mesh; Chirpy is a conversational assistant inside the Meshtastic app itself. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/app-functions.html",
    
    "relUrl": "/fr-rCA/user/app-functions.html"
  },"56": {
    "doc": "App Functions",
    "title": "Enabling App Functions",
    "content": "Control App Functions from Settings → System AI. The screen has: . | A master toggle labeled “Allow AI access”, with the subtitle “Let system AI assistants (e.g. Gemini) discover and use mesh functions”. When off, no functions are exposed to the system. | An individual toggle for each function, so you can expose only the capabilities you want. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. The functions are grouped into a Write section (functions that change something or send data to your mesh) and a Read section (functions that only return information). The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Write Functions . | Function | What it does | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Read Functions . | Function | What it returns | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | The list of nodes on your mesh. | . | Get channel info | Information about your channels. | . | Get device status | Status of your connected radio. | . | Get node details | Detailed information about a specific node. | . | Get mesh metrics | Telemetry and metrics from your mesh. | . | Get recent messages | Recent messages from your conversations. | . | Get unread summary | A summary of unread messages. | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/app-functions.html#enabling-app-functions",
    
    "relUrl": "/fr-rCA/user/app-functions.html#enabling-app-functions"
  },"57": {
    "doc": "App Functions",
    "title": "Privacy",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/app-functions.html#privacy",
    
    "relUrl": "/fr-rCA/user/app-functions.html#privacy"
  },"58": {
    "doc": "App Functions",
    "title": "Related Topics",
    "content": ". | Messages & Channels — sending messages directly in the app | Nodes — the node list the read functions draw from | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/app-functions.html#related-topics",
    
    "relUrl": "/fr-rCA/user/app-functions.html#related-topics"
  },"59": {
    "doc": "App Functions",
    "title": "App Functions",
    "content": "App Functions expose Meshtastic capabilities to the Android system and to on-device AI assistants (such as Gemini) through the Android App Functions API. With them enabled, an assistant can discover and trigger mesh workflows for you — for example sending a message or checking your mesh status — without you opening the app. App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. App Functions let the system AI assistant act on your mesh; Chirpy is a conversational assistant inside the Meshtastic app itself. ",
    "url": "/Meshtastic-Android/main/srp/user/app-functions.html",
    
    "relUrl": "/srp/user/app-functions.html"
  },"60": {
    "doc": "App Functions",
    "title": "Enabling App Functions",
    "content": "Control App Functions from Settings → System AI. The screen has: . | A master toggle labeled “Allow AI access”, with the subtitle “Let system AI assistants (e.g. Gemini) discover and use mesh functions”. When off, no functions are exposed to the system. | An individual toggle for each function, so you can expose only the capabilities you want. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. The functions are grouped into a Write section (functions that change something or send data to your mesh) and a Read section (functions that only return information). The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Write Functions . | Function | What it does | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Read Functions . | Function | What it returns | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | The list of nodes on your mesh. | . | Get channel info | Information about your channels. | . | Get device status | Status of your connected radio. | . | Get node details | Detailed information about a specific node. | . | Get mesh metrics | Telemetry and metrics from your mesh. | . | Get recent messages | Recent messages from your conversations. | . | Get unread summary | A summary of unread messages. | . ",
    "url": "/Meshtastic-Android/main/srp/user/app-functions.html#enabling-app-functions",
    
    "relUrl": "/srp/user/app-functions.html#enabling-app-functions"
  },"61": {
    "doc": "App Functions",
    "title": "Privacy",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/srp/user/app-functions.html#privacy",
    
    "relUrl": "/srp/user/app-functions.html#privacy"
  },"62": {
    "doc": "App Functions",
    "title": "Related Topics",
    "content": ". | Messages & Channels — sending messages directly in the app | Nodes — the node list the read functions draw from | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/srp/user/app-functions.html#related-topics",
    
    "relUrl": "/srp/user/app-functions.html#related-topics"
  },"63": {
    "doc": "App Functions",
    "title": "App Functions",
    "content": "App Functions expose Meshtastic capabilities to the Android system and to on-device AI assistants (such as Gemini) through the Android App Functions API. With them enabled, an assistant can discover and trigger mesh workflows for you — for example sending a message or checking your mesh status — without you opening the app. App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. App Functions let the system AI assistant act on your mesh; Chirpy is a conversational assistant inside the Meshtastic app itself. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/app-functions.html",
    
    "relUrl": "/ca-rES/user/app-functions.html"
  },"64": {
    "doc": "App Functions",
    "title": "Enabling App Functions",
    "content": "Control App Functions from Settings → System AI. The screen has: . | A master toggle labeled “Allow AI access”, with the subtitle “Let system AI assistants (e.g. Gemini) discover and use mesh functions”. When off, no functions are exposed to the system. | An individual toggle for each function, so you can expose only the capabilities you want. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. The functions are grouped into a Write section (functions that change something or send data to your mesh) and a Read section (functions that only return information). The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Write Functions . | Function | What it does | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Read Functions . | Function | What it returns | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | The list of nodes on your mesh. | . | Get channel info | Information about your channels. | . | Get device status | Status of your connected radio. | . | Get node details | Detailed information about a specific node. | . | Get mesh metrics | Telemetry and metrics from your mesh. | . | Get recent messages | Recent messages from your conversations. | . | Get unread summary | A summary of unread messages. | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/app-functions.html#enabling-app-functions",
    
    "relUrl": "/ca-rES/user/app-functions.html#enabling-app-functions"
  },"65": {
    "doc": "App Functions",
    "title": "Privacy",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/app-functions.html#privacy",
    
    "relUrl": "/ca-rES/user/app-functions.html#privacy"
  },"66": {
    "doc": "App Functions",
    "title": "Related Topics",
    "content": ". | Messages & Channels — sending messages directly in the app | Nodes — the node list the read functions draw from | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/app-functions.html#related-topics",
    
    "relUrl": "/ca-rES/user/app-functions.html#related-topics"
  },"67": {
    "doc": "App Functions",
    "title": "App Functions",
    "content": "App Functions expose Meshtastic capabilities to the Android system and to on-device AI assistants (such as Gemini) through the Android App Functions API. With them enabled, an assistant can discover and trigger mesh workflows for you — for example sending a message or checking your mesh status — without you opening the app. App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. App Functions let the system AI assistant act on your mesh; Chirpy is a conversational assistant inside the Meshtastic app itself. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/app-functions.html",
    
    "relUrl": "/ko-rKR/user/app-functions.html"
  },"68": {
    "doc": "App Functions",
    "title": "Enabling App Functions",
    "content": "Control App Functions from Settings → System AI. The screen has: . | A master toggle labeled “Allow AI access”, with the subtitle “Let system AI assistants (e.g. Gemini) discover and use mesh functions”. When off, no functions are exposed to the system. | An individual toggle for each function, so you can expose only the capabilities you want. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. The functions are grouped into a Write section (functions that change something or send data to your mesh) and a Read section (functions that only return information). The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Write Functions . | Function | What it does | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Read Functions . | Function | What it returns | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | The list of nodes on your mesh. | . | Get channel info | Information about your channels. | . | Get device status | Status of your connected radio. | . | Get node details | Detailed information about a specific node. | . | Get mesh metrics | Telemetry and metrics from your mesh. | . | Get recent messages | Recent messages from your conversations. | . | Get unread summary | A summary of unread messages. | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/app-functions.html#enabling-app-functions",
    
    "relUrl": "/ko-rKR/user/app-functions.html#enabling-app-functions"
  },"69": {
    "doc": "App Functions",
    "title": "Privacy",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/app-functions.html#privacy",
    
    "relUrl": "/ko-rKR/user/app-functions.html#privacy"
  },"70": {
    "doc": "App Functions",
    "title": "Related Topics",
    "content": ". | Messages & Channels — sending messages directly in the app | Nodes — the node list the read functions draw from | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/app-functions.html#related-topics",
    
    "relUrl": "/ko-rKR/user/app-functions.html#related-topics"
  },"71": {
    "doc": "App Functions",
    "title": "App Functions",
    "content": "App Functions expose Meshtastic capabilities to the Android system and to on-device AI assistants (such as Gemini) through the Android App Functions API. With them enabled, an assistant can discover and trigger mesh workflows for you — for example sending a message or checking your mesh status — without you opening the app. App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. App Functions let the system AI assistant act on your mesh; Chirpy is a conversational assistant inside the Meshtastic app itself. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/app-functions.html",
    
    "relUrl": "/sv-rSE/user/app-functions.html"
  },"72": {
    "doc": "App Functions",
    "title": "Enabling App Functions",
    "content": "Control App Functions from Settings → System AI. The screen has: . | A master toggle labeled “Allow AI access”, with the subtitle “Let system AI assistants (e.g. Gemini) discover and use mesh functions”. When off, no functions are exposed to the system. | An individual toggle for each function, so you can expose only the capabilities you want. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. The functions are grouped into a Write section (functions that change something or send data to your mesh) and a Read section (functions that only return information). The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Write Functions . | Function | What it does | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Read Functions . | Function | What it returns | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | The list of nodes on your mesh. | . | Get channel info | Information about your channels. | . | Get device status | Status of your connected radio. | . | Get node details | Detailed information about a specific node. | . | Get mesh metrics | Telemetry and metrics from your mesh. | . | Get recent messages | Recent messages from your conversations. | . | Get unread summary | A summary of unread messages. | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/app-functions.html#enabling-app-functions",
    
    "relUrl": "/sv-rSE/user/app-functions.html#enabling-app-functions"
  },"73": {
    "doc": "App Functions",
    "title": "Privacy",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/app-functions.html#privacy",
    
    "relUrl": "/sv-rSE/user/app-functions.html#privacy"
  },"74": {
    "doc": "App Functions",
    "title": "Related Topics",
    "content": ". | Messages & Channels — sending messages directly in the app | Nodes — the node list the read functions draw from | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/app-functions.html#related-topics",
    
    "relUrl": "/sv-rSE/user/app-functions.html#related-topics"
  },"75": {
    "doc": "App Functions",
    "title": "App Functions",
    "content": "App Functions expose Meshtastic capabilities to the Android system and to on-device AI assistants (such as Gemini) through the Android App Functions API. With them enabled, an assistant can discover and trigger mesh workflows for you — for example sending a message or checking your mesh status — without you opening the app. App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. App Functions let the system AI assistant act on your mesh; Chirpy is a conversational assistant inside the Meshtastic app itself. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/app-functions.html",
    
    "relUrl": "/ht-rHT/user/app-functions.html"
  },"76": {
    "doc": "App Functions",
    "title": "Enabling App Functions",
    "content": "Control App Functions from Settings → System AI. The screen has: . | A master toggle labeled “Allow AI access”, with the subtitle “Let system AI assistants (e.g. Gemini) discover and use mesh functions”. When off, no functions are exposed to the system. | An individual toggle for each function, so you can expose only the capabilities you want. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. The functions are grouped into a Write section (functions that change something or send data to your mesh) and a Read section (functions that only return information). The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Write Functions . | Function | What it does | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Read Functions . | Function | What it returns | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | The list of nodes on your mesh. | . | Get channel info | Information about your channels. | . | Get device status | Status of your connected radio. | . | Get node details | Detailed information about a specific node. | . | Get mesh metrics | Telemetry and metrics from your mesh. | . | Get recent messages | Recent messages from your conversations. | . | Get unread summary | A summary of unread messages. | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/app-functions.html#enabling-app-functions",
    
    "relUrl": "/ht-rHT/user/app-functions.html#enabling-app-functions"
  },"77": {
    "doc": "App Functions",
    "title": "Privacy",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/app-functions.html#privacy",
    
    "relUrl": "/ht-rHT/user/app-functions.html#privacy"
  },"78": {
    "doc": "App Functions",
    "title": "Related Topics",
    "content": ". | Messages & Channels — sending messages directly in the app | Nodes — the node list the read functions draw from | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/app-functions.html#related-topics",
    
    "relUrl": "/ht-rHT/user/app-functions.html#related-topics"
  },"79": {
    "doc": "App Functions",
    "title": "App Functions",
    "content": "App Functions expose Meshtastic capabilities to the Android system and to on-device AI assistants (such as Gemini) through the Android App Functions API. With them enabled, an assistant can discover and trigger mesh workflows for you — for example sending a message or checking your mesh status — without you opening the app. App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. App Functions let the system AI assistant act on your mesh; Chirpy is a conversational assistant inside the Meshtastic app itself. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/app-functions.html",
    
    "relUrl": "/sr-rLatn/user/app-functions.html"
  },"80": {
    "doc": "App Functions",
    "title": "Enabling App Functions",
    "content": "Control App Functions from Settings → System AI. The screen has: . | A master toggle labeled “Allow AI access”, with the subtitle “Let system AI assistants (e.g. Gemini) discover and use mesh functions”. When off, no functions are exposed to the system. | An individual toggle for each function, so you can expose only the capabilities you want. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. The functions are grouped into a Write section (functions that change something or send data to your mesh) and a Read section (functions that only return information). The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Write Functions . | Function | What it does | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Read Functions . | Function | What it returns | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | The list of nodes on your mesh. | . | Get channel info | Information about your channels. | . | Get device status | Status of your connected radio. | . | Get node details | Detailed information about a specific node. | . | Get mesh metrics | Telemetry and metrics from your mesh. | . | Get recent messages | Recent messages from your conversations. | . | Get unread summary | A summary of unread messages. | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/app-functions.html#enabling-app-functions",
    
    "relUrl": "/sr-rLatn/user/app-functions.html#enabling-app-functions"
  },"81": {
    "doc": "App Functions",
    "title": "Privacy",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/app-functions.html#privacy",
    
    "relUrl": "/sr-rLatn/user/app-functions.html#privacy"
  },"82": {
    "doc": "App Functions",
    "title": "Related Topics",
    "content": ". | Messages & Channels — sending messages directly in the app | Nodes — the node list the read functions draw from | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/app-functions.html#related-topics",
    
    "relUrl": "/sr-rLatn/user/app-functions.html#related-topics"
  },"83": {
    "doc": "App Functions",
    "title": "App Functions",
    "content": "App Functions expose Meshtastic capabilities to the Android system and to on-device AI assistants (such as Gemini) through the Android App Functions API. With them enabled, an assistant can discover and trigger mesh workflows for you — for example sending a message or checking your mesh status — without you opening the app. App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. App Functions let the system AI assistant act on your mesh; Chirpy is a conversational assistant inside the Meshtastic app itself. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/app-functions.html",
    
    "relUrl": "/nl-rNL/user/app-functions.html"
  },"84": {
    "doc": "App Functions",
    "title": "Enabling App Functions",
    "content": "Control App Functions from Settings → System AI. The screen has: . | A master toggle labeled “Allow AI access”, with the subtitle “Let system AI assistants (e.g. Gemini) discover and use mesh functions”. When off, no functions are exposed to the system. | An individual toggle for each function, so you can expose only the capabilities you want. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. The functions are grouped into a Write section (functions that change something or send data to your mesh) and a Read section (functions that only return information). The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Write Functions . | Function | What it does | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Read Functions . | Function | What it returns | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | The list of nodes on your mesh. | . | Get channel info | Information about your channels. | . | Get device status | Status of your connected radio. | . | Get node details | Detailed information about a specific node. | . | Get mesh metrics | Telemetry and metrics from your mesh. | . | Get recent messages | Recent messages from your conversations. | . | Get unread summary | A summary of unread messages. | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/app-functions.html#enabling-app-functions",
    
    "relUrl": "/nl-rNL/user/app-functions.html#enabling-app-functions"
  },"85": {
    "doc": "App Functions",
    "title": "Privacy",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/app-functions.html#privacy",
    
    "relUrl": "/nl-rNL/user/app-functions.html#privacy"
  },"86": {
    "doc": "App Functions",
    "title": "Related Topics",
    "content": ". | Messages & Channels — sending messages directly in the app | Nodes — the node list the read functions draw from | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/app-functions.html#related-topics",
    
    "relUrl": "/nl-rNL/user/app-functions.html#related-topics"
  },"87": {
    "doc": "App Functions",
    "title": "App Functions",
    "content": "App Functions expose Meshtastic capabilities to the Android system and to on-device AI assistants (such as Gemini) through the Android App Functions API. With them enabled, an assistant can discover and trigger mesh workflows for you — for example sending a message or checking your mesh status — without you opening the app. App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. App Functions let the system AI assistant act on your mesh; Chirpy is a conversational assistant inside the Meshtastic app itself. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/app-functions.html",
    
    "relUrl": "/uk-rUA/user/app-functions.html"
  },"88": {
    "doc": "App Functions",
    "title": "Enabling App Functions",
    "content": "Control App Functions from Settings → System AI. The screen has: . | A master toggle labeled “Allow AI access”, with the subtitle “Let system AI assistants (e.g. Gemini) discover and use mesh functions”. When off, no functions are exposed to the system. | An individual toggle for each function, so you can expose only the capabilities you want. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. The functions are grouped into a Write section (functions that change something or send data to your mesh) and a Read section (functions that only return information). The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Write Functions . | Function | What it does | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Read Functions . | Function | What it returns | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | The list of nodes on your mesh. | . | Get channel info | Information about your channels. | . | Get device status | Status of your connected radio. | . | Get node details | Detailed information about a specific node. | . | Get mesh metrics | Telemetry and metrics from your mesh. | . | Get recent messages | Recent messages from your conversations. | . | Get unread summary | A summary of unread messages. | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/app-functions.html#enabling-app-functions",
    
    "relUrl": "/uk-rUA/user/app-functions.html#enabling-app-functions"
  },"89": {
    "doc": "App Functions",
    "title": "Privacy",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/app-functions.html#privacy",
    
    "relUrl": "/uk-rUA/user/app-functions.html#privacy"
  },"90": {
    "doc": "App Functions",
    "title": "Related Topics",
    "content": ". | Messages & Channels — sending messages directly in the app | Nodes — the node list the read functions draw from | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/app-functions.html#related-topics",
    
    "relUrl": "/uk-rUA/user/app-functions.html#related-topics"
  },"91": {
    "doc": "Sovellustoiminnot",
    "title": "Sovellustoiminnot",
    "content": "Sovellustoiminnot tuovat Meshtastic-ominaisuudet Android-järjestelmälle ja laitteessa toimiville tekoälyavustajille (kuten Gemini) Android App Functions -rajapinnan kautta. Kun ne ovat käytössä, avustaja voi löytää ja käynnistää mesh-toimintoja puolestasi — esimerkiksi lähettää viestin tai tarkistaa mesh-tilan — ilman että avaat sovellusta. Sovellustoiminnot ovat käytettävissä vain Google-version Android-julkaisuissa. ℹ️ Huomautus: Tämä on eri asia kuin sovelluksen sisäinen Chirpy-avustaja. Sovellustoiminnot mahdollistavat sen, että järjestelmän tekoälyavustaja voi toimia mesh-verkon kautta; Chirpy on Meshtastic-sovelluksen sisäinen keskusteluavustaja. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/app-functions.html",
    
    "relUrl": "/fi-rFI/user/app-functions.html"
  },"92": {
    "doc": "Sovellustoiminnot",
    "title": "Sovellustoimintojen käyttöönotto",
    "content": "Hallitse sovellustoimintoja kohdasta Asetukset → Järjestelmätekoäly. Näyttö sisältää: . | Pääkytkin, nimeltään “Salli tekoälyn käyttö”, ja alaotsikko “Salli järjestelmän tekoälyavustajien (esim. Gemini) löytää ja käyttää mesh-toimintoja”. Kun pois käytöstä, toimintoja ei jaeta järjestelmälle. | Yksittäinen kytkin jokaiselle toiminnolle, jotta voit paljastaa vain haluamasi ominaisuudet. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. Toiminnot on jaettu Kirjoita-osioon (toiminnot, jotka muuttavat jotakin tai lähettävät dataa mesh-verkkoon) ja Lue-osioon (toiminnot, jotka palauttavat vain tietoa). The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Kirjoitustoiminnot . | Toiminto | Mitä se tekee | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Lukutoiminnot . | Toiminto | Mitä se palauttaa | . | Get mesh status | Onko yhteys radioon muodostettu ja kuinka monta radiota on verkossa. | . | Get node list | Mesh-verkon radiolista. | . | Get channel info | Tietoa kanavistasi. | . | Get device status | Yhdistetyn radion tila. | . | Get node details | Yksityiskohtaiset tiedot tietystä radiosta. | . | Get mesh metrics | Mesh-verkon telemetria ja metriikat. | . | Get recent messages | Viimeisimmät viestisi keskusteluista. | . | Get unread summary | Yhteenveto lukemattomista viesteistä. | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/app-functions.html#sovellustoimintojen-k%C3%A4ytt%C3%B6%C3%B6notto",
    
    "relUrl": "/fi-rFI/user/app-functions.html#sovellustoimintojen-käyttöönotto"
  },"93": {
    "doc": "Sovellustoiminnot",
    "title": "Yksityisyys",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/app-functions.html#yksityisyys",
    
    "relUrl": "/fi-rFI/user/app-functions.html#yksityisyys"
  },"94": {
    "doc": "Sovellustoiminnot",
    "title": "Aiheeseen liittyvät aiheet",
    "content": ". | Viestit ja kanavat — viestien lähettäminen suoraan sovelluksessa | Radiot — radiolista, josta lukutoiminnot hakevat tiedot | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/app-functions.html#aiheeseen-liittyv%C3%A4t-aiheet",
    
    "relUrl": "/fi-rFI/user/app-functions.html#aiheeseen-liittyvät-aiheet"
  },"95": {
    "doc": "App Functions",
    "title": "App Functions",
    "content": "App Functions expose Meshtastic capabilities to the Android system and to on-device AI assistants (such as Gemini) through the Android App Functions API. With them enabled, an assistant can discover and trigger mesh workflows for you — for example sending a message or checking your mesh status — without you opening the app. App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. App Functions let the system AI assistant act on your mesh; Chirpy is a conversational assistant inside the Meshtastic app itself. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/app-functions.html",
    
    "relUrl": "/is-rIS/user/app-functions.html"
  },"96": {
    "doc": "App Functions",
    "title": "Enabling App Functions",
    "content": "Control App Functions from Settings → System AI. The screen has: . | A master toggle labeled “Allow AI access”, with the subtitle “Let system AI assistants (e.g. Gemini) discover and use mesh functions”. When off, no functions are exposed to the system. | An individual toggle for each function, so you can expose only the capabilities you want. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. The functions are grouped into a Write section (functions that change something or send data to your mesh) and a Read section (functions that only return information). The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Write Functions . | Function | What it does | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Read Functions . | Function | What it returns | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | The list of nodes on your mesh. | . | Get channel info | Information about your channels. | . | Get device status | Status of your connected radio. | . | Get node details | Detailed information about a specific node. | . | Get mesh metrics | Telemetry and metrics from your mesh. | . | Get recent messages | Recent messages from your conversations. | . | Get unread summary | A summary of unread messages. | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/app-functions.html#enabling-app-functions",
    
    "relUrl": "/is-rIS/user/app-functions.html#enabling-app-functions"
  },"97": {
    "doc": "App Functions",
    "title": "Privacy",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/app-functions.html#privacy",
    
    "relUrl": "/is-rIS/user/app-functions.html#privacy"
  },"98": {
    "doc": "App Functions",
    "title": "Related Topics",
    "content": ". | Messages & Channels — sending messages directly in the app | Nodes — the node list the read functions draw from | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/app-functions.html#related-topics",
    
    "relUrl": "/is-rIS/user/app-functions.html#related-topics"
  },"99": {
    "doc": "App Functions",
    "title": "App Functions",
    "content": "App Functions expose Meshtastic capabilities to the Android system and to on-device AI assistants (such as Gemini) through the Android App Functions API. With them enabled, an assistant can discover and trigger mesh workflows for you — for example sending a message or checking your mesh status — without you opening the app. App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. App Functions let the system AI assistant act on your mesh; Chirpy is a conversational assistant inside the Meshtastic app itself. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/app-functions.html",
    
    "relUrl": "/lt-rLT/user/app-functions.html"
  },"100": {
    "doc": "App Functions",
    "title": "Enabling App Functions",
    "content": "Control App Functions from Settings → System AI. The screen has: . | A master toggle labeled “Allow AI access”, with the subtitle “Let system AI assistants (e.g. Gemini) discover and use mesh functions”. When off, no functions are exposed to the system. | An individual toggle for each function, so you can expose only the capabilities you want. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. The functions are grouped into a Write section (functions that change something or send data to your mesh) and a Read section (functions that only return information). The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Write Functions . | Function | What it does | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Read Functions . | Function | What it returns | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | The list of nodes on your mesh. | . | Get channel info | Information about your channels. | . | Get device status | Status of your connected radio. | . | Get node details | Detailed information about a specific node. | . | Get mesh metrics | Telemetry and metrics from your mesh. | . | Get recent messages | Recent messages from your conversations. | . | Get unread summary | A summary of unread messages. | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/app-functions.html#enabling-app-functions",
    
    "relUrl": "/lt-rLT/user/app-functions.html#enabling-app-functions"
  },"101": {
    "doc": "App Functions",
    "title": "Privacy",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/app-functions.html#privacy",
    
    "relUrl": "/lt-rLT/user/app-functions.html#privacy"
  },"102": {
    "doc": "App Functions",
    "title": "Related Topics",
    "content": ". | Messages & Channels — sending messages directly in the app | Nodes — the node list the read functions draw from | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/app-functions.html#related-topics",
    
    "relUrl": "/lt-rLT/user/app-functions.html#related-topics"
  },"103": {
    "doc": "App Functions",
    "title": "App Functions",
    "content": "App Functions expose Meshtastic capabilities to the Android system and to on-device AI assistants (such as Gemini) through the Android App Functions API. With them enabled, an assistant can discover and trigger mesh workflows for you — for example sending a message or checking your mesh status — without you opening the app. App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. App Functions let the system AI assistant act on your mesh; Chirpy is a conversational assistant inside the Meshtastic app itself. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/app-functions.html",
    
    "relUrl": "/gl-rES/user/app-functions.html"
  },"104": {
    "doc": "App Functions",
    "title": "Enabling App Functions",
    "content": "Control App Functions from Settings → System AI. The screen has: . | A master toggle labeled “Allow AI access”, with the subtitle “Let system AI assistants (e.g. Gemini) discover and use mesh functions”. When off, no functions are exposed to the system. | An individual toggle for each function, so you can expose only the capabilities you want. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. The functions are grouped into a Write section (functions that change something or send data to your mesh) and a Read section (functions that only return information). The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Write Functions . | Function | What it does | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Read Functions . | Function | What it returns | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | The list of nodes on your mesh. | . | Get channel info | Information about your channels. | . | Get device status | Status of your connected radio. | . | Get node details | Detailed information about a specific node. | . | Get mesh metrics | Telemetry and metrics from your mesh. | . | Get recent messages | Recent messages from your conversations. | . | Get unread summary | A summary of unread messages. | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/app-functions.html#enabling-app-functions",
    
    "relUrl": "/gl-rES/user/app-functions.html#enabling-app-functions"
  },"105": {
    "doc": "App Functions",
    "title": "Privacy",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/app-functions.html#privacy",
    
    "relUrl": "/gl-rES/user/app-functions.html#privacy"
  },"106": {
    "doc": "App Functions",
    "title": "Related Topics",
    "content": ". | Messages & Channels — sending messages directly in the app | Nodes — the node list the read functions draw from | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/app-functions.html#related-topics",
    
    "relUrl": "/gl-rES/user/app-functions.html#related-topics"
  },"107": {
    "doc": "アプリ機能",
    "title": "アプリ機能",
    "content": "アプリ機能は、Android App Functions API を通じて、Meshtastic の機能を Android システムやオンデバイスの AI アシスタント（Gemini など）に公開します。有効にすると、アシスタントがあなたに代わってメッシュのワークフロー（例：メッセージの送信やメッシュ状態の確認）を見つけて実行でき、アプリを開く必要がありません。 App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. アプリ機能はシステムの AI アシスタントがあなたのメッシュを操作できるようにするもので、Chirpy は Meshtastic アプリ内の対話型アシスタントです。 . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/app-functions.html",
    
    "relUrl": "/ja-rJP/user/app-functions.html"
  },"108": {
    "doc": "アプリ機能",
    "title": "アプリ機能を有効にする",
    "content": "Control App Functions from Settings → System AI. この画面には次があります： . | 「AI のアクセスを許可」というラベルのマスタートグル。サブタイトルは 「システムの AI アシスタント（例：Gemini）がメッシュ機能を見つけて使えるようにする」 です。オフの場合、システムには機能が一切公開されません。 | 各機能ごとの個別トグル。公開したい機能だけを公開できます。 | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. 機能は、書き込みセクション（何かを変更したり、メッシュにデータを送信したりする機能）と、読み取りセクション（情報を返すだけの機能）に分かれています。 . The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. 書き込み機能 . | 機能 | 内容 | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . 読み取り機能 . | 機能 | 返す内容 | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | メッシュ上のノードのリスト。 | . | Get channel info | チャンネルに関する情報。 | . | Get device status | 接続中の無線機の状態。 | . | Get node details | 特定のノードに関する詳細情報。 | . | Get mesh metrics | メッシュからのテレメトリとメトリクス。 | . | Get recent messages | 会話からの最近のメッセージ。 | . | Get unread summary | 未読メッセージの概要。 | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/app-functions.html#%E3%82%A2%E3%83%97%E3%83%AA%E6%A9%9F%E8%83%BD%E3%82%92%E6%9C%89%E5%8A%B9%E3%81%AB%E3%81%99%E3%82%8B",
    
    "relUrl": "/ja-rJP/user/app-functions.html#アプリ機能を有効にする"
  },"109": {
    "doc": "アプリ機能",
    "title": "プライバシー",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/app-functions.html#%E3%83%97%E3%83%A9%E3%82%A4%E3%83%90%E3%82%B7%E3%83%BC",
    
    "relUrl": "/ja-rJP/user/app-functions.html#プライバシー"
  },"110": {
    "doc": "アプリ機能",
    "title": "関連トピック",
    "content": ". | メッセージとチャンネル：アプリで直接メッセージを送信する | ノード：読み取り機能が参照するノードリスト | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/app-functions.html#%E9%96%A2%E9%80%A3%E3%83%88%E3%83%94%E3%83%83%E3%82%AF",
    
    "relUrl": "/ja-rJP/user/app-functions.html#関連トピック"
  },"111": {
    "doc": "App Functions",
    "title": "App Functions",
    "content": "App Functions expose Meshtastic capabilities to the Android system and to on-device AI assistants (such as Gemini) through the Android App Functions API. Wenn diese aktiviert sind, kann ein Assistent Mesh-Workflows für Sie finden und auslösen – zum Beispiel das Senden einer Nachricht oder das Überprüfen Ihres Mesh-Status –, ohne dass Sie die App öffnen müssen. App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. App Functions let the system AI assistant act on your mesh; Chirpy is a conversational assistant inside the Meshtastic app itself. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/app-functions.html",
    
    "relUrl": "/de-rDE/user/app-functions.html"
  },"112": {
    "doc": "App Functions",
    "title": "Enabling App Functions",
    "content": "Control App Functions from Settings → System AI. The screen has: . | A master toggle labeled “Allow AI access”, with the subtitle “Let system AI assistants (e.g. Gemini) discover and use mesh functions”. When off, no functions are exposed to the system. | An individual toggle for each function, so you can expose only the capabilities you want. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. Die Funktionen sind in einen Schreib-Bereich (Funktionen, die etwas ändern oder Daten an Ihr Mesh senden) und einen Lese-Bereich (Funktionen, die lediglich Informationen zurückgeben) unterteilt. The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Write Functions . | Funktion | What it does | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Read Functions . | Funktion | What it returns | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | The list of nodes on your mesh. | . | Get channel info | Information about your channels. | . | Get device status | Status of your connected radio. | . | Get node details | Detailed information about a specific node. | . | Get mesh metrics | Telemetry and metrics from your mesh. | . | Get recent messages | Recent messages from your conversations. | . | Get unread summary | A summary of unread messages. | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/app-functions.html#enabling-app-functions",
    
    "relUrl": "/de-rDE/user/app-functions.html#enabling-app-functions"
  },"113": {
    "doc": "App Functions",
    "title": "Datenschutz",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/app-functions.html#datenschutz",
    
    "relUrl": "/de-rDE/user/app-functions.html#datenschutz"
  },"114": {
    "doc": "App Functions",
    "title": "Verwandte Themen",
    "content": ". | Messages & Channels — sending messages directly in the app | Nodes — the node list the read functions draw from | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/app-functions.html#verwandte-themen",
    
    "relUrl": "/de-rDE/user/app-functions.html#verwandte-themen"
  },"115": {
    "doc": "App Functions",
    "title": "App Functions",
    "content": "App Functions expose Meshtastic capabilities to the Android system and to on-device AI assistants (such as Gemini) through the Android App Functions API. With them enabled, an assistant can discover and trigger mesh workflows for you — for example sending a message or checking your mesh status — without you opening the app. App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. App Functions let the system AI assistant act on your mesh; Chirpy is a conversational assistant inside the Meshtastic app itself. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/app-functions.html",
    
    "relUrl": "/ar-rSA/user/app-functions.html"
  },"116": {
    "doc": "App Functions",
    "title": "Enabling App Functions",
    "content": "Control App Functions from Settings → System AI. The screen has: . | A master toggle labeled “Allow AI access”, with the subtitle “Let system AI assistants (e.g. Gemini) discover and use mesh functions”. When off, no functions are exposed to the system. | An individual toggle for each function, so you can expose only the capabilities you want. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. The functions are grouped into a Write section (functions that change something or send data to your mesh) and a Read section (functions that only return information). The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Write Functions . | Function | What it does | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Read Functions . | Function | What it returns | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | The list of nodes on your mesh. | . | Get channel info | Information about your channels. | . | Get device status | Status of your connected radio. | . | Get node details | Detailed information about a specific node. | . | Get mesh metrics | Telemetry and metrics from your mesh. | . | Get recent messages | Recent messages from your conversations. | . | Get unread summary | A summary of unread messages. | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/app-functions.html#enabling-app-functions",
    
    "relUrl": "/ar-rSA/user/app-functions.html#enabling-app-functions"
  },"117": {
    "doc": "App Functions",
    "title": "Privacy",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/app-functions.html#privacy",
    
    "relUrl": "/ar-rSA/user/app-functions.html#privacy"
  },"118": {
    "doc": "App Functions",
    "title": "Related Topics",
    "content": ". | Messages & Channels — sending messages directly in the app | Nodes — the node list the read functions draw from | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/app-functions.html#related-topics",
    
    "relUrl": "/ar-rSA/user/app-functions.html#related-topics"
  },"119": {
    "doc": "App Functions",
    "title": "App Functions",
    "content": "App Functions expose Meshtastic capabilities to the Android system and to on-device AI assistants (such as Gemini) through the Android App Functions API. With them enabled, an assistant can discover and trigger mesh workflows for you — for example sending a message or checking your mesh status — without you opening the app. App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. App Functions let the system AI assistant act on your mesh; Chirpy is a conversational assistant inside the Meshtastic app itself. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/app-functions.html",
    
    "relUrl": "/hr-rHR/user/app-functions.html"
  },"120": {
    "doc": "App Functions",
    "title": "Enabling App Functions",
    "content": "Control App Functions from Settings → System AI. The screen has: . | A master toggle labeled “Allow AI access”, with the subtitle “Let system AI assistants (e.g. Gemini) discover and use mesh functions”. When off, no functions are exposed to the system. | An individual toggle for each function, so you can expose only the capabilities you want. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. The functions are grouped into a Write section (functions that change something or send data to your mesh) and a Read section (functions that only return information). The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Write Functions . | Function | What it does | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Read Functions . | Function | What it returns | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | The list of nodes on your mesh. | . | Get channel info | Information about your channels. | . | Get device status | Status of your connected radio. | . | Get node details | Detailed information about a specific node. | . | Get mesh metrics | Telemetry and metrics from your mesh. | . | Get recent messages | Recent messages from your conversations. | . | Get unread summary | A summary of unread messages. | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/app-functions.html#enabling-app-functions",
    
    "relUrl": "/hr-rHR/user/app-functions.html#enabling-app-functions"
  },"121": {
    "doc": "App Functions",
    "title": "Privacy",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/app-functions.html#privacy",
    
    "relUrl": "/hr-rHR/user/app-functions.html#privacy"
  },"122": {
    "doc": "App Functions",
    "title": "Related Topics",
    "content": ". | Messages & Channels — sending messages directly in the app | Nodes — the node list the read functions draw from | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/app-functions.html#related-topics",
    
    "relUrl": "/hr-rHR/user/app-functions.html#related-topics"
  },"123": {
    "doc": "App Functions",
    "title": "App Functions",
    "content": "App Functions expose Meshtastic capabilities to the Android system and to on-device AI assistants (such as Gemini) through the Android App Functions API. With them enabled, an assistant can discover and trigger mesh workflows for you — for example sending a message or checking your mesh status — without you opening the app. App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. App Functions let the system AI assistant act on your mesh; Chirpy is a conversational assistant inside the Meshtastic app itself. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/app-functions.html",
    
    "relUrl": "/pt-rPT/user/app-functions.html"
  },"124": {
    "doc": "App Functions",
    "title": "Enabling App Functions",
    "content": "Control App Functions from Settings → System AI. The screen has: . | A master toggle labeled “Allow AI access”, with the subtitle “Let system AI assistants (e.g. Gemini) discover and use mesh functions”. When off, no functions are exposed to the system. | An individual toggle for each function, so you can expose only the capabilities you want. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. The functions are grouped into a Write section (functions that change something or send data to your mesh) and a Read section (functions that only return information). The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Write Functions . | Function | What it does | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Read Functions . | Function | What it returns | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | The list of nodes on your mesh. | . | Get channel info | Information about your channels. | . | Get device status | Status of your connected radio. | . | Get node details | Detailed information about a specific node. | . | Get mesh metrics | Telemetry and metrics from your mesh. | . | Get recent messages | Recent messages from your conversations. | . | Get unread summary | A summary of unread messages. | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/app-functions.html#enabling-app-functions",
    
    "relUrl": "/pt-rPT/user/app-functions.html#enabling-app-functions"
  },"125": {
    "doc": "App Functions",
    "title": "Privacy",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/app-functions.html#privacy",
    
    "relUrl": "/pt-rPT/user/app-functions.html#privacy"
  },"126": {
    "doc": "App Functions",
    "title": "Related Topics",
    "content": ". | Messages & Channels — sending messages directly in the app | Nodes — the node list the read functions draw from | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/app-functions.html#related-topics",
    
    "relUrl": "/pt-rPT/user/app-functions.html#related-topics"
  },"127": {
    "doc": "App Functions",
    "title": "App Functions",
    "content": "App Functions expose Meshtastic capabilities to the Android system and to on-device AI assistants (such as Gemini) through the Android App Functions API. With them enabled, an assistant can discover and trigger mesh workflows for you — for example sending a message or checking your mesh status — without you opening the app. App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. App Functions let the system AI assistant act on your mesh; Chirpy is a conversational assistant inside the Meshtastic app itself. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/app-functions.html",
    
    "relUrl": "/pl-rPL/user/app-functions.html"
  },"128": {
    "doc": "App Functions",
    "title": "Enabling App Functions",
    "content": "Control App Functions from Settings → System AI. The screen has: . | A master toggle labeled “Allow AI access”, with the subtitle “Let system AI assistants (e.g. Gemini) discover and use mesh functions”. When off, no functions are exposed to the system. | An individual toggle for each function, so you can expose only the capabilities you want. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. The functions are grouped into a Write section (functions that change something or send data to your mesh) and a Read section (functions that only return information). The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Write Functions . | Function | What it does | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Read Functions . | Function | What it returns | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | The list of nodes on your mesh. | . | Get channel info | Information about your channels. | . | Get device status | Status of your connected radio. | . | Get node details | Detailed information about a specific node. | . | Get mesh metrics | Telemetry and metrics from your mesh. | . | Get recent messages | Recent messages from your conversations. | . | Get unread summary | A summary of unread messages. | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/app-functions.html#enabling-app-functions",
    
    "relUrl": "/pl-rPL/user/app-functions.html#enabling-app-functions"
  },"129": {
    "doc": "App Functions",
    "title": "Privacy",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/app-functions.html#privacy",
    
    "relUrl": "/pl-rPL/user/app-functions.html#privacy"
  },"130": {
    "doc": "App Functions",
    "title": "Related Topics",
    "content": ". | Messages & Channels — sending messages directly in the app | Nodes — the node list the read functions draw from | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/app-functions.html#related-topics",
    
    "relUrl": "/pl-rPL/user/app-functions.html#related-topics"
  },"131": {
    "doc": "App Functions",
    "title": "App Functions",
    "content": "App Functions expose Meshtastic capabilities to the Android system and to on-device AI assistants (such as Gemini) through the Android App Functions API. With them enabled, an assistant can discover and trigger mesh workflows for you — for example sending a message or checking your mesh status — without you opening the app. App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. App Functions let the system AI assistant act on your mesh; Chirpy is a conversational assistant inside the Meshtastic app itself. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/app-functions.html",
    
    "relUrl": "/zh-rCN/user/app-functions.html"
  },"132": {
    "doc": "App Functions",
    "title": "Enabling App Functions",
    "content": "Control App Functions from Settings → System AI. The screen has: . | A master toggle labeled “Allow AI access”, with the subtitle “Let system AI assistants (e.g. Gemini) discover and use mesh functions”. When off, no functions are exposed to the system. | An individual toggle for each function, so you can expose only the capabilities you want. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. The functions are grouped into a Write section (functions that change something or send data to your mesh) and a Read section (functions that only return information). The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Write Functions . | Function | What it does | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Read Functions . | Function | What it returns | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | The list of nodes on your mesh. | . | Get channel info | Information about your channels. | . | Get device status | Status of your connected radio. | . | Get node details | Detailed information about a specific node. | . | Get mesh metrics | Telemetry and metrics from your mesh. | . | Get recent messages | Recent messages from your conversations. | . | Get unread summary | A summary of unread messages. | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/app-functions.html#enabling-app-functions",
    
    "relUrl": "/zh-rCN/user/app-functions.html#enabling-app-functions"
  },"133": {
    "doc": "App Functions",
    "title": "Privacy",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/app-functions.html#privacy",
    
    "relUrl": "/zh-rCN/user/app-functions.html#privacy"
  },"134": {
    "doc": "App Functions",
    "title": "Related Topics",
    "content": ". | Messages & Channels — sending messages directly in the app | Nodes — the node list the read functions draw from | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/app-functions.html#related-topics",
    
    "relUrl": "/zh-rCN/user/app-functions.html#related-topics"
  },"135": {
    "doc": "App Functions",
    "title": "App Functions",
    "content": "App Functions expose Meshtastic capabilities to the Android system and to on-device AI assistants (such as Gemini) through the Android App Functions API. With them enabled, an assistant can discover and trigger mesh workflows for you — for example sending a message or checking your mesh status — without you opening the app. App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. App Functions let the system AI assistant act on your mesh; Chirpy is a conversational assistant inside the Meshtastic app itself. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/app-functions.html",
    
    "relUrl": "/sq-rAL/user/app-functions.html"
  },"136": {
    "doc": "App Functions",
    "title": "Enabling App Functions",
    "content": "Control App Functions from Settings → System AI. The screen has: . | A master toggle labeled “Allow AI access”, with the subtitle “Let system AI assistants (e.g. Gemini) discover and use mesh functions”. When off, no functions are exposed to the system. | An individual toggle for each function, so you can expose only the capabilities you want. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. The functions are grouped into a Write section (functions that change something or send data to your mesh) and a Read section (functions that only return information). The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Write Functions . | Function | What it does | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Read Functions . | Function | What it returns | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | The list of nodes on your mesh. | . | Get channel info | Information about your channels. | . | Get device status | Status of your connected radio. | . | Get node details | Detailed information about a specific node. | . | Get mesh metrics | Telemetry and metrics from your mesh. | . | Get recent messages | Recent messages from your conversations. | . | Get unread summary | A summary of unread messages. | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/app-functions.html#enabling-app-functions",
    
    "relUrl": "/sq-rAL/user/app-functions.html#enabling-app-functions"
  },"137": {
    "doc": "App Functions",
    "title": "Privacy",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/app-functions.html#privacy",
    
    "relUrl": "/sq-rAL/user/app-functions.html#privacy"
  },"138": {
    "doc": "App Functions",
    "title": "Related Topics",
    "content": ". | Messages & Channels — sending messages directly in the app | Nodes — the node list the read functions draw from | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/app-functions.html#related-topics",
    
    "relUrl": "/sq-rAL/user/app-functions.html#related-topics"
  },"139": {
    "doc": "App Functions",
    "title": "App Functions",
    "content": "App Functions expose Meshtastic capabilities to the Android system and to on-device AI assistants (such as Gemini) through the Android App Functions API. With them enabled, an assistant can discover and trigger mesh workflows for you — for example sending a message or checking your mesh status — without you opening the app. App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. App Functions let the system AI assistant act on your mesh; Chirpy is a conversational assistant inside the Meshtastic app itself. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/app-functions.html",
    
    "relUrl": "/zh-rTW/user/app-functions.html"
  },"140": {
    "doc": "App Functions",
    "title": "Enabling App Functions",
    "content": "Control App Functions from Settings → System AI. The screen has: . | A master toggle labeled “Allow AI access”, with the subtitle “Let system AI assistants (e.g. Gemini) discover and use mesh functions”. When off, no functions are exposed to the system. | An individual toggle for each function, so you can expose only the capabilities you want. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. The functions are grouped into a Write section (functions that change something or send data to your mesh) and a Read section (functions that only return information). The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Write Functions . | Function | What it does | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Read Functions . | Function | What it returns | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | The list of nodes on your mesh. | . | Get channel info | Information about your channels. | . | Get device status | Status of your connected radio. | . | Get node details | Detailed information about a specific node. | . | Get mesh metrics | Telemetry and metrics from your mesh. | . | Get recent messages | Recent messages from your conversations. | . | Get unread summary | A summary of unread messages. | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/app-functions.html#enabling-app-functions",
    
    "relUrl": "/zh-rTW/user/app-functions.html#enabling-app-functions"
  },"141": {
    "doc": "App Functions",
    "title": "隱私",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/app-functions.html#%E9%9A%B1%E7%A7%81",
    
    "relUrl": "/zh-rTW/user/app-functions.html#隱私"
  },"142": {
    "doc": "App Functions",
    "title": "相關主題",
    "content": ". | Messages & Channels — sending messages directly in the app | Nodes — the node list the read functions draw from | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/app-functions.html#%E7%9B%B8%E9%97%9C%E4%B8%BB%E9%A1%8C",
    
    "relUrl": "/zh-rTW/user/app-functions.html#相關主題"
  },"143": {
    "doc": "Rakenduse funktsioonid",
    "title": "Rakenduse funktsioonid",
    "content": "Rakendusfunktsioonid avaldavad Meshtasticu võimalused Androidi süsteemile ja seadmesisestele TI assistentidele (näiteks Gemini) Androidi rakenduste funktsioonide API kaudu. Kui need on lubatud, saab assistent sinu eest kärgvõrgu töövooge avastada ja käivitada – näiteks sõnumi saata või kärgvõrgu olekut kontrollida – ilma, et peaksid rakendust avama. App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. Rakenduse funktsioonid lasevad süsteemi TI assistendil kärgvõrgu kallal tegutseda; Chirpy on vestlusassistent Meshtasticu rakenduses endas. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/app-functions.html",
    
    "relUrl": "/et-rEE/user/app-functions.html"
  },"144": {
    "doc": "Rakenduse funktsioonid",
    "title": "Luba rakenduse funktsioonid",
    "content": "Control App Functions from Settings → System AI. The screen has: . | Pealüliti sildiga “Luba tehisintellektile juurdepääs” alapealkirjaga “Luba süsteemi TI assistentidel (nt Gemini) kärgvõrgu funktsioone avastada ja kasutada”. Väljalülitatud olekus pole süsteemile ühtegi funktsiooni avatud. | Iga funktsiooni jaoks on eraldi lüliti, nii et saad kuvada ainult soovitud võimalusi. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. Funktsioonid on rühmitatud kirjutamis- (Write) sektsiooni (funktsioonid, mis midagi muudavad või andmeid kärgvõrgule saadavad) ja lugemis- (Read) sektsiooni (funktsioonid, mis ainult teavet tagastavad). The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Kirjutamis funktsioonid . | Funktsioon | What it does | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Lugemis funktsioonid . | Funktsioon | What it returns | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | Teie kärgvõrgu sõlmede loend. | . | Get channel info | Teave kanalite kohta. | . | Get device status | Ühendatud raadio olek. | . | Get node details | Detailed information about a specific node. | . | Get mesh metrics | Telemetry and metrics from your mesh. | . | Get recent messages | Recent messages from your conversations. | . | Get unread summary | A summary of unread messages. | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/app-functions.html#luba-rakenduse-funktsioonid",
    
    "relUrl": "/et-rEE/user/app-functions.html#luba-rakenduse-funktsioonid"
  },"145": {
    "doc": "Rakenduse funktsioonid",
    "title": "Privacy",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/app-functions.html#privacy",
    
    "relUrl": "/et-rEE/user/app-functions.html#privacy"
  },"146": {
    "doc": "Rakenduse funktsioonid",
    "title": "Seotud teemad",
    "content": ". | Sõnumid ja kanalid— sõnumite saatmine otse rakenduses | Sõlmed — sõlmede loend, millest lugemisfunktsioonid ammutavad | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/app-functions.html#seotud-teemad",
    
    "relUrl": "/et-rEE/user/app-functions.html#seotud-teemad"
  },"147": {
    "doc": "App Functions",
    "title": "App Functions",
    "content": "App Functions expose Meshtastic capabilities to the Android system and to on-device AI assistants (such as Gemini) through the Android App Functions API. With them enabled, an assistant can discover and trigger mesh workflows for you — for example sending a message or checking your mesh status — without you opening the app. App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. App Functions let the system AI assistant act on your mesh; Chirpy is a conversational assistant inside the Meshtastic app itself. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/app-functions.html",
    
    "relUrl": "/fr-rFR/user/app-functions.html"
  },"148": {
    "doc": "App Functions",
    "title": "Enabling App Functions",
    "content": "Control App Functions from Settings → System AI. The screen has: . | A master toggle labeled “Allow AI access”, with the subtitle “Let system AI assistants (e.g. Gemini) discover and use mesh functions”. When off, no functions are exposed to the system. | An individual toggle for each function, so you can expose only the capabilities you want. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. The functions are grouped into a Write section (functions that change something or send data to your mesh) and a Read section (functions that only return information). The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Write Functions . | Function | What it does | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Read Functions . | Function | What it returns | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | The list of nodes on your mesh. | . | Get channel info | Information about your channels. | . | Get device status | Status of your connected radio. | . | Get node details | Detailed information about a specific node. | . | Get mesh metrics | Telemetry and metrics from your mesh. | . | Get recent messages | Recent messages from your conversations. | . | Get unread summary | A summary of unread messages. | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/app-functions.html#enabling-app-functions",
    
    "relUrl": "/fr-rFR/user/app-functions.html#enabling-app-functions"
  },"149": {
    "doc": "App Functions",
    "title": "Privacy",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/app-functions.html#privacy",
    
    "relUrl": "/fr-rFR/user/app-functions.html#privacy"
  },"150": {
    "doc": "App Functions",
    "title": "Related Topics",
    "content": ". | Messages & Channels — sending messages directly in the app | Nodes — the node list the read functions draw from | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/app-functions.html#related-topics",
    
    "relUrl": "/fr-rFR/user/app-functions.html#related-topics"
  },"151": {
    "doc": "App Functions",
    "title": "App Functions",
    "content": "App Functions expose Meshtastic capabilities to the Android system and to on-device AI assistants (such as Gemini) through the Android App Functions API. With them enabled, an assistant can discover and trigger mesh workflows for you — for example sending a message or checking your mesh status — without you opening the app. App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. App Functions let the system AI assistant act on your mesh; Chirpy is a conversational assistant inside the Meshtastic app itself. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/app-functions.html",
    
    "relUrl": "/tr-rTR/user/app-functions.html"
  },"152": {
    "doc": "App Functions",
    "title": "Enabling App Functions",
    "content": "Control App Functions from Settings → System AI. The screen has: . | A master toggle labeled “Allow AI access”, with the subtitle “Let system AI assistants (e.g. Gemini) discover and use mesh functions”. When off, no functions are exposed to the system. | An individual toggle for each function, so you can expose only the capabilities you want. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. The functions are grouped into a Write section (functions that change something or send data to your mesh) and a Read section (functions that only return information). The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Write Functions . | Function | What it does | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Read Functions . | Function | What it returns | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | The list of nodes on your mesh. | . | Get channel info | Information about your channels. | . | Get device status | Status of your connected radio. | . | Get node details | Detailed information about a specific node. | . | Get mesh metrics | Telemetry and metrics from your mesh. | . | Get recent messages | Recent messages from your conversations. | . | Get unread summary | A summary of unread messages. | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/app-functions.html#enabling-app-functions",
    
    "relUrl": "/tr-rTR/user/app-functions.html#enabling-app-functions"
  },"153": {
    "doc": "App Functions",
    "title": "Privacy",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/app-functions.html#privacy",
    
    "relUrl": "/tr-rTR/user/app-functions.html#privacy"
  },"154": {
    "doc": "App Functions",
    "title": "Related Topics",
    "content": ". | Messages & Channels — sending messages directly in the app | Nodes — the node list the read functions draw from | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/app-functions.html#related-topics",
    
    "relUrl": "/tr-rTR/user/app-functions.html#related-topics"
  },"155": {
    "doc": "App Functions",
    "title": "App Functions",
    "content": "App Functions expose Meshtastic capabilities to the Android system and to on-device AI assistants (such as Gemini) through the Android App Functions API. With them enabled, an assistant can discover and trigger mesh workflows for you — for example sending a message or checking your mesh status — without you opening the app. App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. App Functions let the system AI assistant act on your mesh; Chirpy is a conversational assistant inside the Meshtastic app itself. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/app-functions.html",
    
    "relUrl": "/el-rGR/user/app-functions.html"
  },"156": {
    "doc": "App Functions",
    "title": "Enabling App Functions",
    "content": "Control App Functions from Settings → System AI. The screen has: . | A master toggle labeled “Allow AI access”, with the subtitle “Let system AI assistants (e.g. Gemini) discover and use mesh functions”. When off, no functions are exposed to the system. | An individual toggle for each function, so you can expose only the capabilities you want. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. The functions are grouped into a Write section (functions that change something or send data to your mesh) and a Read section (functions that only return information). The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Write Functions . | Function | What it does | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Read Functions . | Function | What it returns | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | The list of nodes on your mesh. | . | Get channel info | Information about your channels. | . | Get device status | Status of your connected radio. | . | Get node details | Detailed information about a specific node. | . | Get mesh metrics | Telemetry and metrics from your mesh. | . | Get recent messages | Recent messages from your conversations. | . | Get unread summary | A summary of unread messages. | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/app-functions.html#enabling-app-functions",
    
    "relUrl": "/el-rGR/user/app-functions.html#enabling-app-functions"
  },"157": {
    "doc": "App Functions",
    "title": "Privacy",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/app-functions.html#privacy",
    
    "relUrl": "/el-rGR/user/app-functions.html#privacy"
  },"158": {
    "doc": "App Functions",
    "title": "Related Topics",
    "content": ". | Messages & Channels — sending messages directly in the app | Nodes — the node list the read functions draw from | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/app-functions.html#related-topics",
    
    "relUrl": "/el-rGR/user/app-functions.html#related-topics"
  },"159": {
    "doc": "App Functions",
    "title": "App Functions",
    "content": "App Functions expose Meshtastic capabilities to the Android system and to on-device AI assistants (such as Gemini) through the Android App Functions API. With them enabled, an assistant can discover and trigger mesh workflows for you — for example sending a message or checking your mesh status — without you opening the app. App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. App Functions let the system AI assistant act on your mesh; Chirpy is a conversational assistant inside the Meshtastic app itself. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/app-functions.html",
    
    "relUrl": "/ro-rRO/user/app-functions.html"
  },"160": {
    "doc": "App Functions",
    "title": "Enabling App Functions",
    "content": "Control App Functions from Settings → System AI. The screen has: . | A master toggle labeled “Allow AI access”, with the subtitle “Let system AI assistants (e.g. Gemini) discover and use mesh functions”. When off, no functions are exposed to the system. | An individual toggle for each function, so you can expose only the capabilities you want. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. The functions are grouped into a Write section (functions that change something or send data to your mesh) and a Read section (functions that only return information). The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Write Functions . | Function | What it does | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Read Functions . | Function | What it returns | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | The list of nodes on your mesh. | . | Get channel info | Information about your channels. | . | Get device status | Status of your connected radio. | . | Get node details | Detailed information about a specific node. | . | Get mesh metrics | Telemetry and metrics from your mesh. | . | Get recent messages | Recent messages from your conversations. | . | Get unread summary | A summary of unread messages. | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/app-functions.html#enabling-app-functions",
    
    "relUrl": "/ro-rRO/user/app-functions.html#enabling-app-functions"
  },"161": {
    "doc": "App Functions",
    "title": "Privacy",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/app-functions.html#privacy",
    
    "relUrl": "/ro-rRO/user/app-functions.html#privacy"
  },"162": {
    "doc": "App Functions",
    "title": "Related Topics",
    "content": ". | Messages & Channels — sending messages directly in the app | Nodes — the node list the read functions draw from | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/app-functions.html#related-topics",
    
    "relUrl": "/ro-rRO/user/app-functions.html#related-topics"
  },"163": {
    "doc": "App Functions",
    "title": "App Functions",
    "content": "App Functions expose Meshtastic capabilities to the Android system and to on-device AI assistants (such as Gemini) through the Android App Functions API. With them enabled, an assistant can discover and trigger mesh workflows for you — for example sending a message or checking your mesh status — without you opening the app. App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. App Functions let the system AI assistant act on your mesh; Chirpy is a conversational assistant inside the Meshtastic app itself. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/app-functions.html",
    
    "relUrl": "/iw-rIL/user/app-functions.html"
  },"164": {
    "doc": "App Functions",
    "title": "Enabling App Functions",
    "content": "Control App Functions from Settings → System AI. The screen has: . | A master toggle labeled “Allow AI access”, with the subtitle “Let system AI assistants (e.g. Gemini) discover and use mesh functions”. When off, no functions are exposed to the system. | An individual toggle for each function, so you can expose only the capabilities you want. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. The functions are grouped into a Write section (functions that change something or send data to your mesh) and a Read section (functions that only return information). The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Write Functions . | Function | What it does | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Read Functions . | Function | What it returns | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | The list of nodes on your mesh. | . | Get channel info | Information about your channels. | . | Get device status | Status of your connected radio. | . | Get node details | Detailed information about a specific node. | . | Get mesh metrics | Telemetry and metrics from your mesh. | . | Get recent messages | Recent messages from your conversations. | . | Get unread summary | A summary of unread messages. | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/app-functions.html#enabling-app-functions",
    
    "relUrl": "/iw-rIL/user/app-functions.html#enabling-app-functions"
  },"165": {
    "doc": "App Functions",
    "title": "Privacy",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/app-functions.html#privacy",
    
    "relUrl": "/iw-rIL/user/app-functions.html#privacy"
  },"166": {
    "doc": "App Functions",
    "title": "Related Topics",
    "content": ". | Messages & Channels — sending messages directly in the app | Nodes — the node list the read functions draw from | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/app-functions.html#related-topics",
    
    "relUrl": "/iw-rIL/user/app-functions.html#related-topics"
  },"167": {
    "doc": "App Functions",
    "title": "App Functions",
    "content": "App Functions expose Meshtastic capabilities to the Android system and to on-device AI assistants (such as Gemini) through the Android App Functions API. With them enabled, an assistant can discover and trigger mesh workflows for you — for example sending a message or checking your mesh status — without you opening the app. App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. App Functions let the system AI assistant act on your mesh; Chirpy is a conversational assistant inside the Meshtastic app itself. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/app-functions.html",
    
    "relUrl": "/pt-rBR/user/app-functions.html"
  },"168": {
    "doc": "App Functions",
    "title": "Enabling App Functions",
    "content": "Control App Functions from Settings → System AI. The screen has: . | A master toggle labeled “Allow AI access”, with the subtitle “Let system AI assistants (e.g. Gemini) discover and use mesh functions”. When off, no functions are exposed to the system. | An individual toggle for each function, so you can expose only the capabilities you want. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. The functions are grouped into a Write section (functions that change something or send data to your mesh) and a Read section (functions that only return information). The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Write Functions . | Function | What it does | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Read Functions . | Function | What it returns | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | The list of nodes on your mesh. | . | Get channel info | Information about your channels. | . | Get device status | Status of your connected radio. | . | Get node details | Detailed information about a specific node. | . | Get mesh metrics | Telemetry and metrics from your mesh. | . | Get recent messages | Recent messages from your conversations. | . | Get unread summary | A summary of unread messages. | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/app-functions.html#enabling-app-functions",
    
    "relUrl": "/pt-rBR/user/app-functions.html#enabling-app-functions"
  },"169": {
    "doc": "App Functions",
    "title": "Privacy",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/app-functions.html#privacy",
    
    "relUrl": "/pt-rBR/user/app-functions.html#privacy"
  },"170": {
    "doc": "App Functions",
    "title": "Related Topics",
    "content": ". | Messages & Channels — sending messages directly in the app | Nodes — the node list the read functions draw from | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/app-functions.html#related-topics",
    
    "relUrl": "/pt-rBR/user/app-functions.html#related-topics"
  },"171": {
    "doc": "App Functions",
    "title": "App Functions",
    "content": "App Functions expose Meshtastic capabilities to the Android system and to on-device AI assistants (such as Gemini) through the Android App Functions API. With them enabled, an assistant can discover and trigger mesh workflows for you — for example sending a message or checking your mesh status — without you opening the app. App Functions are available on Google-flavor Android builds only. ℹ️ Note: This is separate from the in-app Chirpy assistant. App Functions let the system AI assistant act on your mesh; Chirpy is a conversational assistant inside the Meshtastic app itself. ",
    "url": "/Meshtastic-Android/main/en/user/app-functions.html",
    
    "relUrl": "/en/user/app-functions.html"
  },"172": {
    "doc": "App Functions",
    "title": "Enabling App Functions",
    "content": "Control App Functions from Settings → System AI. The screen has: . | A master toggle labeled “Allow AI access”, with the subtitle “Let system AI assistants (e.g. Gemini) discover and use mesh functions”. When off, no functions are exposed to the system. | An individual toggle for each function, so you can expose only the capabilities you want. | . ⚠️ Important: App Functions ship switched on. On a Google-flavor build the master toggle and every individual function, Send message included, start enabled — so an assistant can read your mesh data and send messages to your mesh until you turn Allow AI access off. The functions are grouped into a Write section (functions that change something or send data to your mesh) and a Read section (functions that only return information). The screenshot has Send message and Get recent messages switched off to illustrate per-function control; a fresh install shows every switch on. Write Functions . | Function | What it does | . | Send message | Sends a text message to a contact (direct message) or to a channel. The mesh carries at most 233 bytes of text, so keep assistant-composed messages short. | . Read Functions . | Function | What it returns | . | Get mesh status | Whether you’re connected to a radio, and how many nodes are online. | . | Get node list | The list of nodes on your mesh. | . | Get channel info | Information about your channels. | . | Get device status | Status of your connected radio. | . | Get node details | Detailed information about a specific node. | . | Get mesh metrics | Telemetry and metrics from your mesh. | . | Get recent messages | Recent messages from your conversations. | . | Get unread summary | A summary of unread messages. | . ",
    "url": "/Meshtastic-Android/main/en/user/app-functions.html#enabling-app-functions",
    
    "relUrl": "/en/user/app-functions.html#enabling-app-functions"
  },"173": {
    "doc": "App Functions",
    "title": "Privacy",
    "content": "🔒 Privacy: The Send message function lets an assistant send messages to your mesh on your behalf, and the read functions expose node, message, and metric data to it. Because all of them start enabled, the choice you make here is what to turn off rather than what to turn on. Each function has its own toggle, and Allow AI access turns all of them off at once. ",
    "url": "/Meshtastic-Android/main/en/user/app-functions.html#privacy",
    
    "relUrl": "/en/user/app-functions.html#privacy"
  },"174": {
    "doc": "App Functions",
    "title": "Related Topics",
    "content": ". | Messages & Channels — sending messages directly in the app | Nodes — the node list the read functions draw from | Node Metrics — the telemetry behind Get mesh metrics | . ",
    "url": "/Meshtastic-Android/main/en/user/app-functions.html#related-topics",
    
    "relUrl": "/en/user/app-functions.html#related-topics"
  },"175": {
    "doc": "Architecture",
    "title": "Architecture",
    "content": "The Meshtastic Android and Desktop apps follow a modular Kotlin Multiplatform (KMP) architecture with clear layer boundaries. iOS is a compile-only validation target; no iOS app ships. ",
    "url": "/Meshtastic-Android/main/en/developer/architecture.html",
    
    "relUrl": "/en/developer/architecture.html"
  },"176": {
    "doc": "Architecture",
    "title": "Layer Overview",
    "content": "┌─────────────────────────────────────────────┐ │ androidApp / desktopApp │ Platform entry points ├─────────────────────────────────────────────┤ │ feature/* modules │ UI + Business Logic ├─────────────────────────────────────────────┤ │ core/* modules │ Shared infrastructure ├─────────────────────────────────────────────┤ │ Platform (Android/JVM/iOS) │ OS-specific bindings └─────────────────────────────────────────────┘ . ",
    "url": "/Meshtastic-Android/main/en/developer/architecture.html#layer-overview",
    
    "relUrl": "/en/developer/architecture.html#layer-overview"
  },"177": {
    "doc": "Architecture",
    "title": "Module Categories",
    "content": "androidApp/ — Android Application . The Android application entry point: . | Activity, Application, and Manifest definitions | Koin DI module composition (AppKoinModule) | Flavor-specific bindings (google/, fdroid/) | Android-only integrations (widgets, services) | . desktopApp/ — Desktop JVM Application . The Desktop (Linux/macOS/Windows) entry point: . | Compose Desktop window management | Desktop-specific DI (DesktopKoinModule) | Platform stubs for Android-only capabilities | DesktopRadioTransportFactory and a jSerialComm-based serial transport; the BLE and TCP transport implementations it wires up are shared code — they live in core:network, built on core:ble’s BLE primitives — not desktopApp-owned | . feature/* — Feature Modules . Each feature/ module owns a vertical slice of functionality: . | Module | Responsibility | . | feature:intro | Onboarding/welcome flow | . | feature:messaging | Messages, channels, contacts, quick chat | . | feature:connections | Bluetooth/USB/TCP connection management | . | feature:map | Map display, waypoints — shared state, policy and the waypoint editor | . | feature:map-maplibre | MapLibre map surfaces — used by the fdroid flavor and Desktop; the google flavor uses Google Maps instead. Tile-source definitions and the custom-source editor are in feature:map, so both renderers share them | . | feature:node | Node list, node detail, metrics | . | feature:settings | All configuration screens | . | feature:firmware | Firmware update flow | . | feature:docs | In-app documentation browser | . | feature:wifi-provision | Wi-Fi provisioning | . | feature:widget | Android home screen widgets | . | feature:discovery | Mesh network discovery | . Feature modules: . | Use the meshtastic.kmp.feature convention plugin | Depend on core modules, never on other feature modules | Own their navigation entries and DI registrations | Contain platform-specific implementations in androidMain/jvmMain/iosMain | . core/* — Core Modules . Shared infrastructure used by all features: . | Module | Responsibility | . | core:common | Utilities, extensions, build config | . | core:navigation | Routes, deep links, Navigation 3 | . | core:ui | Shared Compose components, icons, theme | . | core:resources | Shared string resources | . | core:model | Domain models | . | core:data | Data layer abstractions | . | core:domain | Use cases / business logic | . | core:database | Room KMP database | . | core:datastore | DataStore preferences | . | core:prefs | App preferences | . | core:repository | Repository interfaces | . | core:service | Mesh service layer | . | core:di | DI utilities | . | core:network | HTTP/serial/transport | . | core:ble | Bluetooth LE abstractions | . | core:barcode | QR / barcode scanning (channel-share QR codes) | . | core:nfc | NFC read/write support | . | core:takserver | Embedded TAK server integration | . | core:testing | Test utilities | . | core:konsist | Konsist architecture/convention tests | . Protobuf models come from the external org.meshtastic:protobufs Maven artifact (pinned in gradle/libs.versions.toml). ",
    "url": "/Meshtastic-Android/main/en/developer/architecture.html#module-categories",
    
    "relUrl": "/en/developer/architecture.html#module-categories"
  },"178": {
    "doc": "Architecture",
    "title": "KMP Source Sets",
    "content": "Each module uses the standard KMP source set hierarchy: . src/ ├── commonMain/ ← Shared code (all platforms) ├── commonTest/ ← Shared tests ├── androidMain/ ← Android-specific ├── jvmMain/ ← Desktop JVM-specific ├── iosMain/ ← iOS-specific └── jvmTest/ ← Desktop test host . Golden Rules: . | No android.* imports in commonMain | Platform-specific code goes in appropriate source set | Prefer interfaces + DI over expect/actual for complex behaviors | Use expect/actual only for simple declarations | . ",
    "url": "/Meshtastic-Android/main/en/developer/architecture.html#kmp-source-sets",
    
    "relUrl": "/en/developer/architecture.html#kmp-source-sets"
  },"179": {
    "doc": "Architecture",
    "title": "Dependency Injection",
    "content": "The project uses Koin with annotation processing: . | @Module, @Single, @Factory annotations | @ComponentScan for automatic registration | Feature modules export their own Feature*Module class | App/Desktop compose all modules in their root DI configuration | . ",
    "url": "/Meshtastic-Android/main/en/developer/architecture.html#dependency-injection",
    
    "relUrl": "/en/developer/architecture.html#dependency-injection"
  },"180": {
    "doc": "Architecture",
    "title": "Radio Control",
    "content": "Features issue radio commands through RadioController (core:repository), a composite of four focused sub-interfaces so callers can depend on just the slice they need: . | Sub-interface | Responsibility | . | AdminController | Config, channels, owner, device lifecycle, editSettings { } transactions | . | MessagingController | Send packets, reactions, shared contacts | . | NodeController | Favorite, ignore, mute, remove nodes | . | QueryController | Telemetry, traceroute, position/user-info queries | . RadioControllerImpl (core:service) is the in-process composition root for all targets (Desktop, iOS, single-process Android). It assembles the four sub-controllers via Kotlin interface delegation and adds the cross-cutting concerns (connection state, packet-id, location, device-address switching). Commands are direct suspend calls; admin writes are fire-and-forget because the device is the source of truth (local persistence is an optimistic cache). The layered shape mirrors the meshtastic-sdk AdminApi/TelemetryApi design to ease a future SDK migration. ",
    "url": "/Meshtastic-Android/main/en/developer/architecture.html#radio-control",
    
    "relUrl": "/en/developer/architecture.html#radio-control"
  },"181": {
    "doc": "Architecture",
    "title": "Service Repository",
    "content": "ServiceRepository is the reactive bridge between the mesh service and all feature/UI layers. It is decomposed into focused provider interfaces following the Interface Segregation Principle: . | Interface | Responsibility | . | ConnectionStateProvider | Read-only connectionState: StateFlow<ConnectionState> | . | TracerouteResponseProvider | Traceroute response state + clear | . | NeighborInfoResponseProvider | Neighbor info response state + clear | . | ServiceStateWriter | Write-side for handlers (set, emit, clear*) | . ServiceRepository extends all four interfaces — consumers inject the narrowest interface they actually need. For example, ContactsViewModel injects only ConnectionStateProvider rather than the entire ServiceRepository, preventing accidental access to write operations from UI code. RadioController also extends ConnectionStateProvider so VMs that already inject a controller sub-interface can read connection state without a separate dependency. ",
    "url": "/Meshtastic-Android/main/en/developer/architecture.html#service-repository",
    
    "relUrl": "/en/developer/architecture.html#service-repository"
  },"182": {
    "doc": "Architecture",
    "title": "Navigation",
    "content": "Navigation uses Navigation 3 with typed routes: . | All routes defined in core/navigation/Routes.kt | Routes are @Serializable data classes/objects | Deep links resolved through DeepLinkRouter | Each feature registers its own navigation entries | . See Navigation & Deep Links for details. ",
    "url": "/Meshtastic-Android/main/en/developer/architecture.html#navigation",
    
    "relUrl": "/en/developer/architecture.html#navigation"
  },"183": {
    "doc": "Codebase",
    "title": "Codebase",
    "content": "Repository layout, namespacing conventions, and build system overview. ",
    "url": "/Meshtastic-Android/main/en/developer/codebase.html",
    
    "relUrl": "/en/developer/codebase.html"
  },"184": {
    "doc": "Codebase",
    "title": "Repository Structure",
    "content": "Meshtastic-Android/ ├── androidApp/ # Android application module │ ├── src/main/ # Shared Android code │ ├── src/google/ # Google Play flavor (proprietary Google integrations — Gemini, Maps, Play services) │ └── src/fdroid/ # F-Droid flavor (FOSS-only) ├── desktopApp/ # Desktop JVM application ├── feature/ # Feature modules (KMP) │ ├── intro/ │ ├── messaging/ │ ├── connections/ │ ├── map/ │ ├── map-maplibre/ │ ├── node/ │ ├── settings/ │ ├── firmware/ │ ├── docs/ │ ├── wifi-provision/ │ ├── widget/ │ └── discovery/ ├── core/ # Core infrastructure modules (KMP) │ ├── barcode/ │ ├── ble/ │ ├── common/ │ ├── data/ │ ├── database/ │ ├── datastore/ │ ├── di/ │ ├── domain/ │ ├── konsist/ │ ├── model/ │ ├── navigation/ │ ├── network/ │ ├── nfc/ │ ├── prefs/ │ ├── repository/ │ ├── resources/ │ ├── service/ │ ├── takserver/ │ ├── testing/ │ └── ui/ ├── baselineprofile/ # Baseline Profile generation for :androidApp ├── screenshot-tests/ # Compose Preview screenshot tests (visual-regression gate) ├── docs-screenshots/ # Doc-framed composition screenshots (generate-only, not CI-gated) ├── build-logic/ # Convention plugins and build helpers │ └── convention/ ├── docs/ # Documentation source (markdown) │ └── en/ # English source; other locales live under docs/<locale>/user/ │ ├── user/ │ └── developer/ ├── gradle/ # Gradle wrapper and version catalog │ └── libs.versions.toml ├── specs/ # Feature specifications └── .github/workflows/ # CI/CD workflows . ",
    "url": "/Meshtastic-Android/main/en/developer/codebase.html#repository-structure",
    
    "relUrl": "/en/developer/codebase.html#repository-structure"
  },"185": {
    "doc": "Codebase",
    "title": "Namespacing Convention",
    "content": "All Kotlin packages follow the pattern: . org.meshtastic.{layer}.{module}.{subpackage} . Examples: . | org.meshtastic.core.navigation — core navigation module | org.meshtastic.feature.docs.ui — docs feature UI package | org.meshtastic.app.di — app DI configuration | . ",
    "url": "/Meshtastic-Android/main/en/developer/codebase.html#namespacing-convention",
    
    "relUrl": "/en/developer/codebase.html#namespacing-convention"
  },"186": {
    "doc": "Codebase",
    "title": "Build System",
    "content": "Gradle Kotlin DSL . All build files use Kotlin DSL (.gradle.kts). Configuration: . | Version catalog: gradle/libs.versions.toml | Convention plugins: build-logic/convention/ | Settings: settings.gradle.kts | . Convention Plugins . Located in build-logic/convention/src/main/kotlin/. The full set is registered in build-logic/convention/build.gradle.kts; these are the ones a module build applies most often: . | Plugin | Purpose | . | meshtastic.kmp.feature | Standard feature module setup | . | meshtastic.kmp.library | Shared KMP library module | . | meshtastic.kmp.library.compose | KMP library that also ships Compose UI | . | meshtastic.kmp.jvm.android | JVM + Android target configuration | . | meshtastic.koin | Koin Annotations + K2 compiler plugin | . | meshtastic.kotlinx.serialization | Serialization plugin setup | . | meshtastic.android.room | Room KMP setup and schema location | . | meshtastic.android.screenshot | Compose Preview screenshot testing | . The rest cover the application and library variants, lint, detekt, spotless, Dokka, Kover, AboutLibraries, analytics, secrets, the docs tasks and the root aggregate — read the register(…) block rather than assuming a plugin does or does not exist. Build Variants (Android) . | Flavor | Description | . | google | Google Play distribution; includes proprietary APIs | . | fdroid | F-Droid distribution; FOSS-only dependencies | . Key Gradle Tasks . # Compile check across all KMP targets ./gradlew kmpSmokeCompile # Run all tests ./gradlew allTests # Code quality ./gradlew spotlessCheck detekt # Android build ./gradlew assembleGoogleDebug assembleFdroidDebug # Desktop run ./gradlew :desktopApp:run # Desktop native installers for the current OS (DMG / MSI+EXE / DEB+RPM+AppImage) ./gradlew :desktopApp:packageReleaseDistributionForCurrentOS # API reference (Dokka HTML → build/dokka/html) ./gradlew dokkaGeneratePublicationHtml . ",
    "url": "/Meshtastic-Android/main/en/developer/codebase.html#build-system",
    
    "relUrl": "/en/developer/codebase.html#build-system"
  },"187": {
    "doc": "Codebase",
    "title": "Version Catalog Highlights",
    "content": "Key dependencies in gradle/libs.versions.toml: . | Category | Library | . | Compose | Compose Multiplatform (JetBrains) | . | Navigation | Navigation 3 | . | DI | Koin (annotations) | . | Serialization | kotlinx.serialization | . | Database | Room KMP | . | Networking | Ktor | . | Markdown | multiplatform-markdown-renderer | . | Testing | kotlin-test, compose-ui-test | . ",
    "url": "/Meshtastic-Android/main/en/developer/codebase.html#version-catalog-highlights",
    
    "relUrl": "/en/developer/codebase.html#version-catalog-highlights"
  },"188": {
    "doc": "Connections",
    "title": "Connections",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/connections.html",
    
    "relUrl": "/sk-rSK/user/connections.html"
  },"189": {
    "doc": "Connections",
    "title": "Bluetooth (BLE)",
    "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Use the transport selector — a segmented button row below the connection card — to switch between the Bluetooth, Network, and USB transports (one is active at a time): . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | What it means | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. Connection Status . | Icon | State | Popis | . | 🟢 | Pripojený | Active radio link established | . | 🟡 | Prebieha pripájanie | Handshake in progress | . | 🔴 | Odpojené | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | Vysielač uspaný | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | Connection drops: Move closer to the radio; check for interference. | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/connections.html#bluetooth-ble",
    
    "relUrl": "/sk-rSK/user/connections.html#bluetooth-ble"
  },"190": {
    "doc": "Connections",
    "title": "USB Serial",
    "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | The connection is established automatically. | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/connections.html#usb-serial",
    
    "relUrl": "/sk-rSK/user/connections.html#usb-serial"
  },"191": {
    "doc": "Connections",
    "title": "TCP/IP (Network)",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect tab, select Network in the transport selector. | Choose the radio one of two ways: . | Scan for network devices — toggle this on to auto-discover radios that advertise themselves on the local network (mDNS / _meshtastic._tcp). Discovered devices appear in the list; tap one to connect. | Add device manually… — enter the radio’s IP address (or hostname) and port (default: 4403). | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . Wi-Fi Provisioning for mPWRD-OS . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/connections.html#tcpip-network",
    
    "relUrl": "/sk-rSK/user/connections.html#tcpip-network"
  },"192": {
    "doc": "Connections",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/connections.html#after-your-first-connection",
    
    "relUrl": "/sk-rSK/user/connections.html#after-your-first-connection"
  },"193": {
    "doc": "Connections",
    "title": "Reconnection Behavior",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/connections.html#reconnection-behavior",
    
    "relUrl": "/sk-rSK/user/connections.html#reconnection-behavior"
  },"194": {
    "doc": "Connections",
    "title": "Desktop Connections",
    "content": "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 for platform-specific details and keyboard shortcuts. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/connections.html#desktop-connections",
    
    "relUrl": "/sk-rSK/user/connections.html#desktop-connections"
  },"195": {
    "doc": "Connections",
    "title": "Related Topics",
    "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | Desktop App — desktop-specific connection details | Supported devices — full list of compatible radios on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/connections.html#related-topics",
    
    "relUrl": "/sk-rSK/user/connections.html#related-topics"
  },"196": {
    "doc": "Connections",
    "title": "Connections",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/connections.html",
    
    "relUrl": "/be-rBY/user/connections.html"
  },"197": {
    "doc": "Connections",
    "title": "Bluetooth (BLE)",
    "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Use the transport selector — a segmented button row below the connection card — to switch between the Bluetooth, Network, and USB transports (one is active at a time): . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | What it means | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. Connection Status . | Icon | State | Апісанне | . | 🟢 | Злучаны | Active radio link established | . | 🟡 | Злучаемся | Handshake in progress | . | 🔴 | Адлучана | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | Прылада спіць | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | Connection drops: Move closer to the radio; check for interference. | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/connections.html#bluetooth-ble",
    
    "relUrl": "/be-rBY/user/connections.html#bluetooth-ble"
  },"198": {
    "doc": "Connections",
    "title": "USB Serial",
    "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | The connection is established automatically. | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/connections.html#usb-serial",
    
    "relUrl": "/be-rBY/user/connections.html#usb-serial"
  },"199": {
    "doc": "Connections",
    "title": "TCP/IP (Network)",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect tab, select Network in the transport selector. | Choose the radio one of two ways: . | Scan for network devices — toggle this on to auto-discover radios that advertise themselves on the local network (mDNS / _meshtastic._tcp). Discovered devices appear in the list; tap one to connect. | Add device manually… — enter the radio’s IP address (or hostname) and port (default: 4403). | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . Wi-Fi Provisioning for mPWRD-OS . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/connections.html#tcpip-network",
    
    "relUrl": "/be-rBY/user/connections.html#tcpip-network"
  },"200": {
    "doc": "Connections",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/connections.html#after-your-first-connection",
    
    "relUrl": "/be-rBY/user/connections.html#after-your-first-connection"
  },"201": {
    "doc": "Connections",
    "title": "Reconnection Behavior",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/connections.html#reconnection-behavior",
    
    "relUrl": "/be-rBY/user/connections.html#reconnection-behavior"
  },"202": {
    "doc": "Connections",
    "title": "Desktop Connections",
    "content": "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 for platform-specific details and keyboard shortcuts. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/connections.html#desktop-connections",
    
    "relUrl": "/be-rBY/user/connections.html#desktop-connections"
  },"203": {
    "doc": "Connections",
    "title": "Related Topics",
    "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | Desktop App — desktop-specific connection details | Supported devices — full list of compatible radios on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/connections.html#related-topics",
    
    "relUrl": "/be-rBY/user/connections.html#related-topics"
  },"204": {
    "doc": "Connessioni",
    "title": "Connessioni",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/connections.html",
    
    "relUrl": "/it-rIT/user/connections.html"
  },"205": {
    "doc": "Connessioni",
    "title": "Bluetooth (BLE)",
    "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Use the transport selector — a segmented button row below the connection card — to switch between the Bluetooth, Network, and USB transports (one is active at a time): . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | What it means | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. Connection Status . | Icon | State | Descrizione | . | 🟢 | Connesso | Active radio link established | . | 🟡 | Connessione in corso | Handshake in progress | . | 🔴 | Disconnesso | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | Il dispositivo è inattivo | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | Connection drops: Move closer to the radio; check for interference. | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/connections.html#bluetooth-ble",
    
    "relUrl": "/it-rIT/user/connections.html#bluetooth-ble"
  },"206": {
    "doc": "Connessioni",
    "title": "USB Serial",
    "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Configurazione . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | The connection is established automatically. | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/connections.html#usb-serial",
    
    "relUrl": "/it-rIT/user/connections.html#usb-serial"
  },"207": {
    "doc": "Connessioni",
    "title": "TCP/IP (Network)",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect tab, select Network in the transport selector. | Choose the radio one of two ways: . | Scan for network devices — toggle this on to auto-discover radios that advertise themselves on the local network (mDNS / _meshtastic._tcp). Discovered devices appear in the list; tap one to connect. | Add device manually… — enter the radio’s IP address (or hostname) and port (default: 4403). | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . Provisioning Wi-Fi per mPWRD-OS . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/connections.html#tcpip-network",
    
    "relUrl": "/it-rIT/user/connections.html#tcpip-network"
  },"208": {
    "doc": "Connessioni",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/connections.html#after-your-first-connection",
    
    "relUrl": "/it-rIT/user/connections.html#after-your-first-connection"
  },"209": {
    "doc": "Connessioni",
    "title": "Reconnection Behavior",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/connections.html#reconnection-behavior",
    
    "relUrl": "/it-rIT/user/connections.html#reconnection-behavior"
  },"210": {
    "doc": "Connessioni",
    "title": "Desktop Connections",
    "content": "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 for platform-specific details and keyboard shortcuts. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/connections.html#desktop-connections",
    
    "relUrl": "/it-rIT/user/connections.html#desktop-connections"
  },"211": {
    "doc": "Connessioni",
    "title": "Related Topics",
    "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | Desktop App — desktop-specific connection details | Supported devices — full list of compatible radios on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/connections.html#related-topics",
    
    "relUrl": "/it-rIT/user/connections.html#related-topics"
  },"212": {
    "doc": "Conexiones",
    "title": "Conexiones",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/es-rES/user/connections.html",
    
    "relUrl": "/es-rES/user/connections.html"
  },"213": {
    "doc": "Conexiones",
    "title": "Bluetooth (BLE)",
    "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Use the transport selector — a segmented button row below the connection card — to switch between the Bluetooth, Network, and USB transports (one is active at a time): . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | What it means | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. Connection Status . | Icon | State | Descripción | . | 🟢 | Conectado | Active radio link established | . | 🟡 | Conectando | Handshake in progress | . | 🔴 | Desconectado | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | Dispositivo en reposo | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | Connection drops: Move closer to the radio; check for interference. | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/connections.html#bluetooth-ble",
    
    "relUrl": "/es-rES/user/connections.html#bluetooth-ble"
  },"214": {
    "doc": "Conexiones",
    "title": "USB Serial",
    "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | The connection is established automatically. | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/connections.html#usb-serial",
    
    "relUrl": "/es-rES/user/connections.html#usb-serial"
  },"215": {
    "doc": "Conexiones",
    "title": "TCP/IP (Network)",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect tab, select Network in the transport selector. | Choose the radio one of two ways: . | Scan for network devices — toggle this on to auto-discover radios that advertise themselves on the local network (mDNS / _meshtastic._tcp). Discovered devices appear in the list; tap one to connect. | Add device manually… — enter the radio’s IP address (or hostname) and port (default: 4403). | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . Wi-Fi Provisioning for mPWRD-OS . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/es-rES/user/connections.html#tcpip-network",
    
    "relUrl": "/es-rES/user/connections.html#tcpip-network"
  },"216": {
    "doc": "Conexiones",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/es-rES/user/connections.html#after-your-first-connection",
    
    "relUrl": "/es-rES/user/connections.html#after-your-first-connection"
  },"217": {
    "doc": "Conexiones",
    "title": "Reconnection Behavior",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/es-rES/user/connections.html#reconnection-behavior",
    
    "relUrl": "/es-rES/user/connections.html#reconnection-behavior"
  },"218": {
    "doc": "Conexiones",
    "title": "Desktop Connections",
    "content": "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 for platform-specific details and keyboard shortcuts. ",
    "url": "/Meshtastic-Android/main/es-rES/user/connections.html#desktop-connections",
    
    "relUrl": "/es-rES/user/connections.html#desktop-connections"
  },"219": {
    "doc": "Conexiones",
    "title": "Related Topics",
    "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | Desktop App — desktop-specific connection details | Supported devices — full list of compatible radios on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/connections.html#related-topics",
    
    "relUrl": "/es-rES/user/connections.html#related-topics"
  },"220": {
    "doc": "Connections",
    "title": "Connections",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/connections.html",
    
    "relUrl": "/sl-rSI/user/connections.html"
  },"221": {
    "doc": "Connections",
    "title": "Bluetooth (BLE)",
    "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Use the transport selector — a segmented button row below the connection card — to switch between the Bluetooth, Network, and USB transports (one is active at a time): . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | What it means | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. Connection Status . | Icon | State | Opis | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Prekinjeno | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | Naprava je v “spanju” | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | Connection drops: Move closer to the radio; check for interference. | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/connections.html#bluetooth-ble",
    
    "relUrl": "/sl-rSI/user/connections.html#bluetooth-ble"
  },"222": {
    "doc": "Connections",
    "title": "USB Serial",
    "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | The connection is established automatically. | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/connections.html#usb-serial",
    
    "relUrl": "/sl-rSI/user/connections.html#usb-serial"
  },"223": {
    "doc": "Connections",
    "title": "TCP/IP (Network)",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect tab, select Network in the transport selector. | Choose the radio one of two ways: . | Scan for network devices — toggle this on to auto-discover radios that advertise themselves on the local network (mDNS / _meshtastic._tcp). Discovered devices appear in the list; tap one to connect. | Add device manually… — enter the radio’s IP address (or hostname) and port (default: 4403). | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . Wi-Fi Provisioning for mPWRD-OS . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/connections.html#tcpip-network",
    
    "relUrl": "/sl-rSI/user/connections.html#tcpip-network"
  },"224": {
    "doc": "Connections",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/connections.html#after-your-first-connection",
    
    "relUrl": "/sl-rSI/user/connections.html#after-your-first-connection"
  },"225": {
    "doc": "Connections",
    "title": "Reconnection Behavior",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/connections.html#reconnection-behavior",
    
    "relUrl": "/sl-rSI/user/connections.html#reconnection-behavior"
  },"226": {
    "doc": "Connections",
    "title": "Desktop Connections",
    "content": "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 for platform-specific details and keyboard shortcuts. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/connections.html#desktop-connections",
    
    "relUrl": "/sl-rSI/user/connections.html#desktop-connections"
  },"227": {
    "doc": "Connections",
    "title": "Related Topics",
    "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | Desktop App — desktop-specific connection details | Supported devices — full list of compatible radios on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/connections.html#related-topics",
    
    "relUrl": "/sl-rSI/user/connections.html#related-topics"
  },"228": {
    "doc": "Connections",
    "title": "Connections",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/connections.html",
    
    "relUrl": "/no-rNO/user/connections.html"
  },"229": {
    "doc": "Connections",
    "title": "Bluetooth (BLE)",
    "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Use the transport selector — a segmented button row below the connection card — to switch between the Bluetooth, Network, and USB transports (one is active at a time): . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | What it means | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. Connection Status . | Icon | State | Beskrivelse | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Frakoblet | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | Enhet sover | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | Connection drops: Move closer to the radio; check for interference. | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/connections.html#bluetooth-ble",
    
    "relUrl": "/no-rNO/user/connections.html#bluetooth-ble"
  },"230": {
    "doc": "Connections",
    "title": "USB Serial",
    "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | The connection is established automatically. | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/connections.html#usb-serial",
    
    "relUrl": "/no-rNO/user/connections.html#usb-serial"
  },"231": {
    "doc": "Connections",
    "title": "TCP/IP (Network)",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect tab, select Network in the transport selector. | Choose the radio one of two ways: . | Scan for network devices — toggle this on to auto-discover radios that advertise themselves on the local network (mDNS / _meshtastic._tcp). Discovered devices appear in the list; tap one to connect. | Add device manually… — enter the radio’s IP address (or hostname) and port (default: 4403). | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . Wi-Fi Provisioning for mPWRD-OS . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/connections.html#tcpip-network",
    
    "relUrl": "/no-rNO/user/connections.html#tcpip-network"
  },"232": {
    "doc": "Connections",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/connections.html#after-your-first-connection",
    
    "relUrl": "/no-rNO/user/connections.html#after-your-first-connection"
  },"233": {
    "doc": "Connections",
    "title": "Reconnection Behavior",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/connections.html#reconnection-behavior",
    
    "relUrl": "/no-rNO/user/connections.html#reconnection-behavior"
  },"234": {
    "doc": "Connections",
    "title": "Desktop Connections",
    "content": "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 for platform-specific details and keyboard shortcuts. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/connections.html#desktop-connections",
    
    "relUrl": "/no-rNO/user/connections.html#desktop-connections"
  },"235": {
    "doc": "Connections",
    "title": "Related Topics",
    "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | Desktop App — desktop-specific connection details | Supported devices — full list of compatible radios on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/connections.html#related-topics",
    
    "relUrl": "/no-rNO/user/connections.html#related-topics"
  },"236": {
    "doc": "Connections",
    "title": "Connections",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/connections.html",
    
    "relUrl": "/hu-rHU/user/connections.html"
  },"237": {
    "doc": "Connections",
    "title": "Bluetooth (BLE)",
    "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Use the transport selector — a segmented button row below the connection card — to switch between the Bluetooth, Network, and USB transports (one is active at a time): . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | What it means | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. Connection Status . | Icon | State | Leírás | . | 🟢 | Csatlakoztatva | Active radio link established | . | 🟡 | Csatlakozás… | Handshake in progress | . | 🔴 | Szétkapcsolva | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | Az eszköz alszik | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | Connection drops: Move closer to the radio; check for interference. | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/connections.html#bluetooth-ble",
    
    "relUrl": "/hu-rHU/user/connections.html#bluetooth-ble"
  },"238": {
    "doc": "Connections",
    "title": "USB Serial",
    "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | The connection is established automatically. | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/connections.html#usb-serial",
    
    "relUrl": "/hu-rHU/user/connections.html#usb-serial"
  },"239": {
    "doc": "Connections",
    "title": "TCP/IP (Network)",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect tab, select Network in the transport selector. | Choose the radio one of two ways: . | Scan for network devices — toggle this on to auto-discover radios that advertise themselves on the local network (mDNS / _meshtastic._tcp). Discovered devices appear in the list; tap one to connect. | Add device manually… — enter the radio’s IP address (or hostname) and port (default: 4403). | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . Wi-Fi Provisioning for mPWRD-OS . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/connections.html#tcpip-network",
    
    "relUrl": "/hu-rHU/user/connections.html#tcpip-network"
  },"240": {
    "doc": "Connections",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/connections.html#after-your-first-connection",
    
    "relUrl": "/hu-rHU/user/connections.html#after-your-first-connection"
  },"241": {
    "doc": "Connections",
    "title": "Reconnection Behavior",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/connections.html#reconnection-behavior",
    
    "relUrl": "/hu-rHU/user/connections.html#reconnection-behavior"
  },"242": {
    "doc": "Connections",
    "title": "Desktop Connections",
    "content": "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 for platform-specific details and keyboard shortcuts. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/connections.html#desktop-connections",
    
    "relUrl": "/hu-rHU/user/connections.html#desktop-connections"
  },"243": {
    "doc": "Connections",
    "title": "Related Topics",
    "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | Desktop App — desktop-specific connection details | Supported devices — full list of compatible radios on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/connections.html#related-topics",
    
    "relUrl": "/hu-rHU/user/connections.html#related-topics"
  },"244": {
    "doc": "Соединения",
    "title": "Соединения",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/connections.html",
    
    "relUrl": "/ru-rRU/user/connections.html"
  },"245": {
    "doc": "Соединения",
    "title": "Bluetooth (BLE)",
    "content": "Bluetooth Low Energy является наиболее распространенным методом подключения на Android. Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | Откройте приложение и перейдите на вкладку Подключение. | Нажми Сканировать Bluetooth-устройства — рядом появятся радиостанции Meshtastic. | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Используйте селектор транспорта — ряд сегментированных кнопок под карточкой подключения — для переключения между транспортами Bluetooth, Network и USB (одновременно активен только один): . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | Что это значит | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. Статус подключения . | Иконка | Состояние | Описание | . | 🟢 | Подключено | Подключение активно | . | 🟡 | Подключение | Выполняется рукопожатие | . | 🔴 | Отключено | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | Устройство спит | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . Если устройства не найдены, приложение показывает пустое состояние с инструкциями: . Устранение неполадок Bluetooth . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | Потеря связи: Подойди ближе к ноде; проверь наличие помех. | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | Сопряжение отклонено: Забыть устройство в настройках Bluetooth на Android и повторить попытку. | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/connections.html#bluetooth-ble",
    
    "relUrl": "/ru-rRU/user/connections.html#bluetooth-ble"
  },"246": {
    "doc": "Соединения",
    "title": "Последовательный USB",
    "content": "Подключения через USB предоставляют проводную альтернативу, полезную для настольных компьютеров или когда Bluetooth недоступен. Настройка . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | Соединение устанавливается автоматически. | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/connections.html#%D0%BF%D0%BE%D1%81%D0%BB%D0%B5%D0%B4%D0%BE%D0%B2%D0%B0%D1%82%D0%B5%D0%BB%D1%8C%D0%BD%D1%8B%D0%B9-usb",
    
    "relUrl": "/ru-rRU/user/connections.html#последовательный-usb"
  },"247": {
    "doc": "Соединения",
    "title": "TCP/IP (Сеть)",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Подключение к сети . | Убедись, что радио подключено к той же локальной сети, что и твой телефон/компьютер. | On the Connect tab, select Network in the transport selector. | Выбери радиоустройство одним из двух способов: . | Сканировать сетевые устройства — включи эту опцию чтобы автоматически обнаруживать радиоустройства, которые объявляют о себе в локальной сети (mDNS / _meshtastic._tcp). Обнаруженные устройства появляются в списке; нажми на одно, чтобы подключиться. | Добавить устройство вручную… — введи IP-адрес радиостанции (или имя хоста) и порт (по умолчанию: 4403). | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. Когда использовать TCP . | Радиостанция находится в той же локальной сети | Тестирование с использованием имитирования радиоприемника | Окружающая среда, где возникают помехи Bluetooth | . Настройка Wi-Fi для mPWRD-OS . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/connections.html#tcpip-%D1%81%D0%B5%D1%82%D1%8C",
    
    "relUrl": "/ru-rRU/user/connections.html#tcpip-сеть"
  },"248": {
    "doc": "Соединения",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/connections.html#after-your-first-connection",
    
    "relUrl": "/ru-rRU/user/connections.html#after-your-first-connection"
  },"249": {
    "doc": "Соединения",
    "title": "Поведение при повторном подключении",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/connections.html#%D0%BF%D0%BE%D0%B2%D0%B5%D0%B4%D0%B5%D0%BD%D0%B8%D0%B5-%D0%BF%D1%80%D0%B8-%D0%BF%D0%BE%D0%B2%D1%82%D0%BE%D1%80%D0%BD%D0%BE%D0%BC-%D0%BF%D0%BE%D0%B4%D0%BA%D0%BB%D1%8E%D1%87%D0%B5%D0%BD%D0%B8%D0%B8",
    
    "relUrl": "/ru-rRU/user/connections.html#поведение-при-повторном-подключении"
  },"250": {
    "doc": "Соединения",
    "title": "Подключение к компьютеру",
    "content": "На компьютере (Linux/macOS/Windows) приложение поддерживает: . | Bluetooth (BLE) — через библиотеку Kable; работает на macOS, Linux и Windows | Последовательный USB — основной способ проводного подключения | TCP/IP — для радиостанций, подключенных к сети | . См. десктопное приложение для информации о платформе и сочетаниях клавиш. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/connections.html#%D0%BF%D0%BE%D0%B4%D0%BA%D0%BB%D1%8E%D1%87%D0%B5%D0%BD%D0%B8%D0%B5-%D0%BA-%D0%BA%D0%BE%D0%BC%D0%BF%D1%8C%D1%8E%D1%82%D0%B5%D1%80%D1%83",
    
    "relUrl": "/ru-rRU/user/connections.html#подключение-к-компьютеру"
  },"251": {
    "doc": "Соединения",
    "title": "Связанные темы",
    "content": ". | Начало работы — настройка при первом запуске и разрешения | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | Десктопное приложение — детали подключения, специфичные для настольных компьютеров | Поддерживаемые устройства — полный список совместимых радиоустройств на meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/connections.html#%D1%81%D0%B2%D1%8F%D0%B7%D0%B0%D0%BD%D0%BD%D1%8B%D0%B5-%D1%82%D0%B5%D0%BC%D1%8B",
    
    "relUrl": "/ru-rRU/user/connections.html#связанные-темы"
  },"252": {
    "doc": "Připojení",
    "title": "Připojení",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/connections.html",
    
    "relUrl": "/cs-rCZ/user/connections.html"
  },"253": {
    "doc": "Připojení",
    "title": "Bluetooth (BLE)",
    "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Use the transport selector — a segmented button row below the connection card — to switch between the Bluetooth, Network, and USB transports (one is active at a time): . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | What it means | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. Connection Status . | Icon | State | Popis | . | 🟢 | Připojeno | Active radio link established | . | 🟡 | Připojování | Handshake in progress | . | 🔴 | Odpojeno | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | Zařízení spí | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | Connection drops: Move closer to the radio; check for interference. | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/connections.html#bluetooth-ble",
    
    "relUrl": "/cs-rCZ/user/connections.html#bluetooth-ble"
  },"254": {
    "doc": "Připojení",
    "title": "USB Serial",
    "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | The connection is established automatically. | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/connections.html#usb-serial",
    
    "relUrl": "/cs-rCZ/user/connections.html#usb-serial"
  },"255": {
    "doc": "Připojení",
    "title": "TCP/IP (Network)",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect tab, select Network in the transport selector. | Choose the radio one of two ways: . | Scan for network devices — toggle this on to auto-discover radios that advertise themselves on the local network (mDNS / _meshtastic._tcp). Discovered devices appear in the list; tap one to connect. | Add device manually… — enter the radio’s IP address (or hostname) and port (default: 4403). | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . Nastavení Wi-Fi pro mPWRD-OS . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/connections.html#tcpip-network",
    
    "relUrl": "/cs-rCZ/user/connections.html#tcpip-network"
  },"256": {
    "doc": "Připojení",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/connections.html#after-your-first-connection",
    
    "relUrl": "/cs-rCZ/user/connections.html#after-your-first-connection"
  },"257": {
    "doc": "Připojení",
    "title": "Reconnection Behavior",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/connections.html#reconnection-behavior",
    
    "relUrl": "/cs-rCZ/user/connections.html#reconnection-behavior"
  },"258": {
    "doc": "Připojení",
    "title": "Desktop Connections",
    "content": "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 for platform-specific details and keyboard shortcuts. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/connections.html#desktop-connections",
    
    "relUrl": "/cs-rCZ/user/connections.html#desktop-connections"
  },"259": {
    "doc": "Připojení",
    "title": "Related Topics",
    "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | Desktop App — desktop-specific connection details | Supported devices — full list of compatible radios on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/connections.html#related-topics",
    
    "relUrl": "/cs-rCZ/user/connections.html#related-topics"
  },"260": {
    "doc": "Връзки",
    "title": "Връзки",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/connections.html",
    
    "relUrl": "/bg-rBG/user/connections.html"
  },"261": {
    "doc": "Връзки",
    "title": "Bluetooth (BLE)",
    "content": "Bluetooth Low Energy е методът за свързване по подразбиране и най-често срещаният в Android. Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | Отворете приложението и отидете в раздела Свързване. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Use the transport selector — a segmented button row below the connection card — to switch between the Bluetooth, Network, and USB transports (one is active at a time): . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | What it means | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. Състояние на връзката . | Икона | Състояние | Описание | . | 🟢 | Свързано | Установена активна радиовръзка | . | 🟡 | Свързване | Ръкостискането е в ход | . | 🔴 | Прекъсната връзка | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | Устройството спи | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | Connection drops: Move closer to the radio; check for interference. | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/connections.html#bluetooth-ble",
    
    "relUrl": "/bg-rBG/user/connections.html#bluetooth-ble"
  },"262": {
    "doc": "Връзки",
    "title": "USB Serial",
    "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Настройка . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | The connection is established automatically. | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/connections.html#usb-serial",
    
    "relUrl": "/bg-rBG/user/connections.html#usb-serial"
  },"263": {
    "doc": "Връзки",
    "title": "TCP/IP (Network)",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Свързване през мрежата . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect tab, select Network in the transport selector. | Choose the radio one of two ways: . | Scan for network devices — toggle this on to auto-discover radios that advertise themselves on the local network (mDNS / _meshtastic._tcp). Discovered devices appear in the list; tap one to connect. | Add device manually… — enter the radio’s IP address (or hostname) and port (default: 4403). | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . Осигуряване на Wi-Fi за mPWRD-OS . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/connections.html#tcpip-network",
    
    "relUrl": "/bg-rBG/user/connections.html#tcpip-network"
  },"264": {
    "doc": "Връзки",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/connections.html#after-your-first-connection",
    
    "relUrl": "/bg-rBG/user/connections.html#after-your-first-connection"
  },"265": {
    "doc": "Връзки",
    "title": "Reconnection Behavior",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/connections.html#reconnection-behavior",
    
    "relUrl": "/bg-rBG/user/connections.html#reconnection-behavior"
  },"266": {
    "doc": "Връзки",
    "title": "Desktop Connections",
    "content": "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 for platform-specific details and keyboard shortcuts. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/connections.html#desktop-connections",
    
    "relUrl": "/bg-rBG/user/connections.html#desktop-connections"
  },"267": {
    "doc": "Връзки",
    "title": "Related Topics",
    "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | Desktop App — desktop-specific connection details | Supported devices — full list of compatible radios on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/connections.html#related-topics",
    
    "relUrl": "/bg-rBG/user/connections.html#related-topics"
  },"268": {
    "doc": "Connections",
    "title": "Connections",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/connections.html",
    
    "relUrl": "/ga-rIE/user/connections.html"
  },"269": {
    "doc": "Connections",
    "title": "Bluetooth (BLE)",
    "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Use the transport selector — a segmented button row below the connection card — to switch between the Bluetooth, Network, and USB transports (one is active at a time): . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | What it means | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. Connection Status . | Icon | State | Cur síos | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Na ceangailte | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | Gléas ina chodladh | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | Connection drops: Move closer to the radio; check for interference. | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/connections.html#bluetooth-ble",
    
    "relUrl": "/ga-rIE/user/connections.html#bluetooth-ble"
  },"270": {
    "doc": "Connections",
    "title": "USB Serial",
    "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | The connection is established automatically. | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/connections.html#usb-serial",
    
    "relUrl": "/ga-rIE/user/connections.html#usb-serial"
  },"271": {
    "doc": "Connections",
    "title": "TCP/IP (Network)",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect tab, select Network in the transport selector. | Choose the radio one of two ways: . | Scan for network devices — toggle this on to auto-discover radios that advertise themselves on the local network (mDNS / _meshtastic._tcp). Discovered devices appear in the list; tap one to connect. | Add device manually… — enter the radio’s IP address (or hostname) and port (default: 4403). | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . Wi-Fi Provisioning for mPWRD-OS . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/connections.html#tcpip-network",
    
    "relUrl": "/ga-rIE/user/connections.html#tcpip-network"
  },"272": {
    "doc": "Connections",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/connections.html#after-your-first-connection",
    
    "relUrl": "/ga-rIE/user/connections.html#after-your-first-connection"
  },"273": {
    "doc": "Connections",
    "title": "Reconnection Behavior",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/connections.html#reconnection-behavior",
    
    "relUrl": "/ga-rIE/user/connections.html#reconnection-behavior"
  },"274": {
    "doc": "Connections",
    "title": "Desktop Connections",
    "content": "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 for platform-specific details and keyboard shortcuts. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/connections.html#desktop-connections",
    
    "relUrl": "/ga-rIE/user/connections.html#desktop-connections"
  },"275": {
    "doc": "Connections",
    "title": "Related Topics",
    "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | Desktop App — desktop-specific connection details | Supported devices — full list of compatible radios on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/connections.html#related-topics",
    
    "relUrl": "/ga-rIE/user/connections.html#related-topics"
  },"276": {
    "doc": "Connexions",
    "title": "Connexions",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/connections.html",
    
    "relUrl": "/fr-rCA/user/connections.html"
  },"277": {
    "doc": "Connexions",
    "title": "Bluetooth (BLE)",
    "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Use the transport selector — a segmented button row below the connection card — to switch between the Bluetooth, Network, and USB transports (one is active at a time): . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | What it means | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. Connection Status . | Icon | State | Description | . | 🟢 | Connecté | Active radio link established | . | 🟡 | Connexion en cours | Handshake in progress | . | 🔴 | Déconnecté | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | Appareil en veille | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | Connection drops: Move closer to the radio; check for interference. | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/connections.html#bluetooth-ble",
    
    "relUrl": "/fr-rCA/user/connections.html#bluetooth-ble"
  },"278": {
    "doc": "Connexions",
    "title": "USB Serial",
    "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | The connection is established automatically. | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/connections.html#usb-serial",
    
    "relUrl": "/fr-rCA/user/connections.html#usb-serial"
  },"279": {
    "doc": "Connexions",
    "title": "TCP/IP (Network)",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect tab, select Network in the transport selector. | Choose the radio one of two ways: . | Scan for network devices — toggle this on to auto-discover radios that advertise themselves on the local network (mDNS / _meshtastic._tcp). Discovered devices appear in the list; tap one to connect. | Add device manually… — enter the radio’s IP address (or hostname) and port (default: 4403). | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . Approvisionnement Wi-Fi pour mPWRD-OS . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/connections.html#tcpip-network",
    
    "relUrl": "/fr-rCA/user/connections.html#tcpip-network"
  },"280": {
    "doc": "Connexions",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/connections.html#after-your-first-connection",
    
    "relUrl": "/fr-rCA/user/connections.html#after-your-first-connection"
  },"281": {
    "doc": "Connexions",
    "title": "Reconnection Behavior",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/connections.html#reconnection-behavior",
    
    "relUrl": "/fr-rCA/user/connections.html#reconnection-behavior"
  },"282": {
    "doc": "Connexions",
    "title": "Desktop Connections",
    "content": "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 for platform-specific details and keyboard shortcuts. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/connections.html#desktop-connections",
    
    "relUrl": "/fr-rCA/user/connections.html#desktop-connections"
  },"283": {
    "doc": "Connexions",
    "title": "Related Topics",
    "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | Desktop App — desktop-specific connection details | Supported devices — full list of compatible radios on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/connections.html#related-topics",
    
    "relUrl": "/fr-rCA/user/connections.html#related-topics"
  },"284": {
    "doc": "Connections",
    "title": "Connections",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/srp/user/connections.html",
    
    "relUrl": "/srp/user/connections.html"
  },"285": {
    "doc": "Connections",
    "title": "Bluetooth (BLE)",
    "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Use the transport selector — a segmented button row below the connection card — to switch between the Bluetooth, Network, and USB transports (one is active at a time): . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | What it means | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. Connection Status . | Иконица | State | Опис | . | 🟢 | Блутут повезан | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Раскачено | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | Уређај је у стању спавања | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | Connection drops: Move closer to the radio; check for interference. | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/srp/user/connections.html#bluetooth-ble",
    
    "relUrl": "/srp/user/connections.html#bluetooth-ble"
  },"286": {
    "doc": "Connections",
    "title": "USB Serial",
    "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | The connection is established automatically. | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/srp/user/connections.html#usb-serial",
    
    "relUrl": "/srp/user/connections.html#usb-serial"
  },"287": {
    "doc": "Connections",
    "title": "TCP/IP (Network)",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect tab, select Network in the transport selector. | Choose the radio one of two ways: . | Scan for network devices — toggle this on to auto-discover radios that advertise themselves on the local network (mDNS / _meshtastic._tcp). Discovered devices appear in the list; tap one to connect. | Add device manually… — enter the radio’s IP address (or hostname) and port (default: 4403). | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . Wi-Fi Provisioning for mPWRD-OS . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/srp/user/connections.html#tcpip-network",
    
    "relUrl": "/srp/user/connections.html#tcpip-network"
  },"288": {
    "doc": "Connections",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/srp/user/connections.html#after-your-first-connection",
    
    "relUrl": "/srp/user/connections.html#after-your-first-connection"
  },"289": {
    "doc": "Connections",
    "title": "Reconnection Behavior",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/srp/user/connections.html#reconnection-behavior",
    
    "relUrl": "/srp/user/connections.html#reconnection-behavior"
  },"290": {
    "doc": "Connections",
    "title": "Desktop Connections",
    "content": "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 for platform-specific details and keyboard shortcuts. ",
    "url": "/Meshtastic-Android/main/srp/user/connections.html#desktop-connections",
    
    "relUrl": "/srp/user/connections.html#desktop-connections"
  },"291": {
    "doc": "Connections",
    "title": "Related Topics",
    "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | Desktop App — desktop-specific connection details | Supported devices — full list of compatible radios on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/srp/user/connections.html#related-topics",
    
    "relUrl": "/srp/user/connections.html#related-topics"
  },"292": {
    "doc": "Connections",
    "title": "Connections",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/connections.html",
    
    "relUrl": "/ca-rES/user/connections.html"
  },"293": {
    "doc": "Connections",
    "title": "Bluetooth (BLE)",
    "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Use the transport selector — a segmented button row below the connection card — to switch between the Bluetooth, Network, and USB transports (one is active at a time): . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | What it means | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. Connection Status . | Icon | State | Descripció | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Desconnectat | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | Dispositiu hivernant | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | Connection drops: Move closer to the radio; check for interference. | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/connections.html#bluetooth-ble",
    
    "relUrl": "/ca-rES/user/connections.html#bluetooth-ble"
  },"294": {
    "doc": "Connections",
    "title": "USB Serial",
    "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | The connection is established automatically. | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/connections.html#usb-serial",
    
    "relUrl": "/ca-rES/user/connections.html#usb-serial"
  },"295": {
    "doc": "Connections",
    "title": "TCP/IP (Network)",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect tab, select Network in the transport selector. | Choose the radio one of two ways: . | Scan for network devices — toggle this on to auto-discover radios that advertise themselves on the local network (mDNS / _meshtastic._tcp). Discovered devices appear in the list; tap one to connect. | Add device manually… — enter the radio’s IP address (or hostname) and port (default: 4403). | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . Wi-Fi Provisioning for mPWRD-OS . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/connections.html#tcpip-network",
    
    "relUrl": "/ca-rES/user/connections.html#tcpip-network"
  },"296": {
    "doc": "Connections",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/connections.html#after-your-first-connection",
    
    "relUrl": "/ca-rES/user/connections.html#after-your-first-connection"
  },"297": {
    "doc": "Connections",
    "title": "Reconnection Behavior",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/connections.html#reconnection-behavior",
    
    "relUrl": "/ca-rES/user/connections.html#reconnection-behavior"
  },"298": {
    "doc": "Connections",
    "title": "Desktop Connections",
    "content": "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 for platform-specific details and keyboard shortcuts. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/connections.html#desktop-connections",
    
    "relUrl": "/ca-rES/user/connections.html#desktop-connections"
  },"299": {
    "doc": "Connections",
    "title": "Related Topics",
    "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | Desktop App — desktop-specific connection details | Supported devices — full list of compatible radios on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/connections.html#related-topics",
    
    "relUrl": "/ca-rES/user/connections.html#related-topics"
  },"300": {
    "doc": "Connections",
    "title": "Connections",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/connections.html",
    
    "relUrl": "/ko-rKR/user/connections.html"
  },"301": {
    "doc": "Connections",
    "title": "Bluetooth (BLE)",
    "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Use the transport selector — a segmented button row below the connection card — to switch between the Bluetooth, Network, and USB transports (one is active at a time): . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | What it means | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. Connection Status . | Icon | State | 설명 | . | 🟢 | 연결됨 | Active radio link established | . | 🟡 | 연결 중 | Handshake in progress | . | 🔴 | 연결 끊김 | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | 절전모드 | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | Connection drops: Move closer to the radio; check for interference. | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/connections.html#bluetooth-ble",
    
    "relUrl": "/ko-rKR/user/connections.html#bluetooth-ble"
  },"302": {
    "doc": "Connections",
    "title": "USB Serial",
    "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | The connection is established automatically. | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/connections.html#usb-serial",
    
    "relUrl": "/ko-rKR/user/connections.html#usb-serial"
  },"303": {
    "doc": "Connections",
    "title": "TCP/IP (Network)",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect tab, select Network in the transport selector. | Choose the radio one of two ways: . | Scan for network devices — toggle this on to auto-discover radios that advertise themselves on the local network (mDNS / _meshtastic._tcp). Discovered devices appear in the list; tap one to connect. | Add device manually… — enter the radio’s IP address (or hostname) and port (default: 4403). | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . Wi-Fi Provisioning for mPWRD-OS . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/connections.html#tcpip-network",
    
    "relUrl": "/ko-rKR/user/connections.html#tcpip-network"
  },"304": {
    "doc": "Connections",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/connections.html#after-your-first-connection",
    
    "relUrl": "/ko-rKR/user/connections.html#after-your-first-connection"
  },"305": {
    "doc": "Connections",
    "title": "Reconnection Behavior",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/connections.html#reconnection-behavior",
    
    "relUrl": "/ko-rKR/user/connections.html#reconnection-behavior"
  },"306": {
    "doc": "Connections",
    "title": "Desktop Connections",
    "content": "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 for platform-specific details and keyboard shortcuts. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/connections.html#desktop-connections",
    
    "relUrl": "/ko-rKR/user/connections.html#desktop-connections"
  },"307": {
    "doc": "Connections",
    "title": "Related Topics",
    "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | Desktop App — desktop-specific connection details | Supported devices — full list of compatible radios on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/connections.html#related-topics",
    
    "relUrl": "/ko-rKR/user/connections.html#related-topics"
  },"308": {
    "doc": "Connections",
    "title": "Connections",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/connections.html",
    
    "relUrl": "/sv-rSE/user/connections.html"
  },"309": {
    "doc": "Connections",
    "title": "Bluetooth (BLE)",
    "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Use the transport selector — a segmented button row below the connection card — to switch between the Bluetooth, Network, and USB transports (one is active at a time): . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | What it means | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. Connection Status . | Icon | State | Beskrivning | . | 🟢 | Ansluten | Active radio link established | . | 🟡 | Ansluter | Handshake in progress | . | 🔴 | Frånkopplad | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | Enheten i sovläge | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | Connection drops: Move closer to the radio; check for interference. | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/connections.html#bluetooth-ble",
    
    "relUrl": "/sv-rSE/user/connections.html#bluetooth-ble"
  },"310": {
    "doc": "Connections",
    "title": "USB Serial",
    "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | The connection is established automatically. | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/connections.html#usb-serial",
    
    "relUrl": "/sv-rSE/user/connections.html#usb-serial"
  },"311": {
    "doc": "Connections",
    "title": "TCP/IP (Network)",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect tab, select Network in the transport selector. | Choose the radio one of two ways: . | Scan for network devices — toggle this on to auto-discover radios that advertise themselves on the local network (mDNS / _meshtastic._tcp). Discovered devices appear in the list; tap one to connect. | Add device manually… — enter the radio’s IP address (or hostname) and port (default: 4403). | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . Wi-Fi Provisioning for mPWRD-OS . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/connections.html#tcpip-network",
    
    "relUrl": "/sv-rSE/user/connections.html#tcpip-network"
  },"312": {
    "doc": "Connections",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/connections.html#after-your-first-connection",
    
    "relUrl": "/sv-rSE/user/connections.html#after-your-first-connection"
  },"313": {
    "doc": "Connections",
    "title": "Reconnection Behavior",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/connections.html#reconnection-behavior",
    
    "relUrl": "/sv-rSE/user/connections.html#reconnection-behavior"
  },"314": {
    "doc": "Connections",
    "title": "Desktop Connections",
    "content": "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 for platform-specific details and keyboard shortcuts. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/connections.html#desktop-connections",
    
    "relUrl": "/sv-rSE/user/connections.html#desktop-connections"
  },"315": {
    "doc": "Connections",
    "title": "Related Topics",
    "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | Desktop App — desktop-specific connection details | Supported devices — full list of compatible radios on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/connections.html#related-topics",
    
    "relUrl": "/sv-rSE/user/connections.html#related-topics"
  },"316": {
    "doc": "Connections",
    "title": "Connections",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/connections.html",
    
    "relUrl": "/ht-rHT/user/connections.html"
  },"317": {
    "doc": "Connections",
    "title": "Bluetooth (BLE)",
    "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Use the transport selector — a segmented button row below the connection card — to switch between the Bluetooth, Network, and USB transports (one is active at a time): . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | What it means | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. Connection Status . | Icon | State | Deskripsyon | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Dekonekte | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | Aparèy ap dòmi | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | Connection drops: Move closer to the radio; check for interference. | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/connections.html#bluetooth-ble",
    
    "relUrl": "/ht-rHT/user/connections.html#bluetooth-ble"
  },"318": {
    "doc": "Connections",
    "title": "USB Serial",
    "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | The connection is established automatically. | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/connections.html#usb-serial",
    
    "relUrl": "/ht-rHT/user/connections.html#usb-serial"
  },"319": {
    "doc": "Connections",
    "title": "TCP/IP (Network)",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect tab, select Network in the transport selector. | Choose the radio one of two ways: . | Scan for network devices — toggle this on to auto-discover radios that advertise themselves on the local network (mDNS / _meshtastic._tcp). Discovered devices appear in the list; tap one to connect. | Add device manually… — enter the radio’s IP address (or hostname) and port (default: 4403). | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . Wi-Fi Provisioning for mPWRD-OS . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/connections.html#tcpip-network",
    
    "relUrl": "/ht-rHT/user/connections.html#tcpip-network"
  },"320": {
    "doc": "Connections",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/connections.html#after-your-first-connection",
    
    "relUrl": "/ht-rHT/user/connections.html#after-your-first-connection"
  },"321": {
    "doc": "Connections",
    "title": "Reconnection Behavior",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/connections.html#reconnection-behavior",
    
    "relUrl": "/ht-rHT/user/connections.html#reconnection-behavior"
  },"322": {
    "doc": "Connections",
    "title": "Desktop Connections",
    "content": "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 for platform-specific details and keyboard shortcuts. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/connections.html#desktop-connections",
    
    "relUrl": "/ht-rHT/user/connections.html#desktop-connections"
  },"323": {
    "doc": "Connections",
    "title": "Related Topics",
    "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | Desktop App — desktop-specific connection details | Supported devices — full list of compatible radios on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/connections.html#related-topics",
    
    "relUrl": "/ht-rHT/user/connections.html#related-topics"
  },"324": {
    "doc": "Connections",
    "title": "Connections",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/connections.html",
    
    "relUrl": "/sr-rLatn/user/connections.html"
  },"325": {
    "doc": "Connections",
    "title": "Bluetooth (BLE)",
    "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Use the transport selector — a segmented button row below the connection card — to switch between the Bluetooth, Network, and USB transports (one is active at a time): . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | What it means | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. Connection Status . | Иконица | State | Опис | . | 🟢 | Блутут повезан | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Raskačeno | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | Uređaj je u stanju spavanja | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | Connection drops: Move closer to the radio; check for interference. | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/connections.html#bluetooth-ble",
    
    "relUrl": "/sr-rLatn/user/connections.html#bluetooth-ble"
  },"326": {
    "doc": "Connections",
    "title": "USB Serial",
    "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | The connection is established automatically. | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/connections.html#usb-serial",
    
    "relUrl": "/sr-rLatn/user/connections.html#usb-serial"
  },"327": {
    "doc": "Connections",
    "title": "TCP/IP (Network)",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect tab, select Network in the transport selector. | Choose the radio one of two ways: . | Scan for network devices — toggle this on to auto-discover radios that advertise themselves on the local network (mDNS / _meshtastic._tcp). Discovered devices appear in the list; tap one to connect. | Add device manually… — enter the radio’s IP address (or hostname) and port (default: 4403). | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . Wi-Fi Provisioning for mPWRD-OS . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/connections.html#tcpip-network",
    
    "relUrl": "/sr-rLatn/user/connections.html#tcpip-network"
  },"328": {
    "doc": "Connections",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/connections.html#after-your-first-connection",
    
    "relUrl": "/sr-rLatn/user/connections.html#after-your-first-connection"
  },"329": {
    "doc": "Connections",
    "title": "Reconnection Behavior",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/connections.html#reconnection-behavior",
    
    "relUrl": "/sr-rLatn/user/connections.html#reconnection-behavior"
  },"330": {
    "doc": "Connections",
    "title": "Desktop Connections",
    "content": "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 for platform-specific details and keyboard shortcuts. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/connections.html#desktop-connections",
    
    "relUrl": "/sr-rLatn/user/connections.html#desktop-connections"
  },"331": {
    "doc": "Connections",
    "title": "Related Topics",
    "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | Desktop App — desktop-specific connection details | Supported devices — full list of compatible radios on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/connections.html#related-topics",
    
    "relUrl": "/sr-rLatn/user/connections.html#related-topics"
  },"332": {
    "doc": "Connections",
    "title": "Connections",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/connections.html",
    
    "relUrl": "/nl-rNL/user/connections.html"
  },"333": {
    "doc": "Connections",
    "title": "Bluetooth (BLE)",
    "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Use the transport selector — a segmented button row below the connection card — to switch between the Bluetooth, Network, and USB transports (one is active at a time): . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | What it means | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. Connection Status . | Icon | State | Beschrijving | . | 🟢 | Verbonden | Active radio link established | . | 🟡 | Bezig met verbinden | Handshake in progress | . | 🔴 | Niet verbonden | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | Apparaat in slaapstand | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | Connection drops: Move closer to the radio; check for interference. | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/connections.html#bluetooth-ble",
    
    "relUrl": "/nl-rNL/user/connections.html#bluetooth-ble"
  },"334": {
    "doc": "Connections",
    "title": "USB Serial",
    "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | The connection is established automatically. | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/connections.html#usb-serial",
    
    "relUrl": "/nl-rNL/user/connections.html#usb-serial"
  },"335": {
    "doc": "Connections",
    "title": "TCP/IP (Network)",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect tab, select Network in the transport selector. | Choose the radio one of two ways: . | Scan for network devices — toggle this on to auto-discover radios that advertise themselves on the local network (mDNS / _meshtastic._tcp). Discovered devices appear in the list; tap one to connect. | Add device manually… — enter the radio’s IP address (or hostname) and port (default: 4403). | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . Wi-Fi Provisioning for mPWRD-OS . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/connections.html#tcpip-network",
    
    "relUrl": "/nl-rNL/user/connections.html#tcpip-network"
  },"336": {
    "doc": "Connections",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/connections.html#after-your-first-connection",
    
    "relUrl": "/nl-rNL/user/connections.html#after-your-first-connection"
  },"337": {
    "doc": "Connections",
    "title": "Reconnection Behavior",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/connections.html#reconnection-behavior",
    
    "relUrl": "/nl-rNL/user/connections.html#reconnection-behavior"
  },"338": {
    "doc": "Connections",
    "title": "Desktop Connections",
    "content": "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 for platform-specific details and keyboard shortcuts. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/connections.html#desktop-connections",
    
    "relUrl": "/nl-rNL/user/connections.html#desktop-connections"
  },"339": {
    "doc": "Connections",
    "title": "Related Topics",
    "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | Desktop App — desktop-specific connection details | Supported devices — full list of compatible radios on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/connections.html#related-topics",
    
    "relUrl": "/nl-rNL/user/connections.html#related-topics"
  },"340": {
    "doc": "Connections",
    "title": "Connections",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/connections.html",
    
    "relUrl": "/uk-rUA/user/connections.html"
  },"341": {
    "doc": "Connections",
    "title": "Bluetooth (BLE)",
    "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Use the transport selector — a segmented button row below the connection card — to switch between the Bluetooth, Network, and USB transports (one is active at a time): . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | What it means | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. Connection Status . | Icon | State | Опис | . | 🟢 | Під’єднано | Active radio link established | . | 🟡 | Під’єднання | Handshake in progress | . | 🔴 | Відключено | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | Пристрій в режимі сну | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | Connection drops: Move closer to the radio; check for interference. | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/connections.html#bluetooth-ble",
    
    "relUrl": "/uk-rUA/user/connections.html#bluetooth-ble"
  },"342": {
    "doc": "Connections",
    "title": "USB Serial",
    "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | The connection is established automatically. | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/connections.html#usb-serial",
    
    "relUrl": "/uk-rUA/user/connections.html#usb-serial"
  },"343": {
    "doc": "Connections",
    "title": "TCP/IP (Network)",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect tab, select Network in the transport selector. | Choose the radio one of two ways: . | Scan for network devices — toggle this on to auto-discover radios that advertise themselves on the local network (mDNS / _meshtastic._tcp). Discovered devices appear in the list; tap one to connect. | Add device manually… — enter the radio’s IP address (or hostname) and port (default: 4403). | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . Налаштування Wi-Fi для mPWRD-OS . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/connections.html#tcpip-network",
    
    "relUrl": "/uk-rUA/user/connections.html#tcpip-network"
  },"344": {
    "doc": "Connections",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/connections.html#after-your-first-connection",
    
    "relUrl": "/uk-rUA/user/connections.html#after-your-first-connection"
  },"345": {
    "doc": "Connections",
    "title": "Reconnection Behavior",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/connections.html#reconnection-behavior",
    
    "relUrl": "/uk-rUA/user/connections.html#reconnection-behavior"
  },"346": {
    "doc": "Connections",
    "title": "Desktop Connections",
    "content": "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 for platform-specific details and keyboard shortcuts. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/connections.html#desktop-connections",
    
    "relUrl": "/uk-rUA/user/connections.html#desktop-connections"
  },"347": {
    "doc": "Connections",
    "title": "Related Topics",
    "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | Desktop App — desktop-specific connection details | Supported devices — full list of compatible radios on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/connections.html#related-topics",
    
    "relUrl": "/uk-rUA/user/connections.html#related-topics"
  },"348": {
    "doc": "Yhteydet",
    "title": "Yhteydet",
    "content": "Meshtastic tukee useita yhteystapoja puhelimen tai työpöydän ja radion väliseen tiedonsiirtoon. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/connections.html",
    
    "relUrl": "/fi-rFI/user/connections.html"
  },"349": {
    "doc": "Yhteydet",
    "title": "Bluetooth (BLE)",
    "content": "Bluetooth Low Energy on oletus ja yleisin yhteystapa Androidilla. Radion pariliittäminen . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | Avaa sovellus ja siirry Yhdistä-välilehdelle. | Napauta Hae bluetooth-laitteita — lähellä olevat Meshtastic-radiot ilmestyvät näkyville. | Valitse radiosi luettelosta. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Vaihda bluetooth-, verkko- ja USB-yhteyksien välillä käyttämällä yhteyskortin alapuolella olevaa yhteysvalitsinta (vain yksi yhteystapa voi olla aktiivinen kerrallaan): . 💡 Vinkki: Jos radioasi ei näy, varmista, ettei se ole jo yhdistetty toiseen puhelimeen tai ettei se ole kantaman ulkopuolella. Näytössä kerrotaan kaikki sovelluksen puolella olevat syyt, jotka estävät haun, sekä niiden ratkaisut: . | Näet seuraavan | Mitä se tarkoittaa | . | Kortti pyytää Lähistön laitteet -käyttöoikeutta | Käyttöoikeutta ei ole myönnetty. Myönnä käyttöoikeus pyytää sitä. Kun Android lakkaa kysymästä, painikkeeksi muuttuu Avaa asetukset. | . | Bluetooth on pois käytöstä | Bluetooth-sovitin on poistettu käytöstä – kortti avaa Bluetooth-asetukset. | . | Bluetooth-laitteiden haku edellyttää myös sijaintipalvelujen käyttöä | Vain Android 11:ssä ja vanhemmissa versioissa: käyttöoikeus on myönnetty, mutta järjestelmän sijaintipalvelut ovat pois käytöstä. | . | Ei korttia, tyhjä luettelo | Mikään sovelluksen puolella ei estä hakua – radio on kantaman ulkopuolella, pois käytöstä tai jo yhdistetty toiseen laitteeseen. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. Yhteyden tila . | Ikoni | Tila | Kuvaus | . | 🟢 | Yhdistetty | Aktiivinen radiolinkki muodostettu | . | 🟡 | Yhdistetään | Yhteyden muodostus käynnissä | . | 🔴 | Ei yhdistetty | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | Laite on lepotilassa | Radio on kevyessä lepotilassa — sovellus odottaa sen heräävän ja muodostavan yhteyden uudelleen, kyse ei ole virheestä | . Nämä ovat neljä yhteystilaa, joita sovellus käyttää. “Laite lepotilassa” on normaali virransäästöasetuksissa eikä vaadi mitään toimenpiteitä. Yhteyttä muodostettaessa tilailmaisin näyttää nykyisen yhteyden tilan — napauta Lopeta yhteyden muodostaminen keskeyttääksesi yrityksen: . Jos laitteita ei löydy, sovellus näyttää tyhjän näkymän ohjeiden kanssa: . Bluetoothin vianmääritys . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | Yhteys katkeaa: Siirry lähemmäs radiota ja tarkista mahdolliset häiriöt. | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | Paritus hylätty: Poista laite Androidin Bluetooth-asetuksista ja yritä uudelleen. | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/connections.html#bluetooth-ble",
    
    "relUrl": "/fi-rFI/user/connections.html#bluetooth-ble"
  },"350": {
    "doc": "Yhteydet",
    "title": "USB-sarjaporttiyhteys",
    "content": "USB-yhteydet tarjoavat langallisen vaihtoehdon, hyödyllinen työpöytäkäytössä tai kun Bluetooth ei ole käytettävissä. Asetukset . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | Sovellus pyytää USB-käyttöoikeutta — napauta Salli. | Yhteys muodostetaan automaattisesti. | . ℹ️ Huomautus: USB-yhteydet edellyttävät Android-laitteissa OTG-tukea. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/connections.html#usb-sarjaporttiyhteys",
    
    "relUrl": "/fi-rFI/user/connections.html#usb-sarjaporttiyhteys"
  },"351": {
    "doc": "Yhteydet",
    "title": "TCP/IP (Verkko)",
    "content": "Jotkin Meshtastic-radiot tukevat WiFi-/Ethernet-yhteyttä, jolloin TCP-pohjaiset yhteydet toimivat lähiverkon kautta. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Yhdistäminen verkon kautta . | Varmista, että radio on samassa lähiverkossa kuin puhelimesi tai tietokoneesi. | On the Connect tab, select Network in the transport selector. | Valitse radio jommallakummalla seuraavista tavoista: . | Hae verkkolaitteita — ota tämä käyttöön, jotta lähiverkossa itsensä ilmoittavat radiot löytyvät automaattisesti (mDNS / _meshtastic._tcp). Löydetyt laitteet näkyvät luettelossa; yhdistä napauttamalla haluamaasi laitetta. | Lisää laite manuaalisesti — anna radion IP-osoite (tai isäntänimi) ja portti (oletus: 4403). | . | Aiemmin käytetyt verkko-osoitteet muistetaan kohdassa Viimeisimmät verkkolaitteet, jotta yhteyden muodostaminen uudelleen käy nopeasti (poista osoite koskettamalla sitä pitkään). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. Milloin TCP-yhteyttä kannattaa käyttää . | Radio on samassa lähiverkossa | Testaus simuloidulla radiolla | Ympäristöt, joissa Bluetoothissa on häiriöongelmia | . WiFi-määritys mPWRD-OS:lle . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/connections.html#tcpip-verkko",
    
    "relUrl": "/fi-rFI/user/connections.html#tcpip-verkko"
  },"352": {
    "doc": "Yhteydet",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/connections.html#after-your-first-connection",
    
    "relUrl": "/fi-rFI/user/connections.html#after-your-first-connection"
  },"353": {
    "doc": "Yhteydet",
    "title": "Uudelleenyhdistämisen toiminta",
    "content": "Sovellus muodostaa käynnistyessään automaattisesti yhteyden viimeksi valittuun radioon. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/connections.html#uudelleenyhdist%C3%A4misen-toiminta",
    
    "relUrl": "/fi-rFI/user/connections.html#uudelleenyhdistämisen-toiminta"
  },"354": {
    "doc": "Yhteydet",
    "title": "Työpöytäyhteydet",
    "content": "Työpöydällä (Linux/macOS/Windows) sovellus tukee: . | Bluetooth (BLE) — Kable-kirjaston kautta; toimii macOS:llä, Linuxilla ja Windowsilla | USB-sarjaportti — ensisijainen langallinen yhteystapa | TCP/IP — verkkoyhteydellä oleville radioille | . Katso Työpöytäsovellus alustakohtaiset tiedot ja pikanäppäimet. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/connections.html#ty%C3%B6p%C3%B6yt%C3%A4yhteydet",
    
    "relUrl": "/fi-rFI/user/connections.html#työpöytäyhteydet"
  },"355": {
    "doc": "Yhteydet",
    "title": "Aiheeseen liittyvät aiheet",
    "content": ". | Aloitus — ensikäynnistyksen käyttöönotto ja käyttöoikeudet | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Radiot — katso, ketkä muut ovat mesh-verkossasi | Työpöytäsovellus — työpöytäkohtaiset yhteystiedot | Tuetut laitteet — täydellinen lista yhteensopivista radioista meshtastic.org -sivustolla | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/connections.html#aiheeseen-liittyv%C3%A4t-aiheet",
    
    "relUrl": "/fi-rFI/user/connections.html#aiheeseen-liittyvät-aiheet"
  },"356": {
    "doc": "Connections",
    "title": "Connections",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/connections.html",
    
    "relUrl": "/is-rIS/user/connections.html"
  },"357": {
    "doc": "Connections",
    "title": "Bluetooth (BLE)",
    "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Use the transport selector — a segmented button row below the connection card — to switch between the Bluetooth, Network, and USB transports (one is active at a time): . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | What it means | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. Connection Status . | Icon | State | Lýsing | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Aftengd | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | Radíó er í svefnham | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | Connection drops: Move closer to the radio; check for interference. | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/connections.html#bluetooth-ble",
    
    "relUrl": "/is-rIS/user/connections.html#bluetooth-ble"
  },"358": {
    "doc": "Connections",
    "title": "USB Serial",
    "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | The connection is established automatically. | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/connections.html#usb-serial",
    
    "relUrl": "/is-rIS/user/connections.html#usb-serial"
  },"359": {
    "doc": "Connections",
    "title": "TCP/IP (Network)",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect tab, select Network in the transport selector. | Choose the radio one of two ways: . | Scan for network devices — toggle this on to auto-discover radios that advertise themselves on the local network (mDNS / _meshtastic._tcp). Discovered devices appear in the list; tap one to connect. | Add device manually… — enter the radio’s IP address (or hostname) and port (default: 4403). | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . Wi-Fi Provisioning for mPWRD-OS . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/connections.html#tcpip-network",
    
    "relUrl": "/is-rIS/user/connections.html#tcpip-network"
  },"360": {
    "doc": "Connections",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/connections.html#after-your-first-connection",
    
    "relUrl": "/is-rIS/user/connections.html#after-your-first-connection"
  },"361": {
    "doc": "Connections",
    "title": "Reconnection Behavior",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/connections.html#reconnection-behavior",
    
    "relUrl": "/is-rIS/user/connections.html#reconnection-behavior"
  },"362": {
    "doc": "Connections",
    "title": "Desktop Connections",
    "content": "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 for platform-specific details and keyboard shortcuts. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/connections.html#desktop-connections",
    
    "relUrl": "/is-rIS/user/connections.html#desktop-connections"
  },"363": {
    "doc": "Connections",
    "title": "Related Topics",
    "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | Desktop App — desktop-specific connection details | Supported devices — full list of compatible radios on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/connections.html#related-topics",
    
    "relUrl": "/is-rIS/user/connections.html#related-topics"
  },"364": {
    "doc": "Connections",
    "title": "Connections",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/connections.html",
    
    "relUrl": "/lt-rLT/user/connections.html"
  },"365": {
    "doc": "Connections",
    "title": "Bluetooth (BLE)",
    "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Use the transport selector — a segmented button row below the connection card — to switch between the Bluetooth, Network, and USB transports (one is active at a time): . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | What it means | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. Connection Status . | Icon | State | Aprašymas | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Atsijungta | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | Įrenginys miega | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | Connection drops: Move closer to the radio; check for interference. | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/connections.html#bluetooth-ble",
    
    "relUrl": "/lt-rLT/user/connections.html#bluetooth-ble"
  },"366": {
    "doc": "Connections",
    "title": "USB Serial",
    "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | The connection is established automatically. | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/connections.html#usb-serial",
    
    "relUrl": "/lt-rLT/user/connections.html#usb-serial"
  },"367": {
    "doc": "Connections",
    "title": "TCP/IP (Network)",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect tab, select Network in the transport selector. | Choose the radio one of two ways: . | Scan for network devices — toggle this on to auto-discover radios that advertise themselves on the local network (mDNS / _meshtastic._tcp). Discovered devices appear in the list; tap one to connect. | Add device manually… — enter the radio’s IP address (or hostname) and port (default: 4403). | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . Wi-Fi Provisioning for mPWRD-OS . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/connections.html#tcpip-network",
    
    "relUrl": "/lt-rLT/user/connections.html#tcpip-network"
  },"368": {
    "doc": "Connections",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/connections.html#after-your-first-connection",
    
    "relUrl": "/lt-rLT/user/connections.html#after-your-first-connection"
  },"369": {
    "doc": "Connections",
    "title": "Reconnection Behavior",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/connections.html#reconnection-behavior",
    
    "relUrl": "/lt-rLT/user/connections.html#reconnection-behavior"
  },"370": {
    "doc": "Connections",
    "title": "Desktop Connections",
    "content": "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 for platform-specific details and keyboard shortcuts. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/connections.html#desktop-connections",
    
    "relUrl": "/lt-rLT/user/connections.html#desktop-connections"
  },"371": {
    "doc": "Connections",
    "title": "Related Topics",
    "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | Desktop App — desktop-specific connection details | Supported devices — full list of compatible radios on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/connections.html#related-topics",
    
    "relUrl": "/lt-rLT/user/connections.html#related-topics"
  },"372": {
    "doc": "Connections",
    "title": "Connections",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/connections.html",
    
    "relUrl": "/gl-rES/user/connections.html"
  },"373": {
    "doc": "Connections",
    "title": "Bluetooth (BLE)",
    "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Use the transport selector — a segmented button row below the connection card — to switch between the Bluetooth, Network, and USB transports (one is active at a time): . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | What it means | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. Connection Status . | Icon | State | Descrición | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Desconectado | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | Dispositivo durmindo | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | Connection drops: Move closer to the radio; check for interference. | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/connections.html#bluetooth-ble",
    
    "relUrl": "/gl-rES/user/connections.html#bluetooth-ble"
  },"374": {
    "doc": "Connections",
    "title": "USB Serial",
    "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | The connection is established automatically. | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/connections.html#usb-serial",
    
    "relUrl": "/gl-rES/user/connections.html#usb-serial"
  },"375": {
    "doc": "Connections",
    "title": "TCP/IP (Network)",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect tab, select Network in the transport selector. | Choose the radio one of two ways: . | Scan for network devices — toggle this on to auto-discover radios that advertise themselves on the local network (mDNS / _meshtastic._tcp). Discovered devices appear in the list; tap one to connect. | Add device manually… — enter the radio’s IP address (or hostname) and port (default: 4403). | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . Wi-Fi Provisioning for mPWRD-OS . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/connections.html#tcpip-network",
    
    "relUrl": "/gl-rES/user/connections.html#tcpip-network"
  },"376": {
    "doc": "Connections",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/connections.html#after-your-first-connection",
    
    "relUrl": "/gl-rES/user/connections.html#after-your-first-connection"
  },"377": {
    "doc": "Connections",
    "title": "Reconnection Behavior",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/connections.html#reconnection-behavior",
    
    "relUrl": "/gl-rES/user/connections.html#reconnection-behavior"
  },"378": {
    "doc": "Connections",
    "title": "Desktop Connections",
    "content": "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 for platform-specific details and keyboard shortcuts. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/connections.html#desktop-connections",
    
    "relUrl": "/gl-rES/user/connections.html#desktop-connections"
  },"379": {
    "doc": "Connections",
    "title": "Related Topics",
    "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | Desktop App — desktop-specific connection details | Supported devices — full list of compatible radios on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/connections.html#related-topics",
    
    "relUrl": "/gl-rES/user/connections.html#related-topics"
  },"380": {
    "doc": "コネクション",
    "title": "コネクション",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/connections.html",
    
    "relUrl": "/ja-rJP/user/connections.html"
  },"381": {
    "doc": "コネクション",
    "title": "Bluetooth（BLE）",
    "content": "Bluetooth Low Energy は、Android で標準的かつ最も一般的な接続方法です。 . Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | アプリを開き、「接続」タブに移動します。 | 「Bluetooth デバイスをスキャン」をタップすると、近くの Meshtastic 無線機が表示されます。 | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. 接続カードの下にあるセグメント化されたボタン列（接続方式のセレクター）を使って、Bluetooth・ネットワーク・USB の接続方式を切り替えます（一度に 1 つが有効になります）： . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | 意味 | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. 接続ステータス . | アイコン | 状態 | 説明 | . | 🟢 | 接続済 | 無線リンクが確立しています | . | 🟡 | 接続中 | ハンドシェイク中 | . | 🔴 | 切断 | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | デバイスはスリープ状態です | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . デバイスが見つからない場合、アプリは操作手順とともに空の状態を表示します： . Bluetooth のトラブルシューティング . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | 接続が切れる： 無線機に近づき、電波干渉がないか確認します。 | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | ペアリングが拒否される： Android の Bluetooth 設定でデバイスの登録を解除し、やり直します。 | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/connections.html#bluetoothble",
    
    "relUrl": "/ja-rJP/user/connections.html#bluetoothble"
  },"382": {
    "doc": "コネクション",
    "title": "USB シリアル",
    "content": "USB 接続は有線での代替手段で、デスクトップや Bluetooth が使えない場合に便利です。 . セットアップ . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | 接続が自動的に確立されます。 | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/connections.html#usb-%E3%82%B7%E3%83%AA%E3%82%A2%E3%83%AB",
    
    "relUrl": "/ja-rJP/user/connections.html#usb-シリアル"
  },"383": {
    "doc": "コネクション",
    "title": "TCP/IP（ネットワーク）",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. ネットワーク経由で接続する . | 無線機がスマートフォン／デスクトップと同じローカルネットワーク上にあることを確認します。 | On the Connect tab, select Network in the transport selector. | 無線機は次の 2 通りの方法で選べます： . | ネットワークデバイスをスキャン：これをオンにすると、ローカルネットワーク上で自身を告知している無線機（mDNS ／ _meshtastic._tcp）を自動的に探索します。見つかったデバイスがリストに表示されるので、タップして接続します。 | デバイスを手動で追加…：無線機の IP アドレス（またはホスト名）とポート（既定：4403）を入力します。 | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. TCP を使う場面 . | 無線機が同じローカルネットワーク上にある | シミュレートされた無線機でテストする | Bluetooth の電波干渉が問題になる環境 | . mPWRD-OS の Wi-Fi プロビジョニング . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/connections.html#tcpip%E3%83%8D%E3%83%83%E3%83%88%E3%83%AF%E3%83%BC%E3%82%AF",
    
    "relUrl": "/ja-rJP/user/connections.html#tcpipネットワーク"
  },"384": {
    "doc": "コネクション",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/connections.html#after-your-first-connection",
    
    "relUrl": "/ja-rJP/user/connections.html#after-your-first-connection"
  },"385": {
    "doc": "コネクション",
    "title": "再接続の動作",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/connections.html#%E5%86%8D%E6%8E%A5%E7%B6%9A%E3%81%AE%E5%8B%95%E4%BD%9C",
    
    "relUrl": "/ja-rJP/user/connections.html#再接続の動作"
  },"386": {
    "doc": "コネクション",
    "title": "デスクトップでの接続",
    "content": "デスクトップ（Linux／macOS／Windows）では、アプリは次の接続方式に対応しています： . | Bluetooth（BLE）： Kable ライブラリを使用。macOS、Linux、Windows で動作します | USB シリアル： 主要な有線接続方法 | TCP/IP： ネットワーク接続された無線機向け | . プラットフォームごとの詳細やキーボードショートカットについては、デスクトップアプリ を参照してください。 . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/connections.html#%E3%83%87%E3%82%B9%E3%82%AF%E3%83%88%E3%83%83%E3%83%97%E3%81%A7%E3%81%AE%E6%8E%A5%E7%B6%9A",
    
    "relUrl": "/ja-rJP/user/connections.html#デスクトップでの接続"
  },"387": {
    "doc": "コネクション",
    "title": "関連トピック",
    "content": ". | はじめに：初回起動時のセットアップと権限 | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | デスクトップアプリ：デスクトップ固有の接続に関する詳細 | 対応デバイス：meshtastic.org にある互換無線機の一覧 | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/connections.html#%E9%96%A2%E9%80%A3%E3%83%88%E3%83%94%E3%83%83%E3%82%AF",
    
    "relUrl": "/ja-rJP/user/connections.html#関連トピック"
  },"388": {
    "doc": "Verbindungen",
    "title": "Verbindungen",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/connections.html",
    
    "relUrl": "/de-rDE/user/connections.html"
  },"389": {
    "doc": "Verbindungen",
    "title": "Bluetooth (BLE)",
    "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Use the transport selector — a segmented button row below the connection card — to switch between the Bluetooth, Network, and USB transports (one is active at a time): . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | What it means | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. Connection Status . | Symbol | Status | Beschreibung | . | 🟢 | Verbunden | Active radio link established | . | 🟡 | Wird verbunden | Handshake in progress | . | 🔴 | Verbindung getrennt | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | Gerät schläft | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | Connection drops: Move closer to the radio; check for interference. | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/connections.html#bluetooth-ble",
    
    "relUrl": "/de-rDE/user/connections.html#bluetooth-ble"
  },"390": {
    "doc": "Verbindungen",
    "title": "USB Serial",
    "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Einstellungen . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | The connection is established automatically. | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/connections.html#usb-serial",
    
    "relUrl": "/de-rDE/user/connections.html#usb-serial"
  },"391": {
    "doc": "Verbindungen",
    "title": "TCP/IP (Network)",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect tab, select Network in the transport selector. | Choose the radio one of two ways: . | Scan for network devices — toggle this on to auto-discover radios that advertise themselves on the local network (mDNS / _meshtastic._tcp). Discovered devices appear in the list; tap one to connect. | Add device manually… — enter the radio’s IP address (or hostname) and port (default: 4403). | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . WLAN Unterstützung für mPWRD-OS . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/connections.html#tcpip-network",
    
    "relUrl": "/de-rDE/user/connections.html#tcpip-network"
  },"392": {
    "doc": "Verbindungen",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/connections.html#after-your-first-connection",
    
    "relUrl": "/de-rDE/user/connections.html#after-your-first-connection"
  },"393": {
    "doc": "Verbindungen",
    "title": "Reconnection Behavior",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/connections.html#reconnection-behavior",
    
    "relUrl": "/de-rDE/user/connections.html#reconnection-behavior"
  },"394": {
    "doc": "Verbindungen",
    "title": "Desktop Connections",
    "content": "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 for platform-specific details and keyboard shortcuts. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/connections.html#desktop-connections",
    
    "relUrl": "/de-rDE/user/connections.html#desktop-connections"
  },"395": {
    "doc": "Verbindungen",
    "title": "Related Topics",
    "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | Desktop App — desktop-specific connection details | Supported devices — full list of compatible radios on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/connections.html#related-topics",
    
    "relUrl": "/de-rDE/user/connections.html#related-topics"
  },"396": {
    "doc": "Connections",
    "title": "Connections",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/connections.html",
    
    "relUrl": "/ar-rSA/user/connections.html"
  },"397": {
    "doc": "Connections",
    "title": "Bluetooth (BLE)",
    "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Use the transport selector — a segmented button row below the connection card — to switch between the Bluetooth, Network, and USB transports (one is active at a time): . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | What it means | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. Connection Status . | Icon | State | الوصف | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | انقطع الاتصال | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | الجهاز في وضعية السكون | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | Connection drops: Move closer to the radio; check for interference. | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/connections.html#bluetooth-ble",
    
    "relUrl": "/ar-rSA/user/connections.html#bluetooth-ble"
  },"398": {
    "doc": "Connections",
    "title": "USB Serial",
    "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | The connection is established automatically. | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/connections.html#usb-serial",
    
    "relUrl": "/ar-rSA/user/connections.html#usb-serial"
  },"399": {
    "doc": "Connections",
    "title": "TCP/IP (Network)",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect tab, select Network in the transport selector. | Choose the radio one of two ways: . | Scan for network devices — toggle this on to auto-discover radios that advertise themselves on the local network (mDNS / _meshtastic._tcp). Discovered devices appear in the list; tap one to connect. | Add device manually… — enter the radio’s IP address (or hostname) and port (default: 4403). | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . Wi-Fi Provisioning for mPWRD-OS . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/connections.html#tcpip-network",
    
    "relUrl": "/ar-rSA/user/connections.html#tcpip-network"
  },"400": {
    "doc": "Connections",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/connections.html#after-your-first-connection",
    
    "relUrl": "/ar-rSA/user/connections.html#after-your-first-connection"
  },"401": {
    "doc": "Connections",
    "title": "Reconnection Behavior",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/connections.html#reconnection-behavior",
    
    "relUrl": "/ar-rSA/user/connections.html#reconnection-behavior"
  },"402": {
    "doc": "Connections",
    "title": "Desktop Connections",
    "content": "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 for platform-specific details and keyboard shortcuts. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/connections.html#desktop-connections",
    
    "relUrl": "/ar-rSA/user/connections.html#desktop-connections"
  },"403": {
    "doc": "Connections",
    "title": "Related Topics",
    "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | Desktop App — desktop-specific connection details | Supported devices — full list of compatible radios on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/connections.html#related-topics",
    
    "relUrl": "/ar-rSA/user/connections.html#related-topics"
  },"404": {
    "doc": "Connections",
    "title": "Connections",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/connections.html",
    
    "relUrl": "/hr-rHR/user/connections.html"
  },"405": {
    "doc": "Connections",
    "title": "Bluetooth (BLE)",
    "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Use the transport selector — a segmented button row below the connection card — to switch between the Bluetooth, Network, and USB transports (one is active at a time): . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | What it means | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. Connection Status . | Icon | State | Opis | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Odspojeno | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | Uređaj je u stanju mirovanja | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | Connection drops: Move closer to the radio; check for interference. | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/connections.html#bluetooth-ble",
    
    "relUrl": "/hr-rHR/user/connections.html#bluetooth-ble"
  },"406": {
    "doc": "Connections",
    "title": "USB Serial",
    "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | The connection is established automatically. | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/connections.html#usb-serial",
    
    "relUrl": "/hr-rHR/user/connections.html#usb-serial"
  },"407": {
    "doc": "Connections",
    "title": "TCP/IP (Network)",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect tab, select Network in the transport selector. | Choose the radio one of two ways: . | Scan for network devices — toggle this on to auto-discover radios that advertise themselves on the local network (mDNS / _meshtastic._tcp). Discovered devices appear in the list; tap one to connect. | Add device manually… — enter the radio’s IP address (or hostname) and port (default: 4403). | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . Wi-Fi Provisioning for mPWRD-OS . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/connections.html#tcpip-network",
    
    "relUrl": "/hr-rHR/user/connections.html#tcpip-network"
  },"408": {
    "doc": "Connections",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/connections.html#after-your-first-connection",
    
    "relUrl": "/hr-rHR/user/connections.html#after-your-first-connection"
  },"409": {
    "doc": "Connections",
    "title": "Reconnection Behavior",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/connections.html#reconnection-behavior",
    
    "relUrl": "/hr-rHR/user/connections.html#reconnection-behavior"
  },"410": {
    "doc": "Connections",
    "title": "Desktop Connections",
    "content": "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 for platform-specific details and keyboard shortcuts. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/connections.html#desktop-connections",
    
    "relUrl": "/hr-rHR/user/connections.html#desktop-connections"
  },"411": {
    "doc": "Connections",
    "title": "Related Topics",
    "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | Desktop App — desktop-specific connection details | Supported devices — full list of compatible radios on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/connections.html#related-topics",
    
    "relUrl": "/hr-rHR/user/connections.html#related-topics"
  },"412": {
    "doc": "Ligações",
    "title": "Ligações",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/connections.html",
    
    "relUrl": "/pt-rPT/user/connections.html"
  },"413": {
    "doc": "Ligações",
    "title": "Bluetooth (BLE)",
    "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Use the transport selector — a segmented button row below the connection card — to switch between the Bluetooth, Network, and USB transports (one is active at a time): . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | What it means | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. Connection Status . | Icon | State | Descrição | . | 🟢 | Ligado | Active radio link established | . | 🟡 | A ligar | Handshake in progress | . | 🔴 | Desconectado | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | Dispositivo a dormir | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | Connection drops: Move closer to the radio; check for interference. | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/connections.html#bluetooth-ble",
    
    "relUrl": "/pt-rPT/user/connections.html#bluetooth-ble"
  },"414": {
    "doc": "Ligações",
    "title": "USB Serial",
    "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | The connection is established automatically. | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/connections.html#usb-serial",
    
    "relUrl": "/pt-rPT/user/connections.html#usb-serial"
  },"415": {
    "doc": "Ligações",
    "title": "TCP/IP (Network)",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect tab, select Network in the transport selector. | Choose the radio one of two ways: . | Scan for network devices — toggle this on to auto-discover radios that advertise themselves on the local network (mDNS / _meshtastic._tcp). Discovered devices appear in the list; tap one to connect. | Add device manually… — enter the radio’s IP address (or hostname) and port (default: 4403). | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . Wi-Fi Provisioning for mPWRD-OS . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/connections.html#tcpip-network",
    
    "relUrl": "/pt-rPT/user/connections.html#tcpip-network"
  },"416": {
    "doc": "Ligações",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/connections.html#after-your-first-connection",
    
    "relUrl": "/pt-rPT/user/connections.html#after-your-first-connection"
  },"417": {
    "doc": "Ligações",
    "title": "Reconnection Behavior",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/connections.html#reconnection-behavior",
    
    "relUrl": "/pt-rPT/user/connections.html#reconnection-behavior"
  },"418": {
    "doc": "Ligações",
    "title": "Desktop Connections",
    "content": "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 for platform-specific details and keyboard shortcuts. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/connections.html#desktop-connections",
    
    "relUrl": "/pt-rPT/user/connections.html#desktop-connections"
  },"419": {
    "doc": "Ligações",
    "title": "Related Topics",
    "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | Desktop App — desktop-specific connection details | Supported devices — full list of compatible radios on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/connections.html#related-topics",
    
    "relUrl": "/pt-rPT/user/connections.html#related-topics"
  },"420": {
    "doc": "Connections",
    "title": "Connections",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/connections.html",
    
    "relUrl": "/pl-rPL/user/connections.html"
  },"421": {
    "doc": "Connections",
    "title": "Bluetooth (BLE)",
    "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Use the transport selector — a segmented button row below the connection card — to switch between the Bluetooth, Network, and USB transports (one is active at a time): . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | What it means | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. Connection Status . | Icon | State | Opis | . | 🟢 | Połączony | Active radio link established | . | 🟡 | Łączenie | Handshake in progress | . | 🔴 | Rozłączono | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | Urządzenie uśpione | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | Connection drops: Move closer to the radio; check for interference. | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/connections.html#bluetooth-ble",
    
    "relUrl": "/pl-rPL/user/connections.html#bluetooth-ble"
  },"422": {
    "doc": "Connections",
    "title": "USB Serial",
    "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | The connection is established automatically. | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/connections.html#usb-serial",
    
    "relUrl": "/pl-rPL/user/connections.html#usb-serial"
  },"423": {
    "doc": "Connections",
    "title": "TCP/IP (Network)",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect tab, select Network in the transport selector. | Choose the radio one of two ways: . | Scan for network devices — toggle this on to auto-discover radios that advertise themselves on the local network (mDNS / _meshtastic._tcp). Discovered devices appear in the list; tap one to connect. | Add device manually… — enter the radio’s IP address (or hostname) and port (default: 4403). | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . Wi-Fi Provisioning for mPWRD-OS . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/connections.html#tcpip-network",
    
    "relUrl": "/pl-rPL/user/connections.html#tcpip-network"
  },"424": {
    "doc": "Connections",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/connections.html#after-your-first-connection",
    
    "relUrl": "/pl-rPL/user/connections.html#after-your-first-connection"
  },"425": {
    "doc": "Connections",
    "title": "Reconnection Behavior",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/connections.html#reconnection-behavior",
    
    "relUrl": "/pl-rPL/user/connections.html#reconnection-behavior"
  },"426": {
    "doc": "Connections",
    "title": "Desktop Connections",
    "content": "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 for platform-specific details and keyboard shortcuts. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/connections.html#desktop-connections",
    
    "relUrl": "/pl-rPL/user/connections.html#desktop-connections"
  },"427": {
    "doc": "Connections",
    "title": "Related Topics",
    "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | Desktop App — desktop-specific connection details | Supported devices — full list of compatible radios on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/connections.html#related-topics",
    
    "relUrl": "/pl-rPL/user/connections.html#related-topics"
  },"428": {
    "doc": "连接数",
    "title": "连接数",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/connections.html",
    
    "relUrl": "/zh-rCN/user/connections.html"
  },"429": {
    "doc": "连接数",
    "title": "Bluetooth (BLE)",
    "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Use the transport selector — a segmented button row below the connection card — to switch between the Bluetooth, Network, and USB transports (one is active at a time): . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | What it means | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. Connection Status . | 图标 | State | 说明 | . | 🟢 | 已连接 | Active radio link established | . | 🟡 | 正在连接 | Handshake in progress | . | 🔴 | 已断开连接 | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | 设备休眠中 | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | Connection drops: Move closer to the radio; check for interference. | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/connections.html#bluetooth-ble",
    
    "relUrl": "/zh-rCN/user/connections.html#bluetooth-ble"
  },"430": {
    "doc": "连接数",
    "title": "USB Serial",
    "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | The connection is established automatically. | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/connections.html#usb-serial",
    
    "relUrl": "/zh-rCN/user/connections.html#usb-serial"
  },"431": {
    "doc": "连接数",
    "title": "TCP/IP (Network)",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect tab, select Network in the transport selector. | Choose the radio one of two ways: . | Scan for network devices — toggle this on to auto-discover radios that advertise themselves on the local network (mDNS / _meshtastic._tcp). Discovered devices appear in the list; tap one to connect. | Add device manually… — enter the radio’s IP address (or hostname) and port (default: 4403). | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . MPWRD-OS 系统 Wi-Fi 配置 . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/connections.html#tcpip-network",
    
    "relUrl": "/zh-rCN/user/connections.html#tcpip-network"
  },"432": {
    "doc": "连接数",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/connections.html#after-your-first-connection",
    
    "relUrl": "/zh-rCN/user/connections.html#after-your-first-connection"
  },"433": {
    "doc": "连接数",
    "title": "Reconnection Behavior",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/connections.html#reconnection-behavior",
    
    "relUrl": "/zh-rCN/user/connections.html#reconnection-behavior"
  },"434": {
    "doc": "连接数",
    "title": "Desktop Connections",
    "content": "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 for platform-specific details and keyboard shortcuts. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/connections.html#desktop-connections",
    
    "relUrl": "/zh-rCN/user/connections.html#desktop-connections"
  },"435": {
    "doc": "连接数",
    "title": "Related Topics",
    "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | Desktop App — desktop-specific connection details | Supported devices — full list of compatible radios on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/connections.html#related-topics",
    
    "relUrl": "/zh-rCN/user/connections.html#related-topics"
  },"436": {
    "doc": "Connections",
    "title": "Connections",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/connections.html",
    
    "relUrl": "/sq-rAL/user/connections.html"
  },"437": {
    "doc": "Connections",
    "title": "Bluetooth (BLE)",
    "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Use the transport selector — a segmented button row below the connection card — to switch between the Bluetooth, Network, and USB transports (one is active at a time): . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | What it means | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. Connection Status . | Icon | State | Përshkrimi | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | I shkëputur | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | Pajisja po fle | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | Connection drops: Move closer to the radio; check for interference. | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/connections.html#bluetooth-ble",
    
    "relUrl": "/sq-rAL/user/connections.html#bluetooth-ble"
  },"438": {
    "doc": "Connections",
    "title": "USB Serial",
    "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | The connection is established automatically. | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/connections.html#usb-serial",
    
    "relUrl": "/sq-rAL/user/connections.html#usb-serial"
  },"439": {
    "doc": "Connections",
    "title": "TCP/IP (Network)",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect tab, select Network in the transport selector. | Choose the radio one of two ways: . | Scan for network devices — toggle this on to auto-discover radios that advertise themselves on the local network (mDNS / _meshtastic._tcp). Discovered devices appear in the list; tap one to connect. | Add device manually… — enter the radio’s IP address (or hostname) and port (default: 4403). | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . Wi-Fi Provisioning for mPWRD-OS . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/connections.html#tcpip-network",
    
    "relUrl": "/sq-rAL/user/connections.html#tcpip-network"
  },"440": {
    "doc": "Connections",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/connections.html#after-your-first-connection",
    
    "relUrl": "/sq-rAL/user/connections.html#after-your-first-connection"
  },"441": {
    "doc": "Connections",
    "title": "Reconnection Behavior",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/connections.html#reconnection-behavior",
    
    "relUrl": "/sq-rAL/user/connections.html#reconnection-behavior"
  },"442": {
    "doc": "Connections",
    "title": "Desktop Connections",
    "content": "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 for platform-specific details and keyboard shortcuts. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/connections.html#desktop-connections",
    
    "relUrl": "/sq-rAL/user/connections.html#desktop-connections"
  },"443": {
    "doc": "Connections",
    "title": "Related Topics",
    "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | Desktop App — desktop-specific connection details | Supported devices — full list of compatible radios on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/connections.html#related-topics",
    
    "relUrl": "/sq-rAL/user/connections.html#related-topics"
  },"444": {
    "doc": "連線",
    "title": "連線",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/connections.html",
    
    "relUrl": "/zh-rTW/user/connections.html"
  },"445": {
    "doc": "連線",
    "title": "藍牙（BLE）",
    "content": "藍牙低功耗是 Android 上預設且最常見的連線方式。 . Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | 開啟應用程式，並前往「連線」頁籤。 | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Use the transport selector — a segmented button row below the connection card — to switch between the Bluetooth, Network, and USB transports (one is active at a time): . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | 代表意義 | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. 連線狀態 . | 圖示 | 狀態 | 描述說明 | . | 🟢 | 已連線 | 無線電連線已建立 | . | 🟡 | 正在連線 | 交握進行中 | . | 🔴 | 已中斷連線 | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | 設備休眠中 | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . 若未找到任何裝置，應用程式將顯示空白畫面並提供操作說明： . 藍牙疑難排解 . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | 連線中斷：請靠近無線電裝置，並檢查是否有訊號干擾。 | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | 配對遭拒：請至 Android 藍牙設定中移除該裝置後重新配對。 | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/connections.html#%E8%97%8D%E7%89%99ble",
    
    "relUrl": "/zh-rTW/user/connections.html#藍牙ble"
  },"446": {
    "doc": "連線",
    "title": "USB 序列埠",
    "content": "USB 連線提供有線替代方案，適用於桌上型電腦或藍牙無法使用的情況。 . 設定 . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | 連線將自動建立。 | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/connections.html#usb-%E5%BA%8F%E5%88%97%E5%9F%A0",
    
    "relUrl": "/zh-rTW/user/connections.html#usb-序列埠"
  },"447": {
    "doc": "連線",
    "title": "TCP/IP (Network)",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect tab, select Network in the transport selector. | Choose the radio one of two ways: . | Scan for network devices — toggle this on to auto-discover radios that advertise themselves on the local network (mDNS / _meshtastic._tcp). Discovered devices appear in the list; tap one to connect. | Add device manually… — enter the radio’s IP address (or hostname) and port (default: 4403). | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. 何時使用 TCP . | 無線電裝置與裝置位於同一區域網路 | 使用模擬無線電裝置進行測試 | 藍牙訊號受干擾的環境 | . mPWRD-OS 的 Wi-Fi 設定 . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/connections.html#tcpip-network",
    
    "relUrl": "/zh-rTW/user/connections.html#tcpip-network"
  },"448": {
    "doc": "連線",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/connections.html#after-your-first-connection",
    
    "relUrl": "/zh-rTW/user/connections.html#after-your-first-connection"
  },"449": {
    "doc": "連線",
    "title": "重新連線行為",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/connections.html#%E9%87%8D%E6%96%B0%E9%80%A3%E7%B7%9A%E8%A1%8C%E7%82%BA",
    
    "relUrl": "/zh-rTW/user/connections.html#重新連線行為"
  },"450": {
    "doc": "連線",
    "title": "桌面版連線",
    "content": "在桌面版（Linux／macOS／Windows）上，應用程式支援： . | 藍牙（BLE）—— 透過 Kable 函式庫；支援 macOS、Linux 及 Windows | USB 序列埠 — 主要的有線連線方式 | TCP/IP — 適用於透過網路連線的無線電裝置 | . 請參閱〔桌面版應用程式〕(desktop) 以了解各平台的詳細說明與鍵盤快速鍵。 . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/connections.html#%E6%A1%8C%E9%9D%A2%E7%89%88%E9%80%A3%E7%B7%9A",
    
    "relUrl": "/zh-rTW/user/connections.html#桌面版連線"
  },"451": {
    "doc": "連線",
    "title": "相關主題",
    "content": ". | 〔快速入門〕(onboarding) — 首次啟動的設定與權限 | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | 〔桌面版應用程式〕(desktop) — 桌面版連線詳細說明 | 〔支援的裝置〕(https://meshtastic.org/docs/hardware/devices)— meshtastic.org 上的完整相容無線電裝置清單 | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/connections.html#%E7%9B%B8%E9%97%9C%E4%B8%BB%E9%A1%8C",
    
    "relUrl": "/zh-rTW/user/connections.html#相關主題"
  },"452": {
    "doc": "Ühendus",
    "title": "Ühendus",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/connections.html",
    
    "relUrl": "/et-rEE/user/connections.html"
  },"453": {
    "doc": "Ühendus",
    "title": "Sinihammas (BLE)",
    "content": "Sinihamba madal voolutarve on Androidi vaike- ja levinuim ühendusviis. Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | Ava rakendus ja navigeeri vahekaardile Ühendused. | Puuduta valikut Otsi sinihamba seadmeid – kuvatakse lähedalasuvad Meshtasticu raadiod. | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Sinihamba, võrgu ja USB-transpordi vahel vahetamiseks (üks on korraga aktiivne) kasutage transpordivalijat – ühenduskaardi all asuvat segmenteeritud nuppude rida: . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | What it means | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. Ühenduse olek . | Ikoon | Olek | Kirjeldus | . | 🟢 | Ühendatud | Aktiivne raadioside loodud | . | 🟡 | Ühendan | Kätlemine on pooleli | . | 🔴 | Ühendus katkenud | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | Seade on unerežiimis | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . Kui seadmeid ei leita, kuvab rakendus tühja oleku koos juhistega: . Sinihamba veaotsing . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | Connection drops: Move closer to the radio; check for interference. | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | Sidumine tagasi lükatud: Unusta seade Androidi sinihamba ​​seadetes ja proovi uuesti. | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/connections.html#sinihammas-ble",
    
    "relUrl": "/et-rEE/user/connections.html#sinihammas-ble"
  },"454": {
    "doc": "Ühendus",
    "title": "USB port",
    "content": "USB ühendused pakuvad juhtmega alternatiivi, mis on kasulik lauaarvutite puhul või kui sinihammas pole saadaval. Seadistamine . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | The connection is established automatically. | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/connections.html#usb-port",
    
    "relUrl": "/et-rEE/user/connections.html#usb-port"
  },"455": {
    "doc": "Ühendus",
    "title": "TCP/IP (võrk)",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Connecting over the Network . | Veendu, et raadio on samas kohtvõrgus kui sinu telefon/lauaarvuti. | On the Connect tab, select Network in the transport selector. | Choose the radio one of two ways: . | Võrguseadmete otsimine – lülita see sisse, et automaatselt avastada raadioid, mis reklaamivad end kohalikus võrgus (mDNS / _meshtastic._tcp). Leitud seadmed kuvatakse loendis; ühenduse loomiseks puuduta neist ühte. | Lisa seade käsitsi… — Sisesta raadio IP-aadress (või hostinimi) ja port (vaikimisi: 4403). | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. Millal kasutada TCP . | Raadio on samas kohalikus võrgus | Testing with a simulated radio | Asukohad kus sinihambal on häireid | . WiFi ühenduse loomine mPWRD-OS-i jaoks . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/connections.html#tcpip-v%C3%B5rk",
    
    "relUrl": "/et-rEE/user/connections.html#tcpip-võrk"
  },"456": {
    "doc": "Ühendus",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/connections.html#after-your-first-connection",
    
    "relUrl": "/et-rEE/user/connections.html#after-your-first-connection"
  },"457": {
    "doc": "Ühendus",
    "title": "Reconnection Behavior",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/connections.html#reconnection-behavior",
    
    "relUrl": "/et-rEE/user/connections.html#reconnection-behavior"
  },"458": {
    "doc": "Ühendus",
    "title": "Desktop Connections",
    "content": "On Desktop (Linux/macOS/Windows), the app supports: . | Sinihammas (BLE) — Kable’i teegi kaudu; töötab macOS-is, Linuxis ja Windowsis | USB port – peamine juhtmega ühendusmeetod | TCP/IP – võrguühendusega raadiote jaoks | . Platvormipõhiste üksikasjade ja kiirklahvide kohta vaata [Töölauarakendus] (desktop). ",
    "url": "/Meshtastic-Android/main/et-rEE/user/connections.html#desktop-connections",
    
    "relUrl": "/et-rEE/user/connections.html#desktop-connections"
  },"459": {
    "doc": "Ühendus",
    "title": "Seotud teemad",
    "content": ". | Alustamine — esmakäivituse seadistamine ja load | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | Desktop App — desktop-specific connection details | Supported devices — full list of compatible radios on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/connections.html#seotud-teemad",
    
    "relUrl": "/et-rEE/user/connections.html#seotud-teemad"
  },"460": {
    "doc": "Connexions",
    "title": "Connexions",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/connections.html",
    
    "relUrl": "/fr-rFR/user/connections.html"
  },"461": {
    "doc": "Connexions",
    "title": "Bluetooth (BLE)",
    "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Use the transport selector — a segmented button row below the connection card — to switch between the Bluetooth, Network, and USB transports (one is active at a time): . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | What it means | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. Connection Status . | Icon | State | Description | . | 🟢 | Connecté | Active radio link established | . | 🟡 | Connexion en cours | Handshake in progress | . | 🔴 | Déconnecté | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | Appareil en veille | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | Connection drops: Move closer to the radio; check for interference. | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/connections.html#bluetooth-ble",
    
    "relUrl": "/fr-rFR/user/connections.html#bluetooth-ble"
  },"462": {
    "doc": "Connexions",
    "title": "USB Serial",
    "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | The connection is established automatically. | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/connections.html#usb-serial",
    
    "relUrl": "/fr-rFR/user/connections.html#usb-serial"
  },"463": {
    "doc": "Connexions",
    "title": "TCP/IP (Network)",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect tab, select Network in the transport selector. | Choose the radio one of two ways: . | Scan for network devices — toggle this on to auto-discover radios that advertise themselves on the local network (mDNS / _meshtastic._tcp). Discovered devices appear in the list; tap one to connect. | Add device manually… — enter the radio’s IP address (or hostname) and port (default: 4403). | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . Approvisionnement Wi-Fi pour mPWRD-OS . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/connections.html#tcpip-network",
    
    "relUrl": "/fr-rFR/user/connections.html#tcpip-network"
  },"464": {
    "doc": "Connexions",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/connections.html#after-your-first-connection",
    
    "relUrl": "/fr-rFR/user/connections.html#after-your-first-connection"
  },"465": {
    "doc": "Connexions",
    "title": "Reconnection Behavior",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/connections.html#reconnection-behavior",
    
    "relUrl": "/fr-rFR/user/connections.html#reconnection-behavior"
  },"466": {
    "doc": "Connexions",
    "title": "Desktop Connections",
    "content": "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 for platform-specific details and keyboard shortcuts. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/connections.html#desktop-connections",
    
    "relUrl": "/fr-rFR/user/connections.html#desktop-connections"
  },"467": {
    "doc": "Connexions",
    "title": "Related Topics",
    "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | Desktop App — desktop-specific connection details | Supported devices — full list of compatible radios on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/connections.html#related-topics",
    
    "relUrl": "/fr-rFR/user/connections.html#related-topics"
  },"468": {
    "doc": "Bağlantılar",
    "title": "Bağlantılar",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/connections.html",
    
    "relUrl": "/tr-rTR/user/connections.html"
  },"469": {
    "doc": "Bağlantılar",
    "title": "Bluetooth (BLE)",
    "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Use the transport selector — a segmented button row below the connection card — to switch between the Bluetooth, Network, and USB transports (one is active at a time): . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | What it means | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. Connection Status . | Icon | State | Açıklaması | . | 🟢 | Bağlandı | Active radio link established | . | 🟡 | Bağlanıyor | Handshake in progress | . | 🔴 | Bağlantı kesildi | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | Cihaz uyku durumunda | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | Connection drops: Move closer to the radio; check for interference. | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/connections.html#bluetooth-ble",
    
    "relUrl": "/tr-rTR/user/connections.html#bluetooth-ble"
  },"470": {
    "doc": "Bağlantılar",
    "title": "USB Serial",
    "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | The connection is established automatically. | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/connections.html#usb-serial",
    
    "relUrl": "/tr-rTR/user/connections.html#usb-serial"
  },"471": {
    "doc": "Bağlantılar",
    "title": "TCP/IP (Network)",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect tab, select Network in the transport selector. | Choose the radio one of two ways: . | Scan for network devices — toggle this on to auto-discover radios that advertise themselves on the local network (mDNS / _meshtastic._tcp). Discovered devices appear in the list; tap one to connect. | Add device manually… — enter the radio’s IP address (or hostname) and port (default: 4403). | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . Wi-Fi Provisioning for mPWRD-OS . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/connections.html#tcpip-network",
    
    "relUrl": "/tr-rTR/user/connections.html#tcpip-network"
  },"472": {
    "doc": "Bağlantılar",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/connections.html#after-your-first-connection",
    
    "relUrl": "/tr-rTR/user/connections.html#after-your-first-connection"
  },"473": {
    "doc": "Bağlantılar",
    "title": "Reconnection Behavior",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/connections.html#reconnection-behavior",
    
    "relUrl": "/tr-rTR/user/connections.html#reconnection-behavior"
  },"474": {
    "doc": "Bağlantılar",
    "title": "Desktop Connections",
    "content": "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 for platform-specific details and keyboard shortcuts. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/connections.html#desktop-connections",
    
    "relUrl": "/tr-rTR/user/connections.html#desktop-connections"
  },"475": {
    "doc": "Bağlantılar",
    "title": "Related Topics",
    "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | Desktop App — desktop-specific connection details | Supported devices — full list of compatible radios on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/connections.html#related-topics",
    
    "relUrl": "/tr-rTR/user/connections.html#related-topics"
  },"476": {
    "doc": "Connections",
    "title": "Connections",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/connections.html",
    
    "relUrl": "/el-rGR/user/connections.html"
  },"477": {
    "doc": "Connections",
    "title": "Bluetooth (BLE)",
    "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Use the transport selector — a segmented button row below the connection card — to switch between the Bluetooth, Network, and USB transports (one is active at a time): . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | What it means | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. Connection Status . | Icon | State | Περιγραφή | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Αποσυνδεδεμένο | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | Συσκευή σε ύπνωση | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | Connection drops: Move closer to the radio; check for interference. | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/connections.html#bluetooth-ble",
    
    "relUrl": "/el-rGR/user/connections.html#bluetooth-ble"
  },"478": {
    "doc": "Connections",
    "title": "USB Serial",
    "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | The connection is established automatically. | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/connections.html#usb-serial",
    
    "relUrl": "/el-rGR/user/connections.html#usb-serial"
  },"479": {
    "doc": "Connections",
    "title": "TCP/IP (Network)",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect tab, select Network in the transport selector. | Choose the radio one of two ways: . | Scan for network devices — toggle this on to auto-discover radios that advertise themselves on the local network (mDNS / _meshtastic._tcp). Discovered devices appear in the list; tap one to connect. | Add device manually… — enter the radio’s IP address (or hostname) and port (default: 4403). | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . Wi-Fi Provisioning for mPWRD-OS . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/connections.html#tcpip-network",
    
    "relUrl": "/el-rGR/user/connections.html#tcpip-network"
  },"480": {
    "doc": "Connections",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/connections.html#after-your-first-connection",
    
    "relUrl": "/el-rGR/user/connections.html#after-your-first-connection"
  },"481": {
    "doc": "Connections",
    "title": "Reconnection Behavior",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/connections.html#reconnection-behavior",
    
    "relUrl": "/el-rGR/user/connections.html#reconnection-behavior"
  },"482": {
    "doc": "Connections",
    "title": "Desktop Connections",
    "content": "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 for platform-specific details and keyboard shortcuts. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/connections.html#desktop-connections",
    
    "relUrl": "/el-rGR/user/connections.html#desktop-connections"
  },"483": {
    "doc": "Connections",
    "title": "Related Topics",
    "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | Desktop App — desktop-specific connection details | Supported devices — full list of compatible radios on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/connections.html#related-topics",
    
    "relUrl": "/el-rGR/user/connections.html#related-topics"
  },"484": {
    "doc": "Connections",
    "title": "Connections",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/connections.html",
    
    "relUrl": "/ro-rRO/user/connections.html"
  },"485": {
    "doc": "Connections",
    "title": "Bluetooth (BLE)",
    "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Use the transport selector — a segmented button row below the connection card — to switch between the Bluetooth, Network, and USB transports (one is active at a time): . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | What it means | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. Connection Status . | Icon | State | Descriere | . | 🟢 | Conectat | Active radio link established | . | 🟡 | Conectare | Handshake in progress | . | 🔴 | Deconectat | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | Adormirea dispozitivului | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | Connection drops: Move closer to the radio; check for interference. | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/connections.html#bluetooth-ble",
    
    "relUrl": "/ro-rRO/user/connections.html#bluetooth-ble"
  },"486": {
    "doc": "Connections",
    "title": "USB Serial",
    "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | The connection is established automatically. | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/connections.html#usb-serial",
    
    "relUrl": "/ro-rRO/user/connections.html#usb-serial"
  },"487": {
    "doc": "Connections",
    "title": "TCP/IP (Network)",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect tab, select Network in the transport selector. | Choose the radio one of two ways: . | Scan for network devices — toggle this on to auto-discover radios that advertise themselves on the local network (mDNS / _meshtastic._tcp). Discovered devices appear in the list; tap one to connect. | Add device manually… — enter the radio’s IP address (or hostname) and port (default: 4403). | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . Wi-Fi Provisioning for mPWRD-OS . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/connections.html#tcpip-network",
    
    "relUrl": "/ro-rRO/user/connections.html#tcpip-network"
  },"488": {
    "doc": "Connections",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/connections.html#after-your-first-connection",
    
    "relUrl": "/ro-rRO/user/connections.html#after-your-first-connection"
  },"489": {
    "doc": "Connections",
    "title": "Reconnection Behavior",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/connections.html#reconnection-behavior",
    
    "relUrl": "/ro-rRO/user/connections.html#reconnection-behavior"
  },"490": {
    "doc": "Connections",
    "title": "Desktop Connections",
    "content": "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 for platform-specific details and keyboard shortcuts. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/connections.html#desktop-connections",
    
    "relUrl": "/ro-rRO/user/connections.html#desktop-connections"
  },"491": {
    "doc": "Connections",
    "title": "Related Topics",
    "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | Desktop App — desktop-specific connection details | Supported devices — full list of compatible radios on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/connections.html#related-topics",
    
    "relUrl": "/ro-rRO/user/connections.html#related-topics"
  },"492": {
    "doc": "Connections",
    "title": "Connections",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/connections.html",
    
    "relUrl": "/iw-rIL/user/connections.html"
  },"493": {
    "doc": "Connections",
    "title": "Bluetooth (BLE)",
    "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Use the transport selector — a segmented button row below the connection card — to switch between the Bluetooth, Network, and USB transports (one is active at a time): . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | What it means | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. Connection Status . | Icon | State | תיאור | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | מנותק | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | מכשיר במצב שינה | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | Connection drops: Move closer to the radio; check for interference. | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/connections.html#bluetooth-ble",
    
    "relUrl": "/iw-rIL/user/connections.html#bluetooth-ble"
  },"494": {
    "doc": "Connections",
    "title": "USB Serial",
    "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | The connection is established automatically. | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/connections.html#usb-serial",
    
    "relUrl": "/iw-rIL/user/connections.html#usb-serial"
  },"495": {
    "doc": "Connections",
    "title": "TCP/IP (Network)",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect tab, select Network in the transport selector. | Choose the radio one of two ways: . | Scan for network devices — toggle this on to auto-discover radios that advertise themselves on the local network (mDNS / _meshtastic._tcp). Discovered devices appear in the list; tap one to connect. | Add device manually… — enter the radio’s IP address (or hostname) and port (default: 4403). | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . Wi-Fi Provisioning for mPWRD-OS . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/connections.html#tcpip-network",
    
    "relUrl": "/iw-rIL/user/connections.html#tcpip-network"
  },"496": {
    "doc": "Connections",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/connections.html#after-your-first-connection",
    
    "relUrl": "/iw-rIL/user/connections.html#after-your-first-connection"
  },"497": {
    "doc": "Connections",
    "title": "Reconnection Behavior",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/connections.html#reconnection-behavior",
    
    "relUrl": "/iw-rIL/user/connections.html#reconnection-behavior"
  },"498": {
    "doc": "Connections",
    "title": "Desktop Connections",
    "content": "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 for platform-specific details and keyboard shortcuts. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/connections.html#desktop-connections",
    
    "relUrl": "/iw-rIL/user/connections.html#desktop-connections"
  },"499": {
    "doc": "Connections",
    "title": "Related Topics",
    "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | Desktop App — desktop-specific connection details | Supported devices — full list of compatible radios on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/connections.html#related-topics",
    
    "relUrl": "/iw-rIL/user/connections.html#related-topics"
  },"500": {
    "doc": "Conexões",
    "title": "Conexões",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/connections.html",
    
    "relUrl": "/pt-rBR/user/connections.html"
  },"501": {
    "doc": "Conexões",
    "title": "Bluetooth (BLE)",
    "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Use the transport selector — a segmented button row below the connection card — to switch between the Bluetooth, Network, and USB transports (one is active at a time): . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | What it means | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. Connection Status . | Icon | State | Descrição | . | 🟢 | Conectado | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Desconectado | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | Dispositivo em suspensão (sleep) | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | Connection drops: Move closer to the radio; check for interference. | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/connections.html#bluetooth-ble",
    
    "relUrl": "/pt-rBR/user/connections.html#bluetooth-ble"
  },"502": {
    "doc": "Conexões",
    "title": "USB Serial",
    "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | The connection is established automatically. | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/connections.html#usb-serial",
    
    "relUrl": "/pt-rBR/user/connections.html#usb-serial"
  },"503": {
    "doc": "Conexões",
    "title": "TCP/IP (Network)",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect tab, select Network in the transport selector. | Choose the radio one of two ways: . | Scan for network devices — toggle this on to auto-discover radios that advertise themselves on the local network (mDNS / _meshtastic._tcp). Discovered devices appear in the list; tap one to connect. | Add device manually… — enter the radio’s IP address (or hostname) and port (default: 4403). | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . Wi-Fi Provisioning for mPWRD-OS . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/connections.html#tcpip-network",
    
    "relUrl": "/pt-rBR/user/connections.html#tcpip-network"
  },"504": {
    "doc": "Conexões",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/connections.html#after-your-first-connection",
    
    "relUrl": "/pt-rBR/user/connections.html#after-your-first-connection"
  },"505": {
    "doc": "Conexões",
    "title": "Reconnection Behavior",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/connections.html#reconnection-behavior",
    
    "relUrl": "/pt-rBR/user/connections.html#reconnection-behavior"
  },"506": {
    "doc": "Conexões",
    "title": "Desktop Connections",
    "content": "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 for platform-specific details and keyboard shortcuts. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/connections.html#desktop-connections",
    
    "relUrl": "/pt-rBR/user/connections.html#desktop-connections"
  },"507": {
    "doc": "Conexões",
    "title": "Related Topics",
    "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | Desktop App — desktop-specific connection details | Supported devices — full list of compatible radios on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/connections.html#related-topics",
    
    "relUrl": "/pt-rBR/user/connections.html#related-topics"
  },"508": {
    "doc": "Connections",
    "title": "Connections",
    "content": "Meshtastic supports multiple transport methods to communicate between your phone or desktop and a radio. ",
    "url": "/Meshtastic-Android/main/en/user/connections.html",
    
    "relUrl": "/en/user/connections.html"
  },"509": {
    "doc": "Connections",
    "title": "Bluetooth (BLE)",
    "content": "Bluetooth Low Energy is the default and most common connection method on Android. Pairing a Radio . | Power on your radio. Most radios advertise over Bluetooth as soon as they boot — there is no pairing mode to enter. Radios with a color touchscreen ship with Bluetooth switched off, so turn it on from the radio’s own on-screen menu first. | Open the app and navigate to the Connect tab. | Tap Scan for Bluetooth devices — nearby Meshtastic radios will appear. | Select your radio from the list. | Android asks you to pair. If your radio has a screen, it shows a six-digit PIN — type that into the Android dialog. If your radio has no screen, the PIN is 123456. | . You can change the pairing method, or turn Bluetooth on for a radio that ships with it off, under Settings → Device configuration → Bluetooth — see Settings — Radio & User. For more information, see Bluetooth configuration on meshtastic.org. Use the transport selector — a segmented button row below the connection card — to switch between the Bluetooth, Network, and USB transports (one is active at a time): . 💡 Tip: If your radio doesn’t appear, check that it isn’t already connected to another phone, or out of range. The screen names anything on the app’s side that is blocking a scan, with the fix attached: . | What you see | What it means | . | A card asking for Nearby devices | The permission has not been granted. Grant permission requests it; once Android stops prompting, the button becomes Open settings. | . | Bluetooth is off | The adapter is disabled — the card opens Bluetooth settings. | . | Bluetooth scanning also needs location services | Android 11 and older only: the permission is held but the system location toggle is off. | . | No card, empty list | Nothing on this side is blocking the scan — the radio is out of range, off, or already connected elsewhere. | . The explanation lives in that card, not in the scan control: tapping Scan for Bluetooth devices after you have declined once asks Android again directly. Connection Status . | Icon | State | Description | . | 🟢 | Connected | Active radio link established | . | 🟡 | Connecting | Handshake in progress | . | 🔴 | Disconnected | No active connection. The app retries automatically, with a growing delay between attempts | . | ⚪ | Device sleeping | The radio is in light sleep — the app is waiting for it to wake and reconnect, not failing | . These are the four states the app models. “Device sleeping” is normal on power-saving configurations and needs no action. When connecting, a status indicator shows the current connection state — tap Stop Connecting to abandon the attempt: . If no devices are found, the app shows an empty state with instructions: . Troubleshooting Bluetooth . | Radio not found: Turn Bluetooth off and back on. On Android 11 and older, also check that system location services are switched on — those releases do not return scan results without them. | Bluetooth scan couldn’t start: Try again, and toggle Bluetooth off and on if it repeats. | Connection drops: Move closer to the radio; check for interference. | Pairing failed, or pairing did not complete: Check that the Nearby devices permission is granted, then pair again. | Pairing rejected: Forget the device in Android Bluetooth settings and retry. | Could not establish a stable connection after repeated attempts: The app stopped retrying after three failed handshakes — a radio that keeps failing here is usually crashing on reconnect. Power-cycle the radio, then tap it again on the Connect tab to start a fresh attempt. | . ",
    "url": "/Meshtastic-Android/main/en/user/connections.html#bluetooth-ble",
    
    "relUrl": "/en/user/connections.html#bluetooth-ble"
  },"510": {
    "doc": "Connections",
    "title": "USB Serial",
    "content": "USB connections provide a wired alternative, useful for desktop or when Bluetooth is unavailable. Setup . | Connect your radio to your phone with a USB data cable. Charge-only cables carry no data lines, and a radio on one never appears in the list. | The app prompts for USB permission — tap Allow. | The connection is established automatically. | . ℹ️ Note: USB connections require OTG support on Android devices. Troubleshooting USB . | USB permission denied: Unplug the radio and plug it back in — Android asks again on reconnect. | No radio in the list: Check that the cable carries data rather than only power, and that the phone supports OTG. | . ",
    "url": "/Meshtastic-Android/main/en/user/connections.html#usb-serial",
    
    "relUrl": "/en/user/connections.html#usb-serial"
  },"511": {
    "doc": "Connections",
    "title": "TCP/IP (Network)",
    "content": "Some Meshtastic radios support Wi-Fi/Ethernet connectivity, allowing TCP-based connections over your local network. Get the radio onto your network first. Connect to it over Bluetooth or USB, open Settings → Device configuration → Network, and under Wi-Fi Options turn on Wi-Fi enabled and enter the SSID and Password. The Network screen appears only for radios whose hardware supports Wi-Fi or Ethernet. Once the radio has an address, come back and connect to it over the network. Connecting over the Network . | Make sure the radio is on the same local network as your phone/desktop. | On the Connect tab, select Network in the transport selector. | Choose the radio one of two ways: . | Scan for network devices — toggle this on to auto-discover radios that advertise themselves on the local network (mDNS / _meshtastic._tcp). Discovered devices appear in the list; tap one to connect. | Add device manually… — enter the radio’s IP address (or hostname) and port (default: 4403). | . | Previously-used network addresses are remembered under Recent Network Devices for quick reconnection (touch & hold to remove one). | . Network discovery uses mDNS, which only works when both your phone and the radio are on the same subnet. If the phone is not on Wi-Fi at all, the app warns that a network scan may find nothing. On Android 17 and newer, the app needs the Local network permission to reach a radio on your own Wi-Fi at all — not only to discover it — so typing the address by hand does not work around a denied permission. Grant it from the card on the Network pane, or from the Permissions section of Settings. A radio on a public address, or one reached over a VPN, needs no permission. When to Use TCP . | Radio is on the same local network | Testing with a simulated radio | Environments where Bluetooth has interference issues | . Wi-Fi Provisioning for mPWRD-OS . Settings → Wi-Fi Provisioning for mPWRD-OS is a separate, narrower tool. It sends Wi-Fi credentials over Bluetooth to mPWRD-OS devices only, using their own protocol — it does not configure Wi-Fi on an ordinary Meshtastic radio. It is available on both Android and desktop. | Open the screen and wait while the app finds the device over Bluetooth. | Tap Scan for Networks, then pick a network from Available Networks — or turn on Hidden network and type the name into Network Name (SSID). | Enter the Password and tap Apply. | . If the scan reports No networks found or fails outright, move the phone closer to the device and scan again. If Failed to apply Wi-Fi configuration comes back, check the password and try again. ",
    "url": "/Meshtastic-Android/main/en/user/connections.html#tcpip-network",
    
    "relUrl": "/en/user/connections.html#tcpip-network"
  },"512": {
    "doc": "Connections",
    "title": "After Your First Connection",
    "content": "Being connected is not the same as being able to transmit. A radio leaves the factory with no LoRa region set, and it does not transmit until you set one. When you connect such a radio, the Connect tab shows a Set your region card; tap it to open the LoRa screen and choose the region you are in. Once the region is set, the tab warns you if the radio is receive-only: a Transmit is disabled card, reading “This device can receive but will not send anything over LoRa.” Tap it to open the same screen and turn Transmit Enabled back on. Only one of the two cards appears at a time — an unset region already stops the radio transmitting, so the app names that first and holds the transmit card back until you have set a region. For more information, see Settings — Radio & User. ",
    "url": "/Meshtastic-Android/main/en/user/connections.html#after-your-first-connection",
    
    "relUrl": "/en/user/connections.html#after-your-first-connection"
  },"513": {
    "doc": "Connections",
    "title": "Reconnection Behavior",
    "content": "The app reconnects to the last selected radio on startup. You can switch transports from the Connect tab at any time. To disconnect, tap the disconnect button on the Connect tab: . ",
    "url": "/Meshtastic-Android/main/en/user/connections.html#reconnection-behavior",
    
    "relUrl": "/en/user/connections.html#reconnection-behavior"
  },"514": {
    "doc": "Connections",
    "title": "Desktop Connections",
    "content": "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 for platform-specific details and keyboard shortcuts. ",
    "url": "/Meshtastic-Android/main/en/user/connections.html#desktop-connections",
    
    "relUrl": "/en/user/connections.html#desktop-connections"
  },"515": {
    "doc": "Connections",
    "title": "Related Topics",
    "content": ". | Getting Started — first-launch setup and permissions | Settings — Radio & User — Bluetooth, region, and network configuration | Messages & Channels — send your first message once the radio is connected | Nodes — see who else is on your mesh | Desktop App — desktop-specific connection details | Supported devices — full list of compatible radios on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/en/user/connections.html#related-topics",
    
    "relUrl": "/en/user/connections.html#related-topics"
  },"516": {
    "doc": "Contributing",
    "title": "Contributing",
    "content": "Guidelines for contributing to the Meshtastic Android/Desktop project (a KMP codebase that also compiles for iOS). ",
    "url": "/Meshtastic-Android/main/en/developer/contributing.html",
    
    "relUrl": "/en/developer/contributing.html"
  },"517": {
    "doc": "Contributing",
    "title": "Branch Naming",
    "content": "Branches use conventional-commit style prefixes: . | Prefix | Use for | . | feat/<scope> | New user-visible behavior | . | fix/<scope> | Bug fixes | . | refactor/<scope> | Code structure changes | . | chore/<scope> | Tooling, deps, CI, cleanup | . | docs/<scope> | Documentation only | . | build/<scope> | Build system changes | . | ci/<scope> | CI workflow changes | . | test/<scope> | Test additions or fixes | . | deps/<scope> | Dependency updates | . Timestamp-based spec prefixes (YYYYMMDD-HHMMSS-feature-name, as created by /speckit.git.feature) are also valid for spec-driven work. Examples: . | feat/desktop-ble-transport | fix/bluetooth-reconnect | 20260601-074653-air-quality-telemetry | . ",
    "url": "/Meshtastic-Android/main/en/developer/contributing.html#branch-naming",
    
    "relUrl": "/en/developer/contributing.html#branch-naming"
  },"518": {
    "doc": "Contributing",
    "title": "Development Workflow",
    "content": ". | Fork the repository (external contributors) or create a branch (maintainers). | Implement your changes following the architecture guidelines. | Test locally: ./gradlew spotlessCheck detekt kmpSmokeCompile test allTests | Commit with clear, descriptive messages. | Push and open a Pull Request. | . ",
    "url": "/Meshtastic-Android/main/en/developer/contributing.html#development-workflow",
    
    "relUrl": "/en/developer/contributing.html#development-workflow"
  },"519": {
    "doc": "Contributing",
    "title": "Commit Messages",
    "content": "Follow conventional commit style: . feat(docs): add in-app documentation browser fix(ble): handle reconnection timeout refactor(navigation): migrate to typed routes test(search): add keyword ranking tests . ",
    "url": "/Meshtastic-Android/main/en/developer/contributing.html#commit-messages",
    
    "relUrl": "/en/developer/contributing.html#commit-messages"
  },"520": {
    "doc": "Contributing",
    "title": "Pull Request Checklist",
    "content": "Before submitting: . | Code compiles on all targets: ./gradlew kmpSmokeCompile | All tests pass: ./gradlew allTests | Code style passes: ./gradlew spotlessCheck | Static analysis passes: ./gradlew detekt | New code has appropriate test coverage | No android.* imports in commonMain | Koin modules registered if new DI is added | Routes added to Routes.kt if new navigation is introduced | Documentation updated if user-facing behavior changes | . ",
    "url": "/Meshtastic-Android/main/en/developer/contributing.html#pull-request-checklist",
    
    "relUrl": "/en/developer/contributing.html#pull-request-checklist"
  },"521": {
    "doc": "Contributing",
    "title": "Code Style",
    "content": ". | Formatting: Enforced by Spotless (KtLint rules) | Static analysis: Detekt with project-specific configuration | Imports: No wildcard imports; organized automatically by Spotless | Line length: 120 characters maximum | . Run formatting: ./gradlew spotlessApply . ",
    "url": "/Meshtastic-Android/main/en/developer/contributing.html#code-style",
    
    "relUrl": "/en/developer/contributing.html#code-style"
  },"522": {
    "doc": "Contributing",
    "title": "Architecture Rules",
    "content": ". | Feature modules must not depend on other feature modules | commonMain must not contain android.*, java.io.*, or platform-specific imports | Prefer interface + DI over expect/actual for complex platform behaviors | All navigation routes must be @Serializable and defined in Routes.kt | Use Koin annotations (@Single, @Factory, @Module) for dependency injection | . ",
    "url": "/Meshtastic-Android/main/en/developer/contributing.html#architecture-rules",
    
    "relUrl": "/en/developer/contributing.html#architecture-rules"
  },"523": {
    "doc": "Contributing",
    "title": "Verification",
    "content": "Full pre-merge verification: ./gradlew spotlessCheck detekt kmpSmokeCompile test allTests . For docs-specific changes, also run: ./gradlew generateDocsBundle validateDocsBundle . Prose in docs/en/ follows Section 11 of the Meshtastic Client Design Standards — see Documentation Style for what’s specific to this repository. ",
    "url": "/Meshtastic-Android/main/en/developer/contributing.html#verification",
    
    "relUrl": "/en/developer/contributing.html#verification"
  },"524": {
    "doc": "Contributing",
    "title": "Getting Help",
    "content": ". | Meshtastic Discord — #app-development channel | GitHub Issues — for bug reports and feature requests | GitHub Discussions — for questions and ideas | . ",
    "url": "/Meshtastic-Android/main/en/developer/contributing.html#getting-help",
    
    "relUrl": "/en/developer/contributing.html#getting-help"
  },"525": {
    "doc": "Debug Logs",
    "title": "Debug Logs",
    "content": "When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/debug-logs.html",
    
    "relUrl": "/sk-rSK/user/debug-logs.html"
  },"526": {
    "doc": "Debug Logs",
    "title": "The two tabs",
    "content": "The Debug Panel has two tabs: . | Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior. | App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs. | . Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/debug-logs.html#the-two-tabs",
    
    "relUrl": "/sk-rSK/user/debug-logs.html#the-two-tabs"
  },"527": {
    "doc": "Debug Logs",
    "title": "Viewing app logs",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | Search — type in the search box to filter to matching lines. | Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown. | Refresh — the refresh icon re-reads the latest logs. | . Error and warning lines are tinted so problems stand out. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/debug-logs.html#viewing-app-logs",
    
    "relUrl": "/sk-rSK/user/debug-logs.html#viewing-app-logs"
  },"528": {
    "doc": "Debug Logs",
    "title": "Exporting",
    "content": "Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/debug-logs.html#exporting",
    
    "relUrl": "/sk-rSK/user/debug-logs.html#exporting"
  },"529": {
    "doc": "Debug Logs",
    "title": "Desktop",
    "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/debug-logs.html#desktop",
    
    "relUrl": "/sk-rSK/user/debug-logs.html#desktop"
  },"530": {
    "doc": "Debug Logs",
    "title": "Related Topics",
    "content": ". | Help & In-App Docs — reading this documentation offline inside the app | Connections — if the problem is getting connected to your radio in the first place | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/debug-logs.html#related-topics",
    
    "relUrl": "/sk-rSK/user/debug-logs.html#related-topics"
  },"531": {
    "doc": "Debug Logs",
    "title": "Debug Logs",
    "content": "When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/debug-logs.html",
    
    "relUrl": "/be-rBY/user/debug-logs.html"
  },"532": {
    "doc": "Debug Logs",
    "title": "The two tabs",
    "content": "The Debug Panel has two tabs: . | Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior. | App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs. | . Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/debug-logs.html#the-two-tabs",
    
    "relUrl": "/be-rBY/user/debug-logs.html#the-two-tabs"
  },"533": {
    "doc": "Debug Logs",
    "title": "Viewing app logs",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | Search — type in the search box to filter to matching lines. | Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown. | Refresh — the refresh icon re-reads the latest logs. | . Error and warning lines are tinted so problems stand out. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/debug-logs.html#viewing-app-logs",
    
    "relUrl": "/be-rBY/user/debug-logs.html#viewing-app-logs"
  },"534": {
    "doc": "Debug Logs",
    "title": "Exporting",
    "content": "Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/debug-logs.html#exporting",
    
    "relUrl": "/be-rBY/user/debug-logs.html#exporting"
  },"535": {
    "doc": "Debug Logs",
    "title": "Desktop",
    "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/debug-logs.html#desktop",
    
    "relUrl": "/be-rBY/user/debug-logs.html#desktop"
  },"536": {
    "doc": "Debug Logs",
    "title": "Related Topics",
    "content": ". | Help & In-App Docs — reading this documentation offline inside the app | Connections — if the problem is getting connected to your radio in the first place | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/debug-logs.html#related-topics",
    
    "relUrl": "/be-rBY/user/debug-logs.html#related-topics"
  },"537": {
    "doc": "Debug Logs",
    "title": "Debug Logs",
    "content": "When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/debug-logs.html",
    
    "relUrl": "/it-rIT/user/debug-logs.html"
  },"538": {
    "doc": "Debug Logs",
    "title": "The two tabs",
    "content": "The Debug Panel has two tabs: . | Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior. | App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs. | . Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/debug-logs.html#the-two-tabs",
    
    "relUrl": "/it-rIT/user/debug-logs.html#the-two-tabs"
  },"539": {
    "doc": "Debug Logs",
    "title": "Viewing app logs",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | Search — type in the search box to filter to matching lines. | Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown. | Refresh — the refresh icon re-reads the latest logs. | . Error and warning lines are tinted so problems stand out. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/debug-logs.html#viewing-app-logs",
    
    "relUrl": "/it-rIT/user/debug-logs.html#viewing-app-logs"
  },"540": {
    "doc": "Debug Logs",
    "title": "Exporting",
    "content": "Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/debug-logs.html#exporting",
    
    "relUrl": "/it-rIT/user/debug-logs.html#exporting"
  },"541": {
    "doc": "Debug Logs",
    "title": "Desktop",
    "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/debug-logs.html#desktop",
    
    "relUrl": "/it-rIT/user/debug-logs.html#desktop"
  },"542": {
    "doc": "Debug Logs",
    "title": "Related Topics",
    "content": ". | Help & In-App Docs — reading this documentation offline inside the app | Connections — if the problem is getting connected to your radio in the first place | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/debug-logs.html#related-topics",
    
    "relUrl": "/it-rIT/user/debug-logs.html#related-topics"
  },"543": {
    "doc": "Debug Logs",
    "title": "Debug Logs",
    "content": "When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down. ",
    "url": "/Meshtastic-Android/main/es-rES/user/debug-logs.html",
    
    "relUrl": "/es-rES/user/debug-logs.html"
  },"544": {
    "doc": "Debug Logs",
    "title": "The two tabs",
    "content": "The Debug Panel has two tabs: . | Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior. | App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs. | . Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both. ",
    "url": "/Meshtastic-Android/main/es-rES/user/debug-logs.html#the-two-tabs",
    
    "relUrl": "/es-rES/user/debug-logs.html#the-two-tabs"
  },"545": {
    "doc": "Debug Logs",
    "title": "Viewing app logs",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | Search — type in the search box to filter to matching lines. | Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown. | Refresh — the refresh icon re-reads the latest logs. | . Error and warning lines are tinted so problems stand out. ",
    "url": "/Meshtastic-Android/main/es-rES/user/debug-logs.html#viewing-app-logs",
    
    "relUrl": "/es-rES/user/debug-logs.html#viewing-app-logs"
  },"546": {
    "doc": "Debug Logs",
    "title": "Exporting",
    "content": "Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/es-rES/user/debug-logs.html#exporting",
    
    "relUrl": "/es-rES/user/debug-logs.html#exporting"
  },"547": {
    "doc": "Debug Logs",
    "title": "Desktop",
    "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
    "url": "/Meshtastic-Android/main/es-rES/user/debug-logs.html#desktop",
    
    "relUrl": "/es-rES/user/debug-logs.html#desktop"
  },"548": {
    "doc": "Debug Logs",
    "title": "Related Topics",
    "content": ". | Help & In-App Docs — reading this documentation offline inside the app | Connections — if the problem is getting connected to your radio in the first place | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/debug-logs.html#related-topics",
    
    "relUrl": "/es-rES/user/debug-logs.html#related-topics"
  },"549": {
    "doc": "Debug Logs",
    "title": "Debug Logs",
    "content": "When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/debug-logs.html",
    
    "relUrl": "/sl-rSI/user/debug-logs.html"
  },"550": {
    "doc": "Debug Logs",
    "title": "The two tabs",
    "content": "The Debug Panel has two tabs: . | Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior. | App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs. | . Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/debug-logs.html#the-two-tabs",
    
    "relUrl": "/sl-rSI/user/debug-logs.html#the-two-tabs"
  },"551": {
    "doc": "Debug Logs",
    "title": "Viewing app logs",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | Search — type in the search box to filter to matching lines. | Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown. | Refresh — the refresh icon re-reads the latest logs. | . Error and warning lines are tinted so problems stand out. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/debug-logs.html#viewing-app-logs",
    
    "relUrl": "/sl-rSI/user/debug-logs.html#viewing-app-logs"
  },"552": {
    "doc": "Debug Logs",
    "title": "Exporting",
    "content": "Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/debug-logs.html#exporting",
    
    "relUrl": "/sl-rSI/user/debug-logs.html#exporting"
  },"553": {
    "doc": "Debug Logs",
    "title": "Desktop",
    "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/debug-logs.html#desktop",
    
    "relUrl": "/sl-rSI/user/debug-logs.html#desktop"
  },"554": {
    "doc": "Debug Logs",
    "title": "Related Topics",
    "content": ". | Help & In-App Docs — reading this documentation offline inside the app | Connections — if the problem is getting connected to your radio in the first place | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/debug-logs.html#related-topics",
    
    "relUrl": "/sl-rSI/user/debug-logs.html#related-topics"
  },"555": {
    "doc": "Debug Logs",
    "title": "Debug Logs",
    "content": "When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/debug-logs.html",
    
    "relUrl": "/no-rNO/user/debug-logs.html"
  },"556": {
    "doc": "Debug Logs",
    "title": "The two tabs",
    "content": "The Debug Panel has two tabs: . | Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior. | App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs. | . Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/debug-logs.html#the-two-tabs",
    
    "relUrl": "/no-rNO/user/debug-logs.html#the-two-tabs"
  },"557": {
    "doc": "Debug Logs",
    "title": "Viewing app logs",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | Search — type in the search box to filter to matching lines. | Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown. | Refresh — the refresh icon re-reads the latest logs. | . Error and warning lines are tinted so problems stand out. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/debug-logs.html#viewing-app-logs",
    
    "relUrl": "/no-rNO/user/debug-logs.html#viewing-app-logs"
  },"558": {
    "doc": "Debug Logs",
    "title": "Exporting",
    "content": "Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/debug-logs.html#exporting",
    
    "relUrl": "/no-rNO/user/debug-logs.html#exporting"
  },"559": {
    "doc": "Debug Logs",
    "title": "Desktop",
    "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/debug-logs.html#desktop",
    
    "relUrl": "/no-rNO/user/debug-logs.html#desktop"
  },"560": {
    "doc": "Debug Logs",
    "title": "Related Topics",
    "content": ". | Help & In-App Docs — reading this documentation offline inside the app | Connections — if the problem is getting connected to your radio in the first place | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/debug-logs.html#related-topics",
    
    "relUrl": "/no-rNO/user/debug-logs.html#related-topics"
  },"561": {
    "doc": "Debug Logs",
    "title": "Debug Logs",
    "content": "When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/debug-logs.html",
    
    "relUrl": "/hu-rHU/user/debug-logs.html"
  },"562": {
    "doc": "Debug Logs",
    "title": "The two tabs",
    "content": "The Debug Panel has two tabs: . | Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior. | App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs. | . Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/debug-logs.html#the-two-tabs",
    
    "relUrl": "/hu-rHU/user/debug-logs.html#the-two-tabs"
  },"563": {
    "doc": "Debug Logs",
    "title": "Viewing app logs",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | Search — type in the search box to filter to matching lines. | Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown. | Refresh — the refresh icon re-reads the latest logs. | . Error and warning lines are tinted so problems stand out. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/debug-logs.html#viewing-app-logs",
    
    "relUrl": "/hu-rHU/user/debug-logs.html#viewing-app-logs"
  },"564": {
    "doc": "Debug Logs",
    "title": "Exporting",
    "content": "Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/debug-logs.html#exporting",
    
    "relUrl": "/hu-rHU/user/debug-logs.html#exporting"
  },"565": {
    "doc": "Debug Logs",
    "title": "Desktop",
    "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/debug-logs.html#desktop",
    
    "relUrl": "/hu-rHU/user/debug-logs.html#desktop"
  },"566": {
    "doc": "Debug Logs",
    "title": "Related Topics",
    "content": ". | Help & In-App Docs — reading this documentation offline inside the app | Connections — if the problem is getting connected to your radio in the first place | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/debug-logs.html#related-topics",
    
    "relUrl": "/hu-rHU/user/debug-logs.html#related-topics"
  },"567": {
    "doc": "Отладочные журналы",
    "title": "Отладочные журналы",
    "content": "Когда что-то работает неправильно, отладочные журналы приложения — это самое полезное, что вы можете приложить к отчёту об ошибке. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. Откройте Панель отладки через Настройки → Дополнительно → Панель отладки. If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. Захват журнала, охватывающий момент возникновения проблемы, превращает «это не работает» в то, что разработчик действительно может отследить. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/debug-logs.html",
    
    "relUrl": "/ru-rRU/user/debug-logs.html"
  },"568": {
    "doc": "Отладочные журналы",
    "title": "Две вкладки",
    "content": "Панель отладки содержит две вкладки: . | Пакеты — декодированный трафик mesh-сети, который ваше радио отправило и получило (сообщения уровня протокола). Полезно для диагностики поведения mesh-сети и маршрутизации. | Журналы приложения — собственный диагностический журнал приложения (Android logcat), включая предупреждения, ошибки и трассировки стека самого приложения. Обычно именно это требуется для отчёта об ошибке. | . Каждая вкладка имеет собственную кнопку экспорта и создаёт отдельный файл, поэтому вы можете сохранить тот, который нужен — или сразу оба. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/debug-logs.html#%D0%B4%D0%B2%D0%B5-%D0%B2%D0%BA%D0%BB%D0%B0%D0%B4%D0%BA%D0%B8",
    
    "relUrl": "/ru-rRU/user/debug-logs.html#две-вкладки"
  },"569": {
    "doc": "Отладочные журналы",
    "title": "Просмотр журналов приложения",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | Поиск — введите текст в поле поиска, чтобы отфильтровать строки по совпадению. | Фильтр по уровню — кнопки V / D / I / W / E переключают отображение строк с уровнями Verbose (Подробный), Debug (Отладка), Info (Информация), Warn (Предупреждение) и Error (Ошибка). Нажмите на уровень, чтобы скрыть его; нажмите ещё раз, чтобы вернуть обратно. Строки с фатальными ошибками отображаются всегда. | Обновить — значок обновления заново считывает последние записи журнала. | . Строки с ошибками и предупреждениями подсвечиваются цветом, чтобы проблемы выделялись. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/debug-logs.html#%D0%BF%D1%80%D0%BE%D1%81%D0%BC%D0%BE%D1%82%D1%80-%D0%B6%D1%83%D1%80%D0%BD%D0%B0%D0%BB%D0%BE%D0%B2-%D0%BF%D1%80%D0%B8%D0%BB%D0%BE%D0%B6%D0%B5%D0%BD%D0%B8%D1%8F",
    
    "relUrl": "/ru-rRU/user/debug-logs.html#просмотр-журналов-приложения"
  },"570": {
    "doc": "Отладочные журналы",
    "title": "Экспорт",
    "content": "Нажмите на значок загрузки, чтобы сохранить текущие журналы в файл. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Прикрепите этот файл к своей задаче на GitHub. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/debug-logs.html#%D1%8D%D0%BA%D1%81%D0%BF%D0%BE%D1%80%D1%82",
    
    "relUrl": "/ru-rRU/user/debug-logs.html#экспорт"
  },"571": {
    "doc": "Отладочные журналы",
    "title": "Desktop",
    "content": "У компьютерного приложения нет системного logcat, поэтому вкладка Журналы приложения вместо этого показывает собственный захваченный вывод журнала приложения. Поиск, фильтрация и экспорт работают точно так же. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/debug-logs.html#desktop",
    
    "relUrl": "/ru-rRU/user/debug-logs.html#desktop"
  },"572": {
    "doc": "Отладочные журналы",
    "title": "Связанные темы",
    "content": ". | Справка и встроенная документация — чтение этой документации офлайн внутри приложения | Подключения — если проблема в первую очередь связана с подключением к вашему радио | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/debug-logs.html#%D1%81%D0%B2%D1%8F%D0%B7%D0%B0%D0%BD%D0%BD%D1%8B%D0%B5-%D1%82%D0%B5%D0%BC%D1%8B",
    
    "relUrl": "/ru-rRU/user/debug-logs.html#связанные-темы"
  },"573": {
    "doc": "Debug Logs",
    "title": "Debug Logs",
    "content": "When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/debug-logs.html",
    
    "relUrl": "/cs-rCZ/user/debug-logs.html"
  },"574": {
    "doc": "Debug Logs",
    "title": "The two tabs",
    "content": "The Debug Panel has two tabs: . | Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior. | App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs. | . Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/debug-logs.html#the-two-tabs",
    
    "relUrl": "/cs-rCZ/user/debug-logs.html#the-two-tabs"
  },"575": {
    "doc": "Debug Logs",
    "title": "Viewing app logs",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | Search — type in the search box to filter to matching lines. | Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown. | Refresh — the refresh icon re-reads the latest logs. | . Error and warning lines are tinted so problems stand out. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/debug-logs.html#viewing-app-logs",
    
    "relUrl": "/cs-rCZ/user/debug-logs.html#viewing-app-logs"
  },"576": {
    "doc": "Debug Logs",
    "title": "Exporting",
    "content": "Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/debug-logs.html#exporting",
    
    "relUrl": "/cs-rCZ/user/debug-logs.html#exporting"
  },"577": {
    "doc": "Debug Logs",
    "title": "Desktop",
    "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/debug-logs.html#desktop",
    
    "relUrl": "/cs-rCZ/user/debug-logs.html#desktop"
  },"578": {
    "doc": "Debug Logs",
    "title": "Related Topics",
    "content": ". | Help & In-App Docs — reading this documentation offline inside the app | Connections — if the problem is getting connected to your radio in the first place | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/debug-logs.html#related-topics",
    
    "relUrl": "/cs-rCZ/user/debug-logs.html#related-topics"
  },"579": {
    "doc": "Debug Logs",
    "title": "Debug Logs",
    "content": "When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/debug-logs.html",
    
    "relUrl": "/bg-rBG/user/debug-logs.html"
  },"580": {
    "doc": "Debug Logs",
    "title": "The two tabs",
    "content": "The Debug Panel has two tabs: . | Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior. | App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs. | . Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/debug-logs.html#the-two-tabs",
    
    "relUrl": "/bg-rBG/user/debug-logs.html#the-two-tabs"
  },"581": {
    "doc": "Debug Logs",
    "title": "Viewing app logs",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | Search — type in the search box to filter to matching lines. | Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown. | Refresh — the refresh icon re-reads the latest logs. | . Error and warning lines are tinted so problems stand out. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/debug-logs.html#viewing-app-logs",
    
    "relUrl": "/bg-rBG/user/debug-logs.html#viewing-app-logs"
  },"582": {
    "doc": "Debug Logs",
    "title": "Exporting",
    "content": "Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/debug-logs.html#exporting",
    
    "relUrl": "/bg-rBG/user/debug-logs.html#exporting"
  },"583": {
    "doc": "Debug Logs",
    "title": "Desktop",
    "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/debug-logs.html#desktop",
    
    "relUrl": "/bg-rBG/user/debug-logs.html#desktop"
  },"584": {
    "doc": "Debug Logs",
    "title": "Related Topics",
    "content": ". | Help & In-App Docs — reading this documentation offline inside the app | Connections — if the problem is getting connected to your radio in the first place | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/debug-logs.html#related-topics",
    
    "relUrl": "/bg-rBG/user/debug-logs.html#related-topics"
  },"585": {
    "doc": "Debug Logs",
    "title": "Debug Logs",
    "content": "When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/debug-logs.html",
    
    "relUrl": "/ga-rIE/user/debug-logs.html"
  },"586": {
    "doc": "Debug Logs",
    "title": "The two tabs",
    "content": "The Debug Panel has two tabs: . | Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior. | App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs. | . Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/debug-logs.html#the-two-tabs",
    
    "relUrl": "/ga-rIE/user/debug-logs.html#the-two-tabs"
  },"587": {
    "doc": "Debug Logs",
    "title": "Viewing app logs",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | Search — type in the search box to filter to matching lines. | Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown. | Refresh — the refresh icon re-reads the latest logs. | . Error and warning lines are tinted so problems stand out. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/debug-logs.html#viewing-app-logs",
    
    "relUrl": "/ga-rIE/user/debug-logs.html#viewing-app-logs"
  },"588": {
    "doc": "Debug Logs",
    "title": "Exporting",
    "content": "Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/debug-logs.html#exporting",
    
    "relUrl": "/ga-rIE/user/debug-logs.html#exporting"
  },"589": {
    "doc": "Debug Logs",
    "title": "Desktop",
    "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/debug-logs.html#desktop",
    
    "relUrl": "/ga-rIE/user/debug-logs.html#desktop"
  },"590": {
    "doc": "Debug Logs",
    "title": "Related Topics",
    "content": ". | Help & In-App Docs — reading this documentation offline inside the app | Connections — if the problem is getting connected to your radio in the first place | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/debug-logs.html#related-topics",
    
    "relUrl": "/ga-rIE/user/debug-logs.html#related-topics"
  },"591": {
    "doc": "Debug Logs",
    "title": "Debug Logs",
    "content": "When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/debug-logs.html",
    
    "relUrl": "/fr-rCA/user/debug-logs.html"
  },"592": {
    "doc": "Debug Logs",
    "title": "The two tabs",
    "content": "The Debug Panel has two tabs: . | Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior. | App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs. | . Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/debug-logs.html#the-two-tabs",
    
    "relUrl": "/fr-rCA/user/debug-logs.html#the-two-tabs"
  },"593": {
    "doc": "Debug Logs",
    "title": "Viewing app logs",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | Search — type in the search box to filter to matching lines. | Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown. | Refresh — the refresh icon re-reads the latest logs. | . Error and warning lines are tinted so problems stand out. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/debug-logs.html#viewing-app-logs",
    
    "relUrl": "/fr-rCA/user/debug-logs.html#viewing-app-logs"
  },"594": {
    "doc": "Debug Logs",
    "title": "Exporting",
    "content": "Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/debug-logs.html#exporting",
    
    "relUrl": "/fr-rCA/user/debug-logs.html#exporting"
  },"595": {
    "doc": "Debug Logs",
    "title": "Desktop",
    "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/debug-logs.html#desktop",
    
    "relUrl": "/fr-rCA/user/debug-logs.html#desktop"
  },"596": {
    "doc": "Debug Logs",
    "title": "Related Topics",
    "content": ". | Help & In-App Docs — reading this documentation offline inside the app | Connections — if the problem is getting connected to your radio in the first place | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/debug-logs.html#related-topics",
    
    "relUrl": "/fr-rCA/user/debug-logs.html#related-topics"
  },"597": {
    "doc": "Дебаг логови",
    "title": "Дебаг логови",
    "content": "When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down. ",
    "url": "/Meshtastic-Android/main/srp/user/debug-logs.html",
    
    "relUrl": "/srp/user/debug-logs.html"
  },"598": {
    "doc": "Дебаг логови",
    "title": "The two tabs",
    "content": "The Debug Panel has two tabs: . | Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior. | App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs. | . Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both. ",
    "url": "/Meshtastic-Android/main/srp/user/debug-logs.html#the-two-tabs",
    
    "relUrl": "/srp/user/debug-logs.html#the-two-tabs"
  },"599": {
    "doc": "Дебаг логови",
    "title": "Viewing app logs",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | Search — type in the search box to filter to matching lines. | Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown. | Refresh — the refresh icon re-reads the latest logs. | . Error and warning lines are tinted so problems stand out. ",
    "url": "/Meshtastic-Android/main/srp/user/debug-logs.html#viewing-app-logs",
    
    "relUrl": "/srp/user/debug-logs.html#viewing-app-logs"
  },"600": {
    "doc": "Дебаг логови",
    "title": "Exporting",
    "content": "Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/srp/user/debug-logs.html#exporting",
    
    "relUrl": "/srp/user/debug-logs.html#exporting"
  },"601": {
    "doc": "Дебаг логови",
    "title": "Desktop",
    "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
    "url": "/Meshtastic-Android/main/srp/user/debug-logs.html#desktop",
    
    "relUrl": "/srp/user/debug-logs.html#desktop"
  },"602": {
    "doc": "Дебаг логови",
    "title": "Related Topics",
    "content": ". | Help & In-App Docs — reading this documentation offline inside the app | Connections — if the problem is getting connected to your radio in the first place | . ",
    "url": "/Meshtastic-Android/main/srp/user/debug-logs.html#related-topics",
    
    "relUrl": "/srp/user/debug-logs.html#related-topics"
  },"603": {
    "doc": "Debug Logs",
    "title": "Debug Logs",
    "content": "When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/debug-logs.html",
    
    "relUrl": "/ca-rES/user/debug-logs.html"
  },"604": {
    "doc": "Debug Logs",
    "title": "The two tabs",
    "content": "The Debug Panel has two tabs: . | Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior. | App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs. | . Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/debug-logs.html#the-two-tabs",
    
    "relUrl": "/ca-rES/user/debug-logs.html#the-two-tabs"
  },"605": {
    "doc": "Debug Logs",
    "title": "Viewing app logs",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | Search — type in the search box to filter to matching lines. | Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown. | Refresh — the refresh icon re-reads the latest logs. | . Error and warning lines are tinted so problems stand out. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/debug-logs.html#viewing-app-logs",
    
    "relUrl": "/ca-rES/user/debug-logs.html#viewing-app-logs"
  },"606": {
    "doc": "Debug Logs",
    "title": "Exporting",
    "content": "Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/debug-logs.html#exporting",
    
    "relUrl": "/ca-rES/user/debug-logs.html#exporting"
  },"607": {
    "doc": "Debug Logs",
    "title": "Desktop",
    "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/debug-logs.html#desktop",
    
    "relUrl": "/ca-rES/user/debug-logs.html#desktop"
  },"608": {
    "doc": "Debug Logs",
    "title": "Related Topics",
    "content": ". | Help & In-App Docs — reading this documentation offline inside the app | Connections — if the problem is getting connected to your radio in the first place | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/debug-logs.html#related-topics",
    
    "relUrl": "/ca-rES/user/debug-logs.html#related-topics"
  },"609": {
    "doc": "Debug Logs",
    "title": "Debug Logs",
    "content": "When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/debug-logs.html",
    
    "relUrl": "/ko-rKR/user/debug-logs.html"
  },"610": {
    "doc": "Debug Logs",
    "title": "The two tabs",
    "content": "The Debug Panel has two tabs: . | Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior. | App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs. | . Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/debug-logs.html#the-two-tabs",
    
    "relUrl": "/ko-rKR/user/debug-logs.html#the-two-tabs"
  },"611": {
    "doc": "Debug Logs",
    "title": "Viewing app logs",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | Search — type in the search box to filter to matching lines. | Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown. | Refresh — the refresh icon re-reads the latest logs. | . Error and warning lines are tinted so problems stand out. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/debug-logs.html#viewing-app-logs",
    
    "relUrl": "/ko-rKR/user/debug-logs.html#viewing-app-logs"
  },"612": {
    "doc": "Debug Logs",
    "title": "Exporting",
    "content": "Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/debug-logs.html#exporting",
    
    "relUrl": "/ko-rKR/user/debug-logs.html#exporting"
  },"613": {
    "doc": "Debug Logs",
    "title": "Desktop",
    "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/debug-logs.html#desktop",
    
    "relUrl": "/ko-rKR/user/debug-logs.html#desktop"
  },"614": {
    "doc": "Debug Logs",
    "title": "Related Topics",
    "content": ". | Help & In-App Docs — reading this documentation offline inside the app | Connections — if the problem is getting connected to your radio in the first place | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/debug-logs.html#related-topics",
    
    "relUrl": "/ko-rKR/user/debug-logs.html#related-topics"
  },"615": {
    "doc": "Debug Logs",
    "title": "Debug Logs",
    "content": "When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/debug-logs.html",
    
    "relUrl": "/sv-rSE/user/debug-logs.html"
  },"616": {
    "doc": "Debug Logs",
    "title": "The two tabs",
    "content": "The Debug Panel has two tabs: . | Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior. | App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs. | . Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/debug-logs.html#the-two-tabs",
    
    "relUrl": "/sv-rSE/user/debug-logs.html#the-two-tabs"
  },"617": {
    "doc": "Debug Logs",
    "title": "Viewing app logs",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | Search — type in the search box to filter to matching lines. | Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown. | Refresh — the refresh icon re-reads the latest logs. | . Error and warning lines are tinted so problems stand out. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/debug-logs.html#viewing-app-logs",
    
    "relUrl": "/sv-rSE/user/debug-logs.html#viewing-app-logs"
  },"618": {
    "doc": "Debug Logs",
    "title": "Exporting",
    "content": "Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/debug-logs.html#exporting",
    
    "relUrl": "/sv-rSE/user/debug-logs.html#exporting"
  },"619": {
    "doc": "Debug Logs",
    "title": "Desktop",
    "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/debug-logs.html#desktop",
    
    "relUrl": "/sv-rSE/user/debug-logs.html#desktop"
  },"620": {
    "doc": "Debug Logs",
    "title": "Related Topics",
    "content": ". | Help & In-App Docs — reading this documentation offline inside the app | Connections — if the problem is getting connected to your radio in the first place | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/debug-logs.html#related-topics",
    
    "relUrl": "/sv-rSE/user/debug-logs.html#related-topics"
  },"621": {
    "doc": "Debug Logs",
    "title": "Debug Logs",
    "content": "When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/debug-logs.html",
    
    "relUrl": "/ht-rHT/user/debug-logs.html"
  },"622": {
    "doc": "Debug Logs",
    "title": "The two tabs",
    "content": "The Debug Panel has two tabs: . | Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior. | App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs. | . Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/debug-logs.html#the-two-tabs",
    
    "relUrl": "/ht-rHT/user/debug-logs.html#the-two-tabs"
  },"623": {
    "doc": "Debug Logs",
    "title": "Viewing app logs",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | Search — type in the search box to filter to matching lines. | Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown. | Refresh — the refresh icon re-reads the latest logs. | . Error and warning lines are tinted so problems stand out. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/debug-logs.html#viewing-app-logs",
    
    "relUrl": "/ht-rHT/user/debug-logs.html#viewing-app-logs"
  },"624": {
    "doc": "Debug Logs",
    "title": "Exporting",
    "content": "Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/debug-logs.html#exporting",
    
    "relUrl": "/ht-rHT/user/debug-logs.html#exporting"
  },"625": {
    "doc": "Debug Logs",
    "title": "Desktop",
    "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/debug-logs.html#desktop",
    
    "relUrl": "/ht-rHT/user/debug-logs.html#desktop"
  },"626": {
    "doc": "Debug Logs",
    "title": "Related Topics",
    "content": ". | Help & In-App Docs — reading this documentation offline inside the app | Connections — if the problem is getting connected to your radio in the first place | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/debug-logs.html#related-topics",
    
    "relUrl": "/ht-rHT/user/debug-logs.html#related-topics"
  },"627": {
    "doc": "Дебаг логови",
    "title": "Дебаг логови",
    "content": "When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/debug-logs.html",
    
    "relUrl": "/sr-rLatn/user/debug-logs.html"
  },"628": {
    "doc": "Дебаг логови",
    "title": "The two tabs",
    "content": "The Debug Panel has two tabs: . | Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior. | App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs. | . Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/debug-logs.html#the-two-tabs",
    
    "relUrl": "/sr-rLatn/user/debug-logs.html#the-two-tabs"
  },"629": {
    "doc": "Дебаг логови",
    "title": "Viewing app logs",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | Search — type in the search box to filter to matching lines. | Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown. | Refresh — the refresh icon re-reads the latest logs. | . Error and warning lines are tinted so problems stand out. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/debug-logs.html#viewing-app-logs",
    
    "relUrl": "/sr-rLatn/user/debug-logs.html#viewing-app-logs"
  },"630": {
    "doc": "Дебаг логови",
    "title": "Exporting",
    "content": "Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/debug-logs.html#exporting",
    
    "relUrl": "/sr-rLatn/user/debug-logs.html#exporting"
  },"631": {
    "doc": "Дебаг логови",
    "title": "Desktop",
    "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/debug-logs.html#desktop",
    
    "relUrl": "/sr-rLatn/user/debug-logs.html#desktop"
  },"632": {
    "doc": "Дебаг логови",
    "title": "Related Topics",
    "content": ". | Help & In-App Docs — reading this documentation offline inside the app | Connections — if the problem is getting connected to your radio in the first place | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/debug-logs.html#related-topics",
    
    "relUrl": "/sr-rLatn/user/debug-logs.html#related-topics"
  },"633": {
    "doc": "Debug Logs",
    "title": "Debug Logs",
    "content": "When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/debug-logs.html",
    
    "relUrl": "/nl-rNL/user/debug-logs.html"
  },"634": {
    "doc": "Debug Logs",
    "title": "The two tabs",
    "content": "The Debug Panel has two tabs: . | Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior. | App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs. | . Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/debug-logs.html#the-two-tabs",
    
    "relUrl": "/nl-rNL/user/debug-logs.html#the-two-tabs"
  },"635": {
    "doc": "Debug Logs",
    "title": "Viewing app logs",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | Search — type in the search box to filter to matching lines. | Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown. | Refresh — the refresh icon re-reads the latest logs. | . Error and warning lines are tinted so problems stand out. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/debug-logs.html#viewing-app-logs",
    
    "relUrl": "/nl-rNL/user/debug-logs.html#viewing-app-logs"
  },"636": {
    "doc": "Debug Logs",
    "title": "Exporting",
    "content": "Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/debug-logs.html#exporting",
    
    "relUrl": "/nl-rNL/user/debug-logs.html#exporting"
  },"637": {
    "doc": "Debug Logs",
    "title": "Desktop",
    "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/debug-logs.html#desktop",
    
    "relUrl": "/nl-rNL/user/debug-logs.html#desktop"
  },"638": {
    "doc": "Debug Logs",
    "title": "Related Topics",
    "content": ". | Help & In-App Docs — reading this documentation offline inside the app | Connections — if the problem is getting connected to your radio in the first place | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/debug-logs.html#related-topics",
    
    "relUrl": "/nl-rNL/user/debug-logs.html#related-topics"
  },"639": {
    "doc": "Debug Logs",
    "title": "Debug Logs",
    "content": "When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/debug-logs.html",
    
    "relUrl": "/uk-rUA/user/debug-logs.html"
  },"640": {
    "doc": "Debug Logs",
    "title": "The two tabs",
    "content": "The Debug Panel has two tabs: . | Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior. | App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs. | . Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/debug-logs.html#the-two-tabs",
    
    "relUrl": "/uk-rUA/user/debug-logs.html#the-two-tabs"
  },"641": {
    "doc": "Debug Logs",
    "title": "Viewing app logs",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | Search — type in the search box to filter to matching lines. | Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown. | Refresh — the refresh icon re-reads the latest logs. | . Error and warning lines are tinted so problems stand out. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/debug-logs.html#viewing-app-logs",
    
    "relUrl": "/uk-rUA/user/debug-logs.html#viewing-app-logs"
  },"642": {
    "doc": "Debug Logs",
    "title": "Exporting",
    "content": "Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/debug-logs.html#exporting",
    
    "relUrl": "/uk-rUA/user/debug-logs.html#exporting"
  },"643": {
    "doc": "Debug Logs",
    "title": "Desktop",
    "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/debug-logs.html#desktop",
    
    "relUrl": "/uk-rUA/user/debug-logs.html#desktop"
  },"644": {
    "doc": "Debug Logs",
    "title": "Related Topics",
    "content": ". | Help & In-App Docs — reading this documentation offline inside the app | Connections — if the problem is getting connected to your radio in the first place | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/debug-logs.html#related-topics",
    
    "relUrl": "/uk-rUA/user/debug-logs.html#related-topics"
  },"645": {
    "doc": "Virheenjäljityslokitiedot",
    "title": "Virheenjäljityslokitiedot",
    "content": "Kun jokin toimii odottamattomasti, sovelluksen virheenjäljityslokitiedot ovat hyödyllisin liite vikaraporttiin. Meshtastic voi kerätä ne puolestasi suoraan sovelluksessa — niiden keräämiseen ei tarvita adb:tä eikä työpöydän työkaluja. Avaa Virheenjäljityspaneeli kohdasta Asetukset → Lisäasetukset → Virheenjäljityspaneeli. Jos teet vikailmoituksen, vie lokit (katso Lokien vieminen) ja liitä .txt-tiedosto raporttiisi Meshtastic-Androidin vikaseurannassa. Lokitietotallenne, joka kattaa hetken jolloin ongelma ilmeni, auttaa muuttamaan “ei toimi” -kuvauksen sellaiseksi, jonka kehittäjä pystyy oikeasti selvittämään. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/debug-logs.html",
    
    "relUrl": "/fi-rFI/user/debug-logs.html"
  },"646": {
    "doc": "Virheenjäljityslokitiedot",
    "title": "Kaksi välilehteä",
    "content": "Virheenjäljityspaneelissa on kaksi välilehteä: . | Paketit — radion lähettämä ja vastaanottama purettu mesh-liikenne (protokollatason viestit). Hyödyllinen mesh-verkon ja reitityksen toiminnan diagnosointiin. | Sovelluslokitiedot — sovelluksen oma diagnostiikkaloki (Androidin logcat), joka sisältää varoitukset, virheet ja pinoseurannat itse sovelluksesta. Tätä tarvitaan yleensä vikaraportissa. | . Jokaisella välilehdellä on oma Vie-painikkeensa, ja kumpikin tuottaa oman tiedostonsa. Voit siis liittää raporttiin vain tarvittavan tiedoston tai molemmat. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/debug-logs.html#kaksi-v%C3%A4lilehte%C3%A4",
    
    "relUrl": "/fi-rFI/user/debug-logs.html#kaksi-välilehteä"
  },"647": {
    "doc": "Virheenjäljityslokitiedot",
    "title": "Sovelluslokitietojen tarkastelu",
    "content": "Sovelluksen lokit -välilehdellä näkyvät tämän sovelluksen uusimmat lokirivit — ei koskaan muiden puhelimesi sovellusten. | Haku — kirjoita hakukenttään suodattaaksesi vastaavat lokirivit. | Tasosuodatin — V / D / I / W / E -painikkeilla voit näyttää tai piilottaa Verbose-, Debug-, Info-, Warn- ja Error-lokirivit. Piilota taso napauttamalla sitä. Napauta uudelleen, niin se tulee takaisin näkyviin. Vakavat virheet näytetään aina. | Päivitä — päivityskuvake lukee uusimmat lokitiedot uudelleen. | . Virhe- ja varoitusrivit on korostettu, jotta ongelmat erottuvat paremmin. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/debug-logs.html#sovelluslokitietojen-tarkastelu",
    
    "relUrl": "/fi-rFI/user/debug-logs.html#sovelluslokitietojen-tarkastelu"
  },"648": {
    "doc": "Virheenjäljityslokitiedot",
    "title": "Lokien vienti",
    "content": "Napauta latauskuvaketta tallentaaksesi nykyiset lokitiedot tiedostoon. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Liitä tämä tiedosto GitHub-vikaraporttiisi. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/debug-logs.html#lokien-vienti",
    
    "relUrl": "/fi-rFI/user/debug-logs.html#lokien-vienti"
  },"649": {
    "doc": "Virheenjäljityslokitiedot",
    "title": "Työpöytä",
    "content": "Työpöytäsovelluksessa ei ole järjestelmän logcat-lokitietoa, joten Sovelluslokit-välilehti näyttää sen sijaan sovelluksen itse keräämät lokit. Haku, suodatus ja vienti toimivat samalla tavalla. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/debug-logs.html#ty%C3%B6p%C3%B6yt%C3%A4",
    
    "relUrl": "/fi-rFI/user/debug-logs.html#työpöytä"
  },"650": {
    "doc": "Virheenjäljityslokitiedot",
    "title": "Aiheeseen liittyvät aiheet",
    "content": ". | Ohjeet ja sovelluksen sisäinen dokumentaatio — tämän dokumentaation lukeminen offline-tilassa sovelluksessa | Yhteydet — jos ongelma liittyy radion yhdistämiseen | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/debug-logs.html#aiheeseen-liittyv%C3%A4t-aiheet",
    
    "relUrl": "/fi-rFI/user/debug-logs.html#aiheeseen-liittyvät-aiheet"
  },"651": {
    "doc": "Debug Logs",
    "title": "Debug Logs",
    "content": "When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/debug-logs.html",
    
    "relUrl": "/is-rIS/user/debug-logs.html"
  },"652": {
    "doc": "Debug Logs",
    "title": "The two tabs",
    "content": "The Debug Panel has two tabs: . | Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior. | App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs. | . Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/debug-logs.html#the-two-tabs",
    
    "relUrl": "/is-rIS/user/debug-logs.html#the-two-tabs"
  },"653": {
    "doc": "Debug Logs",
    "title": "Viewing app logs",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | Search — type in the search box to filter to matching lines. | Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown. | Refresh — the refresh icon re-reads the latest logs. | . Error and warning lines are tinted so problems stand out. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/debug-logs.html#viewing-app-logs",
    
    "relUrl": "/is-rIS/user/debug-logs.html#viewing-app-logs"
  },"654": {
    "doc": "Debug Logs",
    "title": "Exporting",
    "content": "Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/debug-logs.html#exporting",
    
    "relUrl": "/is-rIS/user/debug-logs.html#exporting"
  },"655": {
    "doc": "Debug Logs",
    "title": "Desktop",
    "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/debug-logs.html#desktop",
    
    "relUrl": "/is-rIS/user/debug-logs.html#desktop"
  },"656": {
    "doc": "Debug Logs",
    "title": "Related Topics",
    "content": ". | Help & In-App Docs — reading this documentation offline inside the app | Connections — if the problem is getting connected to your radio in the first place | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/debug-logs.html#related-topics",
    
    "relUrl": "/is-rIS/user/debug-logs.html#related-topics"
  },"657": {
    "doc": "Debug Logs",
    "title": "Debug Logs",
    "content": "When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/debug-logs.html",
    
    "relUrl": "/lt-rLT/user/debug-logs.html"
  },"658": {
    "doc": "Debug Logs",
    "title": "The two tabs",
    "content": "The Debug Panel has two tabs: . | Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior. | App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs. | . Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/debug-logs.html#the-two-tabs",
    
    "relUrl": "/lt-rLT/user/debug-logs.html#the-two-tabs"
  },"659": {
    "doc": "Debug Logs",
    "title": "Viewing app logs",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | Search — type in the search box to filter to matching lines. | Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown. | Refresh — the refresh icon re-reads the latest logs. | . Error and warning lines are tinted so problems stand out. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/debug-logs.html#viewing-app-logs",
    
    "relUrl": "/lt-rLT/user/debug-logs.html#viewing-app-logs"
  },"660": {
    "doc": "Debug Logs",
    "title": "Exporting",
    "content": "Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/debug-logs.html#exporting",
    
    "relUrl": "/lt-rLT/user/debug-logs.html#exporting"
  },"661": {
    "doc": "Debug Logs",
    "title": "Desktop",
    "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/debug-logs.html#desktop",
    
    "relUrl": "/lt-rLT/user/debug-logs.html#desktop"
  },"662": {
    "doc": "Debug Logs",
    "title": "Related Topics",
    "content": ". | Help & In-App Docs — reading this documentation offline inside the app | Connections — if the problem is getting connected to your radio in the first place | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/debug-logs.html#related-topics",
    
    "relUrl": "/lt-rLT/user/debug-logs.html#related-topics"
  },"663": {
    "doc": "Debug Logs",
    "title": "Debug Logs",
    "content": "When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/debug-logs.html",
    
    "relUrl": "/gl-rES/user/debug-logs.html"
  },"664": {
    "doc": "Debug Logs",
    "title": "The two tabs",
    "content": "The Debug Panel has two tabs: . | Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior. | App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs. | . Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/debug-logs.html#the-two-tabs",
    
    "relUrl": "/gl-rES/user/debug-logs.html#the-two-tabs"
  },"665": {
    "doc": "Debug Logs",
    "title": "Viewing app logs",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | Search — type in the search box to filter to matching lines. | Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown. | Refresh — the refresh icon re-reads the latest logs. | . Error and warning lines are tinted so problems stand out. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/debug-logs.html#viewing-app-logs",
    
    "relUrl": "/gl-rES/user/debug-logs.html#viewing-app-logs"
  },"666": {
    "doc": "Debug Logs",
    "title": "Exporting",
    "content": "Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/debug-logs.html#exporting",
    
    "relUrl": "/gl-rES/user/debug-logs.html#exporting"
  },"667": {
    "doc": "Debug Logs",
    "title": "Desktop",
    "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/debug-logs.html#desktop",
    
    "relUrl": "/gl-rES/user/debug-logs.html#desktop"
  },"668": {
    "doc": "Debug Logs",
    "title": "Related Topics",
    "content": ". | Help & In-App Docs — reading this documentation offline inside the app | Connections — if the problem is getting connected to your radio in the first place | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/debug-logs.html#related-topics",
    
    "relUrl": "/gl-rES/user/debug-logs.html#related-topics"
  },"669": {
    "doc": "デバッグログ",
    "title": "デバッグログ",
    "content": "何か不具合が起きたとき、アプリのデバッグログは、バグ報告に添付できる最も役立つものです。 Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. 「設定 → 詳細設定 → デバッグパネル」から「デバッグパネル」を開きます。 . If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. 問題が起きた瞬間を含むログのキャプチャは、「動かない」という報告を、開発者が実際に追跡できるものに変えます。 . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/debug-logs.html",
    
    "relUrl": "/ja-rJP/user/debug-logs.html"
  },"670": {
    "doc": "デバッグログ",
    "title": "2 つのタブ",
    "content": "デバッグパネルには 2 つのタブがあります： . | パケット：無線機が送受信した、デコード済みのメッシュトラフィック（プロトコルレベルのメッセージ）。メッシュやルーティングの動作を診断するのに役立ちます。 | アプリログ：アプリ自身の診断ログ（Android の logcat）。アプリからの警告、エラー、スタックトレースを含みます。通常、バグ報告に必要なのはこちらです。 | . 各タブには独自のエクスポートボタンがあり、それぞれ別のファイルを生成するため、関連する方を、または両方を取得できます。 . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/debug-logs.html#2-%E3%81%A4%E3%81%AE%E3%82%BF%E3%83%96",
    
    "relUrl": "/ja-rJP/user/debug-logs.html#2-つのタブ"
  },"671": {
    "doc": "デバッグログ",
    "title": "アプリログを表示する",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | 検索：検索ボックスに入力すると、一致する行に絞り込めます。 | レベルフィルター：V／D／I／W／E のチップで、Verbose、Debug、Info、Warn、Error の行を切り替えます。レベルをタップすると非表示になり、もう一度タップすると再表示されます。 Fatal の行は常に表示されます。 | 更新：更新アイコンで最新のログを読み直します。 | . エラーと警告の行は色付けされ、問題が目立つようになっています。 . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/debug-logs.html#%E3%82%A2%E3%83%97%E3%83%AA%E3%83%AD%E3%82%B0%E3%82%92%E8%A1%A8%E7%A4%BA%E3%81%99%E3%82%8B",
    
    "relUrl": "/ja-rJP/user/debug-logs.html#アプリログを表示する"
  },"672": {
    "doc": "デバッグログ",
    "title": "エクスポート",
    "content": "ダウンロードアイコンをタップすると、現在のログをファイルに保存できます。 The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. そのファイルを GitHub の issue に添付してください。 . 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/debug-logs.html#%E3%82%A8%E3%82%AF%E3%82%B9%E3%83%9D%E3%83%BC%E3%83%88",
    
    "relUrl": "/ja-rJP/user/debug-logs.html#エクスポート"
  },"673": {
    "doc": "デバッグログ",
    "title": "デスクトップ",
    "content": "デスクトップアプリにはシステムの logcat がないため、「アプリログ」タブは代わりに、アプリ自身がキャプチャしたログ出力を表示します。検索、絞り込み、エクスポートは同じように機能します。 . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/debug-logs.html#%E3%83%87%E3%82%B9%E3%82%AF%E3%83%88%E3%83%83%E3%83%97",
    
    "relUrl": "/ja-rJP/user/debug-logs.html#デスクトップ"
  },"674": {
    "doc": "デバッグログ",
    "title": "関連トピック",
    "content": ". | ヘルプとアプリ内ドキュメント：このドキュメントをアプリ内でオフラインで読む | コネクション：そもそも無線機に接続できないことが問題の場合 | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/debug-logs.html#%E9%96%A2%E9%80%A3%E3%83%88%E3%83%94%E3%83%83%E3%82%AF",
    
    "relUrl": "/ja-rJP/user/debug-logs.html#関連トピック"
  },"675": {
    "doc": "Fehlersuchprotokolle",
    "title": "Fehlersuchprotokolle",
    "content": "When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/debug-logs.html",
    
    "relUrl": "/de-rDE/user/debug-logs.html"
  },"676": {
    "doc": "Fehlersuchprotokolle",
    "title": "The two tabs",
    "content": "The Debug Panel has two tabs: . | Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior. | App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs. | . Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/debug-logs.html#the-two-tabs",
    
    "relUrl": "/de-rDE/user/debug-logs.html#the-two-tabs"
  },"677": {
    "doc": "Fehlersuchprotokolle",
    "title": "Viewing app logs",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | Search — type in the search box to filter to matching lines. | Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown. | Refresh — the refresh icon re-reads the latest logs. | . Error and warning lines are tinted so problems stand out. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/debug-logs.html#viewing-app-logs",
    
    "relUrl": "/de-rDE/user/debug-logs.html#viewing-app-logs"
  },"678": {
    "doc": "Fehlersuchprotokolle",
    "title": "Exporting",
    "content": "Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/debug-logs.html#exporting",
    
    "relUrl": "/de-rDE/user/debug-logs.html#exporting"
  },"679": {
    "doc": "Fehlersuchprotokolle",
    "title": "Desktop",
    "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/debug-logs.html#desktop",
    
    "relUrl": "/de-rDE/user/debug-logs.html#desktop"
  },"680": {
    "doc": "Fehlersuchprotokolle",
    "title": "Related Topics",
    "content": ". | Help & In-App Docs — reading this documentation offline inside the app | Connections — if the problem is getting connected to your radio in the first place | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/debug-logs.html#related-topics",
    
    "relUrl": "/de-rDE/user/debug-logs.html#related-topics"
  },"681": {
    "doc": "Debug Logs",
    "title": "Debug Logs",
    "content": "When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/debug-logs.html",
    
    "relUrl": "/ar-rSA/user/debug-logs.html"
  },"682": {
    "doc": "Debug Logs",
    "title": "The two tabs",
    "content": "The Debug Panel has two tabs: . | Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior. | App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs. | . Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/debug-logs.html#the-two-tabs",
    
    "relUrl": "/ar-rSA/user/debug-logs.html#the-two-tabs"
  },"683": {
    "doc": "Debug Logs",
    "title": "Viewing app logs",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | Search — type in the search box to filter to matching lines. | Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown. | Refresh — the refresh icon re-reads the latest logs. | . Error and warning lines are tinted so problems stand out. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/debug-logs.html#viewing-app-logs",
    
    "relUrl": "/ar-rSA/user/debug-logs.html#viewing-app-logs"
  },"684": {
    "doc": "Debug Logs",
    "title": "Exporting",
    "content": "Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/debug-logs.html#exporting",
    
    "relUrl": "/ar-rSA/user/debug-logs.html#exporting"
  },"685": {
    "doc": "Debug Logs",
    "title": "Desktop",
    "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/debug-logs.html#desktop",
    
    "relUrl": "/ar-rSA/user/debug-logs.html#desktop"
  },"686": {
    "doc": "Debug Logs",
    "title": "Related Topics",
    "content": ". | Help & In-App Docs — reading this documentation offline inside the app | Connections — if the problem is getting connected to your radio in the first place | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/debug-logs.html#related-topics",
    
    "relUrl": "/ar-rSA/user/debug-logs.html#related-topics"
  },"687": {
    "doc": "Debug Logs",
    "title": "Debug Logs",
    "content": "When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/debug-logs.html",
    
    "relUrl": "/hr-rHR/user/debug-logs.html"
  },"688": {
    "doc": "Debug Logs",
    "title": "The two tabs",
    "content": "The Debug Panel has two tabs: . | Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior. | App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs. | . Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/debug-logs.html#the-two-tabs",
    
    "relUrl": "/hr-rHR/user/debug-logs.html#the-two-tabs"
  },"689": {
    "doc": "Debug Logs",
    "title": "Viewing app logs",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | Search — type in the search box to filter to matching lines. | Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown. | Refresh — the refresh icon re-reads the latest logs. | . Error and warning lines are tinted so problems stand out. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/debug-logs.html#viewing-app-logs",
    
    "relUrl": "/hr-rHR/user/debug-logs.html#viewing-app-logs"
  },"690": {
    "doc": "Debug Logs",
    "title": "Exporting",
    "content": "Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/debug-logs.html#exporting",
    
    "relUrl": "/hr-rHR/user/debug-logs.html#exporting"
  },"691": {
    "doc": "Debug Logs",
    "title": "Desktop",
    "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/debug-logs.html#desktop",
    
    "relUrl": "/hr-rHR/user/debug-logs.html#desktop"
  },"692": {
    "doc": "Debug Logs",
    "title": "Related Topics",
    "content": ". | Help & In-App Docs — reading this documentation offline inside the app | Connections — if the problem is getting connected to your radio in the first place | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/debug-logs.html#related-topics",
    
    "relUrl": "/hr-rHR/user/debug-logs.html#related-topics"
  },"693": {
    "doc": "Debug Logs",
    "title": "Debug Logs",
    "content": "When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/debug-logs.html",
    
    "relUrl": "/pt-rPT/user/debug-logs.html"
  },"694": {
    "doc": "Debug Logs",
    "title": "The two tabs",
    "content": "The Debug Panel has two tabs: . | Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior. | App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs. | . Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/debug-logs.html#the-two-tabs",
    
    "relUrl": "/pt-rPT/user/debug-logs.html#the-two-tabs"
  },"695": {
    "doc": "Debug Logs",
    "title": "Viewing app logs",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | Search — type in the search box to filter to matching lines. | Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown. | Refresh — the refresh icon re-reads the latest logs. | . Error and warning lines are tinted so problems stand out. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/debug-logs.html#viewing-app-logs",
    
    "relUrl": "/pt-rPT/user/debug-logs.html#viewing-app-logs"
  },"696": {
    "doc": "Debug Logs",
    "title": "Exporting",
    "content": "Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/debug-logs.html#exporting",
    
    "relUrl": "/pt-rPT/user/debug-logs.html#exporting"
  },"697": {
    "doc": "Debug Logs",
    "title": "Desktop",
    "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/debug-logs.html#desktop",
    
    "relUrl": "/pt-rPT/user/debug-logs.html#desktop"
  },"698": {
    "doc": "Debug Logs",
    "title": "Related Topics",
    "content": ". | Help & In-App Docs — reading this documentation offline inside the app | Connections — if the problem is getting connected to your radio in the first place | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/debug-logs.html#related-topics",
    
    "relUrl": "/pt-rPT/user/debug-logs.html#related-topics"
  },"699": {
    "doc": "Debug Logs",
    "title": "Debug Logs",
    "content": "When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/debug-logs.html",
    
    "relUrl": "/pl-rPL/user/debug-logs.html"
  },"700": {
    "doc": "Debug Logs",
    "title": "The two tabs",
    "content": "The Debug Panel has two tabs: . | Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior. | App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs. | . Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/debug-logs.html#the-two-tabs",
    
    "relUrl": "/pl-rPL/user/debug-logs.html#the-two-tabs"
  },"701": {
    "doc": "Debug Logs",
    "title": "Viewing app logs",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | Search — type in the search box to filter to matching lines. | Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown. | Refresh — the refresh icon re-reads the latest logs. | . Error and warning lines are tinted so problems stand out. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/debug-logs.html#viewing-app-logs",
    
    "relUrl": "/pl-rPL/user/debug-logs.html#viewing-app-logs"
  },"702": {
    "doc": "Debug Logs",
    "title": "Exporting",
    "content": "Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/debug-logs.html#exporting",
    
    "relUrl": "/pl-rPL/user/debug-logs.html#exporting"
  },"703": {
    "doc": "Debug Logs",
    "title": "Desktop",
    "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/debug-logs.html#desktop",
    
    "relUrl": "/pl-rPL/user/debug-logs.html#desktop"
  },"704": {
    "doc": "Debug Logs",
    "title": "Related Topics",
    "content": ". | Help & In-App Docs — reading this documentation offline inside the app | Connections — if the problem is getting connected to your radio in the first place | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/debug-logs.html#related-topics",
    
    "relUrl": "/pl-rPL/user/debug-logs.html#related-topics"
  },"705": {
    "doc": "Debug Logs",
    "title": "Debug Logs",
    "content": "When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/debug-logs.html",
    
    "relUrl": "/zh-rCN/user/debug-logs.html"
  },"706": {
    "doc": "Debug Logs",
    "title": "The two tabs",
    "content": "The Debug Panel has two tabs: . | Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior. | App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs. | . Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/debug-logs.html#the-two-tabs",
    
    "relUrl": "/zh-rCN/user/debug-logs.html#the-two-tabs"
  },"707": {
    "doc": "Debug Logs",
    "title": "Viewing app logs",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | Search — type in the search box to filter to matching lines. | Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown. | Refresh — the refresh icon re-reads the latest logs. | . Error and warning lines are tinted so problems stand out. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/debug-logs.html#viewing-app-logs",
    
    "relUrl": "/zh-rCN/user/debug-logs.html#viewing-app-logs"
  },"708": {
    "doc": "Debug Logs",
    "title": "Exporting",
    "content": "Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/debug-logs.html#exporting",
    
    "relUrl": "/zh-rCN/user/debug-logs.html#exporting"
  },"709": {
    "doc": "Debug Logs",
    "title": "Desktop",
    "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/debug-logs.html#desktop",
    
    "relUrl": "/zh-rCN/user/debug-logs.html#desktop"
  },"710": {
    "doc": "Debug Logs",
    "title": "Related Topics",
    "content": ". | Help & In-App Docs — reading this documentation offline inside the app | Connections — if the problem is getting connected to your radio in the first place | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/debug-logs.html#related-topics",
    
    "relUrl": "/zh-rCN/user/debug-logs.html#related-topics"
  },"711": {
    "doc": "Debug Logs",
    "title": "Debug Logs",
    "content": "When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/debug-logs.html",
    
    "relUrl": "/sq-rAL/user/debug-logs.html"
  },"712": {
    "doc": "Debug Logs",
    "title": "The two tabs",
    "content": "The Debug Panel has two tabs: . | Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior. | App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs. | . Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/debug-logs.html#the-two-tabs",
    
    "relUrl": "/sq-rAL/user/debug-logs.html#the-two-tabs"
  },"713": {
    "doc": "Debug Logs",
    "title": "Viewing app logs",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | Search — type in the search box to filter to matching lines. | Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown. | Refresh — the refresh icon re-reads the latest logs. | . Error and warning lines are tinted so problems stand out. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/debug-logs.html#viewing-app-logs",
    
    "relUrl": "/sq-rAL/user/debug-logs.html#viewing-app-logs"
  },"714": {
    "doc": "Debug Logs",
    "title": "Exporting",
    "content": "Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/debug-logs.html#exporting",
    
    "relUrl": "/sq-rAL/user/debug-logs.html#exporting"
  },"715": {
    "doc": "Debug Logs",
    "title": "Desktop",
    "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/debug-logs.html#desktop",
    
    "relUrl": "/sq-rAL/user/debug-logs.html#desktop"
  },"716": {
    "doc": "Debug Logs",
    "title": "Related Topics",
    "content": ". | Help & In-App Docs — reading this documentation offline inside the app | Connections — if the problem is getting connected to your radio in the first place | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/debug-logs.html#related-topics",
    
    "relUrl": "/sq-rAL/user/debug-logs.html#related-topics"
  },"717": {
    "doc": "Debug Logs",
    "title": "Debug Logs",
    "content": "When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/debug-logs.html",
    
    "relUrl": "/zh-rTW/user/debug-logs.html"
  },"718": {
    "doc": "Debug Logs",
    "title": "The two tabs",
    "content": "The Debug Panel has two tabs: . | Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior. | App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs. | . Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/debug-logs.html#the-two-tabs",
    
    "relUrl": "/zh-rTW/user/debug-logs.html#the-two-tabs"
  },"719": {
    "doc": "Debug Logs",
    "title": "Viewing app logs",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | Search — type in the search box to filter to matching lines. | Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown. | Refresh — the refresh icon re-reads the latest logs. | . Error and warning lines are tinted so problems stand out. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/debug-logs.html#viewing-app-logs",
    
    "relUrl": "/zh-rTW/user/debug-logs.html#viewing-app-logs"
  },"720": {
    "doc": "Debug Logs",
    "title": "Exporting",
    "content": "Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/debug-logs.html#exporting",
    
    "relUrl": "/zh-rTW/user/debug-logs.html#exporting"
  },"721": {
    "doc": "Debug Logs",
    "title": "桌面版",
    "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/debug-logs.html#%E6%A1%8C%E9%9D%A2%E7%89%88",
    
    "relUrl": "/zh-rTW/user/debug-logs.html#桌面版"
  },"722": {
    "doc": "Debug Logs",
    "title": "相關主題",
    "content": ". | Help & In-App Docs — reading this documentation offline inside the app | Connections — if the problem is getting connected to your radio in the first place | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/debug-logs.html#%E7%9B%B8%E9%97%9C%E4%B8%BB%E9%A1%8C",
    
    "relUrl": "/zh-rTW/user/debug-logs.html#相關主題"
  },"723": {
    "doc": "Arendaja logid",
    "title": "Arendaja logid",
    "content": "Kui midagi töötab valesti, on rakenduse arendajalogid kõige kasulikum asi, mida saad veateatele lisada. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. Ava Arendajapaneel, valides Seaded → Täpsemad → Arendajapaneel. If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/debug-logs.html",
    
    "relUrl": "/et-rEE/user/debug-logs.html"
  },"724": {
    "doc": "Arendaja logid",
    "title": "The two tabs",
    "content": "Arendajapaneelil on kaks vahekaarti: . | Paketid – dekodeeritud võrguliiklus, mida raadio on saatnud ja vastu võtnud (protokollitasemel sõnumid). Useful for diagnosing mesh and routing behavior. | App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs. | . Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/debug-logs.html#the-two-tabs",
    
    "relUrl": "/et-rEE/user/debug-logs.html#the-two-tabs"
  },"725": {
    "doc": "Arendaja logid",
    "title": "Viewing app logs",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | Otsi – sisesta otsingukasti otsing, et filtreerida sobivate ridade hulgast. | Tasemefilter — V / D / I / W / E kiibid lülitavad sisse üksikasjaliku, arendaja-, teabe-, hoiatus- ja vearea. Tap a level to hide it; tap again to bring it back. Fataalseid jooni näidatakse alati. | Värskenda – värskendamise ikoon loeb uuesti viimased logid. | . Error and warning lines are tinted so problems stand out. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/debug-logs.html#viewing-app-logs",
    
    "relUrl": "/et-rEE/user/debug-logs.html#viewing-app-logs"
  },"726": {
    "doc": "Arendaja logid",
    "title": "Eksportimine",
    "content": "Praeguste logide faili salvestamiseks puuduta ikooni allalaadimine. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/debug-logs.html#eksportimine",
    
    "relUrl": "/et-rEE/user/debug-logs.html#eksportimine"
  },"727": {
    "doc": "Arendaja logid",
    "title": "Töölaud",
    "content": "Töölauarakendusel puudub süsteemi logcat, seega kuvatakse vahekaardil Rakenduse logid rakenduse enda jäädvustatud logide väljundit. Otsimine, filtreerimine ja eksportimine toimivad samamoodi. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/debug-logs.html#t%C3%B6%C3%B6laud",
    
    "relUrl": "/et-rEE/user/debug-logs.html#töölaud"
  },"728": {
    "doc": "Arendaja logid",
    "title": "Seotud teemad",
    "content": ". | Abi ja rakendusesisesed dokumendid — selle dokumentatsiooni lugemine rakenduses võrguühenduseta | Connections — if the problem is getting connected to your radio in the first place | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/debug-logs.html#seotud-teemad",
    
    "relUrl": "/et-rEE/user/debug-logs.html#seotud-teemad"
  },"729": {
    "doc": "Debug Logs",
    "title": "Debug Logs",
    "content": "When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/debug-logs.html",
    
    "relUrl": "/fr-rFR/user/debug-logs.html"
  },"730": {
    "doc": "Debug Logs",
    "title": "The two tabs",
    "content": "The Debug Panel has two tabs: . | Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior. | App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs. | . Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/debug-logs.html#the-two-tabs",
    
    "relUrl": "/fr-rFR/user/debug-logs.html#the-two-tabs"
  },"731": {
    "doc": "Debug Logs",
    "title": "Viewing app logs",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | Search — type in the search box to filter to matching lines. | Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown. | Refresh — the refresh icon re-reads the latest logs. | . Error and warning lines are tinted so problems stand out. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/debug-logs.html#viewing-app-logs",
    
    "relUrl": "/fr-rFR/user/debug-logs.html#viewing-app-logs"
  },"732": {
    "doc": "Debug Logs",
    "title": "Exporting",
    "content": "Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/debug-logs.html#exporting",
    
    "relUrl": "/fr-rFR/user/debug-logs.html#exporting"
  },"733": {
    "doc": "Debug Logs",
    "title": "Desktop",
    "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/debug-logs.html#desktop",
    
    "relUrl": "/fr-rFR/user/debug-logs.html#desktop"
  },"734": {
    "doc": "Debug Logs",
    "title": "Related Topics",
    "content": ". | Help & In-App Docs — reading this documentation offline inside the app | Connections — if the problem is getting connected to your radio in the first place | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/debug-logs.html#related-topics",
    
    "relUrl": "/fr-rFR/user/debug-logs.html#related-topics"
  },"735": {
    "doc": "Debug Logs",
    "title": "Debug Logs",
    "content": "When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/debug-logs.html",
    
    "relUrl": "/tr-rTR/user/debug-logs.html"
  },"736": {
    "doc": "Debug Logs",
    "title": "The two tabs",
    "content": "The Debug Panel has two tabs: . | Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior. | App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs. | . Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/debug-logs.html#the-two-tabs",
    
    "relUrl": "/tr-rTR/user/debug-logs.html#the-two-tabs"
  },"737": {
    "doc": "Debug Logs",
    "title": "Viewing app logs",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | Search — type in the search box to filter to matching lines. | Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown. | Refresh — the refresh icon re-reads the latest logs. | . Error and warning lines are tinted so problems stand out. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/debug-logs.html#viewing-app-logs",
    
    "relUrl": "/tr-rTR/user/debug-logs.html#viewing-app-logs"
  },"738": {
    "doc": "Debug Logs",
    "title": "Exporting",
    "content": "Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/debug-logs.html#exporting",
    
    "relUrl": "/tr-rTR/user/debug-logs.html#exporting"
  },"739": {
    "doc": "Debug Logs",
    "title": "Desktop",
    "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/debug-logs.html#desktop",
    
    "relUrl": "/tr-rTR/user/debug-logs.html#desktop"
  },"740": {
    "doc": "Debug Logs",
    "title": "Related Topics",
    "content": ". | Help & In-App Docs — reading this documentation offline inside the app | Connections — if the problem is getting connected to your radio in the first place | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/debug-logs.html#related-topics",
    
    "relUrl": "/tr-rTR/user/debug-logs.html#related-topics"
  },"741": {
    "doc": "Debug Logs",
    "title": "Debug Logs",
    "content": "When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/debug-logs.html",
    
    "relUrl": "/el-rGR/user/debug-logs.html"
  },"742": {
    "doc": "Debug Logs",
    "title": "The two tabs",
    "content": "The Debug Panel has two tabs: . | Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior. | App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs. | . Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/debug-logs.html#the-two-tabs",
    
    "relUrl": "/el-rGR/user/debug-logs.html#the-two-tabs"
  },"743": {
    "doc": "Debug Logs",
    "title": "Viewing app logs",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | Search — type in the search box to filter to matching lines. | Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown. | Refresh — the refresh icon re-reads the latest logs. | . Error and warning lines are tinted so problems stand out. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/debug-logs.html#viewing-app-logs",
    
    "relUrl": "/el-rGR/user/debug-logs.html#viewing-app-logs"
  },"744": {
    "doc": "Debug Logs",
    "title": "Exporting",
    "content": "Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/debug-logs.html#exporting",
    
    "relUrl": "/el-rGR/user/debug-logs.html#exporting"
  },"745": {
    "doc": "Debug Logs",
    "title": "Desktop",
    "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/debug-logs.html#desktop",
    
    "relUrl": "/el-rGR/user/debug-logs.html#desktop"
  },"746": {
    "doc": "Debug Logs",
    "title": "Related Topics",
    "content": ". | Help & In-App Docs — reading this documentation offline inside the app | Connections — if the problem is getting connected to your radio in the first place | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/debug-logs.html#related-topics",
    
    "relUrl": "/el-rGR/user/debug-logs.html#related-topics"
  },"747": {
    "doc": "Debug Logs",
    "title": "Debug Logs",
    "content": "When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/debug-logs.html",
    
    "relUrl": "/ro-rRO/user/debug-logs.html"
  },"748": {
    "doc": "Debug Logs",
    "title": "The two tabs",
    "content": "The Debug Panel has two tabs: . | Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior. | App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs. | . Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/debug-logs.html#the-two-tabs",
    
    "relUrl": "/ro-rRO/user/debug-logs.html#the-two-tabs"
  },"749": {
    "doc": "Debug Logs",
    "title": "Viewing app logs",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | Search — type in the search box to filter to matching lines. | Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown. | Refresh — the refresh icon re-reads the latest logs. | . Error and warning lines are tinted so problems stand out. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/debug-logs.html#viewing-app-logs",
    
    "relUrl": "/ro-rRO/user/debug-logs.html#viewing-app-logs"
  },"750": {
    "doc": "Debug Logs",
    "title": "Exporting",
    "content": "Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/debug-logs.html#exporting",
    
    "relUrl": "/ro-rRO/user/debug-logs.html#exporting"
  },"751": {
    "doc": "Debug Logs",
    "title": "Desktop",
    "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/debug-logs.html#desktop",
    
    "relUrl": "/ro-rRO/user/debug-logs.html#desktop"
  },"752": {
    "doc": "Debug Logs",
    "title": "Related Topics",
    "content": ". | Help & In-App Docs — reading this documentation offline inside the app | Connections — if the problem is getting connected to your radio in the first place | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/debug-logs.html#related-topics",
    
    "relUrl": "/ro-rRO/user/debug-logs.html#related-topics"
  },"753": {
    "doc": "Debug Logs",
    "title": "Debug Logs",
    "content": "When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/debug-logs.html",
    
    "relUrl": "/iw-rIL/user/debug-logs.html"
  },"754": {
    "doc": "Debug Logs",
    "title": "The two tabs",
    "content": "The Debug Panel has two tabs: . | Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior. | App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs. | . Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/debug-logs.html#the-two-tabs",
    
    "relUrl": "/iw-rIL/user/debug-logs.html#the-two-tabs"
  },"755": {
    "doc": "Debug Logs",
    "title": "Viewing app logs",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | Search — type in the search box to filter to matching lines. | Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown. | Refresh — the refresh icon re-reads the latest logs. | . Error and warning lines are tinted so problems stand out. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/debug-logs.html#viewing-app-logs",
    
    "relUrl": "/iw-rIL/user/debug-logs.html#viewing-app-logs"
  },"756": {
    "doc": "Debug Logs",
    "title": "Exporting",
    "content": "Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/debug-logs.html#exporting",
    
    "relUrl": "/iw-rIL/user/debug-logs.html#exporting"
  },"757": {
    "doc": "Debug Logs",
    "title": "Desktop",
    "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/debug-logs.html#desktop",
    
    "relUrl": "/iw-rIL/user/debug-logs.html#desktop"
  },"758": {
    "doc": "Debug Logs",
    "title": "Related Topics",
    "content": ". | Help & In-App Docs — reading this documentation offline inside the app | Connections — if the problem is getting connected to your radio in the first place | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/debug-logs.html#related-topics",
    
    "relUrl": "/iw-rIL/user/debug-logs.html#related-topics"
  },"759": {
    "doc": "Debug Logs",
    "title": "Debug Logs",
    "content": "When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/debug-logs.html",
    
    "relUrl": "/pt-rBR/user/debug-logs.html"
  },"760": {
    "doc": "Debug Logs",
    "title": "The two tabs",
    "content": "The Debug Panel has two tabs: . | Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior. | App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs. | . Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/debug-logs.html#the-two-tabs",
    
    "relUrl": "/pt-rBR/user/debug-logs.html#the-two-tabs"
  },"761": {
    "doc": "Debug Logs",
    "title": "Viewing app logs",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | Search — type in the search box to filter to matching lines. | Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown. | Refresh — the refresh icon re-reads the latest logs. | . Error and warning lines are tinted so problems stand out. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/debug-logs.html#viewing-app-logs",
    
    "relUrl": "/pt-rBR/user/debug-logs.html#viewing-app-logs"
  },"762": {
    "doc": "Debug Logs",
    "title": "Exporting",
    "content": "Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/debug-logs.html#exporting",
    
    "relUrl": "/pt-rBR/user/debug-logs.html#exporting"
  },"763": {
    "doc": "Debug Logs",
    "title": "Desktop",
    "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/debug-logs.html#desktop",
    
    "relUrl": "/pt-rBR/user/debug-logs.html#desktop"
  },"764": {
    "doc": "Debug Logs",
    "title": "Related Topics",
    "content": ". | Help & In-App Docs — reading this documentation offline inside the app | Connections — if the problem is getting connected to your radio in the first place | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/debug-logs.html#related-topics",
    
    "relUrl": "/pt-rBR/user/debug-logs.html#related-topics"
  },"765": {
    "doc": "Debug Logs",
    "title": "Debug Logs",
    "content": "When something misbehaves, the app’s debug logs are the single most useful thing you can attach to a bug report. Meshtastic can capture them for you, from inside the app — you don’t need adb or any desktop tooling to collect them. Open the Debug Panel from Settings → Advanced → Debug Panel. If you’re filing an issue, export your logs (see Exporting) and attach the .txt file to your report on the Meshtastic-Android issue tracker. A log capture that covers the moment the problem happened turns “it doesn’t work” into something a developer can actually track down. ",
    "url": "/Meshtastic-Android/main/en/user/debug-logs.html",
    
    "relUrl": "/en/user/debug-logs.html"
  },"766": {
    "doc": "Debug Logs",
    "title": "The two tabs",
    "content": "The Debug Panel has two tabs: . | Packets — the decoded mesh traffic your radio has sent and received (protocol-level messages). Useful for diagnosing mesh and routing behavior. | App logs — the app’s own diagnostic log (Android logcat), including warnings, errors, and stack traces from the app itself. This is usually what a bug report needs. | . Each tab has its own export button and produces its own file, so you can grab whichever is relevant — or both. ",
    "url": "/Meshtastic-Android/main/en/user/debug-logs.html#the-two-tabs",
    
    "relUrl": "/en/user/debug-logs.html#the-two-tabs"
  },"767": {
    "doc": "Debug Logs",
    "title": "Viewing app logs",
    "content": "The App logs tab shows the most recent log lines from this app only — never other apps on your phone. | Search — type in the search box to filter to matching lines. | Level filter — the V / D / I / W / E chips toggle Verbose, Debug, Info, Warn, and Error lines. Tap a level to hide it; tap again to bring it back. Fatal lines are always shown. | Refresh — the refresh icon re-reads the latest logs. | . Error and warning lines are tinted so problems stand out. ",
    "url": "/Meshtastic-Android/main/en/user/debug-logs.html#viewing-app-logs",
    
    "relUrl": "/en/user/debug-logs.html#viewing-app-logs"
  },"768": {
    "doc": "Debug Logs",
    "title": "Exporting",
    "content": "Tap the download icon to save the current logs to a file. The app first shows a warning about what the file contains — confirm it, then choose where the file goes through the system file picker. The file is named with a timestamp (for example meshtastic_logcat_20260701_143312.txt) so repeated exports never overwrite each other. The same warning guards the Packets tab export. Attach that file to your GitHub issue. 🔒 Privacy: Exports automatically redact private keys, admin keys, session passkeys, and channel PSKs, and suppress raw packet bytes. Everything else stays — the file can contain your message text, precise locations, and node details. Read it before sharing it publicly, and share privately if you have any doubt. ",
    "url": "/Meshtastic-Android/main/en/user/debug-logs.html#exporting",
    
    "relUrl": "/en/user/debug-logs.html#exporting"
  },"769": {
    "doc": "Debug Logs",
    "title": "Desktop",
    "content": "The desktop app has no system logcat, so the App logs tab shows the app’s own captured log output instead. Search, filtering, and export work the same way. ",
    "url": "/Meshtastic-Android/main/en/user/debug-logs.html#desktop",
    
    "relUrl": "/en/user/debug-logs.html#desktop"
  },"770": {
    "doc": "Debug Logs",
    "title": "Related Topics",
    "content": ". | Help & In-App Docs — reading this documentation offline inside the app | Connections — if the problem is getting connected to your radio in the first place | . ",
    "url": "/Meshtastic-Android/main/en/user/debug-logs.html#related-topics",
    
    "relUrl": "/en/user/debug-logs.html#related-topics"
  },"771": {
    "doc": "Desktop App",
    "title": "Desktop App",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/desktop.html",
    
    "relUrl": "/sk-rSK/user/desktop.html"
  },"772": {
    "doc": "Desktop App",
    "title": "Installation",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from the releases page | Or build from source | . Windows . | Download the .msi or .exe installer from the releases page | Or build from source | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/desktop.html#installation",
    
    "relUrl": "/sk-rSK/user/desktop.html#installation"
  },"773": {
    "doc": "Desktop App",
    "title": "Connecting Your Radio",
    "content": "USB Serial (Primary) . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . For network-connected radios: . | Enter the radio’s IP address and port (default: 4403). | Click Connect. | . Bluetooth (BLE) . Bluetooth Low Energy is supported on desktop via the Kable library: . | Ensure your system has a Bluetooth adapter. The app scans for nearby Meshtastic radios automatically. | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/desktop.html#connecting-your-radio",
    
    "relUrl": "/sk-rSK/user/desktop.html#connecting-your-radio"
  },"774": {
    "doc": "Desktop App",
    "title": "Feature Parity",
    "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Mapa | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | Site Planner | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | Nastavenia | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | AI Assistant (Chirpy) | ✓* | ✗ | Google flavor Android only | . | App Functions (system AI) | ✓† | ✗ | Google flavor Android only | . *Chirpy AI requires Android 14+ on Google flavor builds with supported hardware. †App Functions exposes app actions to the Android system AI on Google flavor builds. See App Functions. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/desktop.html#feature-parity",
    
    "relUrl": "/sk-rSK/user/desktop.html#feature-parity"
  },"775": {
    "doc": "Desktop App",
    "title": "UI Differences",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. Keyboard Shortcuts . Shortcuts use ⌘ (Command) on macOS and Ctrl on Windows and Linux. (The Super / Windows key is not bound.) . | Shortcut | Action | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | Open Settings | . | ⌘/Ctrl+1 | Switch to Messages tab | . | ⌘/Ctrl+2 | Switch to Nodes tab | . | ⌘/Ctrl+3 | Switch to Map tab | . | ⌘/Ctrl+4 | Switch to Connect tab | . | ⌘/Ctrl+/ | Open About | . Window & System Tray . | Window resizing — responsive layout adapts to window dimensions | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | 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. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/desktop.html#ui-differences",
    
    "relUrl": "/sk-rSK/user/desktop.html#ui-differences"
  },"776": {
    "doc": "Desktop App",
    "title": "Built-in Documentation Browser",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. The browser supports full-text search across all documentation: . Individual doc pages render with full formatting: . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/desktop.html#built-in-documentation-browser",
    
    "relUrl": "/sk-rSK/user/desktop.html#built-in-documentation-browser"
  },"777": {
    "doc": "Desktop App",
    "title": "Building from Source",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Requirements: . | JDK 25 (Gradle can provision the toolchain itself via foojay) | No Android SDK required for desktop-only builds | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/desktop.html#building-from-source",
    
    "relUrl": "/sk-rSK/user/desktop.html#building-from-source"
  },"778": {
    "doc": "Desktop App",
    "title": "Known Limitations",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | 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) | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/desktop.html#known-limitations",
    
    "relUrl": "/sk-rSK/user/desktop.html#known-limitations"
  },"779": {
    "doc": "Desktop App",
    "title": "Related Topics",
    "content": ". | Connections — connection methods overview | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/desktop.html#related-topics",
    
    "relUrl": "/sk-rSK/user/desktop.html#related-topics"
  },"780": {
    "doc": "Desktop App",
    "title": "Desktop App",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/desktop.html",
    
    "relUrl": "/be-rBY/user/desktop.html"
  },"781": {
    "doc": "Desktop App",
    "title": "Установка",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from the releases page | Or build from source | . Windows . | Download the .msi or .exe installer from the releases page | Or build from source | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/desktop.html#%D1%83%D1%81%D1%82%D0%B0%D0%BD%D0%BE%D0%B2%D0%BA%D0%B0",
    
    "relUrl": "/be-rBY/user/desktop.html#установка"
  },"782": {
    "doc": "Desktop App",
    "title": "Connecting Your Radio",
    "content": "USB Serial (Primary) . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . For network-connected radios: . | Enter the radio’s IP address and port (default: 4403). | Click Connect. | . Bluetooth (BLE) . Bluetooth Low Energy is supported on desktop via the Kable library: . | Ensure your system has a Bluetooth adapter. The app scans for nearby Meshtastic radios automatically. | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/desktop.html#connecting-your-radio",
    
    "relUrl": "/be-rBY/user/desktop.html#connecting-your-radio"
  },"783": {
    "doc": "Desktop App",
    "title": "Feature Parity",
    "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Map | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | Site Planner | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | Налады | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | AI Assistant (Chirpy) | ✓* | ✗ | Google flavor Android only | . | App Functions (system AI) | ✓† | ✗ | Google flavor Android only | . *Chirpy AI requires Android 14+ on Google flavor builds with supported hardware. †App Functions exposes app actions to the Android system AI on Google flavor builds. See App Functions. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/desktop.html#feature-parity",
    
    "relUrl": "/be-rBY/user/desktop.html#feature-parity"
  },"784": {
    "doc": "Desktop App",
    "title": "UI Differences",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. Keyboard Shortcuts . Shortcuts use ⌘ (Command) on macOS and Ctrl on Windows and Linux. (The Super / Windows key is not bound.) . | Shortcut | Action | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | Open Settings | . | ⌘/Ctrl+1 | Switch to Messages tab | . | ⌘/Ctrl+2 | Switch to Nodes tab | . | ⌘/Ctrl+3 | Switch to Map tab | . | ⌘/Ctrl+4 | Switch to Connect tab | . | ⌘/Ctrl+/ | Open About | . Window & System Tray . | Window resizing — responsive layout adapts to window dimensions | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | 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. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/desktop.html#ui-differences",
    
    "relUrl": "/be-rBY/user/desktop.html#ui-differences"
  },"785": {
    "doc": "Desktop App",
    "title": "Built-in Documentation Browser",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. The browser supports full-text search across all documentation: . Individual doc pages render with full formatting: . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/desktop.html#built-in-documentation-browser",
    
    "relUrl": "/be-rBY/user/desktop.html#built-in-documentation-browser"
  },"786": {
    "doc": "Desktop App",
    "title": "Building from Source",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Requirements: . | JDK 25 (Gradle can provision the toolchain itself via foojay) | No Android SDK required for desktop-only builds | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/desktop.html#building-from-source",
    
    "relUrl": "/be-rBY/user/desktop.html#building-from-source"
  },"787": {
    "doc": "Desktop App",
    "title": "Known Limitations",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | 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) | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/desktop.html#known-limitations",
    
    "relUrl": "/be-rBY/user/desktop.html#known-limitations"
  },"788": {
    "doc": "Desktop App",
    "title": "Related Topics",
    "content": ". | Connections — connection methods overview | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/desktop.html#related-topics",
    
    "relUrl": "/be-rBY/user/desktop.html#related-topics"
  },"789": {
    "doc": "Desktop App",
    "title": "Desktop App",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/desktop.html",
    
    "relUrl": "/it-rIT/user/desktop.html"
  },"790": {
    "doc": "Desktop App",
    "title": "Installazione",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from the releases page | Or build from source | . Windows . | Download the .msi or .exe installer from the releases page | Or build from source | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/desktop.html#installazione",
    
    "relUrl": "/it-rIT/user/desktop.html#installazione"
  },"791": {
    "doc": "Desktop App",
    "title": "Connecting Your Radio",
    "content": "USB Serial (Primary) . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . For network-connected radios: . | Enter the radio’s IP address and port (default: 4403). | Click Connect. | . Bluetooth (BLE) . Bluetooth Low Energy is supported on desktop via the Kable library: . | Ensure your system has a Bluetooth adapter. The app scans for nearby Meshtastic radios automatically. | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/desktop.html#connecting-your-radio",
    
    "relUrl": "/it-rIT/user/desktop.html#connecting-your-radio"
  },"792": {
    "doc": "Desktop App",
    "title": "Feature Parity",
    "content": "| Feature | Android | Desktop | Note | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Mappa | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | Site Planner | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | Impostazioni | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Aggiornamento Firmware | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | AI Assistant (Chirpy) | ✓* | ✗ | Google flavor Android only | . | App Functions (system AI) | ✓† | ✗ | Google flavor Android only | . *Chirpy AI requires Android 14+ on Google flavor builds with supported hardware. †App Functions exposes app actions to the Android system AI on Google flavor builds. See App Functions. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/desktop.html#feature-parity",
    
    "relUrl": "/it-rIT/user/desktop.html#feature-parity"
  },"793": {
    "doc": "Desktop App",
    "title": "UI Differences",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. Keyboard Shortcuts . Shortcuts use ⌘ (Command) on macOS and Ctrl on Windows and Linux. (The Super / Windows key is not bound.) . | Shortcut | Action | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | Open Settings | . | ⌘/Ctrl+1 | Switch to Messages tab | . | ⌘/Ctrl+2 | Switch to Nodes tab | . | ⌘/Ctrl+3 | Switch to Map tab | . | ⌘/Ctrl+4 | Switch to Connect tab | . | ⌘/Ctrl+/ | Open About | . Window & System Tray . | Window resizing — responsive layout adapts to window dimensions | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | 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. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/desktop.html#ui-differences",
    
    "relUrl": "/it-rIT/user/desktop.html#ui-differences"
  },"794": {
    "doc": "Desktop App",
    "title": "Built-in Documentation Browser",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. The browser supports full-text search across all documentation: . Individual doc pages render with full formatting: . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/desktop.html#built-in-documentation-browser",
    
    "relUrl": "/it-rIT/user/desktop.html#built-in-documentation-browser"
  },"795": {
    "doc": "Desktop App",
    "title": "Building from Source",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Requisiti: . | JDK 25 (Gradle can provision the toolchain itself via foojay) | No Android SDK required for desktop-only builds | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/desktop.html#building-from-source",
    
    "relUrl": "/it-rIT/user/desktop.html#building-from-source"
  },"796": {
    "doc": "Desktop App",
    "title": "Limitazioni conosciute",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | 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) | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/desktop.html#limitazioni-conosciute",
    
    "relUrl": "/it-rIT/user/desktop.html#limitazioni-conosciute"
  },"797": {
    "doc": "Desktop App",
    "title": "Related Topics",
    "content": ". | Connections — connection methods overview | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/desktop.html#related-topics",
    
    "relUrl": "/it-rIT/user/desktop.html#related-topics"
  },"798": {
    "doc": "Desktop App",
    "title": "Desktop App",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/es-rES/user/desktop.html",
    
    "relUrl": "/es-rES/user/desktop.html"
  },"799": {
    "doc": "Desktop App",
    "title": "Installation",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from the releases page | Or build from source | . Windows . | Download the .msi or .exe installer from the releases page | Or build from source | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/desktop.html#installation",
    
    "relUrl": "/es-rES/user/desktop.html#installation"
  },"800": {
    "doc": "Desktop App",
    "title": "Connecting Your Radio",
    "content": "USB Serial (Primary) . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . For network-connected radios: . | Enter the radio’s IP address and port (default: 4403). | Click Connect. | . Bluetooth (BLE) . Bluetooth Low Energy is supported on desktop via the Kable library: . | Ensure your system has a Bluetooth adapter. The app scans for nearby Meshtastic radios automatically. | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/desktop.html#connecting-your-radio",
    
    "relUrl": "/es-rES/user/desktop.html#connecting-your-radio"
  },"801": {
    "doc": "Desktop App",
    "title": "Feature Parity",
    "content": "| Feature | Android | Desktop | Notas | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Mapa | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | Site Planner | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | Ajustes | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Actualización de firmware | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | AI Assistant (Chirpy) | ✓* | ✗ | Google flavor Android only | . | App Functions (system AI) | ✓† | ✗ | Google flavor Android only | . *Chirpy AI requires Android 14+ on Google flavor builds with supported hardware. †App Functions exposes app actions to the Android system AI on Google flavor builds. See App Functions. ",
    "url": "/Meshtastic-Android/main/es-rES/user/desktop.html#feature-parity",
    
    "relUrl": "/es-rES/user/desktop.html#feature-parity"
  },"802": {
    "doc": "Desktop App",
    "title": "UI Differences",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. Keyboard Shortcuts . Shortcuts use ⌘ (Command) on macOS and Ctrl on Windows and Linux. (The Super / Windows key is not bound.) . | Shortcut | Action | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | Open Settings | . | ⌘/Ctrl+1 | Switch to Messages tab | . | ⌘/Ctrl+2 | Switch to Nodes tab | . | ⌘/Ctrl+3 | Switch to Map tab | . | ⌘/Ctrl+4 | Switch to Connect tab | . | ⌘/Ctrl+/ | Open About | . Window & System Tray . | Window resizing — responsive layout adapts to window dimensions | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | 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. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/es-rES/user/desktop.html#ui-differences",
    
    "relUrl": "/es-rES/user/desktop.html#ui-differences"
  },"803": {
    "doc": "Desktop App",
    "title": "Built-in Documentation Browser",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. The browser supports full-text search across all documentation: . Individual doc pages render with full formatting: . ",
    "url": "/Meshtastic-Android/main/es-rES/user/desktop.html#built-in-documentation-browser",
    
    "relUrl": "/es-rES/user/desktop.html#built-in-documentation-browser"
  },"804": {
    "doc": "Desktop App",
    "title": "Building from Source",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Requirements: . | JDK 25 (Gradle can provision the toolchain itself via foojay) | No Android SDK required for desktop-only builds | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/desktop.html#building-from-source",
    
    "relUrl": "/es-rES/user/desktop.html#building-from-source"
  },"805": {
    "doc": "Desktop App",
    "title": "Known Limitations",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | 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) | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/desktop.html#known-limitations",
    
    "relUrl": "/es-rES/user/desktop.html#known-limitations"
  },"806": {
    "doc": "Desktop App",
    "title": "Related Topics",
    "content": ". | Connections — connection methods overview | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/desktop.html#related-topics",
    
    "relUrl": "/es-rES/user/desktop.html#related-topics"
  },"807": {
    "doc": "Desktop App",
    "title": "Desktop App",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/desktop.html",
    
    "relUrl": "/sl-rSI/user/desktop.html"
  },"808": {
    "doc": "Desktop App",
    "title": "Installation",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from the releases page | Or build from source | . Windows . | Download the .msi or .exe installer from the releases page | Or build from source | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/desktop.html#installation",
    
    "relUrl": "/sl-rSI/user/desktop.html#installation"
  },"809": {
    "doc": "Desktop App",
    "title": "Connecting Your Radio",
    "content": "USB Serial (Primary) . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . For network-connected radios: . | Enter the radio’s IP address and port (default: 4403). | Click Connect. | . Bluetooth (BLE) . Bluetooth Low Energy is supported on desktop via the Kable library: . | Ensure your system has a Bluetooth adapter. The app scans for nearby Meshtastic radios automatically. | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/desktop.html#connecting-your-radio",
    
    "relUrl": "/sl-rSI/user/desktop.html#connecting-your-radio"
  },"810": {
    "doc": "Desktop App",
    "title": "Feature Parity",
    "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Map | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | Site Planner | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | Settings | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | AI Assistant (Chirpy) | ✓* | ✗ | Google flavor Android only | . | App Functions (system AI) | ✓† | ✗ | Google flavor Android only | . *Chirpy AI requires Android 14+ on Google flavor builds with supported hardware. †App Functions exposes app actions to the Android system AI on Google flavor builds. See App Functions. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/desktop.html#feature-parity",
    
    "relUrl": "/sl-rSI/user/desktop.html#feature-parity"
  },"811": {
    "doc": "Desktop App",
    "title": "UI Differences",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. Keyboard Shortcuts . Shortcuts use ⌘ (Command) on macOS and Ctrl on Windows and Linux. (The Super / Windows key is not bound.) . | Shortcut | Action | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | Open Settings | . | ⌘/Ctrl+1 | Switch to Messages tab | . | ⌘/Ctrl+2 | Switch to Nodes tab | . | ⌘/Ctrl+3 | Switch to Map tab | . | ⌘/Ctrl+4 | Switch to Connect tab | . | ⌘/Ctrl+/ | Open About | . Window & System Tray . | Window resizing — responsive layout adapts to window dimensions | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | 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. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/desktop.html#ui-differences",
    
    "relUrl": "/sl-rSI/user/desktop.html#ui-differences"
  },"812": {
    "doc": "Desktop App",
    "title": "Built-in Documentation Browser",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. The browser supports full-text search across all documentation: . Individual doc pages render with full formatting: . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/desktop.html#built-in-documentation-browser",
    
    "relUrl": "/sl-rSI/user/desktop.html#built-in-documentation-browser"
  },"813": {
    "doc": "Desktop App",
    "title": "Building from Source",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Requirements: . | JDK 25 (Gradle can provision the toolchain itself via foojay) | No Android SDK required for desktop-only builds | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/desktop.html#building-from-source",
    
    "relUrl": "/sl-rSI/user/desktop.html#building-from-source"
  },"814": {
    "doc": "Desktop App",
    "title": "Known Limitations",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | 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) | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/desktop.html#known-limitations",
    
    "relUrl": "/sl-rSI/user/desktop.html#known-limitations"
  },"815": {
    "doc": "Desktop App",
    "title": "Related Topics",
    "content": ". | Connections — connection methods overview | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/desktop.html#related-topics",
    
    "relUrl": "/sl-rSI/user/desktop.html#related-topics"
  },"816": {
    "doc": "Desktop App",
    "title": "Desktop App",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/desktop.html",
    
    "relUrl": "/no-rNO/user/desktop.html"
  },"817": {
    "doc": "Desktop App",
    "title": "Installation",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from the releases page | Or build from source | . Windows . | Download the .msi or .exe installer from the releases page | Or build from source | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/desktop.html#installation",
    
    "relUrl": "/no-rNO/user/desktop.html#installation"
  },"818": {
    "doc": "Desktop App",
    "title": "Connecting Your Radio",
    "content": "USB Serial (Primary) . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . For network-connected radios: . | Enter the radio’s IP address and port (default: 4403). | Click Connect. | . Bluetooth (BLE) . Bluetooth Low Energy is supported on desktop via the Kable library: . | Ensure your system has a Bluetooth adapter. The app scans for nearby Meshtastic radios automatically. | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/desktop.html#connecting-your-radio",
    
    "relUrl": "/no-rNO/user/desktop.html#connecting-your-radio"
  },"819": {
    "doc": "Desktop App",
    "title": "Feature Parity",
    "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Map | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | Site Planner | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | Settings | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | AI Assistant (Chirpy) | ✓* | ✗ | Google flavor Android only | . | App Functions (system AI) | ✓† | ✗ | Google flavor Android only | . *Chirpy AI requires Android 14+ on Google flavor builds with supported hardware. †App Functions exposes app actions to the Android system AI on Google flavor builds. See App Functions. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/desktop.html#feature-parity",
    
    "relUrl": "/no-rNO/user/desktop.html#feature-parity"
  },"820": {
    "doc": "Desktop App",
    "title": "UI Differences",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. Keyboard Shortcuts . Shortcuts use ⌘ (Command) on macOS and Ctrl on Windows and Linux. (The Super / Windows key is not bound.) . | Shortcut | Action | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | Open Settings | . | ⌘/Ctrl+1 | Switch to Messages tab | . | ⌘/Ctrl+2 | Switch to Nodes tab | . | ⌘/Ctrl+3 | Switch to Map tab | . | ⌘/Ctrl+4 | Switch to Connect tab | . | ⌘/Ctrl+/ | Open About | . Window & System Tray . | Window resizing — responsive layout adapts to window dimensions | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | 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. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/desktop.html#ui-differences",
    
    "relUrl": "/no-rNO/user/desktop.html#ui-differences"
  },"821": {
    "doc": "Desktop App",
    "title": "Built-in Documentation Browser",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. The browser supports full-text search across all documentation: . Individual doc pages render with full formatting: . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/desktop.html#built-in-documentation-browser",
    
    "relUrl": "/no-rNO/user/desktop.html#built-in-documentation-browser"
  },"822": {
    "doc": "Desktop App",
    "title": "Building from Source",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Requirements: . | JDK 25 (Gradle can provision the toolchain itself via foojay) | No Android SDK required for desktop-only builds | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/desktop.html#building-from-source",
    
    "relUrl": "/no-rNO/user/desktop.html#building-from-source"
  },"823": {
    "doc": "Desktop App",
    "title": "Known Limitations",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | 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) | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/desktop.html#known-limitations",
    
    "relUrl": "/no-rNO/user/desktop.html#known-limitations"
  },"824": {
    "doc": "Desktop App",
    "title": "Related Topics",
    "content": ". | Connections — connection methods overview | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/desktop.html#related-topics",
    
    "relUrl": "/no-rNO/user/desktop.html#related-topics"
  },"825": {
    "doc": "Desktop App",
    "title": "Desktop App",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/desktop.html",
    
    "relUrl": "/hu-rHU/user/desktop.html"
  },"826": {
    "doc": "Desktop App",
    "title": "Installation",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from the releases page | Or build from source | . Windows . | Download the .msi or .exe installer from the releases page | Or build from source | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/desktop.html#installation",
    
    "relUrl": "/hu-rHU/user/desktop.html#installation"
  },"827": {
    "doc": "Desktop App",
    "title": "Connecting Your Radio",
    "content": "USB Serial (Primary) . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . For network-connected radios: . | Enter the radio’s IP address and port (default: 4403). | Click Connect. | . Bluetooth (BLE) . Bluetooth Low Energy is supported on desktop via the Kable library: . | Ensure your system has a Bluetooth adapter. The app scans for nearby Meshtastic radios automatically. | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/desktop.html#connecting-your-radio",
    
    "relUrl": "/hu-rHU/user/desktop.html#connecting-your-radio"
  },"828": {
    "doc": "Desktop App",
    "title": "Feature Parity",
    "content": "| Feature | Android | Desktop | Jegyzetek | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Térkép | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | Site Planner | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | Beállítások | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | AI Assistant (Chirpy) | ✓* | ✗ | Google flavor Android only | . | App Functions (system AI) | ✓† | ✗ | Google flavor Android only | . *Chirpy AI requires Android 14+ on Google flavor builds with supported hardware. †App Functions exposes app actions to the Android system AI on Google flavor builds. See App Functions. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/desktop.html#feature-parity",
    
    "relUrl": "/hu-rHU/user/desktop.html#feature-parity"
  },"829": {
    "doc": "Desktop App",
    "title": "UI Differences",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. Keyboard Shortcuts . Shortcuts use ⌘ (Command) on macOS and Ctrl on Windows and Linux. (The Super / Windows key is not bound.) . | Shortcut | Action | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | Open Settings | . | ⌘/Ctrl+1 | Switch to Messages tab | . | ⌘/Ctrl+2 | Switch to Nodes tab | . | ⌘/Ctrl+3 | Switch to Map tab | . | ⌘/Ctrl+4 | Switch to Connect tab | . | ⌘/Ctrl+/ | Open About | . Window & System Tray . | Window resizing — responsive layout adapts to window dimensions | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | 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. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/desktop.html#ui-differences",
    
    "relUrl": "/hu-rHU/user/desktop.html#ui-differences"
  },"830": {
    "doc": "Desktop App",
    "title": "Built-in Documentation Browser",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. The browser supports full-text search across all documentation: . Individual doc pages render with full formatting: . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/desktop.html#built-in-documentation-browser",
    
    "relUrl": "/hu-rHU/user/desktop.html#built-in-documentation-browser"
  },"831": {
    "doc": "Desktop App",
    "title": "Building from Source",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Requirements: . | JDK 25 (Gradle can provision the toolchain itself via foojay) | No Android SDK required for desktop-only builds | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/desktop.html#building-from-source",
    
    "relUrl": "/hu-rHU/user/desktop.html#building-from-source"
  },"832": {
    "doc": "Desktop App",
    "title": "Known Limitations",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | 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) | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/desktop.html#known-limitations",
    
    "relUrl": "/hu-rHU/user/desktop.html#known-limitations"
  },"833": {
    "doc": "Desktop App",
    "title": "Related Topics",
    "content": ". | Connections — connection methods overview | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/desktop.html#related-topics",
    
    "relUrl": "/hu-rHU/user/desktop.html#related-topics"
  },"834": {
    "doc": "Настольное приложение",
    "title": "Настольное приложение",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/desktop.html",
    
    "relUrl": "/ru-rRU/user/desktop.html"
  },"835": {
    "doc": "Настольное приложение",
    "title": "Установка",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | Или соберите из исходного кода с помощью ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from the releases page | Или соберите из исходных кодов | . Windows . | Download the .msi or .exe installer from the releases page | Или соберите из исходных кодов | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/desktop.html#%D1%83%D1%81%D1%82%D0%B0%D0%BD%D0%BE%D0%B2%D0%BA%D0%B0",
    
    "relUrl": "/ru-rRU/user/desktop.html#установка"
  },"836": {
    "doc": "Настольное приложение",
    "title": "Подключение твоей радиостанции",
    "content": "Последовательная USB (Основной) . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . Для радиостанций, подключённых по сети: . | Введите IP-адрес и порт радиостанции (по умолчанию: 4403). | Нажмите “Подключиться”. | . Bluetooth (BLE) . Bluetooth Low Energy is supported on desktop via the Kable library: . | Убедитесь, что ваша система оснащена Bluetooth-адаптером. Приложение автоматически сканирует находящиеся поблизости радиостанции Meshtastic. | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/desktop.html#%D0%BF%D0%BE%D0%B4%D0%BA%D0%BB%D1%8E%D1%87%D0%B5%D0%BD%D0%B8%D0%B5-%D1%82%D0%B2%D0%BE%D0%B5%D0%B9-%D1%80%D0%B0%D0%B4%D0%B8%D0%BE%D1%81%D1%82%D0%B0%D0%BD%D1%86%D0%B8%D0%B8",
    
    "relUrl": "/ru-rRU/user/desktop.html#подключение-твоей-радиостанции"
  },"837": {
    "doc": "Настольное приложение",
    "title": "Паритет функций",
    "content": "| Функция | Android | Desktop | Заметки | . | Обмен сообщениями | ✓ | ✓ | Полное равенство | . | Список узлов | ✓ | ✓ | Полное равенство | . | Карта | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | Планировщик участков | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | Настройки | ✓ | ✓ | Полное равенство | . | Bluetooth (BLE) | ✓ | ✓ | Через Kable в настольном приложении | . | Обновление прошивки | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | Уведомления | ✓ | ✓ | Системные уведомления | . | Виджеты | ✓ | ✗ | Только Android | . | AI-ассистент (Chirpy) | ✓* | ✗ | Только в Google-версии для Android | . | Функции приложения (системный ИИ) | ✓† | ✗ | Только в Google-версии для Android | . *Chirpy AI требует Android 14+ в Google-версии на поддерживаемом оборудовании. †Функции приложения предоставляют действия приложения системному ИИ Android в Google-версии. См. Функции приложения. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/desktop.html#%D0%BF%D0%B0%D1%80%D0%B8%D1%82%D0%B5%D1%82-%D1%84%D1%83%D0%BD%D0%BA%D1%86%D0%B8%D0%B9",
    
    "relUrl": "/ru-rRU/user/desktop.html#паритет-функций"
  },"838": {
    "doc": "Настольное приложение",
    "title": "Различия интерфейса",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. Сочетания клавиш . Сочетания клавиш используют ⌘ (Command) на macOS и Ctrl на Windows и Linux. (Клавиша Super / Windows не используется.) . | Сочетание | Действие | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | Открыть настройки | . | ⌘/Ctrl+1 | Перейти во вкладку “Сообщения” | . | ⌘/Ctrl+2 | Перейти во вкладку “Узлы” | . | ⌘/Ctrl+3 | Перейти во вкладку “Карта” | . | ⌘/Ctrl+4 | Перейти во вкладку “Подключение” | . | ⌘/Ctrl+/ | Открыть “О программе” | . Окно и системный трей . | Изменение размера окна — адаптивный макет подстраивается под размеры окна | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | Меню трея — щёлкните правой кнопкой мыши по значку в трее, чтобы показать окно или выйти | Взаимодействие с мышью — состояния при наведении и стандартная настольная навигация | . Настройки уведомлений . The desktop app provides in-app toggles for controlling which notifications are shown. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/desktop.html#%D1%80%D0%B0%D0%B7%D0%BB%D0%B8%D1%87%D0%B8%D1%8F-%D0%B8%D0%BD%D1%82%D0%B5%D1%80%D1%84%D0%B5%D0%B9%D1%81%D0%B0",
    
    "relUrl": "/ru-rRU/user/desktop.html#различия-интерфейса"
  },"839": {
    "doc": "Настольное приложение",
    "title": "Встроенный браузер документации",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. Браузер поддерживает полнотекстовый поиск по всей документации: . Отдельные страницы документации отображаются с полным форматированием: . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/desktop.html#%D0%B2%D1%81%D1%82%D1%80%D0%BE%D0%B5%D0%BD%D0%BD%D1%8B%D0%B9-%D0%B1%D1%80%D0%B0%D1%83%D0%B7%D0%B5%D1%80-%D0%B4%D0%BE%D0%BA%D1%83%D0%BC%D0%B5%D0%BD%D1%82%D0%B0%D1%86%D0%B8%D0%B8",
    
    "relUrl": "/ru-rRU/user/desktop.html#встроенный-браузер-документации"
  },"840": {
    "doc": "Настольное приложение",
    "title": "Сборка из исходного кода",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Требования: . | JDK 25 (Gradle can provision the toolchain itself via foojay) | Для сборки только настольной версии Android SDK не требуется | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/desktop.html#%D1%81%D0%B1%D0%BE%D1%80%D0%BA%D0%B0-%D0%B8%D0%B7-%D0%B8%D1%81%D1%85%D0%BE%D0%B4%D0%BD%D0%BE%D0%B3%D0%BE-%D0%BA%D0%BE%D0%B4%D0%B0",
    
    "relUrl": "/ru-rRU/user/desktop.html#сборка-из-исходного-кода"
  },"841": {
    "doc": "Настольное приложение",
    "title": "Известные ограничения",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | Некоторые специфичные для Android функции (виджеты, отдельные каналы уведомлений) недоступны | Производительность может варьироваться на маломощном оборудовании при запуске Compose Desktop | BLE-связывание пока не поддерживается в настольном приложении (сопряжение работает без связывания) | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/desktop.html#%D0%B8%D0%B7%D0%B2%D0%B5%D1%81%D1%82%D0%BD%D1%8B%D0%B5-%D0%BE%D0%B3%D1%80%D0%B0%D0%BD%D0%B8%D1%87%D0%B5%D0%BD%D0%B8%D1%8F",
    
    "relUrl": "/ru-rRU/user/desktop.html#известные-ограничения"
  },"842": {
    "doc": "Настольное приложение",
    "title": "Связанные темы",
    "content": ". | Подключения — обзор методов подключения | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/desktop.html#%D1%81%D0%B2%D1%8F%D0%B7%D0%B0%D0%BD%D0%BD%D1%8B%D0%B5-%D1%82%D0%B5%D0%BC%D1%8B",
    
    "relUrl": "/ru-rRU/user/desktop.html#связанные-темы"
  },"843": {
    "doc": "Desktop App",
    "title": "Desktop App",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/desktop.html",
    
    "relUrl": "/cs-rCZ/user/desktop.html"
  },"844": {
    "doc": "Desktop App",
    "title": "Installation",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from the releases page | Or build from source | . Windows . | Download the .msi or .exe installer from the releases page | Or build from source | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/desktop.html#installation",
    
    "relUrl": "/cs-rCZ/user/desktop.html#installation"
  },"845": {
    "doc": "Desktop App",
    "title": "Connecting Your Radio",
    "content": "USB Serial (Primary) . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . For network-connected radios: . | Enter the radio’s IP address and port (default: 4403). | Click Connect. | . Bluetooth (BLE) . Bluetooth Low Energy is supported on desktop via the Kable library: . | Ensure your system has a Bluetooth adapter. The app scans for nearby Meshtastic radios automatically. | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/desktop.html#connecting-your-radio",
    
    "relUrl": "/cs-rCZ/user/desktop.html#connecting-your-radio"
  },"846": {
    "doc": "Desktop App",
    "title": "Feature Parity",
    "content": "| Feature | Android | Desktop | Poznámka | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Mapa | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | Plánovač mesh sítě | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | Nastavení | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Aktualizace firmware | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | AI Assistant (Chirpy) | ✓* | ✗ | Google flavor Android only | . | App Functions (system AI) | ✓† | ✗ | Google flavor Android only | . *Chirpy AI requires Android 14+ on Google flavor builds with supported hardware. †App Functions exposes app actions to the Android system AI on Google flavor builds. See App Functions. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/desktop.html#feature-parity",
    
    "relUrl": "/cs-rCZ/user/desktop.html#feature-parity"
  },"847": {
    "doc": "Desktop App",
    "title": "UI Differences",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. Keyboard Shortcuts . Shortcuts use ⌘ (Command) on macOS and Ctrl on Windows and Linux. (The Super / Windows key is not bound.) . | Shortcut | Action | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | Open Settings | . | ⌘/Ctrl+1 | Switch to Messages tab | . | ⌘/Ctrl+2 | Switch to Nodes tab | . | ⌘/Ctrl+3 | Switch to Map tab | . | ⌘/Ctrl+4 | Switch to Connect tab | . | ⌘/Ctrl+/ | Open About | . Window & System Tray . | Window resizing — responsive layout adapts to window dimensions | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | 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. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/desktop.html#ui-differences",
    
    "relUrl": "/cs-rCZ/user/desktop.html#ui-differences"
  },"848": {
    "doc": "Desktop App",
    "title": "Built-in Documentation Browser",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. The browser supports full-text search across all documentation: . Individual doc pages render with full formatting: . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/desktop.html#built-in-documentation-browser",
    
    "relUrl": "/cs-rCZ/user/desktop.html#built-in-documentation-browser"
  },"849": {
    "doc": "Desktop App",
    "title": "Building from Source",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Požadavky: . | JDK 25 (Gradle can provision the toolchain itself via foojay) | No Android SDK required for desktop-only builds | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/desktop.html#building-from-source",
    
    "relUrl": "/cs-rCZ/user/desktop.html#building-from-source"
  },"850": {
    "doc": "Desktop App",
    "title": "Known Limitations",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | 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) | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/desktop.html#known-limitations",
    
    "relUrl": "/cs-rCZ/user/desktop.html#known-limitations"
  },"851": {
    "doc": "Desktop App",
    "title": "Related Topics",
    "content": ". | Connections — connection methods overview | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/desktop.html#related-topics",
    
    "relUrl": "/cs-rCZ/user/desktop.html#related-topics"
  },"852": {
    "doc": "Настолно приложение",
    "title": "Настолно приложение",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/desktop.html",
    
    "relUrl": "/bg-rBG/user/desktop.html"
  },"853": {
    "doc": "Настолно приложение",
    "title": "Инсталация",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from the releases page | Или изградете от изходния код | . Windows . | Download the .msi or .exe installer from the releases page | Или изградете от изходния код | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/desktop.html#%D0%B8%D0%BD%D1%81%D1%82%D0%B0%D0%BB%D0%B0%D1%86%D0%B8%D1%8F",
    
    "relUrl": "/bg-rBG/user/desktop.html#инсталация"
  },"854": {
    "doc": "Настолно приложение",
    "title": "Connecting Your Radio",
    "content": "USB Serial (Primary) . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . For network-connected radios: . | Enter the radio’s IP address and port (default: 4403). | Click Connect. | . Bluetooth (BLE) . Bluetooth Low Energy is supported on desktop via the Kable library: . | Ensure your system has a Bluetooth adapter. The app scans for nearby Meshtastic radios automatically. | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/desktop.html#connecting-your-radio",
    
    "relUrl": "/bg-rBG/user/desktop.html#connecting-your-radio"
  },"855": {
    "doc": "Настолно приложение",
    "title": "Feature Parity",
    "content": "| Feature | Android | Desktop | Бележки | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Карта | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | Site Planner | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | Настройки | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Актуализация на фърмуера | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | Известия | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | AI Assistant (Chirpy) | ✓* | ✗ | Google flavor Android only | . | App Functions (system AI) | ✓† | ✗ | Google flavor Android only | . *Chirpy AI requires Android 14+ on Google flavor builds with supported hardware. †App Functions exposes app actions to the Android system AI on Google flavor builds. See App Functions. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/desktop.html#feature-parity",
    
    "relUrl": "/bg-rBG/user/desktop.html#feature-parity"
  },"856": {
    "doc": "Настолно приложение",
    "title": "UI Differences",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. Клавишни комбинации . Shortcuts use ⌘ (Command) on macOS and Ctrl on Windows and Linux. (The Super / Windows key is not bound.) . | Пряк път | Действие | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | Open Settings | . | ⌘/Ctrl+1 | Switch to Messages tab | . | ⌘/Ctrl+2 | Switch to Nodes tab | . | ⌘/Ctrl+3 | Switch to Map tab | . | ⌘/Ctrl+4 | Switch to Connect tab | . | ⌘/Ctrl+/ | Open About | . Window & System Tray . | Window resizing — responsive layout adapts to window dimensions | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | 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. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/desktop.html#ui-differences",
    
    "relUrl": "/bg-rBG/user/desktop.html#ui-differences"
  },"857": {
    "doc": "Настолно приложение",
    "title": "Built-in Documentation Browser",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. The browser supports full-text search across all documentation: . Individual doc pages render with full formatting: . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/desktop.html#built-in-documentation-browser",
    
    "relUrl": "/bg-rBG/user/desktop.html#built-in-documentation-browser"
  },"858": {
    "doc": "Настолно приложение",
    "title": "Building from Source",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Изисквания: . | JDK 25 (Gradle can provision the toolchain itself via foojay) | No Android SDK required for desktop-only builds | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/desktop.html#building-from-source",
    
    "relUrl": "/bg-rBG/user/desktop.html#building-from-source"
  },"859": {
    "doc": "Настолно приложение",
    "title": "Известни ограничения",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | 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) | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/desktop.html#%D0%B8%D0%B7%D0%B2%D0%B5%D1%81%D1%82%D0%BD%D0%B8-%D0%BE%D0%B3%D1%80%D0%B0%D0%BD%D0%B8%D1%87%D0%B5%D0%BD%D0%B8%D1%8F",
    
    "relUrl": "/bg-rBG/user/desktop.html#известни-ограничения"
  },"860": {
    "doc": "Настолно приложение",
    "title": "Свързани теми",
    "content": ". | Connections — connection methods overview | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/desktop.html#%D1%81%D0%B2%D1%8A%D1%80%D0%B7%D0%B0%D0%BD%D0%B8-%D1%82%D0%B5%D0%BC%D0%B8",
    
    "relUrl": "/bg-rBG/user/desktop.html#свързани-теми"
  },"861": {
    "doc": "Desktop App",
    "title": "Desktop App",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/desktop.html",
    
    "relUrl": "/ga-rIE/user/desktop.html"
  },"862": {
    "doc": "Desktop App",
    "title": "Installation",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from the releases page | Or build from source | . Windows . | Download the .msi or .exe installer from the releases page | Or build from source | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/desktop.html#installation",
    
    "relUrl": "/ga-rIE/user/desktop.html#installation"
  },"863": {
    "doc": "Desktop App",
    "title": "Connecting Your Radio",
    "content": "USB Serial (Primary) . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . For network-connected radios: . | Enter the radio’s IP address and port (default: 4403). | Click Connect. | . Bluetooth (BLE) . Bluetooth Low Energy is supported on desktop via the Kable library: . | Ensure your system has a Bluetooth adapter. The app scans for nearby Meshtastic radios automatically. | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/desktop.html#connecting-your-radio",
    
    "relUrl": "/ga-rIE/user/desktop.html#connecting-your-radio"
  },"864": {
    "doc": "Desktop App",
    "title": "Feature Parity",
    "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Map | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | Site Planner | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | Settings | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | AI Assistant (Chirpy) | ✓* | ✗ | Google flavor Android only | . | App Functions (system AI) | ✓† | ✗ | Google flavor Android only | . *Chirpy AI requires Android 14+ on Google flavor builds with supported hardware. †App Functions exposes app actions to the Android system AI on Google flavor builds. See App Functions. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/desktop.html#feature-parity",
    
    "relUrl": "/ga-rIE/user/desktop.html#feature-parity"
  },"865": {
    "doc": "Desktop App",
    "title": "UI Differences",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. Keyboard Shortcuts . Shortcuts use ⌘ (Command) on macOS and Ctrl on Windows and Linux. (The Super / Windows key is not bound.) . | Shortcut | Action | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | Open Settings | . | ⌘/Ctrl+1 | Switch to Messages tab | . | ⌘/Ctrl+2 | Switch to Nodes tab | . | ⌘/Ctrl+3 | Switch to Map tab | . | ⌘/Ctrl+4 | Switch to Connect tab | . | ⌘/Ctrl+/ | Open About | . Window & System Tray . | Window resizing — responsive layout adapts to window dimensions | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | 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. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/desktop.html#ui-differences",
    
    "relUrl": "/ga-rIE/user/desktop.html#ui-differences"
  },"866": {
    "doc": "Desktop App",
    "title": "Built-in Documentation Browser",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. The browser supports full-text search across all documentation: . Individual doc pages render with full formatting: . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/desktop.html#built-in-documentation-browser",
    
    "relUrl": "/ga-rIE/user/desktop.html#built-in-documentation-browser"
  },"867": {
    "doc": "Desktop App",
    "title": "Building from Source",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Requirements: . | JDK 25 (Gradle can provision the toolchain itself via foojay) | No Android SDK required for desktop-only builds | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/desktop.html#building-from-source",
    
    "relUrl": "/ga-rIE/user/desktop.html#building-from-source"
  },"868": {
    "doc": "Desktop App",
    "title": "Known Limitations",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | 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) | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/desktop.html#known-limitations",
    
    "relUrl": "/ga-rIE/user/desktop.html#known-limitations"
  },"869": {
    "doc": "Desktop App",
    "title": "Related Topics",
    "content": ". | Connections — connection methods overview | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/desktop.html#related-topics",
    
    "relUrl": "/ga-rIE/user/desktop.html#related-topics"
  },"870": {
    "doc": "Desktop App",
    "title": "Desktop App",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/desktop.html",
    
    "relUrl": "/fr-rCA/user/desktop.html"
  },"871": {
    "doc": "Desktop App",
    "title": "Installation",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from the releases page | Or build from source | . Windows . | Download the .msi or .exe installer from the releases page | Or build from source | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/desktop.html#installation",
    
    "relUrl": "/fr-rCA/user/desktop.html#installation"
  },"872": {
    "doc": "Desktop App",
    "title": "Connecting Your Radio",
    "content": "USB Serial (Primary) . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . For network-connected radios: . | Enter the radio’s IP address and port (default: 4403). | Click Connect. | . Bluetooth (BLE) . Bluetooth Low Energy is supported on desktop via the Kable library: . | Ensure your system has a Bluetooth adapter. The app scans for nearby Meshtastic radios automatically. | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/desktop.html#connecting-your-radio",
    
    "relUrl": "/fr-rCA/user/desktop.html#connecting-your-radio"
  },"873": {
    "doc": "Desktop App",
    "title": "Feature Parity",
    "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Carte | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | Site Planner | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | Réglages | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Mise à jour du firmware | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | AI Assistant (Chirpy) | ✓* | ✗ | Google flavor Android only | . | App Functions (system AI) | ✓† | ✗ | Google flavor Android only | . *Chirpy AI requires Android 14+ on Google flavor builds with supported hardware. †App Functions exposes app actions to the Android system AI on Google flavor builds. See App Functions. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/desktop.html#feature-parity",
    
    "relUrl": "/fr-rCA/user/desktop.html#feature-parity"
  },"874": {
    "doc": "Desktop App",
    "title": "UI Differences",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. Keyboard Shortcuts . Shortcuts use ⌘ (Command) on macOS and Ctrl on Windows and Linux. (The Super / Windows key is not bound.) . | Shortcut | Action | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | Open Settings | . | ⌘/Ctrl+1 | Switch to Messages tab | . | ⌘/Ctrl+2 | Switch to Nodes tab | . | ⌘/Ctrl+3 | Switch to Map tab | . | ⌘/Ctrl+4 | Switch to Connect tab | . | ⌘/Ctrl+/ | Open About | . Window & System Tray . | Window resizing — responsive layout adapts to window dimensions | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | 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. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/desktop.html#ui-differences",
    
    "relUrl": "/fr-rCA/user/desktop.html#ui-differences"
  },"875": {
    "doc": "Desktop App",
    "title": "Built-in Documentation Browser",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. The browser supports full-text search across all documentation: . Individual doc pages render with full formatting: . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/desktop.html#built-in-documentation-browser",
    
    "relUrl": "/fr-rCA/user/desktop.html#built-in-documentation-browser"
  },"876": {
    "doc": "Desktop App",
    "title": "Building from Source",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Requirements: . | JDK 25 (Gradle can provision the toolchain itself via foojay) | No Android SDK required for desktop-only builds | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/desktop.html#building-from-source",
    
    "relUrl": "/fr-rCA/user/desktop.html#building-from-source"
  },"877": {
    "doc": "Desktop App",
    "title": "Known Limitations",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | 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) | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/desktop.html#known-limitations",
    
    "relUrl": "/fr-rCA/user/desktop.html#known-limitations"
  },"878": {
    "doc": "Desktop App",
    "title": "Related Topics",
    "content": ". | Connections — connection methods overview | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/desktop.html#related-topics",
    
    "relUrl": "/fr-rCA/user/desktop.html#related-topics"
  },"879": {
    "doc": "Desktop App",
    "title": "Desktop App",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/srp/user/desktop.html",
    
    "relUrl": "/srp/user/desktop.html"
  },"880": {
    "doc": "Desktop App",
    "title": "Installation",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from the releases page | Or build from source | . Windows . | Download the .msi or .exe installer from the releases page | Or build from source | . ",
    "url": "/Meshtastic-Android/main/srp/user/desktop.html#installation",
    
    "relUrl": "/srp/user/desktop.html#installation"
  },"881": {
    "doc": "Desktop App",
    "title": "Connecting Your Radio",
    "content": "USB Serial (Primary) . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . For network-connected radios: . | Enter the radio’s IP address and port (default: 4403). | Click Connect. | . Bluetooth (BLE) . Bluetooth Low Energy is supported on desktop via the Kable library: . | Ensure your system has a Bluetooth adapter. The app scans for nearby Meshtastic radios automatically. | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/srp/user/desktop.html#connecting-your-radio",
    
    "relUrl": "/srp/user/desktop.html#connecting-your-radio"
  },"882": {
    "doc": "Desktop App",
    "title": "Feature Parity",
    "content": "| Feature | Android | Desktop | Белешке | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Мапа | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | Site Planner | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | Подешавања | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | AI Assistant (Chirpy) | ✓* | ✗ | Google flavor Android only | . | App Functions (system AI) | ✓† | ✗ | Google flavor Android only | . *Chirpy AI requires Android 14+ on Google flavor builds with supported hardware. †App Functions exposes app actions to the Android system AI on Google flavor builds. See App Functions. ",
    "url": "/Meshtastic-Android/main/srp/user/desktop.html#feature-parity",
    
    "relUrl": "/srp/user/desktop.html#feature-parity"
  },"883": {
    "doc": "Desktop App",
    "title": "UI Differences",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. Keyboard Shortcuts . Shortcuts use ⌘ (Command) on macOS and Ctrl on Windows and Linux. (The Super / Windows key is not bound.) . | Shortcut | Action | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | Отвори подешавања | . | ⌘/Ctrl+1 | Switch to Messages tab | . | ⌘/Ctrl+2 | Switch to Nodes tab | . | ⌘/Ctrl+3 | Switch to Map tab | . | ⌘/Ctrl+4 | Switch to Connect tab | . | ⌘/Ctrl+/ | Open About | . Window & System Tray . | Window resizing — responsive layout adapts to window dimensions | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | 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. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/srp/user/desktop.html#ui-differences",
    
    "relUrl": "/srp/user/desktop.html#ui-differences"
  },"884": {
    "doc": "Desktop App",
    "title": "Built-in Documentation Browser",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. The browser supports full-text search across all documentation: . Individual doc pages render with full formatting: . ",
    "url": "/Meshtastic-Android/main/srp/user/desktop.html#built-in-documentation-browser",
    
    "relUrl": "/srp/user/desktop.html#built-in-documentation-browser"
  },"885": {
    "doc": "Desktop App",
    "title": "Building from Source",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Requirements: . | JDK 25 (Gradle can provision the toolchain itself via foojay) | No Android SDK required for desktop-only builds | . ",
    "url": "/Meshtastic-Android/main/srp/user/desktop.html#building-from-source",
    
    "relUrl": "/srp/user/desktop.html#building-from-source"
  },"886": {
    "doc": "Desktop App",
    "title": "Known Limitations",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | 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) | . ",
    "url": "/Meshtastic-Android/main/srp/user/desktop.html#known-limitations",
    
    "relUrl": "/srp/user/desktop.html#known-limitations"
  },"887": {
    "doc": "Desktop App",
    "title": "Related Topics",
    "content": ". | Connections — connection methods overview | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/srp/user/desktop.html#related-topics",
    
    "relUrl": "/srp/user/desktop.html#related-topics"
  },"888": {
    "doc": "Desktop App",
    "title": "Desktop App",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/desktop.html",
    
    "relUrl": "/ca-rES/user/desktop.html"
  },"889": {
    "doc": "Desktop App",
    "title": "Installation",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from the releases page | Or build from source | . Windows . | Download the .msi or .exe installer from the releases page | Or build from source | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/desktop.html#installation",
    
    "relUrl": "/ca-rES/user/desktop.html#installation"
  },"890": {
    "doc": "Desktop App",
    "title": "Connecting Your Radio",
    "content": "USB Serial (Primary) . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . For network-connected radios: . | Enter the radio’s IP address and port (default: 4403). | Click Connect. | . Bluetooth (BLE) . Bluetooth Low Energy is supported on desktop via the Kable library: . | Ensure your system has a Bluetooth adapter. The app scans for nearby Meshtastic radios automatically. | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/desktop.html#connecting-your-radio",
    
    "relUrl": "/ca-rES/user/desktop.html#connecting-your-radio"
  },"891": {
    "doc": "Desktop App",
    "title": "Feature Parity",
    "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Map | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | Site Planner | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | Settings | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | AI Assistant (Chirpy) | ✓* | ✗ | Google flavor Android only | . | App Functions (system AI) | ✓† | ✗ | Google flavor Android only | . *Chirpy AI requires Android 14+ on Google flavor builds with supported hardware. †App Functions exposes app actions to the Android system AI on Google flavor builds. See App Functions. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/desktop.html#feature-parity",
    
    "relUrl": "/ca-rES/user/desktop.html#feature-parity"
  },"892": {
    "doc": "Desktop App",
    "title": "UI Differences",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. Keyboard Shortcuts . Shortcuts use ⌘ (Command) on macOS and Ctrl on Windows and Linux. (The Super / Windows key is not bound.) . | Shortcut | Action | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | Open Settings | . | ⌘/Ctrl+1 | Switch to Messages tab | . | ⌘/Ctrl+2 | Switch to Nodes tab | . | ⌘/Ctrl+3 | Switch to Map tab | . | ⌘/Ctrl+4 | Switch to Connect tab | . | ⌘/Ctrl+/ | Open About | . Window & System Tray . | Window resizing — responsive layout adapts to window dimensions | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | 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. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/desktop.html#ui-differences",
    
    "relUrl": "/ca-rES/user/desktop.html#ui-differences"
  },"893": {
    "doc": "Desktop App",
    "title": "Built-in Documentation Browser",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. The browser supports full-text search across all documentation: . Individual doc pages render with full formatting: . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/desktop.html#built-in-documentation-browser",
    
    "relUrl": "/ca-rES/user/desktop.html#built-in-documentation-browser"
  },"894": {
    "doc": "Desktop App",
    "title": "Building from Source",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Requirements: . | JDK 25 (Gradle can provision the toolchain itself via foojay) | No Android SDK required for desktop-only builds | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/desktop.html#building-from-source",
    
    "relUrl": "/ca-rES/user/desktop.html#building-from-source"
  },"895": {
    "doc": "Desktop App",
    "title": "Known Limitations",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | 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) | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/desktop.html#known-limitations",
    
    "relUrl": "/ca-rES/user/desktop.html#known-limitations"
  },"896": {
    "doc": "Desktop App",
    "title": "Related Topics",
    "content": ". | Connections — connection methods overview | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/desktop.html#related-topics",
    
    "relUrl": "/ca-rES/user/desktop.html#related-topics"
  },"897": {
    "doc": "Desktop App",
    "title": "Desktop App",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/desktop.html",
    
    "relUrl": "/ko-rKR/user/desktop.html"
  },"898": {
    "doc": "Desktop App",
    "title": "Installation",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from the releases page | Or build from source | . Windows . | Download the .msi or .exe installer from the releases page | Or build from source | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/desktop.html#installation",
    
    "relUrl": "/ko-rKR/user/desktop.html#installation"
  },"899": {
    "doc": "Desktop App",
    "title": "Connecting Your Radio",
    "content": "USB Serial (Primary) . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . For network-connected radios: . | Enter the radio’s IP address and port (default: 4403). | Click Connect. | . Bluetooth (BLE) . Bluetooth Low Energy is supported on desktop via the Kable library: . | Ensure your system has a Bluetooth adapter. The app scans for nearby Meshtastic radios automatically. | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/desktop.html#connecting-your-radio",
    
    "relUrl": "/ko-rKR/user/desktop.html#connecting-your-radio"
  },"900": {
    "doc": "Desktop App",
    "title": "Feature Parity",
    "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | 지도 | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | Site Planner | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | 설정 | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | AI Assistant (Chirpy) | ✓* | ✗ | Google flavor Android only | . | App Functions (system AI) | ✓† | ✗ | Google flavor Android only | . *Chirpy AI requires Android 14+ on Google flavor builds with supported hardware. †App Functions exposes app actions to the Android system AI on Google flavor builds. See App Functions. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/desktop.html#feature-parity",
    
    "relUrl": "/ko-rKR/user/desktop.html#feature-parity"
  },"901": {
    "doc": "Desktop App",
    "title": "UI Differences",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. Keyboard Shortcuts . Shortcuts use ⌘ (Command) on macOS and Ctrl on Windows and Linux. (The Super / Windows key is not bound.) . | Shortcut | Action | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | Open Settings | . | ⌘/Ctrl+1 | Switch to Messages tab | . | ⌘/Ctrl+2 | Switch to Nodes tab | . | ⌘/Ctrl+3 | Switch to Map tab | . | ⌘/Ctrl+4 | Switch to Connect tab | . | ⌘/Ctrl+/ | Open About | . Window & System Tray . | Window resizing — responsive layout adapts to window dimensions | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | 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. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/desktop.html#ui-differences",
    
    "relUrl": "/ko-rKR/user/desktop.html#ui-differences"
  },"902": {
    "doc": "Desktop App",
    "title": "Built-in Documentation Browser",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. The browser supports full-text search across all documentation: . Individual doc pages render with full formatting: . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/desktop.html#built-in-documentation-browser",
    
    "relUrl": "/ko-rKR/user/desktop.html#built-in-documentation-browser"
  },"903": {
    "doc": "Desktop App",
    "title": "Building from Source",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Requirements: . | JDK 25 (Gradle can provision the toolchain itself via foojay) | No Android SDK required for desktop-only builds | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/desktop.html#building-from-source",
    
    "relUrl": "/ko-rKR/user/desktop.html#building-from-source"
  },"904": {
    "doc": "Desktop App",
    "title": "Known Limitations",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | 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) | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/desktop.html#known-limitations",
    
    "relUrl": "/ko-rKR/user/desktop.html#known-limitations"
  },"905": {
    "doc": "Desktop App",
    "title": "Related Topics",
    "content": ". | Connections — connection methods overview | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/desktop.html#related-topics",
    
    "relUrl": "/ko-rKR/user/desktop.html#related-topics"
  },"906": {
    "doc": "Desktop App",
    "title": "Desktop App",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/desktop.html",
    
    "relUrl": "/sv-rSE/user/desktop.html"
  },"907": {
    "doc": "Desktop App",
    "title": "Installation",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from the releases page | Or build from source | . Windows . | Download the .msi or .exe installer from the releases page | Or build from source | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/desktop.html#installation",
    
    "relUrl": "/sv-rSE/user/desktop.html#installation"
  },"908": {
    "doc": "Desktop App",
    "title": "Connecting Your Radio",
    "content": "USB Serial (Primary) . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . For network-connected radios: . | Enter the radio’s IP address and port (default: 4403). | Click Connect. | . Bluetooth (BLE) . Bluetooth Low Energy is supported on desktop via the Kable library: . | Ensure your system has a Bluetooth adapter. The app scans for nearby Meshtastic radios automatically. | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/desktop.html#connecting-your-radio",
    
    "relUrl": "/sv-rSE/user/desktop.html#connecting-your-radio"
  },"909": {
    "doc": "Desktop App",
    "title": "Feature Parity",
    "content": "| Feature | Android | Desktop | Anteckningar | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Karta | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | Site Planner | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | Inställningar | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Uppdatering av fast programvara | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | AI Assistant (Chirpy) | ✓* | ✗ | Google flavor Android only | . | App Functions (system AI) | ✓† | ✗ | Google flavor Android only | . *Chirpy AI requires Android 14+ on Google flavor builds with supported hardware. †App Functions exposes app actions to the Android system AI on Google flavor builds. See App Functions. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/desktop.html#feature-parity",
    
    "relUrl": "/sv-rSE/user/desktop.html#feature-parity"
  },"910": {
    "doc": "Desktop App",
    "title": "UI Differences",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. Keyboard Shortcuts . Shortcuts use ⌘ (Command) on macOS and Ctrl on Windows and Linux. (The Super / Windows key is not bound.) . | Shortcut | Action | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | Open Settings | . | ⌘/Ctrl+1 | Switch to Messages tab | . | ⌘/Ctrl+2 | Switch to Nodes tab | . | ⌘/Ctrl+3 | Switch to Map tab | . | ⌘/Ctrl+4 | Switch to Connect tab | . | ⌘/Ctrl+/ | Open About | . Window & System Tray . | Window resizing — responsive layout adapts to window dimensions | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | 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. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/desktop.html#ui-differences",
    
    "relUrl": "/sv-rSE/user/desktop.html#ui-differences"
  },"911": {
    "doc": "Desktop App",
    "title": "Built-in Documentation Browser",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. The browser supports full-text search across all documentation: . Individual doc pages render with full formatting: . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/desktop.html#built-in-documentation-browser",
    
    "relUrl": "/sv-rSE/user/desktop.html#built-in-documentation-browser"
  },"912": {
    "doc": "Desktop App",
    "title": "Building from Source",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Requirements: . | JDK 25 (Gradle can provision the toolchain itself via foojay) | No Android SDK required for desktop-only builds | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/desktop.html#building-from-source",
    
    "relUrl": "/sv-rSE/user/desktop.html#building-from-source"
  },"913": {
    "doc": "Desktop App",
    "title": "Known Limitations",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | 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) | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/desktop.html#known-limitations",
    
    "relUrl": "/sv-rSE/user/desktop.html#known-limitations"
  },"914": {
    "doc": "Desktop App",
    "title": "Related Topics",
    "content": ". | Connections — connection methods overview | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/desktop.html#related-topics",
    
    "relUrl": "/sv-rSE/user/desktop.html#related-topics"
  },"915": {
    "doc": "Desktop App",
    "title": "Desktop App",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/desktop.html",
    
    "relUrl": "/ht-rHT/user/desktop.html"
  },"916": {
    "doc": "Desktop App",
    "title": "Installation",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from the releases page | Or build from source | . Windows . | Download the .msi or .exe installer from the releases page | Or build from source | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/desktop.html#installation",
    
    "relUrl": "/ht-rHT/user/desktop.html#installation"
  },"917": {
    "doc": "Desktop App",
    "title": "Connecting Your Radio",
    "content": "USB Serial (Primary) . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . For network-connected radios: . | Enter the radio’s IP address and port (default: 4403). | Click Connect. | . Bluetooth (BLE) . Bluetooth Low Energy is supported on desktop via the Kable library: . | Ensure your system has a Bluetooth adapter. The app scans for nearby Meshtastic radios automatically. | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/desktop.html#connecting-your-radio",
    
    "relUrl": "/ht-rHT/user/desktop.html#connecting-your-radio"
  },"918": {
    "doc": "Desktop App",
    "title": "Feature Parity",
    "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Map | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | Site Planner | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | Settings | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | AI Assistant (Chirpy) | ✓* | ✗ | Google flavor Android only | . | App Functions (system AI) | ✓† | ✗ | Google flavor Android only | . *Chirpy AI requires Android 14+ on Google flavor builds with supported hardware. †App Functions exposes app actions to the Android system AI on Google flavor builds. See App Functions. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/desktop.html#feature-parity",
    
    "relUrl": "/ht-rHT/user/desktop.html#feature-parity"
  },"919": {
    "doc": "Desktop App",
    "title": "UI Differences",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. Keyboard Shortcuts . Shortcuts use ⌘ (Command) on macOS and Ctrl on Windows and Linux. (The Super / Windows key is not bound.) . | Shortcut | Action | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | Open Settings | . | ⌘/Ctrl+1 | Switch to Messages tab | . | ⌘/Ctrl+2 | Switch to Nodes tab | . | ⌘/Ctrl+3 | Switch to Map tab | . | ⌘/Ctrl+4 | Switch to Connect tab | . | ⌘/Ctrl+/ | Open About | . Window & System Tray . | Window resizing — responsive layout adapts to window dimensions | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | 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. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/desktop.html#ui-differences",
    
    "relUrl": "/ht-rHT/user/desktop.html#ui-differences"
  },"920": {
    "doc": "Desktop App",
    "title": "Built-in Documentation Browser",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. The browser supports full-text search across all documentation: . Individual doc pages render with full formatting: . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/desktop.html#built-in-documentation-browser",
    
    "relUrl": "/ht-rHT/user/desktop.html#built-in-documentation-browser"
  },"921": {
    "doc": "Desktop App",
    "title": "Building from Source",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Requirements: . | JDK 25 (Gradle can provision the toolchain itself via foojay) | No Android SDK required for desktop-only builds | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/desktop.html#building-from-source",
    
    "relUrl": "/ht-rHT/user/desktop.html#building-from-source"
  },"922": {
    "doc": "Desktop App",
    "title": "Known Limitations",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | 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) | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/desktop.html#known-limitations",
    
    "relUrl": "/ht-rHT/user/desktop.html#known-limitations"
  },"923": {
    "doc": "Desktop App",
    "title": "Related Topics",
    "content": ". | Connections — connection methods overview | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/desktop.html#related-topics",
    
    "relUrl": "/ht-rHT/user/desktop.html#related-topics"
  },"924": {
    "doc": "Desktop App",
    "title": "Desktop App",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/desktop.html",
    
    "relUrl": "/sr-rLatn/user/desktop.html"
  },"925": {
    "doc": "Desktop App",
    "title": "Installation",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from the releases page | Or build from source | . Windows . | Download the .msi or .exe installer from the releases page | Or build from source | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/desktop.html#installation",
    
    "relUrl": "/sr-rLatn/user/desktop.html#installation"
  },"926": {
    "doc": "Desktop App",
    "title": "Connecting Your Radio",
    "content": "USB Serial (Primary) . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . For network-connected radios: . | Enter the radio’s IP address and port (default: 4403). | Click Connect. | . Bluetooth (BLE) . Bluetooth Low Energy is supported on desktop via the Kable library: . | Ensure your system has a Bluetooth adapter. The app scans for nearby Meshtastic radios automatically. | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/desktop.html#connecting-your-radio",
    
    "relUrl": "/sr-rLatn/user/desktop.html#connecting-your-radio"
  },"927": {
    "doc": "Desktop App",
    "title": "Feature Parity",
    "content": "| Feature | Android | Desktop | Белешке | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Мапа | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | Site Planner | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | Подешавања | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | AI Assistant (Chirpy) | ✓* | ✗ | Google flavor Android only | . | App Functions (system AI) | ✓† | ✗ | Google flavor Android only | . *Chirpy AI requires Android 14+ on Google flavor builds with supported hardware. †App Functions exposes app actions to the Android system AI on Google flavor builds. See App Functions. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/desktop.html#feature-parity",
    
    "relUrl": "/sr-rLatn/user/desktop.html#feature-parity"
  },"928": {
    "doc": "Desktop App",
    "title": "UI Differences",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. Keyboard Shortcuts . Shortcuts use ⌘ (Command) on macOS and Ctrl on Windows and Linux. (The Super / Windows key is not bound.) . | Shortcut | Action | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | Отвори подешавања | . | ⌘/Ctrl+1 | Switch to Messages tab | . | ⌘/Ctrl+2 | Switch to Nodes tab | . | ⌘/Ctrl+3 | Switch to Map tab | . | ⌘/Ctrl+4 | Switch to Connect tab | . | ⌘/Ctrl+/ | Open About | . Window & System Tray . | Window resizing — responsive layout adapts to window dimensions | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | 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. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/desktop.html#ui-differences",
    
    "relUrl": "/sr-rLatn/user/desktop.html#ui-differences"
  },"929": {
    "doc": "Desktop App",
    "title": "Built-in Documentation Browser",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. The browser supports full-text search across all documentation: . Individual doc pages render with full formatting: . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/desktop.html#built-in-documentation-browser",
    
    "relUrl": "/sr-rLatn/user/desktop.html#built-in-documentation-browser"
  },"930": {
    "doc": "Desktop App",
    "title": "Building from Source",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Requirements: . | JDK 25 (Gradle can provision the toolchain itself via foojay) | No Android SDK required for desktop-only builds | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/desktop.html#building-from-source",
    
    "relUrl": "/sr-rLatn/user/desktop.html#building-from-source"
  },"931": {
    "doc": "Desktop App",
    "title": "Known Limitations",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | 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) | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/desktop.html#known-limitations",
    
    "relUrl": "/sr-rLatn/user/desktop.html#known-limitations"
  },"932": {
    "doc": "Desktop App",
    "title": "Related Topics",
    "content": ". | Connections — connection methods overview | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/desktop.html#related-topics",
    
    "relUrl": "/sr-rLatn/user/desktop.html#related-topics"
  },"933": {
    "doc": "Desktop App",
    "title": "Desktop App",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/desktop.html",
    
    "relUrl": "/nl-rNL/user/desktop.html"
  },"934": {
    "doc": "Desktop App",
    "title": "Installation",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from the releases page | Or build from source | . Windows . | Download the .msi or .exe installer from the releases page | Or build from source | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/desktop.html#installation",
    
    "relUrl": "/nl-rNL/user/desktop.html#installation"
  },"935": {
    "doc": "Desktop App",
    "title": "Connecting Your Radio",
    "content": "USB Serial (Primary) . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . For network-connected radios: . | Enter the radio’s IP address and port (default: 4403). | Click Connect. | . Bluetooth (BLE) . Bluetooth Low Energy is supported on desktop via the Kable library: . | Ensure your system has a Bluetooth adapter. The app scans for nearby Meshtastic radios automatically. | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/desktop.html#connecting-your-radio",
    
    "relUrl": "/nl-rNL/user/desktop.html#connecting-your-radio"
  },"936": {
    "doc": "Desktop App",
    "title": "Feature Parity",
    "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Kaart | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | Site Planner | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | Instellingen | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | AI Assistant (Chirpy) | ✓* | ✗ | Google flavor Android only | . | App Functions (system AI) | ✓† | ✗ | Google flavor Android only | . *Chirpy AI requires Android 14+ on Google flavor builds with supported hardware. †App Functions exposes app actions to the Android system AI on Google flavor builds. See App Functions. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/desktop.html#feature-parity",
    
    "relUrl": "/nl-rNL/user/desktop.html#feature-parity"
  },"937": {
    "doc": "Desktop App",
    "title": "UI Differences",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. Keyboard Shortcuts . Shortcuts use ⌘ (Command) on macOS and Ctrl on Windows and Linux. (The Super / Windows key is not bound.) . | Shortcut | Action | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | Open Settings | . | ⌘/Ctrl+1 | Switch to Messages tab | . | ⌘/Ctrl+2 | Switch to Nodes tab | . | ⌘/Ctrl+3 | Switch to Map tab | . | ⌘/Ctrl+4 | Switch to Connect tab | . | ⌘/Ctrl+/ | Open About | . Window & System Tray . | Window resizing — responsive layout adapts to window dimensions | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | 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. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/desktop.html#ui-differences",
    
    "relUrl": "/nl-rNL/user/desktop.html#ui-differences"
  },"938": {
    "doc": "Desktop App",
    "title": "Built-in Documentation Browser",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. The browser supports full-text search across all documentation: . Individual doc pages render with full formatting: . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/desktop.html#built-in-documentation-browser",
    
    "relUrl": "/nl-rNL/user/desktop.html#built-in-documentation-browser"
  },"939": {
    "doc": "Desktop App",
    "title": "Building from Source",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Requirements: . | JDK 25 (Gradle can provision the toolchain itself via foojay) | No Android SDK required for desktop-only builds | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/desktop.html#building-from-source",
    
    "relUrl": "/nl-rNL/user/desktop.html#building-from-source"
  },"940": {
    "doc": "Desktop App",
    "title": "Known Limitations",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | 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) | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/desktop.html#known-limitations",
    
    "relUrl": "/nl-rNL/user/desktop.html#known-limitations"
  },"941": {
    "doc": "Desktop App",
    "title": "Related Topics",
    "content": ". | Connections — connection methods overview | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/desktop.html#related-topics",
    
    "relUrl": "/nl-rNL/user/desktop.html#related-topics"
  },"942": {
    "doc": "Desktop App",
    "title": "Desktop App",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/desktop.html",
    
    "relUrl": "/uk-rUA/user/desktop.html"
  },"943": {
    "doc": "Desktop App",
    "title": "Installation",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from the releases page | Or build from source | . Windows . | Download the .msi or .exe installer from the releases page | Or build from source | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/desktop.html#installation",
    
    "relUrl": "/uk-rUA/user/desktop.html#installation"
  },"944": {
    "doc": "Desktop App",
    "title": "Connecting Your Radio",
    "content": "USB Serial (Primary) . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . For network-connected radios: . | Enter the radio’s IP address and port (default: 4403). | Click Connect. | . Bluetooth (BLE) . Bluetooth Low Energy is supported on desktop via the Kable library: . | Ensure your system has a Bluetooth adapter. The app scans for nearby Meshtastic radios automatically. | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/desktop.html#connecting-your-radio",
    
    "relUrl": "/uk-rUA/user/desktop.html#connecting-your-radio"
  },"945": {
    "doc": "Desktop App",
    "title": "Feature Parity",
    "content": "| Feature | Android | Desktop | Нотатки | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Мапа | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | Site Planner | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | Налаштування | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Оновити прошивку | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | AI Assistant (Chirpy) | ✓* | ✗ | Google flavor Android only | . | App Functions (system AI) | ✓† | ✗ | Google flavor Android only | . *Chirpy AI requires Android 14+ on Google flavor builds with supported hardware. †App Functions exposes app actions to the Android system AI on Google flavor builds. See App Functions. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/desktop.html#feature-parity",
    
    "relUrl": "/uk-rUA/user/desktop.html#feature-parity"
  },"946": {
    "doc": "Desktop App",
    "title": "UI Differences",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. Keyboard Shortcuts . Shortcuts use ⌘ (Command) on macOS and Ctrl on Windows and Linux. (The Super / Windows key is not bound.) . | Shortcut | Action | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | Open Settings | . | ⌘/Ctrl+1 | Switch to Messages tab | . | ⌘/Ctrl+2 | Switch to Nodes tab | . | ⌘/Ctrl+3 | Switch to Map tab | . | ⌘/Ctrl+4 | Switch to Connect tab | . | ⌘/Ctrl+/ | Open About | . Window & System Tray . | Window resizing — responsive layout adapts to window dimensions | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | 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. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/desktop.html#ui-differences",
    
    "relUrl": "/uk-rUA/user/desktop.html#ui-differences"
  },"947": {
    "doc": "Desktop App",
    "title": "Built-in Documentation Browser",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. The browser supports full-text search across all documentation: . Individual doc pages render with full formatting: . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/desktop.html#built-in-documentation-browser",
    
    "relUrl": "/uk-rUA/user/desktop.html#built-in-documentation-browser"
  },"948": {
    "doc": "Desktop App",
    "title": "Building from Source",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Requirements: . | JDK 25 (Gradle can provision the toolchain itself via foojay) | No Android SDK required for desktop-only builds | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/desktop.html#building-from-source",
    
    "relUrl": "/uk-rUA/user/desktop.html#building-from-source"
  },"949": {
    "doc": "Desktop App",
    "title": "Known Limitations",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | 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) | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/desktop.html#known-limitations",
    
    "relUrl": "/uk-rUA/user/desktop.html#known-limitations"
  },"950": {
    "doc": "Desktop App",
    "title": "Related Topics",
    "content": ". | Connections — connection methods overview | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/desktop.html#related-topics",
    
    "relUrl": "/uk-rUA/user/desktop.html#related-topics"
  },"951": {
    "doc": "Työpöytäsovellus",
    "title": "Työpöytäsovellus",
    "content": "Tällä sivulla kerrotaan Meshtastic Työpöytä -sovelluksen asentamisesta, radion yhdistämisestä ja siitä, miten se eroaa Android-versiosta. Työpöytä-sovellus käyttää samaa ydinkoodia kuin Android Kotlin Multiplatformin kautta, joten useimmat ominaisuudet toimivat samalla tavalla Linuxissa, macOS:ssä ja Windowsissa. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/desktop.html",
    
    "relUrl": "/fi-rFI/user/desktop.html"
  },"952": {
    "doc": "Työpöytäsovellus",
    "title": "Asennus",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | Tai rakenna lähdekoodista komennolla ./gradlew :desktopApp:run | . macOS . | Lataa .dmg-paketti julkaisusivulta | Tai rakenna lähdekoodista | . Windows . | Download the .msi or .exe installer from the releases page | Tai rakenna lähdekoodista | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/desktop.html#asennus",
    
    "relUrl": "/fi-rFI/user/desktop.html#asennus"
  },"953": {
    "doc": "Työpöytäsovellus",
    "title": "Radioon yhdistäminen",
    "content": "USB-sarjaportti (ensisijainen) . Luotettavin yhteystapa Työpöydällä: . Yhdistä radiosi USB:n kautta. Sovellus tunnistaa sarjaportin automaattisesti. Jos se ei onnistu, valitse portti Yhdistä-valikosta. TCP/IP . Verkkoyhteydellä oleville radioille: . | Syötä radion IP-osoite ja portti (oletus: 4403). | Paina Yhdistä. | . Bluetooth (BLE) . Bluetooth Low Energy on tuettu Työpöydällä Kable-kirjaston avulla: . | Varmista, että järjestelmässäsi on Bluetooth-adapteri. Sovellus etsii lähellä olevia Meshtastic-radioita automaattisesti. | Valitse radiosi Yhdistä-näytöltä. | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/desktop.html#radioon-yhdist%C3%A4minen",
    
    "relUrl": "/fi-rFI/user/desktop.html#radioon-yhdistäminen"
  },"954": {
    "doc": "Työpöytäsovellus",
    "title": "Ominaisuuksien yhtenevyys",
    "content": "| Ominaisuus | Android | Työpöytä | Viestit | . | Viestit | ✓ | ✓ | Täysi yhtenevyys | . | Radiolista | ✓ | ✓ | Täysi yhtenevyys | . | Kartta | ✓ | ✓ | Vuorovaikutteinen MapLibre-kartta, jossa on taustakartan ja karttatasojen valitsimet sekä mukautetut karttalähteet. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Karttatasot (.kml / .kmz / GeoJSON) | ✓ | ✓ | Sama karttatasojen hallinta kuin Androidissa. Tuodut tiedostot piirretään Työpöytä-kartalle | . | Site Planner | ✓ | ✓* | *Avautuu selaimessa Työpöydällä, eikä arviota piirretä Työpöytä-kartalle | . | Asetukset | ✓ | ✓ | Täysi yhtenevyys | . | Bluetooth (BLE) | ✓ | ✓ | Työpöydällä Kable-kirjaston kautta | . | Laiteohjelmiston päivitys | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | Ilmoitukset | ✓ | ✓ | Käyttöjärjestelmän natiivit ilmoitukset | . | Widgetit | ✓ | ✗ | Vain Android | . | Tekoälyavustaja (Chirpy) | ✓* | ✗ | Vain Google-version Android-laitteissa | . | Sovellustoiminnot (järjestelmän tekoäly) | ✓† | ✗ | Vain Google-version Android-laitteissa | . *Chirpy AI vaatii Android 14+ -version Google-version Android-laitteissa, joissa on tuettu laitteisto. †Sovellustoiminnot tuo sovellustoiminnot Android-järjestelmän tekoälylle Google-version Android-laitteissa. Katso Sovellustoiminnot. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/desktop.html#ominaisuuksien-yhtenevyys",
    
    "relUrl": "/fi-rFI/user/desktop.html#ominaisuuksien-yhtenevyys"
  },"955": {
    "doc": "Työpöytäsovellus",
    "title": "Käyttöliittymäerot",
    "content": "Työpöytä-sovellus käyttää samaa Compose Multiplatform -käyttöliittymää, mutta sitä on mukautettu suuremmille näytöille ja Työpöytä-käyttöön. Pikanäppäimet . Pikanäppäimissä käytetään macOS:ssä ⌘-näppäintä (Command) ja Windowsissa sekä Linuxissa Ctrl-näppäintä. (Super-/Windows-näppäimelle ei ole määritetty toimintoa.) . | Pikanäppäin | Toiminto | . | ⌘/Ctrl+Q | Sulje sovellus | . | ⌘/Ctrl+, | Avaa asetukset | . | ⌘/Ctrl+1 | Vaihda Viestit-välilehdelle | . | ⌘/Ctrl+2 | Vaihda Radiot-välilehdelle | . | ⌘/Ctrl+3 | Vaihda Kartta-välilehdelle | . | ⌘/Ctrl+4 | Vaihda Yhdistä-välilehdelle | . | ⌘/Ctrl+/ | Avaa tietoja | . Ikkuna ja järjestelmätarjotin . | Ikkunan koon muuttaminen — responsiivinen asettelu mukautuu ikkunan kokoon | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | Valikko — napsauta järjestelmätarjottimen kuvaketta hiiren oikealla näyttääksesi ikkunan tai sulkeaksesi sovelluksen | Hiiritoiminnot — hover-tilat ja tavallinen työpöydän navigointi | . Ilmoitusasetukset . The desktop app provides in-app toggles for controlling which notifications are shown. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/desktop.html#k%C3%A4ytt%C3%B6liittym%C3%A4erot",
    
    "relUrl": "/fi-rFI/user/desktop.html#käyttöliittymäerot"
  },"956": {
    "doc": "Työpöytäsovellus",
    "title": "Sisäänrakennettu dokumentaatioselain",
    "content": "Työpöytä-sovelluksessa on sisäänrakennettu dokumentaation selain, jonka avulla ohjeisiin pääsee nopeasti poistumatta sovelluksesta. Selain tukee koko dokumentaation laajuista kokotekstihakua: . Yksittäiset dokumenttisivut renderöidään täydellä muotoilulla: . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/desktop.html#sis%C3%A4%C3%A4nrakennettu-dokumentaatioselain",
    
    "relUrl": "/fi-rFI/user/desktop.html#sisäänrakennettu-dokumentaatioselain"
  },"957": {
    "doc": "Työpöytäsovellus",
    "title": "Rakentaminen lähdekoodista",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Vaatimukset: . | JDK 25 (Gradle voi asentaa työkaluketjun itse Foojayn kautta) | Android SDK:ta ei tarvita pelkkien työpöytäversioiden rakentamiseen | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/desktop.html#rakentaminen-l%C3%A4hdekoodista",
    
    "relUrl": "/fi-rFI/user/desktop.html#rakentaminen-lähdekoodista"
  },"958": {
    "doc": "Työpöytäsovellus",
    "title": "Tunnetut rajoitukset",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml-, .kmz- ja GeoJSON-karttatasojen tuonti toimii — katso Kartta ja reittipisteet. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | Jotkin Android-kohtaiset ominaisuudet (widgetit, tietyt ilmoituskanavat) eivät ole käytettävissä | Suorituskyky voi vaihdella heikkotehoisella laitteistolla ajettaessa Compose Desktopia | BLE-paritus ei vielä tallenna laiteparia työpöydällä (paritus toimii ilman tallennusta) | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/desktop.html#tunnetut-rajoitukset",
    
    "relUrl": "/fi-rFI/user/desktop.html#tunnetut-rajoitukset"
  },"959": {
    "doc": "Työpöytäsovellus",
    "title": "Aiheeseen liittyvät aiheet",
    "content": ". | Yhteydet — yhteystapojen yleiskatsaus | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/desktop.html#aiheeseen-liittyv%C3%A4t-aiheet",
    
    "relUrl": "/fi-rFI/user/desktop.html#aiheeseen-liittyvät-aiheet"
  },"960": {
    "doc": "Desktop App",
    "title": "Desktop App",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/desktop.html",
    
    "relUrl": "/is-rIS/user/desktop.html"
  },"961": {
    "doc": "Desktop App",
    "title": "Installation",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from the releases page | Or build from source | . Windows . | Download the .msi or .exe installer from the releases page | Or build from source | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/desktop.html#installation",
    
    "relUrl": "/is-rIS/user/desktop.html#installation"
  },"962": {
    "doc": "Desktop App",
    "title": "Connecting Your Radio",
    "content": "USB Serial (Primary) . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . For network-connected radios: . | Enter the radio’s IP address and port (default: 4403). | Click Connect. | . Bluetooth (BLE) . Bluetooth Low Energy is supported on desktop via the Kable library: . | Ensure your system has a Bluetooth adapter. The app scans for nearby Meshtastic radios automatically. | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/desktop.html#connecting-your-radio",
    
    "relUrl": "/is-rIS/user/desktop.html#connecting-your-radio"
  },"963": {
    "doc": "Desktop App",
    "title": "Feature Parity",
    "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Map | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | Site Planner | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | Settings | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | AI Assistant (Chirpy) | ✓* | ✗ | Google flavor Android only | . | App Functions (system AI) | ✓† | ✗ | Google flavor Android only | . *Chirpy AI requires Android 14+ on Google flavor builds with supported hardware. †App Functions exposes app actions to the Android system AI on Google flavor builds. See App Functions. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/desktop.html#feature-parity",
    
    "relUrl": "/is-rIS/user/desktop.html#feature-parity"
  },"964": {
    "doc": "Desktop App",
    "title": "UI Differences",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. Keyboard Shortcuts . Shortcuts use ⌘ (Command) on macOS and Ctrl on Windows and Linux. (The Super / Windows key is not bound.) . | Shortcut | Action | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | Open Settings | . | ⌘/Ctrl+1 | Switch to Messages tab | . | ⌘/Ctrl+2 | Switch to Nodes tab | . | ⌘/Ctrl+3 | Switch to Map tab | . | ⌘/Ctrl+4 | Switch to Connect tab | . | ⌘/Ctrl+/ | Open About | . Window & System Tray . | Window resizing — responsive layout adapts to window dimensions | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | 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. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/desktop.html#ui-differences",
    
    "relUrl": "/is-rIS/user/desktop.html#ui-differences"
  },"965": {
    "doc": "Desktop App",
    "title": "Built-in Documentation Browser",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. The browser supports full-text search across all documentation: . Individual doc pages render with full formatting: . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/desktop.html#built-in-documentation-browser",
    
    "relUrl": "/is-rIS/user/desktop.html#built-in-documentation-browser"
  },"966": {
    "doc": "Desktop App",
    "title": "Building from Source",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Requirements: . | JDK 25 (Gradle can provision the toolchain itself via foojay) | No Android SDK required for desktop-only builds | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/desktop.html#building-from-source",
    
    "relUrl": "/is-rIS/user/desktop.html#building-from-source"
  },"967": {
    "doc": "Desktop App",
    "title": "Known Limitations",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | 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) | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/desktop.html#known-limitations",
    
    "relUrl": "/is-rIS/user/desktop.html#known-limitations"
  },"968": {
    "doc": "Desktop App",
    "title": "Related Topics",
    "content": ". | Connections — connection methods overview | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/desktop.html#related-topics",
    
    "relUrl": "/is-rIS/user/desktop.html#related-topics"
  },"969": {
    "doc": "Desktop App",
    "title": "Desktop App",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/desktop.html",
    
    "relUrl": "/lt-rLT/user/desktop.html"
  },"970": {
    "doc": "Desktop App",
    "title": "Installation",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from the releases page | Or build from source | . Windows . | Download the .msi or .exe installer from the releases page | Or build from source | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/desktop.html#installation",
    
    "relUrl": "/lt-rLT/user/desktop.html#installation"
  },"971": {
    "doc": "Desktop App",
    "title": "Connecting Your Radio",
    "content": "USB Serial (Primary) . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . For network-connected radios: . | Enter the radio’s IP address and port (default: 4403). | Click Connect. | . Bluetooth (BLE) . Bluetooth Low Energy is supported on desktop via the Kable library: . | Ensure your system has a Bluetooth adapter. The app scans for nearby Meshtastic radios automatically. | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/desktop.html#connecting-your-radio",
    
    "relUrl": "/lt-rLT/user/desktop.html#connecting-your-radio"
  },"972": {
    "doc": "Desktop App",
    "title": "Feature Parity",
    "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Map | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | Site Planner | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | Settings | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | AI Assistant (Chirpy) | ✓* | ✗ | Google flavor Android only | . | App Functions (system AI) | ✓† | ✗ | Google flavor Android only | . *Chirpy AI requires Android 14+ on Google flavor builds with supported hardware. †App Functions exposes app actions to the Android system AI on Google flavor builds. See App Functions. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/desktop.html#feature-parity",
    
    "relUrl": "/lt-rLT/user/desktop.html#feature-parity"
  },"973": {
    "doc": "Desktop App",
    "title": "UI Differences",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. Keyboard Shortcuts . Shortcuts use ⌘ (Command) on macOS and Ctrl on Windows and Linux. (The Super / Windows key is not bound.) . | Shortcut | Action | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | Open Settings | . | ⌘/Ctrl+1 | Switch to Messages tab | . | ⌘/Ctrl+2 | Switch to Nodes tab | . | ⌘/Ctrl+3 | Switch to Map tab | . | ⌘/Ctrl+4 | Switch to Connect tab | . | ⌘/Ctrl+/ | Open About | . Window & System Tray . | Window resizing — responsive layout adapts to window dimensions | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | 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. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/desktop.html#ui-differences",
    
    "relUrl": "/lt-rLT/user/desktop.html#ui-differences"
  },"974": {
    "doc": "Desktop App",
    "title": "Built-in Documentation Browser",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. The browser supports full-text search across all documentation: . Individual doc pages render with full formatting: . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/desktop.html#built-in-documentation-browser",
    
    "relUrl": "/lt-rLT/user/desktop.html#built-in-documentation-browser"
  },"975": {
    "doc": "Desktop App",
    "title": "Building from Source",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Requirements: . | JDK 25 (Gradle can provision the toolchain itself via foojay) | No Android SDK required for desktop-only builds | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/desktop.html#building-from-source",
    
    "relUrl": "/lt-rLT/user/desktop.html#building-from-source"
  },"976": {
    "doc": "Desktop App",
    "title": "Known Limitations",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | 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) | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/desktop.html#known-limitations",
    
    "relUrl": "/lt-rLT/user/desktop.html#known-limitations"
  },"977": {
    "doc": "Desktop App",
    "title": "Related Topics",
    "content": ". | Connections — connection methods overview | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/desktop.html#related-topics",
    
    "relUrl": "/lt-rLT/user/desktop.html#related-topics"
  },"978": {
    "doc": "Desktop App",
    "title": "Desktop App",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/desktop.html",
    
    "relUrl": "/gl-rES/user/desktop.html"
  },"979": {
    "doc": "Desktop App",
    "title": "Installation",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from the releases page | Or build from source | . Windows . | Download the .msi or .exe installer from the releases page | Or build from source | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/desktop.html#installation",
    
    "relUrl": "/gl-rES/user/desktop.html#installation"
  },"980": {
    "doc": "Desktop App",
    "title": "Connecting Your Radio",
    "content": "USB Serial (Primary) . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . For network-connected radios: . | Enter the radio’s IP address and port (default: 4403). | Click Connect. | . Bluetooth (BLE) . Bluetooth Low Energy is supported on desktop via the Kable library: . | Ensure your system has a Bluetooth adapter. The app scans for nearby Meshtastic radios automatically. | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/desktop.html#connecting-your-radio",
    
    "relUrl": "/gl-rES/user/desktop.html#connecting-your-radio"
  },"981": {
    "doc": "Desktop App",
    "title": "Feature Parity",
    "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Map | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | Site Planner | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | Settings | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | AI Assistant (Chirpy) | ✓* | ✗ | Google flavor Android only | . | App Functions (system AI) | ✓† | ✗ | Google flavor Android only | . *Chirpy AI requires Android 14+ on Google flavor builds with supported hardware. †App Functions exposes app actions to the Android system AI on Google flavor builds. See App Functions. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/desktop.html#feature-parity",
    
    "relUrl": "/gl-rES/user/desktop.html#feature-parity"
  },"982": {
    "doc": "Desktop App",
    "title": "UI Differences",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. Keyboard Shortcuts . Shortcuts use ⌘ (Command) on macOS and Ctrl on Windows and Linux. (The Super / Windows key is not bound.) . | Shortcut | Action | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | Open Settings | . | ⌘/Ctrl+1 | Switch to Messages tab | . | ⌘/Ctrl+2 | Switch to Nodes tab | . | ⌘/Ctrl+3 | Switch to Map tab | . | ⌘/Ctrl+4 | Switch to Connect tab | . | ⌘/Ctrl+/ | Open About | . Window & System Tray . | Window resizing — responsive layout adapts to window dimensions | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | 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. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/desktop.html#ui-differences",
    
    "relUrl": "/gl-rES/user/desktop.html#ui-differences"
  },"983": {
    "doc": "Desktop App",
    "title": "Built-in Documentation Browser",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. The browser supports full-text search across all documentation: . Individual doc pages render with full formatting: . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/desktop.html#built-in-documentation-browser",
    
    "relUrl": "/gl-rES/user/desktop.html#built-in-documentation-browser"
  },"984": {
    "doc": "Desktop App",
    "title": "Building from Source",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Requirements: . | JDK 25 (Gradle can provision the toolchain itself via foojay) | No Android SDK required for desktop-only builds | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/desktop.html#building-from-source",
    
    "relUrl": "/gl-rES/user/desktop.html#building-from-source"
  },"985": {
    "doc": "Desktop App",
    "title": "Known Limitations",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | 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) | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/desktop.html#known-limitations",
    
    "relUrl": "/gl-rES/user/desktop.html#known-limitations"
  },"986": {
    "doc": "Desktop App",
    "title": "Related Topics",
    "content": ". | Connections — connection methods overview | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/desktop.html#related-topics",
    
    "relUrl": "/gl-rES/user/desktop.html#related-topics"
  },"987": {
    "doc": "デスクトップアプリ",
    "title": "デスクトップアプリ",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/desktop.html",
    
    "relUrl": "/ja-rJP/user/desktop.html"
  },"988": {
    "doc": "デスクトップアプリ",
    "title": "インストール",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | または、./gradlew :desktopApp:run を使ってソースからビルドします | . macOS . | Download the .dmg package from the releases page | または、ソースからビルドします | . Windows . | Download the .msi or .exe installer from the releases page | または、ソースからビルドします | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/desktop.html#%E3%82%A4%E3%83%B3%E3%82%B9%E3%83%88%E3%83%BC%E3%83%AB",
    
    "relUrl": "/ja-rJP/user/desktop.html#インストール"
  },"989": {
    "doc": "デスクトップアプリ",
    "title": "無線機を接続する",
    "content": "USB シリアル（主要） . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . ネットワーク接続された無線機の場合： . | 無線機の IP アドレスとポート（既定：4403）を入力します。 | 「接続」をクリックします。 | . Bluetooth（BLE） . Bluetooth Low Energy is supported on desktop via the Kable library: . | システムに Bluetooth アダプターがあることを確認します。アプリが近くの Meshtastic 無線機を自動的にスキャンします。 | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/desktop.html#%E7%84%A1%E7%B7%9A%E6%A9%9F%E3%82%92%E6%8E%A5%E7%B6%9A%E3%81%99%E3%82%8B",
    
    "relUrl": "/ja-rJP/user/desktop.html#無線機を接続する"
  },"990": {
    "doc": "デスクトップアプリ",
    "title": "機能の対応状況",
    "content": "| 機能 | Android | デスクトップ | 備考 | . | メッセージング | ✓ | ✓ | 完全対応 | . | ノードリスト | ✓ | ✓ | 完全対応 | . | マップ | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | サイトプランナー | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | 設定 | ✓ | ✓ | 完全対応 | . | Bluetooth（BLE） | ✓ | ✓ | デスクトップでは Kable 経由 | . | ファームウェアの更新 | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | 通知 | ✓ | ✓ | OS ネイティブの通知 | . | ウィジェット | ✓ | ✗ | Android のみ | . | AI アシスタント（Chirpy） | ✓* | ✗ | Google 版の Android のみ | . | アプリ機能（システム AI） | ✓† | ✗ | Google 版の Android のみ | . *Chirpy AI には、対応ハードウェアを備えた Google 版ビルドで Android 14 以降が必要です。 . †アプリ機能は、Google 版ビルドで、アプリの操作を Android のシステム AI に公開します。アプリ機能 を参照してください。 . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/desktop.html#%E6%A9%9F%E8%83%BD%E3%81%AE%E5%AF%BE%E5%BF%9C%E7%8A%B6%E6%B3%81",
    
    "relUrl": "/ja-rJP/user/desktop.html#機能の対応状況"
  },"991": {
    "doc": "デスクトップアプリ",
    "title": "UI の違い",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. キーボードショートカット . ショートカットは、macOS では ⌘（Command）、Windows と Linux では Ctrl を使用します。 （Super／Windows キーは割り当てられていません。） . | ショートカット | 操作 | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | 設定を開く | . | ⌘/Ctrl+1 | メッセージタブに切り替え | . | ⌘/Ctrl+2 | ノードタブに切り替え | . | ⌘/Ctrl+3 | マップタブに切り替え | . | ⌘/Ctrl+4 | 接続タブに切り替え | . | ⌘/Ctrl+/ | バージョン情報を開く | . ウィンドウとシステムトレイ . | ウィンドウのサイズ変更：レスポンシブなレイアウトがウィンドウの寸法に合わせて調整されます | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | トレイメニュー：トレイアイコンを右クリックして、ウィンドウ表示または終了します | マウス操作：ホバー状態と標準的なデスクトップのナビゲーション | . 通知の設定 . The desktop app provides in-app toggles for controlling which notifications are shown. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/desktop.html#ui-%E3%81%AE%E9%81%95%E3%81%84",
    
    "relUrl": "/ja-rJP/user/desktop.html#ui-の違い"
  },"992": {
    "doc": "デスクトップアプリ",
    "title": "組み込みのドキュメントブラウザー",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. ブラウザーは、すべてのドキュメントを対象とした全文検索に対応しています： . 個々のドキュメントページは、完全な書式で表示されます： . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/desktop.html#%E7%B5%84%E3%81%BF%E8%BE%BC%E3%81%BF%E3%81%AE%E3%83%89%E3%82%AD%E3%83%A5%E3%83%A1%E3%83%B3%E3%83%88%E3%83%96%E3%83%A9%E3%82%A6%E3%82%B6%E3%83%BC",
    
    "relUrl": "/ja-rJP/user/desktop.html#組み込みのドキュメントブラウザー"
  },"993": {
    "doc": "デスクトップアプリ",
    "title": "ソースからビルドする",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . 要件： . | JDK 25 (Gradle can provision the toolchain itself via foojay) | デスクトップのみのビルドに Android SDK は不要です | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/desktop.html#%E3%82%BD%E3%83%BC%E3%82%B9%E3%81%8B%E3%82%89%E3%83%93%E3%83%AB%E3%83%89%E3%81%99%E3%82%8B",
    
    "relUrl": "/ja-rJP/user/desktop.html#ソースからビルドする"
  },"994": {
    "doc": "デスクトップアプリ",
    "title": "既知の制限",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | 一部の Android 固有の機能（ウィジェット、特定の通知チャンネル）は利用できません | Compose Desktop を実行する低スペックのハードウェアでは、パフォーマンスが変わることがあります | デスクトップでは BLE のボンディングはまだサポートされていません（ペアリングはボンディングなしで機能します） | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/desktop.html#%E6%97%A2%E7%9F%A5%E3%81%AE%E5%88%B6%E9%99%90",
    
    "relUrl": "/ja-rJP/user/desktop.html#既知の制限"
  },"995": {
    "doc": "デスクトップアプリ",
    "title": "関連トピック",
    "content": ". | コネクション：接続方法の概要 | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/desktop.html#%E9%96%A2%E9%80%A3%E3%83%88%E3%83%94%E3%83%83%E3%82%AF",
    
    "relUrl": "/ja-rJP/user/desktop.html#関連トピック"
  },"996": {
    "doc": "Desktop App",
    "title": "Desktop App",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/desktop.html",
    
    "relUrl": "/de-rDE/user/desktop.html"
  },"997": {
    "doc": "Desktop App",
    "title": "Installation",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from the releases page | Or build from source | . Windows . | Download the .msi or .exe installer from the releases page | Or build from source | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/desktop.html#installation",
    
    "relUrl": "/de-rDE/user/desktop.html#installation"
  },"998": {
    "doc": "Desktop App",
    "title": "Connecting Your Radio",
    "content": "USB Serial (Primary) . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . For network-connected radios: . | Enter the radio’s IP address and port (default: 4403). | Click Connect. | . Bluetooth (BLE) . Bluetooth Low Energy is supported on desktop via the Kable library: . | Ensure your system has a Bluetooth adapter. The app scans for nearby Meshtastic radios automatically. | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/desktop.html#connecting-your-radio",
    
    "relUrl": "/de-rDE/user/desktop.html#connecting-your-radio"
  },"999": {
    "doc": "Desktop App",
    "title": "Feature Parity",
    "content": "| Funktion | Android | Desktop | Knoten | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Karte | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | Site Planner | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | Einstellungen | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Aktualisierung | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | Benachrichtigungen | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | AI Assistant (Chirpy) | ✓* | ✗ | Google flavor Android only | . | App Functions (system AI) | ✓† | ✗ | Google flavor Android only | . *Chirpy AI requires Android 14+ on Google flavor builds with supported hardware. †App Functions exposes app actions to the Android system AI on Google flavor builds. See App Functions. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/desktop.html#feature-parity",
    
    "relUrl": "/de-rDE/user/desktop.html#feature-parity"
  },"1000": {
    "doc": "Desktop App",
    "title": "UI Differences",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. Tastaturkürzel . Shortcuts use ⌘ (Command) on macOS and Ctrl on Windows and Linux. (The Super / Windows key is not bound.) . | Tastaturkürzel | Action | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | Einstellungen öffnen | . | ⌘/Ctrl+1 | Switch to Messages tab | . | ⌘/Ctrl+2 | Switch to Nodes tab | . | ⌘/Ctrl+3 | Switch to Map tab | . | ⌘/Ctrl+4 | Switch to Connect tab | . | ⌘/Ctrl+/ | Open About | . Window & System Tray . | Window resizing — responsive layout adapts to window dimensions | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | 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. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/desktop.html#ui-differences",
    
    "relUrl": "/de-rDE/user/desktop.html#ui-differences"
  },"1001": {
    "doc": "Desktop App",
    "title": "Built-in Documentation Browser",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. The browser supports full-text search across all documentation: . Individual doc pages render with full formatting: . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/desktop.html#built-in-documentation-browser",
    
    "relUrl": "/de-rDE/user/desktop.html#built-in-documentation-browser"
  },"1002": {
    "doc": "Desktop App",
    "title": "Building from Source",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Voraussetzungen: . | JDK 25 (Gradle can provision the toolchain itself via foojay) | No Android SDK required for desktop-only builds | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/desktop.html#building-from-source",
    
    "relUrl": "/de-rDE/user/desktop.html#building-from-source"
  },"1003": {
    "doc": "Desktop App",
    "title": "Bekannte Einschränkungen",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | 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) | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/desktop.html#bekannte-einschr%C3%A4nkungen",
    
    "relUrl": "/de-rDE/user/desktop.html#bekannte-einschränkungen"
  },"1004": {
    "doc": "Desktop App",
    "title": "Related Topics",
    "content": ". | Connections — connection methods overview | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/desktop.html#related-topics",
    
    "relUrl": "/de-rDE/user/desktop.html#related-topics"
  },"1005": {
    "doc": "Desktop App",
    "title": "Desktop App",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/desktop.html",
    
    "relUrl": "/ar-rSA/user/desktop.html"
  },"1006": {
    "doc": "Desktop App",
    "title": "Installation",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from the releases page | Or build from source | . Windows . | Download the .msi or .exe installer from the releases page | Or build from source | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/desktop.html#installation",
    
    "relUrl": "/ar-rSA/user/desktop.html#installation"
  },"1007": {
    "doc": "Desktop App",
    "title": "Connecting Your Radio",
    "content": "USB Serial (Primary) . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . For network-connected radios: . | Enter the radio’s IP address and port (default: 4403). | Click Connect. | . Bluetooth (BLE) . Bluetooth Low Energy is supported on desktop via the Kable library: . | Ensure your system has a Bluetooth adapter. The app scans for nearby Meshtastic radios automatically. | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/desktop.html#connecting-your-radio",
    
    "relUrl": "/ar-rSA/user/desktop.html#connecting-your-radio"
  },"1008": {
    "doc": "Desktop App",
    "title": "Feature Parity",
    "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | الخريطة | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | Site Planner | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | الإعدادات | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | AI Assistant (Chirpy) | ✓* | ✗ | Google flavor Android only | . | App Functions (system AI) | ✓† | ✗ | Google flavor Android only | . *Chirpy AI requires Android 14+ on Google flavor builds with supported hardware. †App Functions exposes app actions to the Android system AI on Google flavor builds. See App Functions. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/desktop.html#feature-parity",
    
    "relUrl": "/ar-rSA/user/desktop.html#feature-parity"
  },"1009": {
    "doc": "Desktop App",
    "title": "UI Differences",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. Keyboard Shortcuts . Shortcuts use ⌘ (Command) on macOS and Ctrl on Windows and Linux. (The Super / Windows key is not bound.) . | Shortcut | Action | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | Open Settings | . | ⌘/Ctrl+1 | Switch to Messages tab | . | ⌘/Ctrl+2 | Switch to Nodes tab | . | ⌘/Ctrl+3 | Switch to Map tab | . | ⌘/Ctrl+4 | Switch to Connect tab | . | ⌘/Ctrl+/ | Open About | . Window & System Tray . | Window resizing — responsive layout adapts to window dimensions | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | 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. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/desktop.html#ui-differences",
    
    "relUrl": "/ar-rSA/user/desktop.html#ui-differences"
  },"1010": {
    "doc": "Desktop App",
    "title": "Built-in Documentation Browser",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. The browser supports full-text search across all documentation: . Individual doc pages render with full formatting: . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/desktop.html#built-in-documentation-browser",
    
    "relUrl": "/ar-rSA/user/desktop.html#built-in-documentation-browser"
  },"1011": {
    "doc": "Desktop App",
    "title": "Building from Source",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Requirements: . | JDK 25 (Gradle can provision the toolchain itself via foojay) | No Android SDK required for desktop-only builds | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/desktop.html#building-from-source",
    
    "relUrl": "/ar-rSA/user/desktop.html#building-from-source"
  },"1012": {
    "doc": "Desktop App",
    "title": "Known Limitations",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | 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) | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/desktop.html#known-limitations",
    
    "relUrl": "/ar-rSA/user/desktop.html#known-limitations"
  },"1013": {
    "doc": "Desktop App",
    "title": "Related Topics",
    "content": ". | Connections — connection methods overview | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/desktop.html#related-topics",
    
    "relUrl": "/ar-rSA/user/desktop.html#related-topics"
  },"1014": {
    "doc": "Desktop App",
    "title": "Desktop App",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/desktop.html",
    
    "relUrl": "/hr-rHR/user/desktop.html"
  },"1015": {
    "doc": "Desktop App",
    "title": "Installation",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from the releases page | Or build from source | . Windows . | Download the .msi or .exe installer from the releases page | Or build from source | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/desktop.html#installation",
    
    "relUrl": "/hr-rHR/user/desktop.html#installation"
  },"1016": {
    "doc": "Desktop App",
    "title": "Connecting Your Radio",
    "content": "USB Serial (Primary) . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . For network-connected radios: . | Enter the radio’s IP address and port (default: 4403). | Click Connect. | . Bluetooth (BLE) . Bluetooth Low Energy is supported on desktop via the Kable library: . | Ensure your system has a Bluetooth adapter. The app scans for nearby Meshtastic radios automatically. | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/desktop.html#connecting-your-radio",
    
    "relUrl": "/hr-rHR/user/desktop.html#connecting-your-radio"
  },"1017": {
    "doc": "Desktop App",
    "title": "Feature Parity",
    "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Map | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | Site Planner | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | Settings | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | AI Assistant (Chirpy) | ✓* | ✗ | Google flavor Android only | . | App Functions (system AI) | ✓† | ✗ | Google flavor Android only | . *Chirpy AI requires Android 14+ on Google flavor builds with supported hardware. †App Functions exposes app actions to the Android system AI on Google flavor builds. See App Functions. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/desktop.html#feature-parity",
    
    "relUrl": "/hr-rHR/user/desktop.html#feature-parity"
  },"1018": {
    "doc": "Desktop App",
    "title": "UI Differences",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. Keyboard Shortcuts . Shortcuts use ⌘ (Command) on macOS and Ctrl on Windows and Linux. (The Super / Windows key is not bound.) . | Shortcut | Action | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | Open Settings | . | ⌘/Ctrl+1 | Switch to Messages tab | . | ⌘/Ctrl+2 | Switch to Nodes tab | . | ⌘/Ctrl+3 | Switch to Map tab | . | ⌘/Ctrl+4 | Switch to Connect tab | . | ⌘/Ctrl+/ | Open About | . Window & System Tray . | Window resizing — responsive layout adapts to window dimensions | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | 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. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/desktop.html#ui-differences",
    
    "relUrl": "/hr-rHR/user/desktop.html#ui-differences"
  },"1019": {
    "doc": "Desktop App",
    "title": "Built-in Documentation Browser",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. The browser supports full-text search across all documentation: . Individual doc pages render with full formatting: . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/desktop.html#built-in-documentation-browser",
    
    "relUrl": "/hr-rHR/user/desktop.html#built-in-documentation-browser"
  },"1020": {
    "doc": "Desktop App",
    "title": "Building from Source",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Requirements: . | JDK 25 (Gradle can provision the toolchain itself via foojay) | No Android SDK required for desktop-only builds | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/desktop.html#building-from-source",
    
    "relUrl": "/hr-rHR/user/desktop.html#building-from-source"
  },"1021": {
    "doc": "Desktop App",
    "title": "Known Limitations",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | 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) | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/desktop.html#known-limitations",
    
    "relUrl": "/hr-rHR/user/desktop.html#known-limitations"
  },"1022": {
    "doc": "Desktop App",
    "title": "Related Topics",
    "content": ". | Connections — connection methods overview | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/desktop.html#related-topics",
    
    "relUrl": "/hr-rHR/user/desktop.html#related-topics"
  },"1023": {
    "doc": "Desktop App",
    "title": "Desktop App",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/desktop.html",
    
    "relUrl": "/pt-rPT/user/desktop.html"
  },"1024": {
    "doc": "Desktop App",
    "title": "Installation",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from the releases page | Or build from source | . Windows . | Download the .msi or .exe installer from the releases page | Or build from source | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/desktop.html#installation",
    
    "relUrl": "/pt-rPT/user/desktop.html#installation"
  },"1025": {
    "doc": "Desktop App",
    "title": "Connecting Your Radio",
    "content": "USB Serial (Primary) . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . For network-connected radios: . | Enter the radio’s IP address and port (default: 4403). | Click Connect. | . Bluetooth (BLE) . Bluetooth Low Energy is supported on desktop via the Kable library: . | Ensure your system has a Bluetooth adapter. The app scans for nearby Meshtastic radios automatically. | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/desktop.html#connecting-your-radio",
    
    "relUrl": "/pt-rPT/user/desktop.html#connecting-your-radio"
  },"1026": {
    "doc": "Desktop App",
    "title": "Feature Parity",
    "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Mapa | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | Site Planner | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | Definições | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | AI Assistant (Chirpy) | ✓* | ✗ | Google flavor Android only | . | App Functions (system AI) | ✓† | ✗ | Google flavor Android only | . *Chirpy AI requires Android 14+ on Google flavor builds with supported hardware. †App Functions exposes app actions to the Android system AI on Google flavor builds. See App Functions. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/desktop.html#feature-parity",
    
    "relUrl": "/pt-rPT/user/desktop.html#feature-parity"
  },"1027": {
    "doc": "Desktop App",
    "title": "UI Differences",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. Keyboard Shortcuts . Shortcuts use ⌘ (Command) on macOS and Ctrl on Windows and Linux. (The Super / Windows key is not bound.) . | Shortcut | Action | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | Open Settings | . | ⌘/Ctrl+1 | Switch to Messages tab | . | ⌘/Ctrl+2 | Switch to Nodes tab | . | ⌘/Ctrl+3 | Switch to Map tab | . | ⌘/Ctrl+4 | Switch to Connect tab | . | ⌘/Ctrl+/ | Open About | . Window & System Tray . | Window resizing — responsive layout adapts to window dimensions | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | 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. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/desktop.html#ui-differences",
    
    "relUrl": "/pt-rPT/user/desktop.html#ui-differences"
  },"1028": {
    "doc": "Desktop App",
    "title": "Built-in Documentation Browser",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. The browser supports full-text search across all documentation: . Individual doc pages render with full formatting: . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/desktop.html#built-in-documentation-browser",
    
    "relUrl": "/pt-rPT/user/desktop.html#built-in-documentation-browser"
  },"1029": {
    "doc": "Desktop App",
    "title": "Building from Source",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Requirements: . | JDK 25 (Gradle can provision the toolchain itself via foojay) | No Android SDK required for desktop-only builds | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/desktop.html#building-from-source",
    
    "relUrl": "/pt-rPT/user/desktop.html#building-from-source"
  },"1030": {
    "doc": "Desktop App",
    "title": "Known Limitations",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | 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) | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/desktop.html#known-limitations",
    
    "relUrl": "/pt-rPT/user/desktop.html#known-limitations"
  },"1031": {
    "doc": "Desktop App",
    "title": "Related Topics",
    "content": ". | Connections — connection methods overview | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/desktop.html#related-topics",
    
    "relUrl": "/pt-rPT/user/desktop.html#related-topics"
  },"1032": {
    "doc": "Desktop App",
    "title": "Desktop App",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/desktop.html",
    
    "relUrl": "/pl-rPL/user/desktop.html"
  },"1033": {
    "doc": "Desktop App",
    "title": "Installation",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from the releases page | Or build from source | . Windows . | Download the .msi or .exe installer from the releases page | Or build from source | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/desktop.html#installation",
    
    "relUrl": "/pl-rPL/user/desktop.html#installation"
  },"1034": {
    "doc": "Desktop App",
    "title": "Connecting Your Radio",
    "content": "USB Serial (Primary) . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . For network-connected radios: . | Enter the radio’s IP address and port (default: 4403). | Click Connect. | . Bluetooth (BLE) . Bluetooth Low Energy is supported on desktop via the Kable library: . | Ensure your system has a Bluetooth adapter. The app scans for nearby Meshtastic radios automatically. | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/desktop.html#connecting-your-radio",
    
    "relUrl": "/pl-rPL/user/desktop.html#connecting-your-radio"
  },"1035": {
    "doc": "Desktop App",
    "title": "Feature Parity",
    "content": "| Feature | Android | Desktop | Notatki | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Mapa | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | Site Planner | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | Ustawienia | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Aktualizacja oprogramowania | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | AI Assistant (Chirpy) | ✓* | ✗ | Google flavor Android only | . | App Functions (system AI) | ✓† | ✗ | Google flavor Android only | . *Chirpy AI requires Android 14+ on Google flavor builds with supported hardware. †App Functions exposes app actions to the Android system AI on Google flavor builds. See App Functions. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/desktop.html#feature-parity",
    
    "relUrl": "/pl-rPL/user/desktop.html#feature-parity"
  },"1036": {
    "doc": "Desktop App",
    "title": "UI Differences",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. Keyboard Shortcuts . Shortcuts use ⌘ (Command) on macOS and Ctrl on Windows and Linux. (The Super / Windows key is not bound.) . | Shortcut | Action | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | Open Settings | . | ⌘/Ctrl+1 | Switch to Messages tab | . | ⌘/Ctrl+2 | Switch to Nodes tab | . | ⌘/Ctrl+3 | Switch to Map tab | . | ⌘/Ctrl+4 | Switch to Connect tab | . | ⌘/Ctrl+/ | Open About | . Window & System Tray . | Window resizing — responsive layout adapts to window dimensions | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | 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. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/desktop.html#ui-differences",
    
    "relUrl": "/pl-rPL/user/desktop.html#ui-differences"
  },"1037": {
    "doc": "Desktop App",
    "title": "Built-in Documentation Browser",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. The browser supports full-text search across all documentation: . Individual doc pages render with full formatting: . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/desktop.html#built-in-documentation-browser",
    
    "relUrl": "/pl-rPL/user/desktop.html#built-in-documentation-browser"
  },"1038": {
    "doc": "Desktop App",
    "title": "Building from Source",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Requirements: . | JDK 25 (Gradle can provision the toolchain itself via foojay) | No Android SDK required for desktop-only builds | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/desktop.html#building-from-source",
    
    "relUrl": "/pl-rPL/user/desktop.html#building-from-source"
  },"1039": {
    "doc": "Desktop App",
    "title": "Known Limitations",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | 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) | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/desktop.html#known-limitations",
    
    "relUrl": "/pl-rPL/user/desktop.html#known-limitations"
  },"1040": {
    "doc": "Desktop App",
    "title": "Related Topics",
    "content": ". | Connections — connection methods overview | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/desktop.html#related-topics",
    
    "relUrl": "/pl-rPL/user/desktop.html#related-topics"
  },"1041": {
    "doc": "Desktop App",
    "title": "Desktop App",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/desktop.html",
    
    "relUrl": "/zh-rCN/user/desktop.html"
  },"1042": {
    "doc": "Desktop App",
    "title": "安装",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from the releases page | Or build from source | . Windows . | Download the .msi or .exe installer from the releases page | Or build from source | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/desktop.html#%E5%AE%89%E8%A3%85",
    
    "relUrl": "/zh-rCN/user/desktop.html#安装"
  },"1043": {
    "doc": "Desktop App",
    "title": "Connecting Your Radio",
    "content": "USB Serial (Primary) . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . For network-connected radios: . | Enter the radio’s IP address and port (default: 4403). | Click Connect. | . Bluetooth (BLE) . Bluetooth Low Energy is supported on desktop via the Kable library: . | Ensure your system has a Bluetooth adapter. The app scans for nearby Meshtastic radios automatically. | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/desktop.html#connecting-your-radio",
    
    "relUrl": "/zh-rCN/user/desktop.html#connecting-your-radio"
  },"1044": {
    "doc": "Desktop App",
    "title": "Feature Parity",
    "content": "| Feature | Android | Desktop | 注 | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | 地图 | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | 站点规划器 | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | 设置 | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | 固件更新 | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | AI Assistant (Chirpy) | ✓* | ✗ | Google flavor Android only | . | App Functions (system AI) | ✓† | ✗ | Google flavor Android only | . *Chirpy AI requires Android 14+ on Google flavor builds with supported hardware. †App Functions exposes app actions to the Android system AI on Google flavor builds. See App Functions. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/desktop.html#feature-parity",
    
    "relUrl": "/zh-rCN/user/desktop.html#feature-parity"
  },"1045": {
    "doc": "Desktop App",
    "title": "UI Differences",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. Keyboard Shortcuts . Shortcuts use ⌘ (Command) on macOS and Ctrl on Windows and Linux. (The Super / Windows key is not bound.) . | Shortcut | Action | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | 打开设置 | . | ⌘/Ctrl+1 | Switch to Messages tab | . | ⌘/Ctrl+2 | Switch to Nodes tab | . | ⌘/Ctrl+3 | Switch to Map tab | . | ⌘/Ctrl+4 | Switch to Connect tab | . | ⌘/Ctrl+/ | Open About | . Window & System Tray . | Window resizing — responsive layout adapts to window dimensions | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | 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. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/desktop.html#ui-differences",
    
    "relUrl": "/zh-rCN/user/desktop.html#ui-differences"
  },"1046": {
    "doc": "Desktop App",
    "title": "Built-in Documentation Browser",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. The browser supports full-text search across all documentation: . Individual doc pages render with full formatting: . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/desktop.html#built-in-documentation-browser",
    
    "relUrl": "/zh-rCN/user/desktop.html#built-in-documentation-browser"
  },"1047": {
    "doc": "Desktop App",
    "title": "Building from Source",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Requirements: . | JDK 25 (Gradle can provision the toolchain itself via foojay) | No Android SDK required for desktop-only builds | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/desktop.html#building-from-source",
    
    "relUrl": "/zh-rCN/user/desktop.html#building-from-source"
  },"1048": {
    "doc": "Desktop App",
    "title": "Known Limitations",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | 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) | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/desktop.html#known-limitations",
    
    "relUrl": "/zh-rCN/user/desktop.html#known-limitations"
  },"1049": {
    "doc": "Desktop App",
    "title": "Related Topics",
    "content": ". | Connections — connection methods overview | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/desktop.html#related-topics",
    
    "relUrl": "/zh-rCN/user/desktop.html#related-topics"
  },"1050": {
    "doc": "Desktop App",
    "title": "Desktop App",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/desktop.html",
    
    "relUrl": "/sq-rAL/user/desktop.html"
  },"1051": {
    "doc": "Desktop App",
    "title": "Installation",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from the releases page | Or build from source | . Windows . | Download the .msi or .exe installer from the releases page | Or build from source | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/desktop.html#installation",
    
    "relUrl": "/sq-rAL/user/desktop.html#installation"
  },"1052": {
    "doc": "Desktop App",
    "title": "Connecting Your Radio",
    "content": "USB Serial (Primary) . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . For network-connected radios: . | Enter the radio’s IP address and port (default: 4403). | Click Connect. | . Bluetooth (BLE) . Bluetooth Low Energy is supported on desktop via the Kable library: . | Ensure your system has a Bluetooth adapter. The app scans for nearby Meshtastic radios automatically. | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/desktop.html#connecting-your-radio",
    
    "relUrl": "/sq-rAL/user/desktop.html#connecting-your-radio"
  },"1053": {
    "doc": "Desktop App",
    "title": "Feature Parity",
    "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Map | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | Site Planner | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | Settings | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | AI Assistant (Chirpy) | ✓* | ✗ | Google flavor Android only | . | App Functions (system AI) | ✓† | ✗ | Google flavor Android only | . *Chirpy AI requires Android 14+ on Google flavor builds with supported hardware. †App Functions exposes app actions to the Android system AI on Google flavor builds. See App Functions. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/desktop.html#feature-parity",
    
    "relUrl": "/sq-rAL/user/desktop.html#feature-parity"
  },"1054": {
    "doc": "Desktop App",
    "title": "UI Differences",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. Keyboard Shortcuts . Shortcuts use ⌘ (Command) on macOS and Ctrl on Windows and Linux. (The Super / Windows key is not bound.) . | Shortcut | Action | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | Open Settings | . | ⌘/Ctrl+1 | Switch to Messages tab | . | ⌘/Ctrl+2 | Switch to Nodes tab | . | ⌘/Ctrl+3 | Switch to Map tab | . | ⌘/Ctrl+4 | Switch to Connect tab | . | ⌘/Ctrl+/ | Open About | . Window & System Tray . | Window resizing — responsive layout adapts to window dimensions | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | 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. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/desktop.html#ui-differences",
    
    "relUrl": "/sq-rAL/user/desktop.html#ui-differences"
  },"1055": {
    "doc": "Desktop App",
    "title": "Built-in Documentation Browser",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. The browser supports full-text search across all documentation: . Individual doc pages render with full formatting: . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/desktop.html#built-in-documentation-browser",
    
    "relUrl": "/sq-rAL/user/desktop.html#built-in-documentation-browser"
  },"1056": {
    "doc": "Desktop App",
    "title": "Building from Source",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Requirements: . | JDK 25 (Gradle can provision the toolchain itself via foojay) | No Android SDK required for desktop-only builds | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/desktop.html#building-from-source",
    
    "relUrl": "/sq-rAL/user/desktop.html#building-from-source"
  },"1057": {
    "doc": "Desktop App",
    "title": "Known Limitations",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | 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) | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/desktop.html#known-limitations",
    
    "relUrl": "/sq-rAL/user/desktop.html#known-limitations"
  },"1058": {
    "doc": "Desktop App",
    "title": "Related Topics",
    "content": ". | Connections — connection methods overview | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/desktop.html#related-topics",
    
    "relUrl": "/sq-rAL/user/desktop.html#related-topics"
  },"1059": {
    "doc": "桌面版應用程式",
    "title": "桌面版應用程式",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/desktop.html",
    
    "relUrl": "/zh-rTW/user/desktop.html"
  },"1060": {
    "doc": "桌面版應用程式",
    "title": "安裝",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | 或使用 ./gradlew :desktopApp:run 從原始碼自行建置 | . macOS . | Download the .dmg package from the releases page | 或從原始碼自行建置 | . Windows . | Download the .msi or .exe installer from the releases page | 或從原始碼自行建置 | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/desktop.html#%E5%AE%89%E8%A3%9D",
    
    "relUrl": "/zh-rTW/user/desktop.html#安裝"
  },"1061": {
    "doc": "桌面版應用程式",
    "title": "連接您的無線電裝置",
    "content": "USB 序列埠（主要方式） . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . 若使用網路連線的無線電裝置： . | 輸入無線電裝置的 IP 位址與連接埠（預設：4403）。 | 點選「連線」。 | . 藍牙（BLE） . Bluetooth Low Energy is supported on desktop via the Kable library: . | 請確認您的系統配備藍牙介面卡。應用程式將自動掃描附近的 Meshtastic 無線電裝置。 | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/desktop.html#%E9%80%A3%E6%8E%A5%E6%82%A8%E7%9A%84%E7%84%A1%E7%B7%9A%E9%9B%BB%E8%A3%9D%E7%BD%AE",
    
    "relUrl": "/zh-rTW/user/desktop.html#連接您的無線電裝置"
  },"1062": {
    "doc": "桌面版應用程式",
    "title": "功能對等性",
    "content": "| 功能 | Android | 桌面版 | 備註 | . | 訊息傳送 | ✓ | ✓ | 完全對等 | . | 節點清單 | ✓ | ✓ | 完全對等 | . | 地圖 | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | Site Planner | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | 設定 | ✓ | ✓ | 完全對等 | . | 藍牙（BLE） | ✓ | ✓ | 桌面版透過 Kable 支援 | . | 韌體更新 | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | 通知 | ✓ | ✓ | 原生作業系統通知 | . | 小工具 | ✓ | ✗ | 僅限 Android | . | AI 助理（Chirpy） | ✓* | ✗ | 僅限 Google 版 Android | . | App Functions (system AI) | ✓† | ✗ | 僅限 Google 版 Android | . *Chirpy AI 需要 Google 版 Android 14 以上版本，且須搭配支援的硬體。 . †App Functions exposes app actions to the Android system AI on Google flavor builds. See App Functions. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/desktop.html#%E5%8A%9F%E8%83%BD%E5%B0%8D%E7%AD%89%E6%80%A7",
    
    "relUrl": "/zh-rTW/user/desktop.html#功能對等性"
  },"1063": {
    "doc": "桌面版應用程式",
    "title": "介面差異",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. 鍵盤快速鍵 . Shortcuts use ⌘ (Command) on macOS and Ctrl on Windows and Linux. (The Super / Windows key is not bound.) . | 快速鍵 | 動作 | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | 開啟設定 | . | ⌘/Ctrl+1 | 切換至訊息頁籤 | . | ⌘/Ctrl+2 | 切換至節點頁籤 | . | ⌘/Ctrl+3 | 切換至地圖頁籤 | . | ⌘/Ctrl+4 | 切換至連線頁籤 | . | ⌘/Ctrl+/ | Open About | . 視窗與系統匣 . | 調整視窗大小 — 響應式版面配置可依視窗尺寸自動調整 | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | 匣列選單 — 在系統匣圖示上按右鍵，可顯示視窗或結束程式 | 滑鼠互動 — 支援停駐狀態與標準桌面導覽操作 | . 通知偏好設定 . The desktop app provides in-app toggles for controlling which notifications are shown. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/desktop.html#%E4%BB%8B%E9%9D%A2%E5%B7%AE%E7%95%B0",
    
    "relUrl": "/zh-rTW/user/desktop.html#介面差異"
  },"1064": {
    "doc": "桌面版應用程式",
    "title": "內建文件瀏覽器",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. 瀏覽器支援跨所有文件的全文搜尋： . 各文件頁面以完整格式呈現： . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/desktop.html#%E5%85%A7%E5%BB%BA%E6%96%87%E4%BB%B6%E7%80%8F%E8%A6%BD%E5%99%A8",
    
    "relUrl": "/zh-rTW/user/desktop.html#內建文件瀏覽器"
  },"1065": {
    "doc": "桌面版應用程式",
    "title": "從原始碼建置",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . 需求： . | JDK 25 (Gradle can provision the toolchain itself via foojay) | 純桌面版建置不需要 Android SDK | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/desktop.html#%E5%BE%9E%E5%8E%9F%E5%A7%8B%E7%A2%BC%E5%BB%BA%E7%BD%AE",
    
    "relUrl": "/zh-rTW/user/desktop.html#從原始碼建置"
  },"1066": {
    "doc": "桌面版應用程式",
    "title": "已知限制",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | 部分 Android 專屬功能（小工具、特定通知頻道）無法使用 | 在低規格硬體上執行 Compose Desktop 時，效能可能有所不同 | 桌面版尚不支援 BLE 綁定（配對功能可在不綁定的情況下正常使用） | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/desktop.html#%E5%B7%B2%E7%9F%A5%E9%99%90%E5%88%B6",
    
    "relUrl": "/zh-rTW/user/desktop.html#已知限制"
  },"1067": {
    "doc": "桌面版應用程式",
    "title": "相關主題",
    "content": ". | 〔連線〕(connections) — 連線方式概覽 | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/desktop.html#%E7%9B%B8%E9%97%9C%E4%B8%BB%E9%A1%8C",
    
    "relUrl": "/zh-rTW/user/desktop.html#相關主題"
  },"1068": {
    "doc": "Desktop App",
    "title": "Desktop App",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/desktop.html",
    
    "relUrl": "/et-rEE/user/desktop.html"
  },"1069": {
    "doc": "Desktop App",
    "title": "Paigaldus",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from the releases page | Or build from source | . Windows . | Download the .msi or .exe installer from the releases page | Or build from source | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/desktop.html#paigaldus",
    
    "relUrl": "/et-rEE/user/desktop.html#paigaldus"
  },"1070": {
    "doc": "Desktop App",
    "title": "Connecting Your Radio",
    "content": "USB port (esmane) . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . For network-connected radios: . | Sisesta raadio IP-aadress ja port (vaikimisi: 4403). | Klõpsa Ühenda. | . Sinihammas (BLE) . Bluetooth Low Energy is supported on desktop via the Kable library: . | Veendu, et süsteemil on sinihamba adapter. Rakendus otsib automaatselt lähedalasuvaid Meshtastic raadioid. | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/desktop.html#connecting-your-radio",
    
    "relUrl": "/et-rEE/user/desktop.html#connecting-your-radio"
  },"1071": {
    "doc": "Desktop App",
    "title": "Feature Parity",
    "content": "| Feature | Android | Desktop | Sõnumid | . | Messaging | ✓ | ✓ | Full parity | . | Sõlmede loend | ✓ | ✓ | Full parity | . | Kaart | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | Saidi planeerija | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | Sätted | ✓ | ✓ | Full parity | . | Sinihammas (BLE) | ✓ | ✓ | Kable’i kaudu töölauale | . | Püsivara uuendus | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | Märguanded | ✓ | ✓ | Emakeelsed op.süsteemi märguanded | . | Widgets | ✓ | ✗ | Android-only | . | TI assistent (Chirpy) | ✓* | ✗ | Google flavor Android only | . | Rakenduse funktsioonid (süstemi TI) | ✓† | ✗ | Google flavor Android only | . *Chirpy tehisintellekti jaoks on vaja Google’i eriversioonidel Android 14+ ja toetatud riistvaraga. †Rakendusfunktsioonid paljastavad rakenduse toimingud Androidi süsteemi tehisintellektile Google’i eri versioonides. Vaata Rakenduse funktsioonid. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/desktop.html#feature-parity",
    
    "relUrl": "/et-rEE/user/desktop.html#feature-parity"
  },"1072": {
    "doc": "Desktop App",
    "title": "UI Differences",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. Kiirklahvid . Otseteed kasutavad macOS-is ⌘ (Command) ja Windowsis ning Linuxis Ctrl. (Super/Windowsi võti pole seotud.) . | Otsetee | Action | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | Ava sätted | . | ⌘/Ctrl+1 | Switch to Messages tab | . | ⌘/Ctrl+2 | Switch to Nodes tab | . | ⌘/Ctrl+3 | Lülitu kaardi vahekaardile | . | ⌘/Ctrl+4 | Switch to Connect tab | . | ⌘/Ctrl+/ | Open About | . Window & System Tray . | Window resizing — responsive layout adapts to window dimensions | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | Salvemenüü – paremklõpsa salveikoonil akna kuvamiseks või sulgemiseks | Hiire interaktsioon — hõljumisseisundid ja standardne töölaua navigeerimine | . Notification Preferences . The desktop app provides in-app toggles for controlling which notifications are shown. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/desktop.html#ui-differences",
    
    "relUrl": "/et-rEE/user/desktop.html#ui-differences"
  },"1073": {
    "doc": "Desktop App",
    "title": "Sisseehitatud dokumentatsioonibrauser",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. Brauser toetab täistekstiotsingut kogu dokumentatsioonis: . Individual doc pages render with full formatting: . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/desktop.html#sisseehitatud-dokumentatsioonibrauser",
    
    "relUrl": "/et-rEE/user/desktop.html#sisseehitatud-dokumentatsioonibrauser"
  },"1074": {
    "doc": "Desktop App",
    "title": "Building from Source",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Nõuded: . | JDK 25 (Gradle can provision the toolchain itself via foojay) | No Android SDK required for desktop-only builds | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/desktop.html#building-from-source",
    
    "relUrl": "/et-rEE/user/desktop.html#building-from-source"
  },"1075": {
    "doc": "Desktop App",
    "title": "Known Limitations",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | Mõned Androidile omased funktsioonid (vidinad, kindlad teavituskanalid) pole saadaval | Performance may vary on low-spec hardware running Compose Desktop | Lauaarvutid ei toeta veel BLE liitmist (sidumine toimib ilma ühendamiseta) | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/desktop.html#known-limitations",
    
    "relUrl": "/et-rEE/user/desktop.html#known-limitations"
  },"1076": {
    "doc": "Desktop App",
    "title": "Seotud teemad",
    "content": ". | [Ühendused] (connections) — ühendusmeetodite ülevaade | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/desktop.html#seotud-teemad",
    
    "relUrl": "/et-rEE/user/desktop.html#seotud-teemad"
  },"1077": {
    "doc": "Desktop App",
    "title": "Desktop App",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/desktop.html",
    
    "relUrl": "/fr-rFR/user/desktop.html"
  },"1078": {
    "doc": "Desktop App",
    "title": "Installation",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from the releases page | Or build from source | . Windows . | Download the .msi or .exe installer from the releases page | Or build from source | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/desktop.html#installation",
    
    "relUrl": "/fr-rFR/user/desktop.html#installation"
  },"1079": {
    "doc": "Desktop App",
    "title": "Connecting Your Radio",
    "content": "USB Serial (Primary) . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . For network-connected radios: . | Enter the radio’s IP address and port (default: 4403). | Click Connect. | . Bluetooth (BLE) . Bluetooth Low Energy is supported on desktop via the Kable library: . | Ensure your system has a Bluetooth adapter. The app scans for nearby Meshtastic radios automatically. | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/desktop.html#connecting-your-radio",
    
    "relUrl": "/fr-rFR/user/desktop.html#connecting-your-radio"
  },"1080": {
    "doc": "Desktop App",
    "title": "Feature Parity",
    "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Carte | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | Site Planner | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | Réglages | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Mise à jour du firmware | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | AI Assistant (Chirpy) | ✓* | ✗ | Google flavor Android only | . | App Functions (system AI) | ✓† | ✗ | Google flavor Android only | . *Chirpy AI requires Android 14+ on Google flavor builds with supported hardware. †App Functions exposes app actions to the Android system AI on Google flavor builds. See App Functions. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/desktop.html#feature-parity",
    
    "relUrl": "/fr-rFR/user/desktop.html#feature-parity"
  },"1081": {
    "doc": "Desktop App",
    "title": "UI Differences",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. Keyboard Shortcuts . Shortcuts use ⌘ (Command) on macOS and Ctrl on Windows and Linux. (The Super / Windows key is not bound.) . | Shortcut | Action | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | Open Settings | . | ⌘/Ctrl+1 | Switch to Messages tab | . | ⌘/Ctrl+2 | Switch to Nodes tab | . | ⌘/Ctrl+3 | Switch to Map tab | . | ⌘/Ctrl+4 | Switch to Connect tab | . | ⌘/Ctrl+/ | Open About | . Window & System Tray . | Window resizing — responsive layout adapts to window dimensions | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | 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. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/desktop.html#ui-differences",
    
    "relUrl": "/fr-rFR/user/desktop.html#ui-differences"
  },"1082": {
    "doc": "Desktop App",
    "title": "Built-in Documentation Browser",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. The browser supports full-text search across all documentation: . Individual doc pages render with full formatting: . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/desktop.html#built-in-documentation-browser",
    
    "relUrl": "/fr-rFR/user/desktop.html#built-in-documentation-browser"
  },"1083": {
    "doc": "Desktop App",
    "title": "Building from Source",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Requirements: . | JDK 25 (Gradle can provision the toolchain itself via foojay) | No Android SDK required for desktop-only builds | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/desktop.html#building-from-source",
    
    "relUrl": "/fr-rFR/user/desktop.html#building-from-source"
  },"1084": {
    "doc": "Desktop App",
    "title": "Known Limitations",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | 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) | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/desktop.html#known-limitations",
    
    "relUrl": "/fr-rFR/user/desktop.html#known-limitations"
  },"1085": {
    "doc": "Desktop App",
    "title": "Related Topics",
    "content": ". | Connections — connection methods overview | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/desktop.html#related-topics",
    
    "relUrl": "/fr-rFR/user/desktop.html#related-topics"
  },"1086": {
    "doc": "Desktop App",
    "title": "Desktop App",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/desktop.html",
    
    "relUrl": "/tr-rTR/user/desktop.html"
  },"1087": {
    "doc": "Desktop App",
    "title": "Installation",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from the releases page | Or build from source | . Windows . | Download the .msi or .exe installer from the releases page | Or build from source | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/desktop.html#installation",
    
    "relUrl": "/tr-rTR/user/desktop.html#installation"
  },"1088": {
    "doc": "Desktop App",
    "title": "Connecting Your Radio",
    "content": "USB Serial (Primary) . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . For network-connected radios: . | Enter the radio’s IP address and port (default: 4403). | Click Connect. | . Bluetooth (BLE) . Bluetooth Low Energy is supported on desktop via the Kable library: . | Ensure your system has a Bluetooth adapter. The app scans for nearby Meshtastic radios automatically. | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/desktop.html#connecting-your-radio",
    
    "relUrl": "/tr-rTR/user/desktop.html#connecting-your-radio"
  },"1089": {
    "doc": "Desktop App",
    "title": "Feature Parity",
    "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Harita | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | Site Planner | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | Ayarlar | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | AI Assistant (Chirpy) | ✓* | ✗ | Google flavor Android only | . | App Functions (system AI) | ✓† | ✗ | Google flavor Android only | . *Chirpy AI requires Android 14+ on Google flavor builds with supported hardware. †App Functions exposes app actions to the Android system AI on Google flavor builds. See App Functions. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/desktop.html#feature-parity",
    
    "relUrl": "/tr-rTR/user/desktop.html#feature-parity"
  },"1090": {
    "doc": "Desktop App",
    "title": "UI Differences",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. Keyboard Shortcuts . Shortcuts use ⌘ (Command) on macOS and Ctrl on Windows and Linux. (The Super / Windows key is not bound.) . | Shortcut | Action | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | Open Settings | . | ⌘/Ctrl+1 | Switch to Messages tab | . | ⌘/Ctrl+2 | Switch to Nodes tab | . | ⌘/Ctrl+3 | Switch to Map tab | . | ⌘/Ctrl+4 | Switch to Connect tab | . | ⌘/Ctrl+/ | Open About | . Window & System Tray . | Window resizing — responsive layout adapts to window dimensions | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | 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. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/desktop.html#ui-differences",
    
    "relUrl": "/tr-rTR/user/desktop.html#ui-differences"
  },"1091": {
    "doc": "Desktop App",
    "title": "Built-in Documentation Browser",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. The browser supports full-text search across all documentation: . Individual doc pages render with full formatting: . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/desktop.html#built-in-documentation-browser",
    
    "relUrl": "/tr-rTR/user/desktop.html#built-in-documentation-browser"
  },"1092": {
    "doc": "Desktop App",
    "title": "Building from Source",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Requirements: . | JDK 25 (Gradle can provision the toolchain itself via foojay) | No Android SDK required for desktop-only builds | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/desktop.html#building-from-source",
    
    "relUrl": "/tr-rTR/user/desktop.html#building-from-source"
  },"1093": {
    "doc": "Desktop App",
    "title": "Known Limitations",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | 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) | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/desktop.html#known-limitations",
    
    "relUrl": "/tr-rTR/user/desktop.html#known-limitations"
  },"1094": {
    "doc": "Desktop App",
    "title": "Related Topics",
    "content": ". | Connections — connection methods overview | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/desktop.html#related-topics",
    
    "relUrl": "/tr-rTR/user/desktop.html#related-topics"
  },"1095": {
    "doc": "Desktop App",
    "title": "Desktop App",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/desktop.html",
    
    "relUrl": "/el-rGR/user/desktop.html"
  },"1096": {
    "doc": "Desktop App",
    "title": "Installation",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from the releases page | Or build from source | . Windows . | Download the .msi or .exe installer from the releases page | Or build from source | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/desktop.html#installation",
    
    "relUrl": "/el-rGR/user/desktop.html#installation"
  },"1097": {
    "doc": "Desktop App",
    "title": "Connecting Your Radio",
    "content": "USB Serial (Primary) . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . For network-connected radios: . | Enter the radio’s IP address and port (default: 4403). | Click Connect. | . Bluetooth (BLE) . Bluetooth Low Energy is supported on desktop via the Kable library: . | Ensure your system has a Bluetooth adapter. The app scans for nearby Meshtastic radios automatically. | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/desktop.html#connecting-your-radio",
    
    "relUrl": "/el-rGR/user/desktop.html#connecting-your-radio"
  },"1098": {
    "doc": "Desktop App",
    "title": "Feature Parity",
    "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Χάρτης | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | Site Planner | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | Ρυθμίσεις | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | AI Assistant (Chirpy) | ✓* | ✗ | Google flavor Android only | . | App Functions (system AI) | ✓† | ✗ | Google flavor Android only | . *Chirpy AI requires Android 14+ on Google flavor builds with supported hardware. †App Functions exposes app actions to the Android system AI on Google flavor builds. See App Functions. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/desktop.html#feature-parity",
    
    "relUrl": "/el-rGR/user/desktop.html#feature-parity"
  },"1099": {
    "doc": "Desktop App",
    "title": "UI Differences",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. Keyboard Shortcuts . Shortcuts use ⌘ (Command) on macOS and Ctrl on Windows and Linux. (The Super / Windows key is not bound.) . | Shortcut | Action | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | Open Settings | . | ⌘/Ctrl+1 | Switch to Messages tab | . | ⌘/Ctrl+2 | Switch to Nodes tab | . | ⌘/Ctrl+3 | Switch to Map tab | . | ⌘/Ctrl+4 | Switch to Connect tab | . | ⌘/Ctrl+/ | Open About | . Window & System Tray . | Window resizing — responsive layout adapts to window dimensions | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | 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. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/desktop.html#ui-differences",
    
    "relUrl": "/el-rGR/user/desktop.html#ui-differences"
  },"1100": {
    "doc": "Desktop App",
    "title": "Built-in Documentation Browser",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. The browser supports full-text search across all documentation: . Individual doc pages render with full formatting: . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/desktop.html#built-in-documentation-browser",
    
    "relUrl": "/el-rGR/user/desktop.html#built-in-documentation-browser"
  },"1101": {
    "doc": "Desktop App",
    "title": "Building from Source",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Requirements: . | JDK 25 (Gradle can provision the toolchain itself via foojay) | No Android SDK required for desktop-only builds | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/desktop.html#building-from-source",
    
    "relUrl": "/el-rGR/user/desktop.html#building-from-source"
  },"1102": {
    "doc": "Desktop App",
    "title": "Known Limitations",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | 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) | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/desktop.html#known-limitations",
    
    "relUrl": "/el-rGR/user/desktop.html#known-limitations"
  },"1103": {
    "doc": "Desktop App",
    "title": "Related Topics",
    "content": ". | Connections — connection methods overview | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/desktop.html#related-topics",
    
    "relUrl": "/el-rGR/user/desktop.html#related-topics"
  },"1104": {
    "doc": "Desktop App",
    "title": "Desktop App",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/desktop.html",
    
    "relUrl": "/ro-rRO/user/desktop.html"
  },"1105": {
    "doc": "Desktop App",
    "title": "Installation",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from the releases page | Or build from source | . Windows . | Download the .msi or .exe installer from the releases page | Or build from source | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/desktop.html#installation",
    
    "relUrl": "/ro-rRO/user/desktop.html#installation"
  },"1106": {
    "doc": "Desktop App",
    "title": "Connecting Your Radio",
    "content": "USB Serial (Primary) . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . For network-connected radios: . | Enter the radio’s IP address and port (default: 4403). | Click Connect. | . Bluetooth (BLE) . Bluetooth Low Energy is supported on desktop via the Kable library: . | Ensure your system has a Bluetooth adapter. The app scans for nearby Meshtastic radios automatically. | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/desktop.html#connecting-your-radio",
    
    "relUrl": "/ro-rRO/user/desktop.html#connecting-your-radio"
  },"1107": {
    "doc": "Desktop App",
    "title": "Feature Parity",
    "content": "| Feature | Android | Desktop | Notițe | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Map | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | Site Planner | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | Setări | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Actualizare firmware | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | AI Assistant (Chirpy) | ✓* | ✗ | Google flavor Android only | . | App Functions (system AI) | ✓† | ✗ | Google flavor Android only | . *Chirpy AI requires Android 14+ on Google flavor builds with supported hardware. †App Functions exposes app actions to the Android system AI on Google flavor builds. See App Functions. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/desktop.html#feature-parity",
    
    "relUrl": "/ro-rRO/user/desktop.html#feature-parity"
  },"1108": {
    "doc": "Desktop App",
    "title": "UI Differences",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. Keyboard Shortcuts . Shortcuts use ⌘ (Command) on macOS and Ctrl on Windows and Linux. (The Super / Windows key is not bound.) . | Shortcut | Action | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | Open Settings | . | ⌘/Ctrl+1 | Switch to Messages tab | . | ⌘/Ctrl+2 | Switch to Nodes tab | . | ⌘/Ctrl+3 | Switch to Map tab | . | ⌘/Ctrl+4 | Switch to Connect tab | . | ⌘/Ctrl+/ | Open About | . Window & System Tray . | Window resizing — responsive layout adapts to window dimensions | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | 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. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/desktop.html#ui-differences",
    
    "relUrl": "/ro-rRO/user/desktop.html#ui-differences"
  },"1109": {
    "doc": "Desktop App",
    "title": "Built-in Documentation Browser",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. The browser supports full-text search across all documentation: . Individual doc pages render with full formatting: . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/desktop.html#built-in-documentation-browser",
    
    "relUrl": "/ro-rRO/user/desktop.html#built-in-documentation-browser"
  },"1110": {
    "doc": "Desktop App",
    "title": "Building from Source",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Requirements: . | JDK 25 (Gradle can provision the toolchain itself via foojay) | No Android SDK required for desktop-only builds | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/desktop.html#building-from-source",
    
    "relUrl": "/ro-rRO/user/desktop.html#building-from-source"
  },"1111": {
    "doc": "Desktop App",
    "title": "Known Limitations",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | 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) | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/desktop.html#known-limitations",
    
    "relUrl": "/ro-rRO/user/desktop.html#known-limitations"
  },"1112": {
    "doc": "Desktop App",
    "title": "Related Topics",
    "content": ". | Connections — connection methods overview | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/desktop.html#related-topics",
    
    "relUrl": "/ro-rRO/user/desktop.html#related-topics"
  },"1113": {
    "doc": "Desktop App",
    "title": "Desktop App",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/desktop.html",
    
    "relUrl": "/iw-rIL/user/desktop.html"
  },"1114": {
    "doc": "Desktop App",
    "title": "Installation",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from the releases page | Or build from source | . Windows . | Download the .msi or .exe installer from the releases page | Or build from source | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/desktop.html#installation",
    
    "relUrl": "/iw-rIL/user/desktop.html#installation"
  },"1115": {
    "doc": "Desktop App",
    "title": "Connecting Your Radio",
    "content": "USB Serial (Primary) . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . For network-connected radios: . | Enter the radio’s IP address and port (default: 4403). | Click Connect. | . Bluetooth (BLE) . Bluetooth Low Energy is supported on desktop via the Kable library: . | Ensure your system has a Bluetooth adapter. The app scans for nearby Meshtastic radios automatically. | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/desktop.html#connecting-your-radio",
    
    "relUrl": "/iw-rIL/user/desktop.html#connecting-your-radio"
  },"1116": {
    "doc": "Desktop App",
    "title": "Feature Parity",
    "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | מפה | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | Site Planner | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | הגדרות | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | AI Assistant (Chirpy) | ✓* | ✗ | Google flavor Android only | . | App Functions (system AI) | ✓† | ✗ | Google flavor Android only | . *Chirpy AI requires Android 14+ on Google flavor builds with supported hardware. †App Functions exposes app actions to the Android system AI on Google flavor builds. See App Functions. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/desktop.html#feature-parity",
    
    "relUrl": "/iw-rIL/user/desktop.html#feature-parity"
  },"1117": {
    "doc": "Desktop App",
    "title": "UI Differences",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. Keyboard Shortcuts . Shortcuts use ⌘ (Command) on macOS and Ctrl on Windows and Linux. (The Super / Windows key is not bound.) . | Shortcut | Action | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | Open Settings | . | ⌘/Ctrl+1 | Switch to Messages tab | . | ⌘/Ctrl+2 | Switch to Nodes tab | . | ⌘/Ctrl+3 | Switch to Map tab | . | ⌘/Ctrl+4 | Switch to Connect tab | . | ⌘/Ctrl+/ | Open About | . Window & System Tray . | Window resizing — responsive layout adapts to window dimensions | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | 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. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/desktop.html#ui-differences",
    
    "relUrl": "/iw-rIL/user/desktop.html#ui-differences"
  },"1118": {
    "doc": "Desktop App",
    "title": "Built-in Documentation Browser",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. The browser supports full-text search across all documentation: . Individual doc pages render with full formatting: . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/desktop.html#built-in-documentation-browser",
    
    "relUrl": "/iw-rIL/user/desktop.html#built-in-documentation-browser"
  },"1119": {
    "doc": "Desktop App",
    "title": "Building from Source",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Requirements: . | JDK 25 (Gradle can provision the toolchain itself via foojay) | No Android SDK required for desktop-only builds | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/desktop.html#building-from-source",
    
    "relUrl": "/iw-rIL/user/desktop.html#building-from-source"
  },"1120": {
    "doc": "Desktop App",
    "title": "Known Limitations",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | 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) | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/desktop.html#known-limitations",
    
    "relUrl": "/iw-rIL/user/desktop.html#known-limitations"
  },"1121": {
    "doc": "Desktop App",
    "title": "Related Topics",
    "content": ". | Connections — connection methods overview | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/desktop.html#related-topics",
    
    "relUrl": "/iw-rIL/user/desktop.html#related-topics"
  },"1122": {
    "doc": "Desktop App",
    "title": "Desktop App",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/desktop.html",
    
    "relUrl": "/pt-rBR/user/desktop.html"
  },"1123": {
    "doc": "Desktop App",
    "title": "Installation",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from the releases page | Or build from source | . Windows . | Download the .msi or .exe installer from the releases page | Or build from source | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/desktop.html#installation",
    
    "relUrl": "/pt-rBR/user/desktop.html#installation"
  },"1124": {
    "doc": "Desktop App",
    "title": "Connecting Your Radio",
    "content": "USB Serial (Primary) . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . For network-connected radios: . | Enter the radio’s IP address and port (default: 4403). | Click Connect. | . Bluetooth (BLE) . Bluetooth Low Energy is supported on desktop via the Kable library: . | Ensure your system has a Bluetooth adapter. The app scans for nearby Meshtastic radios automatically. | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/desktop.html#connecting-your-radio",
    
    "relUrl": "/pt-rBR/user/desktop.html#connecting-your-radio"
  },"1125": {
    "doc": "Desktop App",
    "title": "Feature Parity",
    "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Mapa | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | Site Planner | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | Configurações | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | AI Assistant (Chirpy) | ✓* | ✗ | Google flavor Android only | . | App Functions (system AI) | ✓† | ✗ | Google flavor Android only | . *Chirpy AI requires Android 14+ on Google flavor builds with supported hardware. †App Functions exposes app actions to the Android system AI on Google flavor builds. See App Functions. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/desktop.html#feature-parity",
    
    "relUrl": "/pt-rBR/user/desktop.html#feature-parity"
  },"1126": {
    "doc": "Desktop App",
    "title": "UI Differences",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. Keyboard Shortcuts . Shortcuts use ⌘ (Command) on macOS and Ctrl on Windows and Linux. (The Super / Windows key is not bound.) . | Shortcut | Action | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | Open Settings | . | ⌘/Ctrl+1 | Switch to Messages tab | . | ⌘/Ctrl+2 | Switch to Nodes tab | . | ⌘/Ctrl+3 | Switch to Map tab | . | ⌘/Ctrl+4 | Switch to Connect tab | . | ⌘/Ctrl+/ | Open About | . Window & System Tray . | Window resizing — responsive layout adapts to window dimensions | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | 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. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/desktop.html#ui-differences",
    
    "relUrl": "/pt-rBR/user/desktop.html#ui-differences"
  },"1127": {
    "doc": "Desktop App",
    "title": "Built-in Documentation Browser",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. The browser supports full-text search across all documentation: . Individual doc pages render with full formatting: . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/desktop.html#built-in-documentation-browser",
    
    "relUrl": "/pt-rBR/user/desktop.html#built-in-documentation-browser"
  },"1128": {
    "doc": "Desktop App",
    "title": "Building from Source",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Requirements: . | JDK 25 (Gradle can provision the toolchain itself via foojay) | No Android SDK required for desktop-only builds | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/desktop.html#building-from-source",
    
    "relUrl": "/pt-rBR/user/desktop.html#building-from-source"
  },"1129": {
    "doc": "Desktop App",
    "title": "Known Limitations",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | 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) | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/desktop.html#known-limitations",
    
    "relUrl": "/pt-rBR/user/desktop.html#known-limitations"
  },"1130": {
    "doc": "Desktop App",
    "title": "Related Topics",
    "content": ". | Connections — connection methods overview | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/desktop.html#related-topics",
    
    "relUrl": "/pt-rBR/user/desktop.html#related-topics"
  },"1131": {
    "doc": "Desktop App",
    "title": "Desktop App",
    "content": "This page covers installing the Meshtastic desktop app, connecting a radio, and how it differs from Android. The desktop app shares its core codebase with Android via Kotlin Multiplatform, so most features work identically across Linux, macOS, and Windows. ",
    "url": "/Meshtastic-Android/main/en/user/desktop.html",
    
    "relUrl": "/en/user/desktop.html"
  },"1132": {
    "doc": "Desktop App",
    "title": "Installation",
    "content": "Linux . | Download the .deb, .rpm, or .AppImage package from the releases page | Or install from Flathub: flatpak install flathub org.meshtastic.MeshtasticDesktop | Or build from source using ./gradlew :desktopApp:run | . macOS . | Download the .dmg package from the releases page | Or build from source | . Windows . | Download the .msi or .exe installer from the releases page | Or build from source | . ",
    "url": "/Meshtastic-Android/main/en/user/desktop.html#installation",
    
    "relUrl": "/en/user/desktop.html#installation"
  },"1133": {
    "doc": "Desktop App",
    "title": "Connecting Your Radio",
    "content": "USB Serial (Primary) . The most reliable connection method on desktop: . Connect your radio via USB. The app detects the serial port automatically; if it doesn’t, select the port from the Connect menu. TCP/IP . For network-connected radios: . | Enter the radio’s IP address and port (default: 4403). | Click Connect. | . Bluetooth (BLE) . Bluetooth Low Energy is supported on desktop via the Kable library: . | Ensure your system has a Bluetooth adapter. The app scans for nearby Meshtastic radios automatically. | Select your radio from the Connect screen. | . ",
    "url": "/Meshtastic-Android/main/en/user/desktop.html#connecting-your-radio",
    
    "relUrl": "/en/user/desktop.html#connecting-your-radio"
  },"1134": {
    "doc": "Desktop App",
    "title": "Feature Parity",
    "content": "| Feature | Android | Desktop | Notes | . | Messaging | ✓ | ✓ | Full parity | . | Node List | ✓ | ✓ | Full parity | . | Map | ✓ | ✓ | Interactive MapLibre map, with base map and overlay pickers and custom tile sources. Offline terrain (hillshade and contours) can be downloaded; offline base-map packs and local .mbtiles archives cannot | . | Map layers (.kml/.kmz/GeoJSON) | ✓ | ✓ | Same layer store and sheet as Android; imported files draw on the desktop map | . | Site Planner | ✓ | ✓* | *Opens in your browser on desktop; the estimate is not drawn on the desktop map | . | Settings | ✓ | ✓ | Full parity | . | Bluetooth (BLE) | ✓ | ✓ | Via Kable on desktop | . | Firmware Update | ✓ | ✓ | In-app USB, BLE, and Wi-Fi (ESP32) update work the same as Android. The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only | . | Notifications | ✓ | ✓ | Native OS notifications | . | Widgets | ✓ | ✗ | Android-only | . | AI Assistant (Chirpy) | ✓* | ✗ | Google flavor Android only | . | App Functions (system AI) | ✓† | ✗ | Google flavor Android only | . *Chirpy AI requires Android 14+ on Google flavor builds with supported hardware. †App Functions exposes app actions to the Android system AI on Google flavor builds. See App Functions. ",
    "url": "/Meshtastic-Android/main/en/user/desktop.html#feature-parity",
    
    "relUrl": "/en/user/desktop.html#feature-parity"
  },"1135": {
    "doc": "Desktop App",
    "title": "UI Differences",
    "content": "The desktop app uses the same Compose Multiplatform UI with adaptations for larger screens and desktop interaction. Keyboard Shortcuts . Shortcuts use ⌘ (Command) on macOS and Ctrl on Windows and Linux. (The Super / Windows key is not bound.) . | Shortcut | Action | . | ⌘/Ctrl+Q | Quit the app | . | ⌘/Ctrl+, | Open Settings | . | ⌘/Ctrl+1 | Switch to Messages tab | . | ⌘/Ctrl+2 | Switch to Nodes tab | . | ⌘/Ctrl+3 | Switch to Map tab | . | ⌘/Ctrl+4 | Switch to Connect tab | . | ⌘/Ctrl+/ | Open About | . Window & System Tray . | Window resizing — responsive layout adapts to window dimensions | System tray — closing the window minimizes to the system tray for background mesh operation. On a desktop environment with no tray, there is nowhere to minimize to, so closing quits the app instead | 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. Find them in the App Notifications section of the Settings screen: Direct message notifications, New node notifications, and Low battery notifications. ",
    "url": "/Meshtastic-Android/main/en/user/desktop.html#ui-differences",
    
    "relUrl": "/en/user/desktop.html#ui-differences"
  },"1136": {
    "doc": "Desktop App",
    "title": "Built-in Documentation Browser",
    "content": "The desktop app includes a built-in documentation browser for quick access to help content without leaving the app. The browser supports full-text search across all documentation: . Individual doc pages render with full formatting: . ",
    "url": "/Meshtastic-Android/main/en/user/desktop.html#built-in-documentation-browser",
    
    "relUrl": "/en/user/desktop.html#built-in-documentation-browser"
  },"1137": {
    "doc": "Desktop App",
    "title": "Building from Source",
    "content": "git clone https://github.com/meshtastic/Meshtastic-Android.git cd Meshtastic-Android ./gradlew :desktopApp:run . Requirements: . | JDK 25 (Gradle can provision the toolchain itself via foojay) | No Android SDK required for desktop-only builds | . ",
    "url": "/Meshtastic-Android/main/en/user/desktop.html#building-from-source",
    
    "relUrl": "/en/user/desktop.html#building-from-source"
  },"1138": {
    "doc": "Desktop App",
    "title": "Known Limitations",
    "content": ". | Offline base-map downloads and local .mbtiles archives are not available on desktop. Offline terrain is — see Map & Waypoints. | .kml/.kmz/GeoJSON layer import works — see Map & Waypoints. Site Planner opens in your browser rather than in the app; to bring its coverage estimate onto the map, click the transmitter pin in the browser and use the planner’s GeoJSON export, then add the file as a layer — not the KML export, which is a ground-overlay image this map cannot draw. Custom network tile sources work too — see Map & Waypoints | The USB maintenance flow — nRF52/RP2040 factory erase and bootloader upgrade — is Android-only, and the desktop app does not offer it. Use the Web Flasher instead | 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) | . ",
    "url": "/Meshtastic-Android/main/en/user/desktop.html#known-limitations",
    
    "relUrl": "/en/user/desktop.html#known-limitations"
  },"1139": {
    "doc": "Desktop App",
    "title": "Related Topics",
    "content": ". | Connections — connection methods overview | Firmware Updates — in-app USB, BLE, and Wi-Fi update all work the same as on Android | Map & Waypoints — base maps, layers, custom tile sources, and what the desktop map does not do | . ",
    "url": "/Meshtastic-Android/main/en/user/desktop.html#related-topics",
    
    "relUrl": "/en/user/desktop.html#related-topics"
  },"1140": {
    "doc": "Developer Guide",
    "title": "Developer Guide",
    "content": "Technical documentation for contributing to the Meshtastic Android and Desktop app. ",
    "url": "/Meshtastic-Android/main/en/developer.html",
    
    "relUrl": "/en/developer.html"
  },"1141": {
    "doc": "Developer Guide",
    "title": "Before You Open a PR",
    "content": "Things that trip up first-time contributors — check these before requesting review: . | Formatting passes — run ./gradlew spotlessApply to auto-format, then verify with spotlessCheck | Detekt passes — run ./gradlew detekt and fix all reported issues | All tests pass — run ./gradlew test allTests (both are needed: test covers Android-only modules, allTests covers KMP) | Screenshot tests pass — if you touched any Compose UI, run ./gradlew :screenshot-tests:validateDebugScreenshotTest and update reference images if needed | Protos are an external dependency — protobuf models come from the org.meshtastic:protobufs Maven artifact (pinned in gradle/libs.versions.toml); change protos upstream and bump the version, never edit generated code locally | Docs updated — if you changed user-visible UI, update the corresponding page under docs/en/user/ | Previews updated — if you changed UI composables, update the corresponding *Previews.kt file and the screenshot-test baselines | Branch naming — branches must start with feat/, fix/, chore/, docs/, build/, ci/, refactor/, test/, or deps/ | . ",
    "url": "/Meshtastic-Android/main/en/developer.html#before-you-open-a-pr",
    
    "relUrl": "/en/developer.html#before-you-open-a-pr"
  },"1142": {
    "doc": "Developer Guide",
    "title": "What’s New for Developers",
    "content": "September 2026 — Navigation & Deep Links — Deep links route through Navigation 3’s UriDeepLinkMatcher instead of a hand-rolled when block, and patterns are anchored, so an unmodelled trailing path no longer opens the family root. September 2026 — Measurement & Formatting — NumberFormatter.format follows the OS locale; formatInvariant is the fixed-dot one for payloads another system parses. September 2026 — Documentation Style — Section 11 of the Meshtastic design standards is now the style guide for docs/en/; this page keeps only the repository mechanics, the in-app renderer’s admonition form, and the prose rules the standards leave open. August 2026 — Documentation Style — New page: the house style guide for docs/en/ prose, with rule IDs, a project word list, and the reasoning behind each convention. August 2026 — Map tile sources are one shared catalogue in feature/map (MapTileCatalogue, RasterTileSpec), so both flavors draw the same raster base maps and overlays from one definition. August 2026 — Both maps draw an imported feature’s own icon and drape a KMZ GroundOverlay image at its LatLonBox (rotation included) — MapLibre via an ImageSource quad, Google via GroundOverlayOptions (#3786). August 2026 — Offline map-pack downloads are gated on offlineMapsSupported, since the MapLibre offline API compiles on Desktop but silently downloads nothing there. August 2026 — New module feature/map-maplibre: the F-Droid flavor and Desktop now render every map surface (main map, node track, traceroute, discovery, inline mini-map) through maplibre-compose from one multiplatform module, and osmdroid is gone. The shared rules both renderers must agree on live in feature/map policy classes. ",
    "url": "/Meshtastic-Android/main/en/developer.html#whats-new-for-developers",
    
    "relUrl": "/en/developer.html#whats-new-for-developers"
  },"1143": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery",
    "content": "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. The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Manual exploration — traceroute, Neighbor Info, and the node list, which you can use at any time to investigate specific paths and topology. | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/discovery.html",
    
    "relUrl": "/sk-rSK/user/discovery.html"
  },"1144": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery (Scanner)",
    "content": "Local Mesh Discovery is a dedicated scanning mode that helps you find the best LoRa modem preset for your location and see which nodes are active on each preset. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Before starting, configure these controls: . | Control | Popis | . | LoRa preset picker | Select one or more presets to scan. Discovery dwells on each selected preset in turn. | . | Dwell time | Time to listen on each preset. Choose from 1, 5, 15, 30, 45, 60, 90, 120, or 180 minutes. Longer dwell times collect more packets and give a clearer picture, but take longer. | . | Keep screen awake | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The node is not connected. | No presets have been selected to scan. | The selected preset uses 2.4 GHz, which your hardware doesn’t support. | . Live progress . While a scan runs, Discovery shows its current stage: . | Stage | What’s happening | . | Preparing scan | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Re-establishing the connection after the preset change. | . | Dwelling on <preset> | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analyzing results | Processing the collected packets and ranking the presets. | . | Restoring home preset | Putting your original LoRa configuration back. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. Metrics include: . | Metric | What it tells you | . | RF health | Overall quality of the radio environment on that preset. | . | Channel utilization | How busy the airwaves were during the dwell. | . | Airtime | Transmission time observed. | . | Direct vs. relayed nodes | How many mesh nodes were heard directly versus via a relay. | . | Bad / duplicate packets | Counts of corrupt and repeated packets, indicating congestion or interference. | . Additional features available from the results: . | Scan History — saved sessions you can revisit; view or delete past scans. | Discovery Map — a map of the nodes found during the scan. | Report export — export a report as a PDF on Android, or as text on other platforms. | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/discovery.html#local-mesh-discovery-scanner",
    
    "relUrl": "/sk-rSK/user/discovery.html#local-mesh-discovery-scanner"
  },"1145": {
    "doc": "Local Mesh Discovery",
    "title": "Mesh Beacon",
    "content": "Mesh Beacon lets nodes invite others to join their mesh. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Received invitations appear as Mesh invitations cards on the Discovery screen. Each card shows the sender’s message plus the offered channel, region, preset, and signal quality, with these actions: . | Join — switch to the offered channel and preset (retunes the node and reboots). When the offer matches your current frequency slot, an Add channel action adds it without a reboot. | Discover — seed a Discovery scan with the offered preset so you can survey that mesh before joining (shown only when the beacon offers a preset). | Dismiss — ignore the invitation. | . Channels advertised by beacons also show up in the scan setup as Beacon channels — select one to include it as a scan target. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/discovery.html#mesh-beacon",
    
    "relUrl": "/sk-rSK/user/discovery.html#mesh-beacon"
  },"1146": {
    "doc": "Local Mesh Discovery",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Trasovanie . 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 . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | 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 Response — The traceroute got nothing back. 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. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Informácia o susedoch . 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 . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 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. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. 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 nodes. | . 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 LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/discovery.html#manual-exploration",
    
    "relUrl": "/sk-rSK/user/discovery.html#manual-exploration"
  },"1147": {
    "doc": "Local Mesh Discovery",
    "title": "Tips for Mesh exploration",
    "content": ". | 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 combined with signal data help you understand why some links are strong and others are weak. | Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly. | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/sk-rSK/user/discovery.html#tips-for-mesh-exploration"
  },"1148": {
    "doc": "Local Mesh Discovery",
    "title": "Related Topics",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/discovery.html#related-topics",
    
    "relUrl": "/sk-rSK/user/discovery.html#related-topics"
  },"1149": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery",
    "content": "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. The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Manual exploration — traceroute, Neighbor Info, and the node list, which you can use at any time to investigate specific paths and topology. | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/discovery.html",
    
    "relUrl": "/be-rBY/user/discovery.html"
  },"1150": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery (Scanner)",
    "content": "Local Mesh Discovery is a dedicated scanning mode that helps you find the best LoRa modem preset for your location and see which nodes are active on each preset. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Before starting, configure these controls: . | Control | Апісанне | . | LoRa preset picker | Select one or more presets to scan. Discovery dwells on each selected preset in turn. | . | Dwell time | Time to listen on each preset. Choose from 1, 5, 15, 30, 45, 60, 90, 120, or 180 minutes. Longer dwell times collect more packets and give a clearer picture, but take longer. | . | Keep screen awake | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The node is not connected. | No presets have been selected to scan. | The selected preset uses 2.4 GHz, which your hardware doesn’t support. | . Live progress . While a scan runs, Discovery shows its current stage: . | Stage | What’s happening | . | Preparing scan | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Re-establishing the connection after the preset change. | . | Dwelling on <preset> | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analyzing results | Processing the collected packets and ranking the presets. | . | Restoring home preset | Putting your original LoRa configuration back. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. Metrics include: . | Metric | What it tells you | . | RF health | Overall quality of the radio environment on that preset. | . | Channel utilization | How busy the airwaves were during the dwell. | . | Airtime | Transmission time observed. | . | Direct vs. relayed nodes | How many mesh nodes were heard directly versus via a relay. | . | Bad / duplicate packets | Counts of corrupt and repeated packets, indicating congestion or interference. | . Additional features available from the results: . | Scan History — saved sessions you can revisit; view or delete past scans. | Discovery Map — a map of the nodes found during the scan. | Report export — export a report as a PDF on Android, or as text on other platforms. | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/discovery.html#local-mesh-discovery-scanner",
    
    "relUrl": "/be-rBY/user/discovery.html#local-mesh-discovery-scanner"
  },"1151": {
    "doc": "Local Mesh Discovery",
    "title": "Mesh Beacon",
    "content": "Mesh Beacon lets nodes invite others to join their mesh. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Received invitations appear as Mesh invitations cards on the Discovery screen. Each card shows the sender’s message plus the offered channel, region, preset, and signal quality, with these actions: . | Join — switch to the offered channel and preset (retunes the node and reboots). When the offer matches your current frequency slot, an Add channel action adds it without a reboot. | Discover — seed a Discovery scan with the offered preset so you can survey that mesh before joining (shown only when the beacon offers a preset). | Dismiss — ignore the invitation. | . Channels advertised by beacons also show up in the scan setup as Beacon channels — select one to include it as a scan target. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/discovery.html#mesh-beacon",
    
    "relUrl": "/be-rBY/user/discovery.html#mesh-beacon"
  },"1152": {
    "doc": "Local Mesh Discovery",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. 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 . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | 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 Response — The traceroute got nothing back. 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. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t 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 . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 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. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. 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 nodes. | . 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 LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/discovery.html#manual-exploration",
    
    "relUrl": "/be-rBY/user/discovery.html#manual-exploration"
  },"1153": {
    "doc": "Local Mesh Discovery",
    "title": "Tips for Mesh exploration",
    "content": ". | 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 combined with signal data help you understand why some links are strong and others are weak. | Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly. | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/be-rBY/user/discovery.html#tips-for-mesh-exploration"
  },"1154": {
    "doc": "Local Mesh Discovery",
    "title": "Related Topics",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/discovery.html#related-topics",
    
    "relUrl": "/be-rBY/user/discovery.html#related-topics"
  },"1155": {
    "doc": "Discovery della mesh locale",
    "title": "Discovery della mesh locale",
    "content": "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. The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Manual exploration — traceroute, Neighbor Info, and the node list, which you can use at any time to investigate specific paths and topology. | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/discovery.html",
    
    "relUrl": "/it-rIT/user/discovery.html"
  },"1156": {
    "doc": "Discovery della mesh locale",
    "title": "Local Mesh Discovery (Scanner)",
    "content": "Local Mesh Discovery is a dedicated scanning mode that helps you find the best LoRa modem preset for your location and see which nodes are active on each preset. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Before starting, configure these controls: . | Control | Descrizione | . | LoRa preset picker | Select one or more presets to scan. Discovery dwells on each selected preset in turn. | . | Dwell time | Time to listen on each preset. Choose from 1, 5, 15, 30, 45, 60, 90, 120, or 180 minutes. Longer dwell times collect more packets and give a clearer picture, but take longer. | . | Keep screen awake | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The node is not connected. | No presets have been selected to scan. | The selected preset uses 2.4 GHz, which your hardware doesn’t support. | . Live progress . While a scan runs, Discovery shows its current stage: . | Stage | What’s happening | . | Preparing scan | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Re-establishing the connection after the preset change. | . | Dwelling on <preset> | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analyzing results | Processing the collected packets and ranking the presets. | . | Restoring home preset | Putting your original LoRa configuration back. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. Metrics include: . | Metrico | What it tells you | . | RF health | Overall quality of the radio environment on that preset. | . | Impegno canale | How busy the airwaves were during the dwell. | . | Airtime | Transmission time observed. | . | Direct vs. relayed nodes | How many mesh nodes were heard directly versus via a relay. | . | Bad / duplicate packets | Counts of corrupt and repeated packets, indicating congestion or interference. | . Additional features available from the results: . | Scan History — saved sessions you can revisit; view or delete past scans. | Discovery Map — a map of the nodes found during the scan. | Report export — export a report as a PDF on Android, or as text on other platforms. | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/discovery.html#local-mesh-discovery-scanner",
    
    "relUrl": "/it-rIT/user/discovery.html#local-mesh-discovery-scanner"
  },"1157": {
    "doc": "Discovery della mesh locale",
    "title": "Beacon Mesh",
    "content": "Mesh Beacon lets nodes invite others to join their mesh. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Received invitations appear as Mesh invitations cards on the Discovery screen. Each card shows the sender’s message plus the offered channel, region, preset, and signal quality, with these actions: . | Join — switch to the offered channel and preset (retunes the node and reboots). When the offer matches your current frequency slot, an Add channel action adds it without a reboot. | Discover — seed a Discovery scan with the offered preset so you can survey that mesh before joining (shown only when the beacon offers a preset). | Dismiss — ignore the invitation. | . Channels advertised by beacons also show up in the scan setup as Beacon channels — select one to include it as a scan target. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/discovery.html#beacon-mesh",
    
    "relUrl": "/it-rIT/user/discovery.html#beacon-mesh"
  },"1158": {
    "doc": "Discovery della mesh locale",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. 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 . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | 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 Response — The traceroute got nothing back. 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. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Informazioni Vicinato . 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 . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 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. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. 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 nodes. | . 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 LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/discovery.html#manual-exploration",
    
    "relUrl": "/it-rIT/user/discovery.html#manual-exploration"
  },"1159": {
    "doc": "Discovery della mesh locale",
    "title": "Tips for Mesh exploration",
    "content": ". | 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 combined with signal data help you understand why some links are strong and others are weak. | Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly. | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/it-rIT/user/discovery.html#tips-for-mesh-exploration"
  },"1160": {
    "doc": "Discovery della mesh locale",
    "title": "Related Topics",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/discovery.html#related-topics",
    
    "relUrl": "/it-rIT/user/discovery.html#related-topics"
  },"1161": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery",
    "content": "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. The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Manual exploration — traceroute, Neighbor Info, and the node list, which you can use at any time to investigate specific paths and topology. | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/discovery.html",
    
    "relUrl": "/es-rES/user/discovery.html"
  },"1162": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery (Scanner)",
    "content": "Local Mesh Discovery is a dedicated scanning mode that helps you find the best LoRa modem preset for your location and see which nodes are active on each preset. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Before starting, configure these controls: . | Control | Descripción | . | LoRa preset picker | Select one or more presets to scan. Discovery dwells on each selected preset in turn. | . | Dwell time | Time to listen on each preset. Choose from 1, 5, 15, 30, 45, 60, 90, 120, or 180 minutes. Longer dwell times collect more packets and give a clearer picture, but take longer. | . | Keep screen awake | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The node is not connected. | No presets have been selected to scan. | The selected preset uses 2.4 GHz, which your hardware doesn’t support. | . Live progress . While a scan runs, Discovery shows its current stage: . | Stage | What’s happening | . | Preparing scan | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Re-establishing the connection after the preset change. | . | Dwelling on <preset> | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analyzing results | Processing the collected packets and ranking the presets. | . | Restoring home preset | Putting your original LoRa configuration back. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. Metrics include: . | Métrico | What it tells you | . | RF health | Overall quality of the radio environment on that preset. | . | Channel utilization | How busy the airwaves were during the dwell. | . | Airtime | Transmission time observed. | . | Direct vs. relayed nodes | How many mesh nodes were heard directly versus via a relay. | . | Bad / duplicate packets | Counts of corrupt and repeated packets, indicating congestion or interference. | . Additional features available from the results: . | Scan History — saved sessions you can revisit; view or delete past scans. | Discovery Map — a map of the nodes found during the scan. | Report export — export a report as a PDF on Android, or as text on other platforms. | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/es-rES/user/discovery.html#local-mesh-discovery-scanner",
    
    "relUrl": "/es-rES/user/discovery.html#local-mesh-discovery-scanner"
  },"1163": {
    "doc": "Local Mesh Discovery",
    "title": "Mesh Beacon",
    "content": "Mesh Beacon lets nodes invite others to join their mesh. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Received invitations appear as Mesh invitations cards on the Discovery screen. Each card shows the sender’s message plus the offered channel, region, preset, and signal quality, with these actions: . | Join — switch to the offered channel and preset (retunes the node and reboots). When the offer matches your current frequency slot, an Add channel action adds it without a reboot. | Discover — seed a Discovery scan with the offered preset so you can survey that mesh before joining (shown only when the beacon offers a preset). | Dismiss — ignore the invitation. | . Channels advertised by beacons also show up in the scan setup as Beacon channels — select one to include it as a scan target. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/es-rES/user/discovery.html#mesh-beacon",
    
    "relUrl": "/es-rES/user/discovery.html#mesh-beacon"
  },"1164": {
    "doc": "Local Mesh Discovery",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. 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 . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | 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 Response — The traceroute got nothing back. 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. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Información de Vecinos . 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 . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 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. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. 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 nodes. | . 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 LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ",
    "url": "/Meshtastic-Android/main/es-rES/user/discovery.html#manual-exploration",
    
    "relUrl": "/es-rES/user/discovery.html#manual-exploration"
  },"1165": {
    "doc": "Local Mesh Discovery",
    "title": "Tips for Mesh exploration",
    "content": ". | 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 combined with signal data help you understand why some links are strong and others are weak. | Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly. | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/es-rES/user/discovery.html#tips-for-mesh-exploration"
  },"1166": {
    "doc": "Local Mesh Discovery",
    "title": "Related Topics",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/discovery.html#related-topics",
    
    "relUrl": "/es-rES/user/discovery.html#related-topics"
  },"1167": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery",
    "content": "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. The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Manual exploration — traceroute, Neighbor Info, and the node list, which you can use at any time to investigate specific paths and topology. | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/discovery.html",
    
    "relUrl": "/sl-rSI/user/discovery.html"
  },"1168": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery (Scanner)",
    "content": "Local Mesh Discovery is a dedicated scanning mode that helps you find the best LoRa modem preset for your location and see which nodes are active on each preset. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Before starting, configure these controls: . | Control | Opis | . | LoRa preset picker | Select one or more presets to scan. Discovery dwells on each selected preset in turn. | . | Dwell time | Time to listen on each preset. Choose from 1, 5, 15, 30, 45, 60, 90, 120, or 180 minutes. Longer dwell times collect more packets and give a clearer picture, but take longer. | . | Keep screen awake | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The node is not connected. | No presets have been selected to scan. | The selected preset uses 2.4 GHz, which your hardware doesn’t support. | . Live progress . While a scan runs, Discovery shows its current stage: . | Stage | What’s happening | . | Preparing scan | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Re-establishing the connection after the preset change. | . | Dwelling on <preset> | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analyzing results | Processing the collected packets and ranking the presets. | . | Restoring home preset | Putting your original LoRa configuration back. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. Metrics include: . | Metric | What it tells you | . | RF health | Overall quality of the radio environment on that preset. | . | Channel utilization | How busy the airwaves were during the dwell. | . | Airtime | Transmission time observed. | . | Direct vs. relayed nodes | How many mesh nodes were heard directly versus via a relay. | . | Bad / duplicate packets | Counts of corrupt and repeated packets, indicating congestion or interference. | . Additional features available from the results: . | Scan History — saved sessions you can revisit; view or delete past scans. | Discovery Map — a map of the nodes found during the scan. | Report export — export a report as a PDF on Android, or as text on other platforms. | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/discovery.html#local-mesh-discovery-scanner",
    
    "relUrl": "/sl-rSI/user/discovery.html#local-mesh-discovery-scanner"
  },"1169": {
    "doc": "Local Mesh Discovery",
    "title": "Mesh Beacon",
    "content": "Mesh Beacon lets nodes invite others to join their mesh. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Received invitations appear as Mesh invitations cards on the Discovery screen. Each card shows the sender’s message plus the offered channel, region, preset, and signal quality, with these actions: . | Join — switch to the offered channel and preset (retunes the node and reboots). When the offer matches your current frequency slot, an Add channel action adds it without a reboot. | Discover — seed a Discovery scan with the offered preset so you can survey that mesh before joining (shown only when the beacon offers a preset). | Dismiss — ignore the invitation. | . Channels advertised by beacons also show up in the scan setup as Beacon channels — select one to include it as a scan target. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/discovery.html#mesh-beacon",
    
    "relUrl": "/sl-rSI/user/discovery.html#mesh-beacon"
  },"1170": {
    "doc": "Local Mesh Discovery",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Pot . 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 . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | 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 Response — The traceroute got nothing back. 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. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t 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 . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 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. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. 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 nodes. | . 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 LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/discovery.html#manual-exploration",
    
    "relUrl": "/sl-rSI/user/discovery.html#manual-exploration"
  },"1171": {
    "doc": "Local Mesh Discovery",
    "title": "Tips for Mesh exploration",
    "content": ". | 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 combined with signal data help you understand why some links are strong and others are weak. | Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly. | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/sl-rSI/user/discovery.html#tips-for-mesh-exploration"
  },"1172": {
    "doc": "Local Mesh Discovery",
    "title": "Related Topics",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/discovery.html#related-topics",
    
    "relUrl": "/sl-rSI/user/discovery.html#related-topics"
  },"1173": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery",
    "content": "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. The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Manual exploration — traceroute, Neighbor Info, and the node list, which you can use at any time to investigate specific paths and topology. | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/discovery.html",
    
    "relUrl": "/no-rNO/user/discovery.html"
  },"1174": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery (Scanner)",
    "content": "Local Mesh Discovery is a dedicated scanning mode that helps you find the best LoRa modem preset for your location and see which nodes are active on each preset. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Before starting, configure these controls: . | Control | Beskrivelse | . | LoRa preset picker | Select one or more presets to scan. Discovery dwells on each selected preset in turn. | . | Dwell time | Time to listen on each preset. Choose from 1, 5, 15, 30, 45, 60, 90, 120, or 180 minutes. Longer dwell times collect more packets and give a clearer picture, but take longer. | . | Keep screen awake | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The node is not connected. | No presets have been selected to scan. | The selected preset uses 2.4 GHz, which your hardware doesn’t support. | . Live progress . While a scan runs, Discovery shows its current stage: . | Stage | What’s happening | . | Preparing scan | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Re-establishing the connection after the preset change. | . | Dwelling on <preset> | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analyzing results | Processing the collected packets and ranking the presets. | . | Restoring home preset | Putting your original LoRa configuration back. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. Metrics include: . | Metric | What it tells you | . | RF health | Overall quality of the radio environment on that preset. | . | Channel utilization | How busy the airwaves were during the dwell. | . | Airtime | Transmission time observed. | . | Direct vs. relayed nodes | How many mesh nodes were heard directly versus via a relay. | . | Bad / duplicate packets | Counts of corrupt and repeated packets, indicating congestion or interference. | . Additional features available from the results: . | Scan History — saved sessions you can revisit; view or delete past scans. | Discovery Map — a map of the nodes found during the scan. | Report export — export a report as a PDF on Android, or as text on other platforms. | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/discovery.html#local-mesh-discovery-scanner",
    
    "relUrl": "/no-rNO/user/discovery.html#local-mesh-discovery-scanner"
  },"1175": {
    "doc": "Local Mesh Discovery",
    "title": "Mesh Beacon",
    "content": "Mesh Beacon lets nodes invite others to join their mesh. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Received invitations appear as Mesh invitations cards on the Discovery screen. Each card shows the sender’s message plus the offered channel, region, preset, and signal quality, with these actions: . | Join — switch to the offered channel and preset (retunes the node and reboots). When the offer matches your current frequency slot, an Add channel action adds it without a reboot. | Discover — seed a Discovery scan with the offered preset so you can survey that mesh before joining (shown only when the beacon offers a preset). | Dismiss — ignore the invitation. | . Channels advertised by beacons also show up in the scan setup as Beacon channels — select one to include it as a scan target. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/discovery.html#mesh-beacon",
    
    "relUrl": "/no-rNO/user/discovery.html#mesh-beacon"
  },"1176": {
    "doc": "Local Mesh Discovery",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. 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 . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | 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 Response — The traceroute got nothing back. 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. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t 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 . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 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. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. 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 nodes. | . 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 LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/discovery.html#manual-exploration",
    
    "relUrl": "/no-rNO/user/discovery.html#manual-exploration"
  },"1177": {
    "doc": "Local Mesh Discovery",
    "title": "Tips for Mesh exploration",
    "content": ". | 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 combined with signal data help you understand why some links are strong and others are weak. | Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly. | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/no-rNO/user/discovery.html#tips-for-mesh-exploration"
  },"1178": {
    "doc": "Local Mesh Discovery",
    "title": "Related Topics",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/discovery.html#related-topics",
    
    "relUrl": "/no-rNO/user/discovery.html#related-topics"
  },"1179": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery",
    "content": "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. The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Manual exploration — traceroute, Neighbor Info, and the node list, which you can use at any time to investigate specific paths and topology. | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/discovery.html",
    
    "relUrl": "/hu-rHU/user/discovery.html"
  },"1180": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery (Scanner)",
    "content": "Local Mesh Discovery is a dedicated scanning mode that helps you find the best LoRa modem preset for your location and see which nodes are active on each preset. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Before starting, configure these controls: . | Control | Leírás | . | LoRa preset picker | Select one or more presets to scan. Discovery dwells on each selected preset in turn. | . | Dwell time | Time to listen on each preset. Choose from 1, 5, 15, 30, 45, 60, 90, 120, or 180 minutes. Longer dwell times collect more packets and give a clearer picture, but take longer. | . | Keep screen awake | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The node is not connected. | No presets have been selected to scan. | The selected preset uses 2.4 GHz, which your hardware doesn’t support. | . Live progress . While a scan runs, Discovery shows its current stage: . | Stage | What’s happening | . | Preparing scan | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Re-establishing the connection after the preset change. | . | Dwelling on <preset> | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analyzing results | Processing the collected packets and ranking the presets. | . | Restoring home preset | Putting your original LoRa configuration back. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. Metrics include: . | Metric | What it tells you | . | RF health | Overall quality of the radio environment on that preset. | . | Channel utilization | How busy the airwaves were during the dwell. | . | Airtime | Transmission time observed. | . | Direct vs. relayed nodes | How many mesh nodes were heard directly versus via a relay. | . | Bad / duplicate packets | Counts of corrupt and repeated packets, indicating congestion or interference. | . Additional features available from the results: . | Scan History — saved sessions you can revisit; view or delete past scans. | Discovery Map — a map of the nodes found during the scan. | Report export — export a report as a PDF on Android, or as text on other platforms. | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/discovery.html#local-mesh-discovery-scanner",
    
    "relUrl": "/hu-rHU/user/discovery.html#local-mesh-discovery-scanner"
  },"1181": {
    "doc": "Local Mesh Discovery",
    "title": "Mesh Beacon",
    "content": "Mesh Beacon lets nodes invite others to join their mesh. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Received invitations appear as Mesh invitations cards on the Discovery screen. Each card shows the sender’s message plus the offered channel, region, preset, and signal quality, with these actions: . | Join — switch to the offered channel and preset (retunes the node and reboots). When the offer matches your current frequency slot, an Add channel action adds it without a reboot. | Discover — seed a Discovery scan with the offered preset so you can survey that mesh before joining (shown only when the beacon offers a preset). | Dismiss — ignore the invitation. | . Channels advertised by beacons also show up in the scan setup as Beacon channels — select one to include it as a scan target. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/discovery.html#mesh-beacon",
    
    "relUrl": "/hu-rHU/user/discovery.html#mesh-beacon"
  },"1182": {
    "doc": "Local Mesh Discovery",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. 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 . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | 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 Response — The traceroute got nothing back. 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. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Szomszéd-információ . 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 . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 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. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. 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 nodes. | . 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 LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/discovery.html#manual-exploration",
    
    "relUrl": "/hu-rHU/user/discovery.html#manual-exploration"
  },"1183": {
    "doc": "Local Mesh Discovery",
    "title": "Tips for Mesh exploration",
    "content": ". | 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 combined with signal data help you understand why some links are strong and others are weak. | Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly. | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/hu-rHU/user/discovery.html#tips-for-mesh-exploration"
  },"1184": {
    "doc": "Local Mesh Discovery",
    "title": "Related Topics",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/discovery.html#related-topics",
    
    "relUrl": "/hu-rHU/user/discovery.html#related-topics"
  },"1185": {
    "doc": "Локальное обнаружение сети",
    "title": "Локальное обнаружение сети",
    "content": "Инструменты обнаружения помогают понять, как твоя mesh-сетевая структура соединена — какие ноды могут слышать друг друга, по каким путям проходят сообщения и где существуют узкие места или слабые звенья. Приложение предлагает два дополнительных подхода: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Ручное исследование — трассировка, информация о соседях и список нод, которые ты можешь использовать в любое время для изучения конкретных путей и топологии. | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/discovery.html",
    
    "relUrl": "/ru-rRU/user/discovery.html"
  },"1186": {
    "doc": "Локальное обнаружение сети",
    "title": "Обнаружение локальной сети (Сканер)",
    "content": "Локальное обнаружение mesh-сети — это специализированный режим сканирования, который помогает найти лучший пресет LoRa-модема для твоего местоположения и увидеть, какие ноды активны на каждом пресете. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Перед началом, настройте эти параметры: . | Управление | Описание | . | Выбор пресета LoRa | Выберите один или несколько пресетов для сканирования. Обнаружение по очереди задерживается на каждом выбранном пресете. | . | Время задержки | Время прослушки каждого пресета. Выбери один из вариантов: 1, 5, 15, 30, 45, 60, 90, 120 или 180 минут. Более долгое время задержки собирает больше пакетов и даёт более чёткую картину, но занимает больше времени. | . | Не выключать экран | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Распространённые причины, почему она отключена: . | The node is not connected. | Не выбраны пресеты для сканирования. | Выбранный пресет использует частоту 2,4 ГГц, которую ваше оборудование не поддерживает. | . Live progress . Во время сканирования “Обнаружение” показывает текущий этап: . | Этап | Что происходит | . | Preparing scan | Сохранение твоей текущей конфигурации и подготовка к сканированию. | . | Переключение на <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Восстановление соединения после смены пресета. | . | Dwelling on <preset> | Прослушивание текущего пресета для сбора пакетов с обратным отсчётом до следующего шага. | . | Analyzing results | Обработка собранных пакетов и ранжирование пресетов. | . | Restoring home preset | Возврат твоей исходной конфигурации LoRa. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . По завершении сканирования “Обнаружение” показывает карточку результатов для каждого протестированного пресета, а также общую сводку. Метрики включают: . | Метрическая | Что для тебя это значит | . | Состояние радиоэфира | Общее качество радиообстановки на этом пресете. | . | Использование канала | Насколько загруженным был эфир во время прослушивания. | . | Эфирное время | Наблюдаемое время передачи. | . | Прямые и ретранслированные ноды | Сколько mesh-нод было услышано напрямую, а сколько через ретранслятор. | . | Повреждённые / повторные пакеты | Количество повреждённых и повторных пакетов, указывающее на перегрузку или помехи. | . Дополнительные функции, доступные из результатов: . | История сканирования — сохранённые сеансы, которые ты можешь просмотреть снова; просматривайте или удаляйте прошлые сканирования. | Карта обнаружения — карта нод, найденных во время сканирования. | Экспорт отчёта — экспортируйте отчёт в формате PDF на Android или в виде текста на других платформах. | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/discovery.html#%D0%BE%D0%B1%D0%BD%D0%B0%D1%80%D1%83%D0%B6%D0%B5%D0%BD%D0%B8%D0%B5-%D0%BB%D0%BE%D0%BA%D0%B0%D0%BB%D1%8C%D0%BD%D0%BE%D0%B9-%D1%81%D0%B5%D1%82%D0%B8-%D1%81%D0%BA%D0%B0%D0%BD%D0%B5%D1%80",
    
    "relUrl": "/ru-rRU/user/discovery.html#обнаружение-локальной-сети-сканер"
  },"1187": {
    "doc": "Локальное обнаружение сети",
    "title": "Маяк сети",
    "content": "Маяк mesh-сети позволяет нодам приглашать другие устройства присоединиться к своей сети. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Слушать маяки — принимать приглашения, передаваемые другими нодами. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Полученные приглашения отображаются в виде карточек “Приглашения mesh-сети” на экране “Обнаружение”. На каждой карточке показано сообщение отправителя, а также предлагаемые канал, регион, пресет и качество сигнала, и доступны следующие действия: . | Join — switch to the offered channel and preset (retunes the node and reboots). Если предложение совпадает с вашим текущим частотным слотом, действие “Добавить канал” добавляет его без перезагрузки. | Обнаружить — запустить сканирование «Обнаружения» с предложенным пресетом, чтобы ты мог изучить эту сеть перед присоединением (отображается, только если маяк передаёт пресет). | Отклонить — проигнорировать приглашение. | . Каналы, объявленные маяками, также отображаются в настройках сканирования как Каналы маяков — выберите один, чтобы включить его в число целей сканирования. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/discovery.html#%D0%BC%D0%B0%D1%8F%D0%BA-%D1%81%D0%B5%D1%82%D0%B8",
    
    "relUrl": "/ru-rRU/user/discovery.html#маяк-сети"
  },"1188": {
    "doc": "Локальное обнаружение сети",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. Используйте их для исследования конкретных путей и построения картины топологии — вместе с полным сканированием или вместо него. Трассировка маршрута . Трассировка показывает точный путь, который сообщение проходит от твоей ноды до любой другой ноды в сети. Это самый полезный инструмент для отладки проблем с подключением. Выполнение трассировки . | Перейди в Ноды и коснись ноды, которую ты хочешь отследить. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . Результат трассировки выглядит так: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | На что обращать внимание | Что это значит | . | All hops show Good SNR (green) | Здоровый путь — сообщения идут без сбоев | . | One hop shows a poor SNR (orange or red) | Слабое звено — этот сегмент ретрансляции хрупкий | . | Много хопов (4+) | Длинный путь — подумай о перемещении ноды для его сокращения | . | Другой путь при повторе | Сеть адаптируется — существуют несколько маршрутов (это хорошо!) | . 💡 Совет: Запусти трассировку несколько раз в течение нескольких минут. Если путь изменяется, у твоей сети есть лишние маршруты — признак хорошо связанной сети. Устранение неполадок с трассировкой . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Проверь, что обе ноды имеют хотя бы один канал с одинаковым ключом шифрования. | Время ожидания трассировки истекло — путь может быть слишком длинным (превышен лимит хопов) или нода ретрансляции перегружена. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Асимметричные маршруты — трассировка от A→B может проходить по другому пути, чем B→A. This is normal — radio propagation isn’t always symmetric. | . Информация об окружении . Модуль информации о соседях позволяет каждой ноде передавать список нод, которые она может слышать напрямую (на расстоянии одного хопа). Когда несколько нод делятся своими списками соседей, ты можешь составить карту топологии всей mesh-сети. Включение информации о соседях . | Navigate to Settings → Module configuration → Neighbor Info. | Включение модуля | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Другие ноды с включённым модулем информации о соседях делают то же самое. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Каждая запись о соседе показывает ноду, которая была услышана напрямую, и качество её сигнала. | Объединяйте данные о соседях от нескольких нод, чтобы понять полную топологию mesh-сети. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . Сам по себе список нод — мощный инструмент обнаружения, если ты эффективно будешь использовать его возможности фильтрации и сортировки. Finding new nodes . | Сортируйте по “Последнему приёму”, чтобы увидеть вверху списка ноды, активные в последнее время. | 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 nodes. | . Assessing connectivity . | Сортируйте по «Хопам», чтобы видеть, какие ноды доступны напрямую (0 хопов), а какие — через ретрансляцию. | Сортируйте по “Расстоянию”, чтобы найти близлежащие ноды и убедиться, что они доступны. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Отключите “Исключить инфраструктуру”, чтобы увидеть ноды Router, Router Late и Client Base. | Проверьте качество их сигнала и время последнего приёма, чтобы убедиться, что твои ноды инфраструктуры работают исправно. | . См. раздел Ноды для получения полной информации о параметрах фильтрации и сортировки. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/discovery.html#manual-exploration",
    
    "relUrl": "/ru-rRU/user/discovery.html#manual-exploration"
  },"1189": {
    "doc": "Локальное обнаружение сети",
    "title": "Tips for Mesh exploration",
    "content": ". | Начните с трассировки — она даёт тебе немедленную, пригодную для использования информацию о конкретном пути. | Включите информацию о соседях на ключевых нодах — особенно на роутерах и ретрансляторах, чтобы составить картину магистральной сети. | Проверьте карту — расположение нод на Карте в сочетании с данными о сигнале помогает тебе понять, почему одни соединения сильные, а другие слабые. | Сравнивайте сигнал с течением времени — используйте руководство по Измерителю сигнала для правильной интерпретации значений SNR и RSSI. | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/ru-rRU/user/discovery.html#tips-for-mesh-exploration"
  },"1190": {
    "doc": "Локальное обнаружение сети",
    "title": "Связанные темы",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/discovery.html#%D1%81%D0%B2%D1%8F%D0%B7%D0%B0%D0%BD%D0%BD%D1%8B%D0%B5-%D1%82%D0%B5%D0%BC%D1%8B",
    
    "relUrl": "/ru-rRU/user/discovery.html#связанные-темы"
  },"1191": {
    "doc": "Vyhledávání zařízení v místní mesh síti",
    "title": "Vyhledávání zařízení v místní mesh síti",
    "content": "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. The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Manual exploration — traceroute, Neighbor Info, and the node list, which you can use at any time to investigate specific paths and topology. | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/discovery.html",
    
    "relUrl": "/cs-rCZ/user/discovery.html"
  },"1192": {
    "doc": "Vyhledávání zařízení v místní mesh síti",
    "title": "Local Mesh Discovery (Scanner)",
    "content": "Local Mesh Discovery is a dedicated scanning mode that helps you find the best LoRa modem preset for your location and see which nodes are active on each preset. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Before starting, configure these controls: . | Control | Popis | . | LoRa preset picker | Select one or more presets to scan. Discovery dwells on each selected preset in turn. | . | Dwell time | Time to listen on each preset. Choose from 1, 5, 15, 30, 45, 60, 90, 120, or 180 minutes. Longer dwell times collect more packets and give a clearer picture, but take longer. | . | Keep screen awake | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The node is not connected. | No presets have been selected to scan. | The selected preset uses 2.4 GHz, which your hardware doesn’t support. | . Live progress . While a scan runs, Discovery shows its current stage: . | Stage | What’s happening | . | Preparing scan | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Re-establishing the connection after the preset change. | . | Dwelling on <preset> | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analyzing results | Processing the collected packets and ranking the presets. | . | Restoring home preset | Putting your original LoRa configuration back. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. Metrics include: . | Metrický | What it tells you | . | RF health | Overall quality of the radio environment on that preset. | . | Využití kanálu | How busy the airwaves were during the dwell. | . | Airtime | Transmission time observed. | . | Direct vs. relayed nodes | How many mesh nodes were heard directly versus via a relay. | . | Bad / duplicate packets | Counts of corrupt and repeated packets, indicating congestion or interference. | . Additional features available from the results: . | Scan History — saved sessions you can revisit; view or delete past scans. | Discovery Map — a map of the nodes found during the scan. | Report export — export a report as a PDF on Android, or as text on other platforms. | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/discovery.html#local-mesh-discovery-scanner",
    
    "relUrl": "/cs-rCZ/user/discovery.html#local-mesh-discovery-scanner"
  },"1193": {
    "doc": "Vyhledávání zařízení v místní mesh síti",
    "title": "Mesh maják",
    "content": "Mesh Beacon lets nodes invite others to join their mesh. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Received invitations appear as Mesh invitations cards on the Discovery screen. Each card shows the sender’s message plus the offered channel, region, preset, and signal quality, with these actions: . | Join — switch to the offered channel and preset (retunes the node and reboots). When the offer matches your current frequency slot, an Add channel action adds it without a reboot. | Discover — seed a Discovery scan with the offered preset so you can survey that mesh before joining (shown only when the beacon offers a preset). | Dismiss — ignore the invitation. | . Channels advertised by beacons also show up in the scan setup as Beacon channels — select one to include it as a scan target. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/discovery.html#mesh-maj%C3%A1k",
    
    "relUrl": "/cs-rCZ/user/discovery.html#mesh-maják"
  },"1194": {
    "doc": "Vyhledávání zařízení v místní mesh síti",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. 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 . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | 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 Response — The traceroute got nothing back. 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. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Informace o sousedech . 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 . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 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. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. 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 nodes. | . 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 LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/discovery.html#manual-exploration",
    
    "relUrl": "/cs-rCZ/user/discovery.html#manual-exploration"
  },"1195": {
    "doc": "Vyhledávání zařízení v místní mesh síti",
    "title": "Tips for Mesh exploration",
    "content": ". | 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 combined with signal data help you understand why some links are strong and others are weak. | Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly. | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/cs-rCZ/user/discovery.html#tips-for-mesh-exploration"
  },"1196": {
    "doc": "Vyhledávání zařízení v místní mesh síti",
    "title": "Related Topics",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/discovery.html#related-topics",
    
    "relUrl": "/cs-rCZ/user/discovery.html#related-topics"
  },"1197": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery",
    "content": "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. The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Manual exploration — traceroute, Neighbor Info, and the node list, which you can use at any time to investigate specific paths and topology. | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/discovery.html",
    
    "relUrl": "/bg-rBG/user/discovery.html"
  },"1198": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery (Scanner)",
    "content": "Local Mesh Discovery is a dedicated scanning mode that helps you find the best LoRa modem preset for your location and see which nodes are active on each preset. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Преди да започнете, конфигурирайте тези контроли: . | Контрол | Описание | . | LoRa preset picker | Select one or more presets to scan. Discovery dwells on each selected preset in turn. | . | Dwell time | Time to listen on each preset. Choose from 1, 5, 15, 30, 45, 60, 90, 120, or 180 minutes. Longer dwell times collect more packets and give a clearer picture, but take longer. | . | Keep screen awake | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The node is not connected. | No presets have been selected to scan. | The selected preset uses 2.4 GHz, which your hardware doesn’t support. | . Live progress . While a scan runs, Discovery shows its current stage: . | Stage | What’s happening | . | Preparing scan | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Re-establishing the connection after the preset change. | . | Dwelling on <preset> | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analyzing results | Processing the collected packets and ranking the presets. | . | Restoring home preset | Putting your original LoRa configuration back. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. Metrics include: . | Метрични | What it tells you | . | RF health | Overall quality of the radio environment on that preset. | . | Използване на канала | How busy the airwaves were during the dwell. | . | Airtime | Transmission time observed. | . | Direct vs. relayed nodes | How many mesh nodes were heard directly versus via a relay. | . | Bad / duplicate packets | Counts of corrupt and repeated packets, indicating congestion or interference. | . Additional features available from the results: . | Scan History — saved sessions you can revisit; view or delete past scans. | Discovery Map — a map of the nodes found during the scan. | Report export — export a report as a PDF on Android, or as text on other platforms. | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/discovery.html#local-mesh-discovery-scanner",
    
    "relUrl": "/bg-rBG/user/discovery.html#local-mesh-discovery-scanner"
  },"1199": {
    "doc": "Local Mesh Discovery",
    "title": "Mesh Beacon",
    "content": "Mesh Beacon lets nodes invite others to join their mesh. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Received invitations appear as Mesh invitations cards on the Discovery screen. Each card shows the sender’s message plus the offered channel, region, preset, and signal quality, with these actions: . | Join — switch to the offered channel and preset (retunes the node and reboots). When the offer matches your current frequency slot, an Add channel action adds it without a reboot. | Discover — seed a Discovery scan with the offered preset so you can survey that mesh before joining (shown only when the beacon offers a preset). | Dismiss — ignore the invitation. | . Channels advertised by beacons also show up in the scan setup as Beacon channels — select one to include it as a scan target. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/discovery.html#mesh-beacon",
    
    "relUrl": "/bg-rBG/user/discovery.html#mesh-beacon"
  },"1200": {
    "doc": "Local Mesh Discovery",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Трасиране на маршрут . 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 . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | 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 Response — The traceroute got nothing back. 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. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t 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 . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 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. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. 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 nodes. | . 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 LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/discovery.html#manual-exploration",
    
    "relUrl": "/bg-rBG/user/discovery.html#manual-exploration"
  },"1201": {
    "doc": "Local Mesh Discovery",
    "title": "Tips for Mesh exploration",
    "content": ". | 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 combined with signal data help you understand why some links are strong and others are weak. | Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly. | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/bg-rBG/user/discovery.html#tips-for-mesh-exploration"
  },"1202": {
    "doc": "Local Mesh Discovery",
    "title": "Свързани теми",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/discovery.html#%D1%81%D0%B2%D1%8A%D1%80%D0%B7%D0%B0%D0%BD%D0%B8-%D1%82%D0%B5%D0%BC%D0%B8",
    
    "relUrl": "/bg-rBG/user/discovery.html#свързани-теми"
  },"1203": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery",
    "content": "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. The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Manual exploration — traceroute, Neighbor Info, and the node list, which you can use at any time to investigate specific paths and topology. | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/discovery.html",
    
    "relUrl": "/ga-rIE/user/discovery.html"
  },"1204": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery (Scanner)",
    "content": "Local Mesh Discovery is a dedicated scanning mode that helps you find the best LoRa modem preset for your location and see which nodes are active on each preset. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Before starting, configure these controls: . | Control | Cur síos | . | LoRa preset picker | Select one or more presets to scan. Discovery dwells on each selected preset in turn. | . | Dwell time | Time to listen on each preset. Choose from 1, 5, 15, 30, 45, 60, 90, 120, or 180 minutes. Longer dwell times collect more packets and give a clearer picture, but take longer. | . | Keep screen awake | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The node is not connected. | No presets have been selected to scan. | The selected preset uses 2.4 GHz, which your hardware doesn’t support. | . Live progress . While a scan runs, Discovery shows its current stage: . | Stage | What’s happening | . | Preparing scan | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Re-establishing the connection after the preset change. | . | Dwelling on <preset> | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analyzing results | Processing the collected packets and ranking the presets. | . | Restoring home preset | Putting your original LoRa configuration back. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. Metrics include: . | Metric | What it tells you | . | RF health | Overall quality of the radio environment on that preset. | . | Channel utilization | How busy the airwaves were during the dwell. | . | Airtime | Transmission time observed. | . | Direct vs. relayed nodes | How many mesh nodes were heard directly versus via a relay. | . | Bad / duplicate packets | Counts of corrupt and repeated packets, indicating congestion or interference. | . Additional features available from the results: . | Scan History — saved sessions you can revisit; view or delete past scans. | Discovery Map — a map of the nodes found during the scan. | Report export — export a report as a PDF on Android, or as text on other platforms. | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/discovery.html#local-mesh-discovery-scanner",
    
    "relUrl": "/ga-rIE/user/discovery.html#local-mesh-discovery-scanner"
  },"1205": {
    "doc": "Local Mesh Discovery",
    "title": "Mesh Beacon",
    "content": "Mesh Beacon lets nodes invite others to join their mesh. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Received invitations appear as Mesh invitations cards on the Discovery screen. Each card shows the sender’s message plus the offered channel, region, preset, and signal quality, with these actions: . | Join — switch to the offered channel and preset (retunes the node and reboots). When the offer matches your current frequency slot, an Add channel action adds it without a reboot. | Discover — seed a Discovery scan with the offered preset so you can survey that mesh before joining (shown only when the beacon offers a preset). | Dismiss — ignore the invitation. | . Channels advertised by beacons also show up in the scan setup as Beacon channels — select one to include it as a scan target. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/discovery.html#mesh-beacon",
    
    "relUrl": "/ga-rIE/user/discovery.html#mesh-beacon"
  },"1206": {
    "doc": "Local Mesh Discovery",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Céim rianadóireachta . 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 . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | 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 Response — The traceroute got nothing back. 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. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t 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 . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 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. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. 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 nodes. | . 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 LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/discovery.html#manual-exploration",
    
    "relUrl": "/ga-rIE/user/discovery.html#manual-exploration"
  },"1207": {
    "doc": "Local Mesh Discovery",
    "title": "Tips for Mesh exploration",
    "content": ". | 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 combined with signal data help you understand why some links are strong and others are weak. | Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly. | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/ga-rIE/user/discovery.html#tips-for-mesh-exploration"
  },"1208": {
    "doc": "Local Mesh Discovery",
    "title": "Related Topics",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/discovery.html#related-topics",
    
    "relUrl": "/ga-rIE/user/discovery.html#related-topics"
  },"1209": {
    "doc": "Découverte de maille locale",
    "title": "Découverte de maille locale",
    "content": "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. The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Manual exploration — traceroute, Neighbor Info, and the node list, which you can use at any time to investigate specific paths and topology. | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/discovery.html",
    
    "relUrl": "/fr-rCA/user/discovery.html"
  },"1210": {
    "doc": "Découverte de maille locale",
    "title": "Local Mesh Discovery (Scanner)",
    "content": "Local Mesh Discovery is a dedicated scanning mode that helps you find the best LoRa modem preset for your location and see which nodes are active on each preset. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Before starting, configure these controls: . | Control | Description | . | LoRa preset picker | Select one or more presets to scan. Discovery dwells on each selected preset in turn. | . | Dwell time | Time to listen on each preset. Choose from 1, 5, 15, 30, 45, 60, 90, 120, or 180 minutes. Longer dwell times collect more packets and give a clearer picture, but take longer. | . | Keep screen awake | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The node is not connected. | No presets have been selected to scan. | The selected preset uses 2.4 GHz, which your hardware doesn’t support. | . Live progress . While a scan runs, Discovery shows its current stage: . | Stage | What’s happening | . | Preparing scan | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Re-establishing the connection after the preset change. | . | Dwelling on <preset> | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analyzing results | Processing the collected packets and ranking the presets. | . | Restoring home preset | Putting your original LoRa configuration back. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. Metrics include: . | Métrique | What it tells you | . | RF health | Overall quality of the radio environment on that preset. | . | Utilisation du canal | How busy the airwaves were during the dwell. | . | Temps d’émission | Transmission time observed. | . | Direct vs. relayed nodes | How many mesh nodes were heard directly versus via a relay. | . | Bad / duplicate packets | Counts of corrupt and repeated packets, indicating congestion or interference. | . Additional features available from the results: . | Scan History — saved sessions you can revisit; view or delete past scans. | Discovery Map — a map of the nodes found during the scan. | Report export — export a report as a PDF on Android, or as text on other platforms. | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/discovery.html#local-mesh-discovery-scanner",
    
    "relUrl": "/fr-rCA/user/discovery.html#local-mesh-discovery-scanner"
  },"1211": {
    "doc": "Découverte de maille locale",
    "title": "Mesh Beacon",
    "content": "Mesh Beacon lets nodes invite others to join their mesh. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Received invitations appear as Mesh invitations cards on the Discovery screen. Each card shows the sender’s message plus the offered channel, region, preset, and signal quality, with these actions: . | Join — switch to the offered channel and preset (retunes the node and reboots). When the offer matches your current frequency slot, an Add channel action adds it without a reboot. | Discover — seed a Discovery scan with the offered preset so you can survey that mesh before joining (shown only when the beacon offers a preset). | Dismiss — ignore the invitation. | . Channels advertised by beacons also show up in the scan setup as Beacon channels — select one to include it as a scan target. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/discovery.html#mesh-beacon",
    
    "relUrl": "/fr-rCA/user/discovery.html#mesh-beacon"
  },"1212": {
    "doc": "Découverte de maille locale",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. 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 . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | 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 Response — The traceroute got nothing back. 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. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Informations sur les voisins . 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 . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 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. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. 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 nodes. | . 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 LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/discovery.html#manual-exploration",
    
    "relUrl": "/fr-rCA/user/discovery.html#manual-exploration"
  },"1213": {
    "doc": "Découverte de maille locale",
    "title": "Tips for Mesh exploration",
    "content": ". | 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 combined with signal data help you understand why some links are strong and others are weak. | Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly. | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/fr-rCA/user/discovery.html#tips-for-mesh-exploration"
  },"1214": {
    "doc": "Découverte de maille locale",
    "title": "Related Topics",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/discovery.html#related-topics",
    
    "relUrl": "/fr-rCA/user/discovery.html#related-topics"
  },"1215": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery",
    "content": "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. The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Manual exploration — traceroute, Neighbor Info, and the node list, which you can use at any time to investigate specific paths and topology. | . ",
    "url": "/Meshtastic-Android/main/srp/user/discovery.html",
    
    "relUrl": "/srp/user/discovery.html"
  },"1216": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery (Scanner)",
    "content": "Local Mesh Discovery is a dedicated scanning mode that helps you find the best LoRa modem preset for your location and see which nodes are active on each preset. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Before starting, configure these controls: . | Control | Опис | . | LoRa preset picker | Select one or more presets to scan. Discovery dwells on each selected preset in turn. | . | Dwell time | Time to listen on each preset. Choose from 1, 5, 15, 30, 45, 60, 90, 120, or 180 minutes. Longer dwell times collect more packets and give a clearer picture, but take longer. | . | Keep screen awake | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The node is not connected. | No presets have been selected to scan. | The selected preset uses 2.4 GHz, which your hardware doesn’t support. | . Live progress . While a scan runs, Discovery shows its current stage: . | Stage | What’s happening | . | Preparing scan | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Re-establishing the connection after the preset change. | . | Dwelling on <preset> | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analyzing results | Processing the collected packets and ranking the presets. | . | Restoring home preset | Putting your original LoRa configuration back. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. Metrics include: . | Метрика | What it tells you | . | RF health | Overall quality of the radio environment on that preset. | . | Channel utilization | How busy the airwaves were during the dwell. | . | Време емитовања | Transmission time observed. | . | Direct vs. relayed nodes | How many mesh nodes were heard directly versus via a relay. | . | Bad / duplicate packets | Counts of corrupt and repeated packets, indicating congestion or interference. | . Additional features available from the results: . | Scan History — saved sessions you can revisit; view or delete past scans. | Discovery Map — a map of the nodes found during the scan. | Report export — export a report as a PDF on Android, or as text on other platforms. | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/srp/user/discovery.html#local-mesh-discovery-scanner",
    
    "relUrl": "/srp/user/discovery.html#local-mesh-discovery-scanner"
  },"1217": {
    "doc": "Local Mesh Discovery",
    "title": "Mesh Beacon",
    "content": "Mesh Beacon lets nodes invite others to join their mesh. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Received invitations appear as Mesh invitations cards on the Discovery screen. Each card shows the sender’s message plus the offered channel, region, preset, and signal quality, with these actions: . | Join — switch to the offered channel and preset (retunes the node and reboots). When the offer matches your current frequency slot, an Add channel action adds it without a reboot. | Discover — seed a Discovery scan with the offered preset so you can survey that mesh before joining (shown only when the beacon offers a preset). | Dismiss — ignore the invitation. | . Channels advertised by beacons also show up in the scan setup as Beacon channels — select one to include it as a scan target. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/srp/user/discovery.html#mesh-beacon",
    
    "relUrl": "/srp/user/discovery.html#mesh-beacon"
  },"1218": {
    "doc": "Local Mesh Discovery",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Праћење руте . 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 . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | 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 Response — The traceroute got nothing back. 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. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t 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 . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 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. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. 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 nodes. | . 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 LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ",
    "url": "/Meshtastic-Android/main/srp/user/discovery.html#manual-exploration",
    
    "relUrl": "/srp/user/discovery.html#manual-exploration"
  },"1219": {
    "doc": "Local Mesh Discovery",
    "title": "Tips for Mesh exploration",
    "content": ". | 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 combined with signal data help you understand why some links are strong and others are weak. | Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly. | . ",
    "url": "/Meshtastic-Android/main/srp/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/srp/user/discovery.html#tips-for-mesh-exploration"
  },"1220": {
    "doc": "Local Mesh Discovery",
    "title": "Related Topics",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/srp/user/discovery.html#related-topics",
    
    "relUrl": "/srp/user/discovery.html#related-topics"
  },"1221": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery",
    "content": "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. The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Manual exploration — traceroute, Neighbor Info, and the node list, which you can use at any time to investigate specific paths and topology. | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/discovery.html",
    
    "relUrl": "/ca-rES/user/discovery.html"
  },"1222": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery (Scanner)",
    "content": "Local Mesh Discovery is a dedicated scanning mode that helps you find the best LoRa modem preset for your location and see which nodes are active on each preset. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Before starting, configure these controls: . | Control | Descripció | . | LoRa preset picker | Select one or more presets to scan. Discovery dwells on each selected preset in turn. | . | Dwell time | Time to listen on each preset. Choose from 1, 5, 15, 30, 45, 60, 90, 120, or 180 minutes. Longer dwell times collect more packets and give a clearer picture, but take longer. | . | Keep screen awake | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The node is not connected. | No presets have been selected to scan. | The selected preset uses 2.4 GHz, which your hardware doesn’t support. | . Live progress . While a scan runs, Discovery shows its current stage: . | Stage | What’s happening | . | Preparing scan | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Re-establishing the connection after the preset change. | . | Dwelling on <preset> | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analyzing results | Processing the collected packets and ranking the presets. | . | Restoring home preset | Putting your original LoRa configuration back. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. Metrics include: . | Metric | What it tells you | . | RF health | Overall quality of the radio environment on that preset. | . | Channel utilization | How busy the airwaves were during the dwell. | . | Airtime | Transmission time observed. | . | Direct vs. relayed nodes | How many mesh nodes were heard directly versus via a relay. | . | Bad / duplicate packets | Counts of corrupt and repeated packets, indicating congestion or interference. | . Additional features available from the results: . | Scan History — saved sessions you can revisit; view or delete past scans. | Discovery Map — a map of the nodes found during the scan. | Report export — export a report as a PDF on Android, or as text on other platforms. | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/discovery.html#local-mesh-discovery-scanner",
    
    "relUrl": "/ca-rES/user/discovery.html#local-mesh-discovery-scanner"
  },"1223": {
    "doc": "Local Mesh Discovery",
    "title": "Mesh Beacon",
    "content": "Mesh Beacon lets nodes invite others to join their mesh. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Received invitations appear as Mesh invitations cards on the Discovery screen. Each card shows the sender’s message plus the offered channel, region, preset, and signal quality, with these actions: . | Join — switch to the offered channel and preset (retunes the node and reboots). When the offer matches your current frequency slot, an Add channel action adds it without a reboot. | Discover — seed a Discovery scan with the offered preset so you can survey that mesh before joining (shown only when the beacon offers a preset). | Dismiss — ignore the invitation. | . Channels advertised by beacons also show up in the scan setup as Beacon channels — select one to include it as a scan target. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/discovery.html#mesh-beacon",
    
    "relUrl": "/ca-rES/user/discovery.html#mesh-beacon"
  },"1224": {
    "doc": "Local Mesh Discovery",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. 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 . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | 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 Response — The traceroute got nothing back. 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. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t 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 . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 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. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. 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 nodes. | . 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 LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/discovery.html#manual-exploration",
    
    "relUrl": "/ca-rES/user/discovery.html#manual-exploration"
  },"1225": {
    "doc": "Local Mesh Discovery",
    "title": "Tips for Mesh exploration",
    "content": ". | 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 combined with signal data help you understand why some links are strong and others are weak. | Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly. | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/ca-rES/user/discovery.html#tips-for-mesh-exploration"
  },"1226": {
    "doc": "Local Mesh Discovery",
    "title": "Related Topics",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/discovery.html#related-topics",
    
    "relUrl": "/ca-rES/user/discovery.html#related-topics"
  },"1227": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery",
    "content": "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. The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Manual exploration — traceroute, Neighbor Info, and the node list, which you can use at any time to investigate specific paths and topology. | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/discovery.html",
    
    "relUrl": "/ko-rKR/user/discovery.html"
  },"1228": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery (Scanner)",
    "content": "Local Mesh Discovery is a dedicated scanning mode that helps you find the best LoRa modem preset for your location and see which nodes are active on each preset. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Before starting, configure these controls: . | Control | 설명 | . | LoRa preset picker | Select one or more presets to scan. Discovery dwells on each selected preset in turn. | . | Dwell time | Time to listen on each preset. Choose from 1, 5, 15, 30, 45, 60, 90, 120, or 180 minutes. Longer dwell times collect more packets and give a clearer picture, but take longer. | . | Keep screen awake | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The node is not connected. | No presets have been selected to scan. | The selected preset uses 2.4 GHz, which your hardware doesn’t support. | . Live progress . While a scan runs, Discovery shows its current stage: . | Stage | What’s happening | . | Preparing scan | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Re-establishing the connection after the preset change. | . | Dwelling on <preset> | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analyzing results | Processing the collected packets and ranking the presets. | . | Restoring home preset | Putting your original LoRa configuration back. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. Metrics include: . | Metric | What it tells you | . | RF health | Overall quality of the radio environment on that preset. | . | Channel utilization | How busy the airwaves were during the dwell. | . | Airtime | Transmission time observed. | . | Direct vs. relayed nodes | How many mesh nodes were heard directly versus via a relay. | . | Bad / duplicate packets | Counts of corrupt and repeated packets, indicating congestion or interference. | . Additional features available from the results: . | Scan History — saved sessions you can revisit; view or delete past scans. | Discovery Map — a map of the nodes found during the scan. | Report export — export a report as a PDF on Android, or as text on other platforms. | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/discovery.html#local-mesh-discovery-scanner",
    
    "relUrl": "/ko-rKR/user/discovery.html#local-mesh-discovery-scanner"
  },"1229": {
    "doc": "Local Mesh Discovery",
    "title": "Mesh Beacon",
    "content": "Mesh Beacon lets nodes invite others to join their mesh. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Received invitations appear as Mesh invitations cards on the Discovery screen. Each card shows the sender’s message plus the offered channel, region, preset, and signal quality, with these actions: . | Join — switch to the offered channel and preset (retunes the node and reboots). When the offer matches your current frequency slot, an Add channel action adds it without a reboot. | Discover — seed a Discovery scan with the offered preset so you can survey that mesh before joining (shown only when the beacon offers a preset). | Dismiss — ignore the invitation. | . Channels advertised by beacons also show up in the scan setup as Beacon channels — select one to include it as a scan target. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/discovery.html#mesh-beacon",
    
    "relUrl": "/ko-rKR/user/discovery.html#mesh-beacon"
  },"1230": {
    "doc": "Local Mesh Discovery",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. 추적 루트 . 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 . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | 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 Response — The traceroute got nothing back. 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. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . 이웃 정보 . 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 . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 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. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. 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 nodes. | . 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 LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/discovery.html#manual-exploration",
    
    "relUrl": "/ko-rKR/user/discovery.html#manual-exploration"
  },"1231": {
    "doc": "Local Mesh Discovery",
    "title": "Tips for Mesh exploration",
    "content": ". | 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 combined with signal data help you understand why some links are strong and others are weak. | Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly. | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/ko-rKR/user/discovery.html#tips-for-mesh-exploration"
  },"1232": {
    "doc": "Local Mesh Discovery",
    "title": "Related Topics",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/discovery.html#related-topics",
    
    "relUrl": "/ko-rKR/user/discovery.html#related-topics"
  },"1233": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery",
    "content": "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. The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Manual exploration — traceroute, Neighbor Info, and the node list, which you can use at any time to investigate specific paths and topology. | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/discovery.html",
    
    "relUrl": "/sv-rSE/user/discovery.html"
  },"1234": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery (Scanner)",
    "content": "Local Mesh Discovery is a dedicated scanning mode that helps you find the best LoRa modem preset for your location and see which nodes are active on each preset. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Before starting, configure these controls: . | Control | Beskrivning | . | LoRa preset picker | Select one or more presets to scan. Discovery dwells on each selected preset in turn. | . | Dwell time | Time to listen on each preset. Choose from 1, 5, 15, 30, 45, 60, 90, 120, or 180 minutes. Longer dwell times collect more packets and give a clearer picture, but take longer. | . | Keep screen awake | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The node is not connected. | No presets have been selected to scan. | The selected preset uses 2.4 GHz, which your hardware doesn’t support. | . Live progress . While a scan runs, Discovery shows its current stage: . | Stage | What’s happening | . | Preparing scan | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Re-establishing the connection after the preset change. | . | Dwelling on <preset> | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analyzing results | Processing the collected packets and ranking the presets. | . | Restoring home preset | Putting your original LoRa configuration back. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. Metrics include: . | Metric | What it tells you | . | RF health | Overall quality of the radio environment on that preset. | . | Kanalutnyttjande | How busy the airwaves were during the dwell. | . | Airtime | Transmission time observed. | . | Direct vs. relayed nodes | How many mesh nodes were heard directly versus via a relay. | . | Bad / duplicate packets | Counts of corrupt and repeated packets, indicating congestion or interference. | . Additional features available from the results: . | Scan History — saved sessions you can revisit; view or delete past scans. | Discovery Map — a map of the nodes found during the scan. | Report export — export a report as a PDF on Android, or as text on other platforms. | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/discovery.html#local-mesh-discovery-scanner",
    
    "relUrl": "/sv-rSE/user/discovery.html#local-mesh-discovery-scanner"
  },"1235": {
    "doc": "Local Mesh Discovery",
    "title": "Mesh Beacon",
    "content": "Mesh Beacon lets nodes invite others to join their mesh. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Received invitations appear as Mesh invitations cards on the Discovery screen. Each card shows the sender’s message plus the offered channel, region, preset, and signal quality, with these actions: . | Join — switch to the offered channel and preset (retunes the node and reboots). When the offer matches your current frequency slot, an Add channel action adds it without a reboot. | Discover — seed a Discovery scan with the offered preset so you can survey that mesh before joining (shown only when the beacon offers a preset). | Dismiss — ignore the invitation. | . Channels advertised by beacons also show up in the scan setup as Beacon channels — select one to include it as a scan target. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/discovery.html#mesh-beacon",
    
    "relUrl": "/sv-rSE/user/discovery.html#mesh-beacon"
  },"1236": {
    "doc": "Local Mesh Discovery",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traceroute (spåra rutt) . 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 . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | 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 Response — The traceroute got nothing back. 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. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Granninformation . 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 . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 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. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. 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 nodes. | . 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 LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/discovery.html#manual-exploration",
    
    "relUrl": "/sv-rSE/user/discovery.html#manual-exploration"
  },"1237": {
    "doc": "Local Mesh Discovery",
    "title": "Tips for Mesh exploration",
    "content": ". | 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 combined with signal data help you understand why some links are strong and others are weak. | Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly. | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/sv-rSE/user/discovery.html#tips-for-mesh-exploration"
  },"1238": {
    "doc": "Local Mesh Discovery",
    "title": "Related Topics",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/discovery.html#related-topics",
    
    "relUrl": "/sv-rSE/user/discovery.html#related-topics"
  },"1239": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery",
    "content": "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. The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Manual exploration — traceroute, Neighbor Info, and the node list, which you can use at any time to investigate specific paths and topology. | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/discovery.html",
    
    "relUrl": "/ht-rHT/user/discovery.html"
  },"1240": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery (Scanner)",
    "content": "Local Mesh Discovery is a dedicated scanning mode that helps you find the best LoRa modem preset for your location and see which nodes are active on each preset. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Before starting, configure these controls: . | Control | Deskripsyon | . | LoRa preset picker | Select one or more presets to scan. Discovery dwells on each selected preset in turn. | . | Dwell time | Time to listen on each preset. Choose from 1, 5, 15, 30, 45, 60, 90, 120, or 180 minutes. Longer dwell times collect more packets and give a clearer picture, but take longer. | . | Keep screen awake | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The node is not connected. | No presets have been selected to scan. | The selected preset uses 2.4 GHz, which your hardware doesn’t support. | . Live progress . While a scan runs, Discovery shows its current stage: . | Stage | What’s happening | . | Preparing scan | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Re-establishing the connection after the preset change. | . | Dwelling on <preset> | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analyzing results | Processing the collected packets and ranking the presets. | . | Restoring home preset | Putting your original LoRa configuration back. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. Metrics include: . | Metric | What it tells you | . | RF health | Overall quality of the radio environment on that preset. | . | Channel utilization | How busy the airwaves were during the dwell. | . | Airtime | Transmission time observed. | . | Direct vs. relayed nodes | How many mesh nodes were heard directly versus via a relay. | . | Bad / duplicate packets | Counts of corrupt and repeated packets, indicating congestion or interference. | . Additional features available from the results: . | Scan History — saved sessions you can revisit; view or delete past scans. | Discovery Map — a map of the nodes found during the scan. | Report export — export a report as a PDF on Android, or as text on other platforms. | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/discovery.html#local-mesh-discovery-scanner",
    
    "relUrl": "/ht-rHT/user/discovery.html#local-mesh-discovery-scanner"
  },"1241": {
    "doc": "Local Mesh Discovery",
    "title": "Mesh Beacon",
    "content": "Mesh Beacon lets nodes invite others to join their mesh. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Received invitations appear as Mesh invitations cards on the Discovery screen. Each card shows the sender’s message plus the offered channel, region, preset, and signal quality, with these actions: . | Join — switch to the offered channel and preset (retunes the node and reboots). When the offer matches your current frequency slot, an Add channel action adds it without a reboot. | Discover — seed a Discovery scan with the offered preset so you can survey that mesh before joining (shown only when the beacon offers a preset). | Dismiss — ignore the invitation. | . Channels advertised by beacons also show up in the scan setup as Beacon channels — select one to include it as a scan target. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/discovery.html#mesh-beacon",
    
    "relUrl": "/ht-rHT/user/discovery.html#mesh-beacon"
  },"1242": {
    "doc": "Local Mesh Discovery",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. 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 . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | 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 Response — The traceroute got nothing back. 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. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t 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 . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 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. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. 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 nodes. | . 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 LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/discovery.html#manual-exploration",
    
    "relUrl": "/ht-rHT/user/discovery.html#manual-exploration"
  },"1243": {
    "doc": "Local Mesh Discovery",
    "title": "Tips for Mesh exploration",
    "content": ". | 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 combined with signal data help you understand why some links are strong and others are weak. | Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly. | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/ht-rHT/user/discovery.html#tips-for-mesh-exploration"
  },"1244": {
    "doc": "Local Mesh Discovery",
    "title": "Related Topics",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/discovery.html#related-topics",
    
    "relUrl": "/ht-rHT/user/discovery.html#related-topics"
  },"1245": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery",
    "content": "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. The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Manual exploration — traceroute, Neighbor Info, and the node list, which you can use at any time to investigate specific paths and topology. | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/discovery.html",
    
    "relUrl": "/sr-rLatn/user/discovery.html"
  },"1246": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery (Scanner)",
    "content": "Local Mesh Discovery is a dedicated scanning mode that helps you find the best LoRa modem preset for your location and see which nodes are active on each preset. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Before starting, configure these controls: . | Control | Опис | . | LoRa preset picker | Select one or more presets to scan. Discovery dwells on each selected preset in turn. | . | Dwell time | Time to listen on each preset. Choose from 1, 5, 15, 30, 45, 60, 90, 120, or 180 minutes. Longer dwell times collect more packets and give a clearer picture, but take longer. | . | Keep screen awake | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The node is not connected. | No presets have been selected to scan. | The selected preset uses 2.4 GHz, which your hardware doesn’t support. | . Live progress . While a scan runs, Discovery shows its current stage: . | Stage | What’s happening | . | Preparing scan | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Re-establishing the connection after the preset change. | . | Dwelling on <preset> | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analyzing results | Processing the collected packets and ranking the presets. | . | Restoring home preset | Putting your original LoRa configuration back. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. Metrics include: . | Метрика | What it tells you | . | RF health | Overall quality of the radio environment on that preset. | . | Channel utilization | How busy the airwaves were during the dwell. | . | Време емитовања | Transmission time observed. | . | Direct vs. relayed nodes | How many mesh nodes were heard directly versus via a relay. | . | Bad / duplicate packets | Counts of corrupt and repeated packets, indicating congestion or interference. | . Additional features available from the results: . | Scan History — saved sessions you can revisit; view or delete past scans. | Discovery Map — a map of the nodes found during the scan. | Report export — export a report as a PDF on Android, or as text on other platforms. | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/discovery.html#local-mesh-discovery-scanner",
    
    "relUrl": "/sr-rLatn/user/discovery.html#local-mesh-discovery-scanner"
  },"1247": {
    "doc": "Local Mesh Discovery",
    "title": "Mesh Beacon",
    "content": "Mesh Beacon lets nodes invite others to join their mesh. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Received invitations appear as Mesh invitations cards on the Discovery screen. Each card shows the sender’s message plus the offered channel, region, preset, and signal quality, with these actions: . | Join — switch to the offered channel and preset (retunes the node and reboots). When the offer matches your current frequency slot, an Add channel action adds it without a reboot. | Discover — seed a Discovery scan with the offered preset so you can survey that mesh before joining (shown only when the beacon offers a preset). | Dismiss — ignore the invitation. | . Channels advertised by beacons also show up in the scan setup as Beacon channels — select one to include it as a scan target. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/discovery.html#mesh-beacon",
    
    "relUrl": "/sr-rLatn/user/discovery.html#mesh-beacon"
  },"1248": {
    "doc": "Local Mesh Discovery",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Праћење руте . 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 . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | 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 Response — The traceroute got nothing back. 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. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t 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 . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 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. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. 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 nodes. | . 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 LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/discovery.html#manual-exploration",
    
    "relUrl": "/sr-rLatn/user/discovery.html#manual-exploration"
  },"1249": {
    "doc": "Local Mesh Discovery",
    "title": "Tips for Mesh exploration",
    "content": ". | 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 combined with signal data help you understand why some links are strong and others are weak. | Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly. | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/sr-rLatn/user/discovery.html#tips-for-mesh-exploration"
  },"1250": {
    "doc": "Local Mesh Discovery",
    "title": "Related Topics",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/discovery.html#related-topics",
    
    "relUrl": "/sr-rLatn/user/discovery.html#related-topics"
  },"1251": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery",
    "content": "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. The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Manual exploration — traceroute, Neighbor Info, and the node list, which you can use at any time to investigate specific paths and topology. | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/discovery.html",
    
    "relUrl": "/nl-rNL/user/discovery.html"
  },"1252": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery (Scanner)",
    "content": "Local Mesh Discovery is a dedicated scanning mode that helps you find the best LoRa modem preset for your location and see which nodes are active on each preset. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Before starting, configure these controls: . | Control | Beschrijving | . | LoRa preset picker | Select one or more presets to scan. Discovery dwells on each selected preset in turn. | . | Dwell time | Time to listen on each preset. Choose from 1, 5, 15, 30, 45, 60, 90, 120, or 180 minutes. Longer dwell times collect more packets and give a clearer picture, but take longer. | . | Keep screen awake | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The node is not connected. | No presets have been selected to scan. | The selected preset uses 2.4 GHz, which your hardware doesn’t support. | . Live progress . While a scan runs, Discovery shows its current stage: . | Stage | What’s happening | . | Preparing scan | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Re-establishing the connection after the preset change. | . | Dwelling on <preset> | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analyzing results | Processing the collected packets and ranking the presets. | . | Restoring home preset | Putting your original LoRa configuration back. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. Metrics include: . | Metric | What it tells you | . | RF health | Overall quality of the radio environment on that preset. | . | Channel utilization | How busy the airwaves were during the dwell. | . | Airtime | Transmission time observed. | . | Direct vs. relayed nodes | How many mesh nodes were heard directly versus via a relay. | . | Bad / duplicate packets | Counts of corrupt and repeated packets, indicating congestion or interference. | . Additional features available from the results: . | Scan History — saved sessions you can revisit; view or delete past scans. | Discovery Map — a map of the nodes found during the scan. | Report export — export a report as a PDF on Android, or as text on other platforms. | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/discovery.html#local-mesh-discovery-scanner",
    
    "relUrl": "/nl-rNL/user/discovery.html#local-mesh-discovery-scanner"
  },"1253": {
    "doc": "Local Mesh Discovery",
    "title": "Mesh Beacon",
    "content": "Mesh Beacon lets nodes invite others to join their mesh. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Received invitations appear as Mesh invitations cards on the Discovery screen. Each card shows the sender’s message plus the offered channel, region, preset, and signal quality, with these actions: . | Join — switch to the offered channel and preset (retunes the node and reboots). When the offer matches your current frequency slot, an Add channel action adds it without a reboot. | Discover — seed a Discovery scan with the offered preset so you can survey that mesh before joining (shown only when the beacon offers a preset). | Dismiss — ignore the invitation. | . Channels advertised by beacons also show up in the scan setup as Beacon channels — select one to include it as a scan target. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/discovery.html#mesh-beacon",
    
    "relUrl": "/nl-rNL/user/discovery.html#mesh-beacon"
  },"1254": {
    "doc": "Local Mesh Discovery",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. 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 . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | 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 Response — The traceroute got nothing back. 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. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t 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 . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 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. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. 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 nodes. | . 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 LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/discovery.html#manual-exploration",
    
    "relUrl": "/nl-rNL/user/discovery.html#manual-exploration"
  },"1255": {
    "doc": "Local Mesh Discovery",
    "title": "Tips for Mesh exploration",
    "content": ". | 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 combined with signal data help you understand why some links are strong and others are weak. | Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly. | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/nl-rNL/user/discovery.html#tips-for-mesh-exploration"
  },"1256": {
    "doc": "Local Mesh Discovery",
    "title": "Related Topics",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/discovery.html#related-topics",
    
    "relUrl": "/nl-rNL/user/discovery.html#related-topics"
  },"1257": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery",
    "content": "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. The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Manual exploration — traceroute, Neighbor Info, and the node list, which you can use at any time to investigate specific paths and topology. | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/discovery.html",
    
    "relUrl": "/uk-rUA/user/discovery.html"
  },"1258": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery (Scanner)",
    "content": "Local Mesh Discovery is a dedicated scanning mode that helps you find the best LoRa modem preset for your location and see which nodes are active on each preset. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Before starting, configure these controls: . | Control | Опис | . | LoRa preset picker | Select one or more presets to scan. Discovery dwells on each selected preset in turn. | . | Dwell time | Time to listen on each preset. Choose from 1, 5, 15, 30, 45, 60, 90, 120, or 180 minutes. Longer dwell times collect more packets and give a clearer picture, but take longer. | . | Keep screen awake | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The node is not connected. | No presets have been selected to scan. | The selected preset uses 2.4 GHz, which your hardware doesn’t support. | . Live progress . While a scan runs, Discovery shows its current stage: . | Stage | What’s happening | . | Preparing scan | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Re-establishing the connection after the preset change. | . | Dwelling on <preset> | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analyzing results | Processing the collected packets and ranking the presets. | . | Restoring home preset | Putting your original LoRa configuration back. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. Metrics include: . | Metric | What it tells you | . | RF health | Overall quality of the radio environment on that preset. | . | Channel utilization | How busy the airwaves were during the dwell. | . | Airtime | Transmission time observed. | . | Direct vs. relayed nodes | How many mesh nodes were heard directly versus via a relay. | . | Bad / duplicate packets | Counts of corrupt and repeated packets, indicating congestion or interference. | . Additional features available from the results: . | Scan History — saved sessions you can revisit; view or delete past scans. | Discovery Map — a map of the nodes found during the scan. | Report export — export a report as a PDF on Android, or as text on other platforms. | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/discovery.html#local-mesh-discovery-scanner",
    
    "relUrl": "/uk-rUA/user/discovery.html#local-mesh-discovery-scanner"
  },"1259": {
    "doc": "Local Mesh Discovery",
    "title": "Mesh Beacon",
    "content": "Mesh Beacon lets nodes invite others to join their mesh. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Received invitations appear as Mesh invitations cards on the Discovery screen. Each card shows the sender’s message plus the offered channel, region, preset, and signal quality, with these actions: . | Join — switch to the offered channel and preset (retunes the node and reboots). When the offer matches your current frequency slot, an Add channel action adds it without a reboot. | Discover — seed a Discovery scan with the offered preset so you can survey that mesh before joining (shown only when the beacon offers a preset). | Dismiss — ignore the invitation. | . Channels advertised by beacons also show up in the scan setup as Beacon channels — select one to include it as a scan target. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/discovery.html#mesh-beacon",
    
    "relUrl": "/uk-rUA/user/discovery.html#mesh-beacon"
  },"1260": {
    "doc": "Local Mesh Discovery",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Маршрут . 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 . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | 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 Response — The traceroute got nothing back. 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. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Інформація про сусідів . 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 . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 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. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. 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 nodes. | . 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 LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/discovery.html#manual-exploration",
    
    "relUrl": "/uk-rUA/user/discovery.html#manual-exploration"
  },"1261": {
    "doc": "Local Mesh Discovery",
    "title": "Tips for Mesh exploration",
    "content": ". | 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 combined with signal data help you understand why some links are strong and others are weak. | Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly. | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/uk-rUA/user/discovery.html#tips-for-mesh-exploration"
  },"1262": {
    "doc": "Local Mesh Discovery",
    "title": "Related Topics",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/discovery.html#related-topics",
    
    "relUrl": "/uk-rUA/user/discovery.html#related-topics"
  },"1263": {
    "doc": "Paikallisen mesh-verkon skannaus",
    "title": "Paikallisen mesh-verkon skannaus",
    "content": "Hakutyökalut auttavat ymmärtämään miten mesh-verkko on yhteydessä — mitkä radiot kuulevat toisensa, mitä reittejä viestit kulkevat ja missä on pullonkauloja tai heikkoja yhteyksiä. Sovellus tarjoaa kaksi toisiaan täydentävää lähestymistapaa: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Manuaalinen etsiminen — reitinselvityksen reitit, naapuritiedot ja radiolista, joita voit käyttää milloin tahansa yksittäisten reittien ja topologian tarkasteluun. | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/discovery.html",
    
    "relUrl": "/fi-rFI/user/discovery.html"
  },"1264": {
    "doc": "Paikallisen mesh-verkon skannaus",
    "title": "Paikallinen verkon haku (Scanner)",
    "content": "Paikallinen verkon haku on erillinen skannaustila, joka auttaa löytämään parhaan LoRa-modeemiesiasetuksen sijaintiisi ja näkemään, mitkä radiot ovat aktiivisia kullakin esiasetuksella. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Ennen aloittamista määritä nämä asetukset: . | Säädin | Kuvaus | . | LoRa-esiasetuksen valitsin | Valitse yksi tai useampi esiasetus skannattavaksi. Haku pysähtyy jokaisessa valitussa esiasetuksessa vuorollaan kuuntelemaan liikennettä. | . | Kuunteluaika | Kunkin esiasetuksen kuunteluaika. Valitse 1, 5, 15, 30, 45, 60, 90, 120 tai 180 minuuttia. Pidempi kuunteluaika kerää enemmän paketteja ja antaa tarkemman kuvan, mutta kestää pidempään. | . | Pidä näyttö päällä | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Yleisiä syitä, miksi se on pois käytöstä: . | The node is not connected. | Esiasetuksia ei ole valittu skannattavaksi. | Valittu esiasetus käyttää 2,4 GHz -taajuutta, jota laitteistosi ei tue. | . Live progress . Skannauksen aikana haku näyttää sen nykyisen vaiheen: . | Tila | Mitä tapahtuu | . | Preparing scan | Tallennetaan nykyinen kokoonpano ja valmistaudutaan skannaukseen. | . | Vaihdetaan kohteeseen <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Yhteys muodostetaan uudelleen esiasetuksen vaihdon jälkeen. | . | Dwelling on <preset> | Nykyisen esiasetuksen kuuntelu pakettien keräämiseksi, seuraavaan vaiheeseen siirtymisen laskuri käynnissä. | . | Analyzing results | Kerättyjen pakettien käsittely ja esiasetusten vertailu ja pisteytys. | . | Restoring home preset | Palautetaan alkuperäinen LoRa-konfiguraatio takaisin. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . Kun skannaus valmistuu, haku näyttää jokaiselle testatulle esiasetukselle oman tuloskortin sekä yleisen yhteenvedon. Mittarit sisältävät: . | Metrijärjestelmä | Mitä ne kertovat sinulle | . | Radiolaatu (RF) | Kyseisen esiasetuksen radioympäristön kokonaislaatu | . | Kanavan käyttöaste | Kuinka kuormitetut radiotaajuudet olivat kuuntelun aikana. | . | Lähetysaika | Havaittu lähetysaika. | . | Suorat ja välitetyt radiot | Kuinka monta mesh-radiota kuultiin suoraan verrattuna välitettyihin. | . | Virheelliset / päällekkäiset paketit | Vioittuneiden ja toistettujen pakettien määrä, joka kertoo ruuhkasta tai häiriöistä. | . Tuloksista saatavilla olevat lisätoiminnot: . | Skannaus­historia — tallennetut istunnot, joita voit tarkastella myöhemmin; katsele tai poista aiempia skannauksia. | Haun kartta — kartta skannauksessa löydetyistä radioista. | Raportin vienti — vie raportti PDF-tiedostona Androidilla tai tekstinä muilla alustoilla. | . 💡 Vinkki: Google Play -versiossa Discovery voi luoda tuloksista laitteella toimivan tekoälyyhteenvedon (Gemini Nano). F-Droid-versio käyttää aina algoritmista yhteenvetoa — suljettu ML Kit -riippuvuus on jätetty tarkoituksella pois tästä versiosta, joten saat luettavan yhteenvedon skannauksesta joka tapauksessa. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/discovery.html#paikallinen-verkon-haku-scanner",
    
    "relUrl": "/fi-rFI/user/discovery.html#paikallinen-verkon-haku-scanner"
  },"1265": {
    "doc": "Paikallisen mesh-verkon skannaus",
    "title": "Verkkokutsu",
    "content": "Mesh Beacon antaa radioille mahdollisuuden kutsua muita liittymään mesh-verkkoon. Majakkatilassa oleva radio lähettää säännöllisesti kutsun, jossa voidaan haluttaessa ilmoittaa kanava, alue ja modeemiesiasetus — lähellä olevat radiot voivat havaita sen jo ennen asetusten jakamista. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Kuuntele majakoita – vastaanota muiden radioiden lähettämiä liittymiskutsuja. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Vastaanotetut kutsut näkyvät Mesh-kutsut -korteissa haku-näytössä. Jokainen kortti näyttää lähettäjän viestin sekä tarjotun kanavan, alueen, esiasetuksen ja signaalin laadun. Käytettävissä ovat seuraavat toiminnot: . | Join — switch to the offered channel and preset (retunes the node and reboots). Jos tarjous vastaa nykyistä taajuuspaikkaasi, Lisää kanava lisää sen ilman uudelleenkäynnistystä. | Tutki – aloita Haku tarjotulla esiasetuksella, jotta voit tutkia mesh-verkkoa ennen liittymistä (näkyy vain, jos majakka tarjoaa esiasetuksen). | Hylkää – ohita kutsu. | . Majakoiden ilmoittamat kanavat näkyvät myös Haku-toiminnon asetuksissa kohdassa Majakkakanavat. Valitse kanava lisätäksesi sen hakukohteeksi. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/discovery.html#verkkokutsu",
    
    "relUrl": "/fi-rFI/user/discovery.html#verkkokutsu"
  },"1266": {
    "doc": "Paikallisen mesh-verkon skannaus",
    "title": "Manual exploration",
    "content": "Seuraavat työkalut ovat aina käytettävissä Radiot- ja Radion tiedot -näkymissä. Käytä niitä yksittäisten reittien tutkimiseen ja topologian muodostamiseen, joko osana skannausta tai sen sijaan. Reitinselvitys . Reitinselvitys näyttää tarkan polun, jota kautta viesti kulkee omalta radioltasi mihin tahansa toiseen verkon radioon. Se on yksittäisistä työkaluista hyödyllisin yhteysongelmien vianmääritykseen. Reitinselvityksen suorittaminen . | Siirry kohtaan Radiot ja napauta radiota, jota haluat jäljittää. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . Reitinselvityksen tulos näyttää tältä: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | Mitä kannattaa tarkkailla | Mitä se tarkoittaa | . | All hops show Good SNR (green) | Hyvä reitti — viestit kulkevat luotettavasti | . | One hop shows a poor SNR (orange or red) | Heikko yhteys — tämä välityssegmentti on haavoittuva | . | Useita hyppyjä (4+) | Pitkä reitti — harkitse radion siirtämistä sen lyhentämiseksi | . | Eri reitti uudelleenyrityksellä | Verkko mukautuu — useita reittejä on olemassa (tämä on hyvä!) | . Vinkki: Aja reitinselvitys useita kertoja muutaman minuutin aikana. Jos reitti muuttuu, verkossasi on varareittejä — merkki hyvin kytketystä verkosta. Reitinselvityksen vianmääritys . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Varmista, että molemmat radiot jakavat vähintään yhden kanavan samalla salausavaimella. | Reitinselvitys aikakatkaistu — reitti voi olla liian pitkä (ylittää hyppymäärärajan) tai välittäjä-radio on ruuhkautunut. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Epäsymmetriset reitit — reitinselvitys A→B voi kulkea eri reittiä kuin B→A. This is normal — radio propagation isn’t always symmetric. | . Naapuritieto . Naapuritieto-moduuli antaa jokaisen radion lähettää listan radioista, jotka se voi kuulla suoraan (yhden hypyn päässä). Kun useat radiot jakavat naapurilistansa, voit muodostaa koko verkon topologian kartan. Naapuritiedon käyttöönotto . | Navigate to Settings → Module configuration → Neighbor Info. | Ota moduuli käyttöön. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Myös muut radiot, joissa naapuritieto on käytössä, toimivat samalla tavalla. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Jokainen naapurimerkintä näyttää radion, joka on kuultu suoraan, sekä sen signaalilaadun. | Yhdistä naapuritiedot useista radioista ymmärtääksesi koko mesh-verkon topologian. | . ℹ️ Huomautus: Naapuritieto lisää lähetysaikaa, koska jokainen toiminnon ottanut radio lähettää säännöllisesti naapuriluettelonsa. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . Radiolista on itsessään tehokas hakutyökalu, kun käytät sen suodatus- ja lajitteluominaisuuksia oikein. Finding new nodes . | Lajittele Viimeksi kuultu nähdäksesi viimeksi aktiiviset radiot ylimpänä. | 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 nodes. | . Assessing connectivity . | Lajittele Hyppyjen määrä nähdäksesi mitkä radiot ovat suoraan tavoitettavissa (0 hyppyä) ja mitkä välitettyinä. | Lajittele Etäisyys löytääksesi lähellä olevat radiot ja varmistaaksesi niiden tavoitettavuuden. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Poista Jätä infrastruktuuri pois käytöstä, jos haluat nähdä Router-, Router Late- ja Client Base -radiot. | Tarkista niiden signaalin laatu ja viimeksi kuultu -ajat varmistaaksesi, että infrastruktuuriradiot ovat kunnossa. | . Katso Radiot saadaksesi lisätietoa suodatus- ja lajitteluasetuksista. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/discovery.html#manual-exploration",
    
    "relUrl": "/fi-rFI/user/discovery.html#manual-exploration"
  },"1267": {
    "doc": "Paikallisen mesh-verkon skannaus",
    "title": "Tips for Mesh exploration",
    "content": ". | Aloita reitinselvityksellä — se antaa välittömän ja käytännöllisen tiedon yksittäisestä reitistä. | Ota naapuritieto käyttöön keskeisissä radioissa — erityisesti reitittimissä ja toistimissa, jotta saat näkyvyyden runkoverkkoon. | Tarkista kartta — Kartta yhdessä signaalitiedon kanssa auttaa ymmärtämään, miksi jotkin yhteydet ovat vahvoja ja toiset heikkoja. | Seuraa signaalin muutoksia ajan kuluessa — käytä Signaalimittari -opasta tulkitaksesi SNR- ja RSSI-arvot oikein. | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/fi-rFI/user/discovery.html#tips-for-mesh-exploration"
  },"1268": {
    "doc": "Paikallisen mesh-verkon skannaus",
    "title": "Aiheeseen liittyvät aiheet",
    "content": ". | Radiot — luettelo radioista, jotka nämä skannaukset löytävät | Kartta ja reittipisteet — tarkastele löydettyjä radioita kartalla | Signaalimittari — tulkitse skannauksen raportoimat SNR- ja RSSI-arvot | Asetukset — Moduulit ja ylläpito — määritä Mesh Beacon- ja Naapuritieto-moduulit | Viestit ja kanavat — liity löytämääsi mesh-verkkoon ja aloita viestintä | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/discovery.html#aiheeseen-liittyv%C3%A4t-aiheet",
    
    "relUrl": "/fi-rFI/user/discovery.html#aiheeseen-liittyvät-aiheet"
  },"1269": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery",
    "content": "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. The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Manual exploration — traceroute, Neighbor Info, and the node list, which you can use at any time to investigate specific paths and topology. | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/discovery.html",
    
    "relUrl": "/is-rIS/user/discovery.html"
  },"1270": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery (Scanner)",
    "content": "Local Mesh Discovery is a dedicated scanning mode that helps you find the best LoRa modem preset for your location and see which nodes are active on each preset. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Before starting, configure these controls: . | Control | Lýsing | . | LoRa preset picker | Select one or more presets to scan. Discovery dwells on each selected preset in turn. | . | Dwell time | Time to listen on each preset. Choose from 1, 5, 15, 30, 45, 60, 90, 120, or 180 minutes. Longer dwell times collect more packets and give a clearer picture, but take longer. | . | Keep screen awake | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The node is not connected. | No presets have been selected to scan. | The selected preset uses 2.4 GHz, which your hardware doesn’t support. | . Live progress . While a scan runs, Discovery shows its current stage: . | Stage | What’s happening | . | Preparing scan | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Re-establishing the connection after the preset change. | . | Dwelling on <preset> | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analyzing results | Processing the collected packets and ranking the presets. | . | Restoring home preset | Putting your original LoRa configuration back. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. Metrics include: . | Metric | What it tells you | . | RF health | Overall quality of the radio environment on that preset. | . | Channel utilization | How busy the airwaves were during the dwell. | . | Airtime | Transmission time observed. | . | Direct vs. relayed nodes | How many mesh nodes were heard directly versus via a relay. | . | Bad / duplicate packets | Counts of corrupt and repeated packets, indicating congestion or interference. | . Additional features available from the results: . | Scan History — saved sessions you can revisit; view or delete past scans. | Discovery Map — a map of the nodes found during the scan. | Report export — export a report as a PDF on Android, or as text on other platforms. | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/discovery.html#local-mesh-discovery-scanner",
    
    "relUrl": "/is-rIS/user/discovery.html#local-mesh-discovery-scanner"
  },"1271": {
    "doc": "Local Mesh Discovery",
    "title": "Mesh Beacon",
    "content": "Mesh Beacon lets nodes invite others to join their mesh. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Received invitations appear as Mesh invitations cards on the Discovery screen. Each card shows the sender’s message plus the offered channel, region, preset, and signal quality, with these actions: . | Join — switch to the offered channel and preset (retunes the node and reboots). When the offer matches your current frequency slot, an Add channel action adds it without a reboot. | Discover — seed a Discovery scan with the offered preset so you can survey that mesh before joining (shown only when the beacon offers a preset). | Dismiss — ignore the invitation. | . Channels advertised by beacons also show up in the scan setup as Beacon channels — select one to include it as a scan target. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/discovery.html#mesh-beacon",
    
    "relUrl": "/is-rIS/user/discovery.html#mesh-beacon"
  },"1272": {
    "doc": "Local Mesh Discovery",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Ferilkönnun . 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 . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | 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 Response — The traceroute got nothing back. 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. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t 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 . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 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. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. 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 nodes. | . 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 LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/discovery.html#manual-exploration",
    
    "relUrl": "/is-rIS/user/discovery.html#manual-exploration"
  },"1273": {
    "doc": "Local Mesh Discovery",
    "title": "Tips for Mesh exploration",
    "content": ". | 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 combined with signal data help you understand why some links are strong and others are weak. | Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly. | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/is-rIS/user/discovery.html#tips-for-mesh-exploration"
  },"1274": {
    "doc": "Local Mesh Discovery",
    "title": "Related Topics",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/discovery.html#related-topics",
    
    "relUrl": "/is-rIS/user/discovery.html#related-topics"
  },"1275": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery",
    "content": "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. The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Manual exploration — traceroute, Neighbor Info, and the node list, which you can use at any time to investigate specific paths and topology. | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/discovery.html",
    
    "relUrl": "/lt-rLT/user/discovery.html"
  },"1276": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery (Scanner)",
    "content": "Local Mesh Discovery is a dedicated scanning mode that helps you find the best LoRa modem preset for your location and see which nodes are active on each preset. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Before starting, configure these controls: . | Control | Aprašymas | . | LoRa preset picker | Select one or more presets to scan. Discovery dwells on each selected preset in turn. | . | Dwell time | Time to listen on each preset. Choose from 1, 5, 15, 30, 45, 60, 90, 120, or 180 minutes. Longer dwell times collect more packets and give a clearer picture, but take longer. | . | Keep screen awake | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The node is not connected. | No presets have been selected to scan. | The selected preset uses 2.4 GHz, which your hardware doesn’t support. | . Live progress . While a scan runs, Discovery shows its current stage: . | Stage | What’s happening | . | Preparing scan | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Re-establishing the connection after the preset change. | . | Dwelling on <preset> | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analyzing results | Processing the collected packets and ranking the presets. | . | Restoring home preset | Putting your original LoRa configuration back. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. Metrics include: . | Metric | What it tells you | . | RF health | Overall quality of the radio environment on that preset. | . | Channel utilization | How busy the airwaves were during the dwell. | . | Airtime | Transmission time observed. | . | Direct vs. relayed nodes | How many mesh nodes were heard directly versus via a relay. | . | Bad / duplicate packets | Counts of corrupt and repeated packets, indicating congestion or interference. | . Additional features available from the results: . | Scan History — saved sessions you can revisit; view or delete past scans. | Discovery Map — a map of the nodes found during the scan. | Report export — export a report as a PDF on Android, or as text on other platforms. | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/discovery.html#local-mesh-discovery-scanner",
    
    "relUrl": "/lt-rLT/user/discovery.html#local-mesh-discovery-scanner"
  },"1277": {
    "doc": "Local Mesh Discovery",
    "title": "Mesh Beacon",
    "content": "Mesh Beacon lets nodes invite others to join their mesh. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Received invitations appear as Mesh invitations cards on the Discovery screen. Each card shows the sender’s message plus the offered channel, region, preset, and signal quality, with these actions: . | Join — switch to the offered channel and preset (retunes the node and reboots). When the offer matches your current frequency slot, an Add channel action adds it without a reboot. | Discover — seed a Discovery scan with the offered preset so you can survey that mesh before joining (shown only when the beacon offers a preset). | Dismiss — ignore the invitation. | . Channels advertised by beacons also show up in the scan setup as Beacon channels — select one to include it as a scan target. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/discovery.html#mesh-beacon",
    
    "relUrl": "/lt-rLT/user/discovery.html#mesh-beacon"
  },"1278": {
    "doc": "Local Mesh Discovery",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Žinutės kelias . 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 . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | 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 Response — The traceroute got nothing back. 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. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t 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 . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 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. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. 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 nodes. | . 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 LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/discovery.html#manual-exploration",
    
    "relUrl": "/lt-rLT/user/discovery.html#manual-exploration"
  },"1279": {
    "doc": "Local Mesh Discovery",
    "title": "Tips for Mesh exploration",
    "content": ". | 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 combined with signal data help you understand why some links are strong and others are weak. | Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly. | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/lt-rLT/user/discovery.html#tips-for-mesh-exploration"
  },"1280": {
    "doc": "Local Mesh Discovery",
    "title": "Related Topics",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/discovery.html#related-topics",
    
    "relUrl": "/lt-rLT/user/discovery.html#related-topics"
  },"1281": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery",
    "content": "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. The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Manual exploration — traceroute, Neighbor Info, and the node list, which you can use at any time to investigate specific paths and topology. | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/discovery.html",
    
    "relUrl": "/gl-rES/user/discovery.html"
  },"1282": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery (Scanner)",
    "content": "Local Mesh Discovery is a dedicated scanning mode that helps you find the best LoRa modem preset for your location and see which nodes are active on each preset. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Before starting, configure these controls: . | Control | Descrición | . | LoRa preset picker | Select one or more presets to scan. Discovery dwells on each selected preset in turn. | . | Dwell time | Time to listen on each preset. Choose from 1, 5, 15, 30, 45, 60, 90, 120, or 180 minutes. Longer dwell times collect more packets and give a clearer picture, but take longer. | . | Keep screen awake | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The node is not connected. | No presets have been selected to scan. | The selected preset uses 2.4 GHz, which your hardware doesn’t support. | . Live progress . While a scan runs, Discovery shows its current stage: . | Stage | What’s happening | . | Preparing scan | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Re-establishing the connection after the preset change. | . | Dwelling on <preset> | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analyzing results | Processing the collected packets and ranking the presets. | . | Restoring home preset | Putting your original LoRa configuration back. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. Metrics include: . | Metric | What it tells you | . | RF health | Overall quality of the radio environment on that preset. | . | Channel utilization | How busy the airwaves were during the dwell. | . | Airtime | Transmission time observed. | . | Direct vs. relayed nodes | How many mesh nodes were heard directly versus via a relay. | . | Bad / duplicate packets | Counts of corrupt and repeated packets, indicating congestion or interference. | . Additional features available from the results: . | Scan History — saved sessions you can revisit; view or delete past scans. | Discovery Map — a map of the nodes found during the scan. | Report export — export a report as a PDF on Android, or as text on other platforms. | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/discovery.html#local-mesh-discovery-scanner",
    
    "relUrl": "/gl-rES/user/discovery.html#local-mesh-discovery-scanner"
  },"1283": {
    "doc": "Local Mesh Discovery",
    "title": "Mesh Beacon",
    "content": "Mesh Beacon lets nodes invite others to join their mesh. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Received invitations appear as Mesh invitations cards on the Discovery screen. Each card shows the sender’s message plus the offered channel, region, preset, and signal quality, with these actions: . | Join — switch to the offered channel and preset (retunes the node and reboots). When the offer matches your current frequency slot, an Add channel action adds it without a reboot. | Discover — seed a Discovery scan with the offered preset so you can survey that mesh before joining (shown only when the beacon offers a preset). | Dismiss — ignore the invitation. | . Channels advertised by beacons also show up in the scan setup as Beacon channels — select one to include it as a scan target. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/discovery.html#mesh-beacon",
    
    "relUrl": "/gl-rES/user/discovery.html#mesh-beacon"
  },"1284": {
    "doc": "Local Mesh Discovery",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traza-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 . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | 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 Response — The traceroute got nothing back. 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. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t 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 . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 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. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. 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 nodes. | . 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 LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/discovery.html#manual-exploration",
    
    "relUrl": "/gl-rES/user/discovery.html#manual-exploration"
  },"1285": {
    "doc": "Local Mesh Discovery",
    "title": "Tips for Mesh exploration",
    "content": ". | 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 combined with signal data help you understand why some links are strong and others are weak. | Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly. | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/gl-rES/user/discovery.html#tips-for-mesh-exploration"
  },"1286": {
    "doc": "Local Mesh Discovery",
    "title": "Related Topics",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/discovery.html#related-topics",
    
    "relUrl": "/gl-rES/user/discovery.html#related-topics"
  },"1287": {
    "doc": "ローカルメッシュ探索",
    "title": "ローカルメッシュ探索",
    "content": "探索ツールは、メッシュネットワークがどのようにつながっているか（どのノードが互いに受信できるか、メッセージがどの経路を通るか、ボトルネックや弱いリンクがどこにあるか）を把握するのに役立ちます。 . アプリは、互いを補完する 2 つの方法を提供します： . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | 手動での探索：ルート追跡、隣接ノード情報、ノードリスト。特定の経路やトポロジーを調べるために、いつでも使えます。 | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/discovery.html",
    
    "relUrl": "/ja-rJP/user/discovery.html"
  },"1288": {
    "doc": "ローカルメッシュ探索",
    "title": "ローカルメッシュ探索（スキャナー）",
    "content": "ローカルメッシュ探索は、あなたの場所に最適な LoRa モデムプリセットを見つけ、各プリセットでどのノードがアクティブかを確認できる、専用のスキャンモードです。 It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . 開始する前に、次のコントロールを設定します： . | コントロール | 説明 | . | LoRa プリセットの選択 | スキャンするプリセットを 1 つ以上選択します。探索は、選択した各プリセットに順番に滞在します。 | . | 滞在時間 | 各プリセットで受信する時間。 1、5、15、30、45、60、90、120、180 分から選択します。滞在時間を長くすると、より多くのパケットを収集してより明確な状況が分かりますが、時間もかかります。 | . | 画面をスリープさせない | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. 無効になる主な理由： . | The node is not connected. | スキャンするプリセットが選択されていない。 | 選択したプリセットが、ハードウェアが対応していない 2.4 GHz を使用している。 | . Live progress . スキャンの実行中、探索は現在の段階を表示します： . | 段階 | 実行中の内容 | . | Preparing scan | 現在の構成を保存し、スキャンの準備をしています。 | . | <preset> に切り替え中 | Switching the node to the next preset to test. | . | Reconnecting on <preset> | プリセット変更後に接続を再確立しています。 | . | Dwelling on <preset> | 現在のプリセットで受信してパケットを収集しており、次のステップまでのカウントダウンが表示されます。 | . | Analyzing results | 収集したパケットを処理し、プリセットをランク付けしています。 | . | Restoring home preset | 元の LoRa 構成に戻しています。 | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . スキャンが完了すると、探索はテストした各プリセットのプリセット別の結果カードと、全体の概要を表示します。 . メトリクスには次が含まれます： . | メートル法 | 分かること | . | RF の健全性 | そのプリセットにおける無線環境の総合的な品質。 | . | チャンネル利用率 | 滞在中に電波がどれだけ混雑していたか。 | . | 電波利用時間 | 観測された送信時間。 | . | 直接受信と中継ノード | 直接受信できたメッシュノードと、中継経由のノードの数。 | . | 不良／重複パケット | 破損したパケットと繰り返されたパケットの数で、輻輳や干渉を示します。 | . 結果から利用できる追加機能： . | スキャン履歴：後で見直せる保存済みのセッション。過去のスキャンを表示または削除できます。 | 探索マップ：スキャン中に見つかったノードのマップ。 | レポートのエクスポート：Android では PDF として、他のプラットフォームではテキストとしてレポートをエクスポートします。 | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/discovery.html#%E3%83%AD%E3%83%BC%E3%82%AB%E3%83%AB%E3%83%A1%E3%83%83%E3%82%B7%E3%83%A5%E6%8E%A2%E7%B4%A2%E3%82%B9%E3%82%AD%E3%83%A3%E3%83%8A%E3%83%BC",
    
    "relUrl": "/ja-rJP/user/discovery.html#ローカルメッシュ探索スキャナー"
  },"1289": {
    "doc": "ローカルメッシュ探索",
    "title": "メッシュビーコン",
    "content": "メッシュビーコンを使うと、ノードが他のノードを自分のメッシュに招待できます。 A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | ビーコンを受信：他のノードがブロードキャストする招待を受け取ります。 | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . 受信した招待は、探索画面に「メッシュへの招待」カードとして表示されます。各カードには、送信者のメッセージと、提示されたチャンネル・リージョン・プリセット・信号品質が表示され、次の操作ができます： . | Join — switch to the offered channel and preset (retunes the node and reboots). 提示内容が現在の周波数スロットと一致する場合は、再起動なしで追加できる「チャンネルを追加」の操作が表示されます。 | 探索：提示されたプリセットで探索スキャンを開始し、参加する前にそのメッシュを調べられます（ビーコンがプリセットを提示している場合のみ表示）。 | 閉じる：招待を無視します。 | . ビーコンが告知したチャンネルは、スキャン設定にも「ビーコンのチャンネル」として表示されます。選択すると、スキャン対象に含められます。 . An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/discovery.html#%E3%83%A1%E3%83%83%E3%82%B7%E3%83%A5%E3%83%93%E3%83%BC%E3%82%B3%E3%83%B3",
    
    "relUrl": "/ja-rJP/user/discovery.html#メッシュビーコン"
  },"1290": {
    "doc": "ローカルメッシュ探索",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. 完全なスキャンと併用して、またはその代わりに、特定の経路を調べてトポロジーの全体像を組み立てるのに使えます。 . ルート追跡 . ルート追跡は、メッセージが自分のノードから、メッシュ上の他の任意のノードへ通る正確な経路を明らかにします。接続の問題をデバッグするのに、最も役立つツールです。 . ルート追跡を実行する . | 「ノード」に移動し、追跡したいノードをタップします。 | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . ルート追跡の結果は次のように表示されます： . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | 確認すべき点 | 意味 | . | All hops show Good SNR (green) | 健全な経路。メッセージが確実に流れます | . | One hop shows a poor SNR (orange or red) | 弱いリンク。この中継区間は脆弱です | . | ホップ数が多い（4 以上） | 長い経路。短くするためにノードの再配置を検討してください | . | 再試行で経路が変わる | メッシュが適応しています。複数の経路が存在します（これは良いことです！） | . 💡 ヒント： ルート追跡を数分間かけて何度か実行してください。経路が変わる場合、メッシュには冗長な経路があり、よくつながったネットワークの兆候です。 . ルート追跡によるトラブルシューティング . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. 両方のノードが、同じ暗号化鍵を持つチャンネルを少なくとも 1 つ共有しているか確認してください。 | ルート追跡がタイムアウトする：経路が長すぎる（ホップ数上限を超える）か、中継ノードが混雑している可能性があります。 Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | 非対称な経路：A→B のルート追跡は、B→A とは異なる経路を通ることがあります。 This is normal — radio propagation isn’t always symmetric. | . 隣接ノード情報 . 隣接ノード情報モジュールを使うと、各ノードが直接受信できる（シングルホップの）ノードのリストをブロードキャストできます。複数のノードが隣接ノードのリストを共有すると、メッシュ全体のトポロジーマップを組み立てられます。 . 隣接ノード情報を有効にする . | Navigate to Settings → Module configuration → Neighbor Info. | モジュールを有効にします。 | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. 隣接ノード情報を有効にしている他のノードも、同じことを行います。 . Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 各隣接ノードの項目には、直接受信したノードとその信号品質が表示されます。 | 複数のノードの隣接ノードデータを組み合わせて、メッシュ全体のトポロジーを把握します。 | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . ノードリスト自体も、絞り込みと並べ替えの機能を効果的に使えば、強力な探索ツールになります。 . Finding new nodes . | 「最後の通信」で並べ替えると、最近アクティブだったノードが先頭に表示されます。 | 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 nodes. | . Assessing connectivity . | 「ホップ数」で並べ替えると、直接到達できるノード（0 ホップ）と中継されるノードが分かります。 | 「距離」で並べ替えると、近くのノードを見つけて、到達できるか確認できます。 | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | 「インフラを除外」を無効にすると、ルーター、ルーター・レイト、クライアント・ベースのノードが表示されます。 | 信号品質と最後の通信時刻を確認して、インフラのノードが健全であることを確かめます。 | . 絞り込みと並べ替えのオプションの詳細については、ノード を参照してください。 . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/discovery.html#manual-exploration",
    
    "relUrl": "/ja-rJP/user/discovery.html#manual-exploration"
  },"1291": {
    "doc": "ローカルメッシュ探索",
    "title": "Tips for Mesh exploration",
    "content": ". | まずルート追跡から：特定の経路について、すぐに役立つ情報が得られます。 | 主要なノードで隣接ノード情報を有効に：特にルーターやリピーターで有効にして、バックボーンの全体像を組み立てます。 | マップを確認：マップ 上のノードの位置と信号データを組み合わせると、なぜあるリンクは強く、別のリンクは弱いのかが分かります。 | 信号を時系列で比較：信号メーター のガイドを使って、SNR と RSSI の値を正しく解釈します。 | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/ja-rJP/user/discovery.html#tips-for-mesh-exploration"
  },"1292": {
    "doc": "ローカルメッシュ探索",
    "title": "関連トピック",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/discovery.html#%E9%96%A2%E9%80%A3%E3%83%88%E3%83%94%E3%83%83%E3%82%AF",
    
    "relUrl": "/ja-rJP/user/discovery.html#関連トピック"
  },"1293": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery",
    "content": "Discovery-Tools helfen Ihnen zu verstehen, wie Ihr Mesh-Netzwerk vernetzt ist – welche Knoten einander erreichen können, welche Wege Nachrichten nehmen und wo Engpässe oder Schwachstellen bestehen. The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Manual exploration — traceroute, Neighbor Info, and the node list, which you can use at any time to investigate specific paths and topology. | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/discovery.html",
    
    "relUrl": "/de-rDE/user/discovery.html"
  },"1294": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery (Scanner)",
    "content": "Local Mesh Discovery is a dedicated scanning mode that helps you find the best LoRa modem preset for your location and see which nodes are active on each preset. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Before starting, configure these controls: . | Control | Beschreibung | . | LoRa preset picker | Select one or more presets to scan. Discovery dwells on each selected preset in turn. | . | Dwell time | Time to listen on each preset. Choose from 1, 5, 15, 30, 45, 60, 90, 120, or 180 minutes. Longer dwell times collect more packets and give a clearer picture, but take longer. | . | Keep screen awake | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The node is not connected. | No presets have been selected to scan. | The selected preset uses 2.4 GHz, which your hardware doesn’t support. | . Live progress . While a scan runs, Discovery shows its current stage: . | Phase | What’s happening | . | Preparing scan | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Re-establishing the connection after the preset change. | . | Dwelling on <preset> | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analyzing results | Processing the collected packets and ranking the presets. | . | Restoring home preset | Putting your original LoRa configuration back. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. Metrics include: . | Metrisch | What it tells you | . | RF health | Overall quality of the radio environment on that preset. | . | Kanalauslastung | How busy the airwaves were during the dwell. | . | Airtime | Transmission time observed. | . | Direct vs. relayed nodes | How many mesh nodes were heard directly versus via a relay. | . | Bad / duplicate packets | Counts of corrupt and repeated packets, indicating congestion or interference. | . Additional features available from the results: . | Scan History — saved sessions you can revisit; view or delete past scans. | Discovery Map — a map of the nodes found during the scan. | Report export — export a report as a PDF on Android, or as text on other platforms. | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/discovery.html#local-mesh-discovery-scanner",
    
    "relUrl": "/de-rDE/user/discovery.html#local-mesh-discovery-scanner"
  },"1295": {
    "doc": "Local Mesh Discovery",
    "title": "Mesh Beacon",
    "content": "Mesh Beacon lets nodes invite others to join their mesh. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Received invitations appear as Mesh invitations cards on the Discovery screen. Each card shows the sender’s message plus the offered channel, region, preset, and signal quality, with these actions: . | Join — switch to the offered channel and preset (retunes the node and reboots). When the offer matches your current frequency slot, an Add channel action adds it without a reboot. | Discover — seed a Discovery scan with the offered preset so you can survey that mesh before joining (shown only when the beacon offers a preset). | Dismiss — ignore the invitation. | . Channels advertised by beacons also show up in the scan setup as Beacon channels — select one to include it as a scan target. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/discovery.html#mesh-beacon",
    
    "relUrl": "/de-rDE/user/discovery.html#mesh-beacon"
  },"1296": {
    "doc": "Local Mesh Discovery",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. 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 . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | 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 Response — The traceroute got nothing back. 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. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Nachbarinformation . 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 . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 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. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. 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 nodes. | . 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 LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/discovery.html#manual-exploration",
    
    "relUrl": "/de-rDE/user/discovery.html#manual-exploration"
  },"1297": {
    "doc": "Local Mesh Discovery",
    "title": "Tips for Mesh exploration",
    "content": ". | 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 combined with signal data help you understand why some links are strong and others are weak. | Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly. | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/de-rDE/user/discovery.html#tips-for-mesh-exploration"
  },"1298": {
    "doc": "Local Mesh Discovery",
    "title": "Verwandte Themen",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/discovery.html#verwandte-themen",
    
    "relUrl": "/de-rDE/user/discovery.html#verwandte-themen"
  },"1299": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery",
    "content": "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. The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Manual exploration — traceroute, Neighbor Info, and the node list, which you can use at any time to investigate specific paths and topology. | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/discovery.html",
    
    "relUrl": "/ar-rSA/user/discovery.html"
  },"1300": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery (Scanner)",
    "content": "Local Mesh Discovery is a dedicated scanning mode that helps you find the best LoRa modem preset for your location and see which nodes are active on each preset. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Before starting, configure these controls: . | Control | الوصف | . | LoRa preset picker | Select one or more presets to scan. Discovery dwells on each selected preset in turn. | . | Dwell time | Time to listen on each preset. Choose from 1, 5, 15, 30, 45, 60, 90, 120, or 180 minutes. Longer dwell times collect more packets and give a clearer picture, but take longer. | . | Keep screen awake | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The node is not connected. | No presets have been selected to scan. | The selected preset uses 2.4 GHz, which your hardware doesn’t support. | . Live progress . While a scan runs, Discovery shows its current stage: . | Stage | What’s happening | . | Preparing scan | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Re-establishing the connection after the preset change. | . | Dwelling on <preset> | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analyzing results | Processing the collected packets and ranking the presets. | . | Restoring home preset | Putting your original LoRa configuration back. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. Metrics include: . | Metric | What it tells you | . | RF health | Overall quality of the radio environment on that preset. | . | Channel utilization | How busy the airwaves were during the dwell. | . | Airtime | Transmission time observed. | . | Direct vs. relayed nodes | How many mesh nodes were heard directly versus via a relay. | . | Bad / duplicate packets | Counts of corrupt and repeated packets, indicating congestion or interference. | . Additional features available from the results: . | Scan History — saved sessions you can revisit; view or delete past scans. | Discovery Map — a map of the nodes found during the scan. | Report export — export a report as a PDF on Android, or as text on other platforms. | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/discovery.html#local-mesh-discovery-scanner",
    
    "relUrl": "/ar-rSA/user/discovery.html#local-mesh-discovery-scanner"
  },"1301": {
    "doc": "Local Mesh Discovery",
    "title": "Mesh Beacon",
    "content": "Mesh Beacon lets nodes invite others to join their mesh. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Received invitations appear as Mesh invitations cards on the Discovery screen. Each card shows the sender’s message plus the offered channel, region, preset, and signal quality, with these actions: . | Join — switch to the offered channel and preset (retunes the node and reboots). When the offer matches your current frequency slot, an Add channel action adds it without a reboot. | Discover — seed a Discovery scan with the offered preset so you can survey that mesh before joining (shown only when the beacon offers a preset). | Dismiss — ignore the invitation. | . Channels advertised by beacons also show up in the scan setup as Beacon channels — select one to include it as a scan target. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/discovery.html#mesh-beacon",
    
    "relUrl": "/ar-rSA/user/discovery.html#mesh-beacon"
  },"1302": {
    "doc": "Local Mesh Discovery",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. 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 . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | 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 Response — The traceroute got nothing back. 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. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t 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 . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 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. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. 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 nodes. | . 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 LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/discovery.html#manual-exploration",
    
    "relUrl": "/ar-rSA/user/discovery.html#manual-exploration"
  },"1303": {
    "doc": "Local Mesh Discovery",
    "title": "Tips for Mesh exploration",
    "content": ". | 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 combined with signal data help you understand why some links are strong and others are weak. | Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly. | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/ar-rSA/user/discovery.html#tips-for-mesh-exploration"
  },"1304": {
    "doc": "Local Mesh Discovery",
    "title": "Related Topics",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/discovery.html#related-topics",
    
    "relUrl": "/ar-rSA/user/discovery.html#related-topics"
  },"1305": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery",
    "content": "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. The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Manual exploration — traceroute, Neighbor Info, and the node list, which you can use at any time to investigate specific paths and topology. | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/discovery.html",
    
    "relUrl": "/hr-rHR/user/discovery.html"
  },"1306": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery (Scanner)",
    "content": "Local Mesh Discovery is a dedicated scanning mode that helps you find the best LoRa modem preset for your location and see which nodes are active on each preset. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Before starting, configure these controls: . | Control | Opis | . | LoRa preset picker | Select one or more presets to scan. Discovery dwells on each selected preset in turn. | . | Dwell time | Time to listen on each preset. Choose from 1, 5, 15, 30, 45, 60, 90, 120, or 180 minutes. Longer dwell times collect more packets and give a clearer picture, but take longer. | . | Keep screen awake | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The node is not connected. | No presets have been selected to scan. | The selected preset uses 2.4 GHz, which your hardware doesn’t support. | . Live progress . While a scan runs, Discovery shows its current stage: . | Stage | What’s happening | . | Preparing scan | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Re-establishing the connection after the preset change. | . | Dwelling on <preset> | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analyzing results | Processing the collected packets and ranking the presets. | . | Restoring home preset | Putting your original LoRa configuration back. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. Metrics include: . | Metric | What it tells you | . | RF health | Overall quality of the radio environment on that preset. | . | Channel utilization | How busy the airwaves were during the dwell. | . | Airtime | Transmission time observed. | . | Direct vs. relayed nodes | How many mesh nodes were heard directly versus via a relay. | . | Bad / duplicate packets | Counts of corrupt and repeated packets, indicating congestion or interference. | . Additional features available from the results: . | Scan History — saved sessions you can revisit; view or delete past scans. | Discovery Map — a map of the nodes found during the scan. | Report export — export a report as a PDF on Android, or as text on other platforms. | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/discovery.html#local-mesh-discovery-scanner",
    
    "relUrl": "/hr-rHR/user/discovery.html#local-mesh-discovery-scanner"
  },"1307": {
    "doc": "Local Mesh Discovery",
    "title": "Mesh Beacon",
    "content": "Mesh Beacon lets nodes invite others to join their mesh. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Received invitations appear as Mesh invitations cards on the Discovery screen. Each card shows the sender’s message plus the offered channel, region, preset, and signal quality, with these actions: . | Join — switch to the offered channel and preset (retunes the node and reboots). When the offer matches your current frequency slot, an Add channel action adds it without a reboot. | Discover — seed a Discovery scan with the offered preset so you can survey that mesh before joining (shown only when the beacon offers a preset). | Dismiss — ignore the invitation. | . Channels advertised by beacons also show up in the scan setup as Beacon channels — select one to include it as a scan target. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/discovery.html#mesh-beacon",
    
    "relUrl": "/hr-rHR/user/discovery.html#mesh-beacon"
  },"1308": {
    "doc": "Local Mesh Discovery",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. 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 . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | 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 Response — The traceroute got nothing back. 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. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t 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 . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 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. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. 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 nodes. | . 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 LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/discovery.html#manual-exploration",
    
    "relUrl": "/hr-rHR/user/discovery.html#manual-exploration"
  },"1309": {
    "doc": "Local Mesh Discovery",
    "title": "Tips for Mesh exploration",
    "content": ". | 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 combined with signal data help you understand why some links are strong and others are weak. | Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly. | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/hr-rHR/user/discovery.html#tips-for-mesh-exploration"
  },"1310": {
    "doc": "Local Mesh Discovery",
    "title": "Related Topics",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/discovery.html#related-topics",
    
    "relUrl": "/hr-rHR/user/discovery.html#related-topics"
  },"1311": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery",
    "content": "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. The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Manual exploration — traceroute, Neighbor Info, and the node list, which you can use at any time to investigate specific paths and topology. | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/discovery.html",
    
    "relUrl": "/pt-rPT/user/discovery.html"
  },"1312": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery (Scanner)",
    "content": "Local Mesh Discovery is a dedicated scanning mode that helps you find the best LoRa modem preset for your location and see which nodes are active on each preset. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Before starting, configure these controls: . | Control | Descrição | . | LoRa preset picker | Select one or more presets to scan. Discovery dwells on each selected preset in turn. | . | Dwell time | Time to listen on each preset. Choose from 1, 5, 15, 30, 45, 60, 90, 120, or 180 minutes. Longer dwell times collect more packets and give a clearer picture, but take longer. | . | Keep screen awake | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The node is not connected. | No presets have been selected to scan. | The selected preset uses 2.4 GHz, which your hardware doesn’t support. | . Live progress . While a scan runs, Discovery shows its current stage: . | Stage | What’s happening | . | Preparing scan | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Re-establishing the connection after the preset change. | . | Dwelling on <preset> | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analyzing results | Processing the collected packets and ranking the presets. | . | Restoring home preset | Putting your original LoRa configuration back. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. Metrics include: . | Metric | What it tells you | . | RF health | Overall quality of the radio environment on that preset. | . | Channel utilization | How busy the airwaves were during the dwell. | . | Airtime | Transmission time observed. | . | Direct vs. relayed nodes | How many mesh nodes were heard directly versus via a relay. | . | Bad / duplicate packets | Counts of corrupt and repeated packets, indicating congestion or interference. | . Additional features available from the results: . | Scan History — saved sessions you can revisit; view or delete past scans. | Discovery Map — a map of the nodes found during the scan. | Report export — export a report as a PDF on Android, or as text on other platforms. | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/discovery.html#local-mesh-discovery-scanner",
    
    "relUrl": "/pt-rPT/user/discovery.html#local-mesh-discovery-scanner"
  },"1313": {
    "doc": "Local Mesh Discovery",
    "title": "Mesh Beacon",
    "content": "Mesh Beacon lets nodes invite others to join their mesh. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Received invitations appear as Mesh invitations cards on the Discovery screen. Each card shows the sender’s message plus the offered channel, region, preset, and signal quality, with these actions: . | Join — switch to the offered channel and preset (retunes the node and reboots). When the offer matches your current frequency slot, an Add channel action adds it without a reboot. | Discover — seed a Discovery scan with the offered preset so you can survey that mesh before joining (shown only when the beacon offers a preset). | Dismiss — ignore the invitation. | . Channels advertised by beacons also show up in the scan setup as Beacon channels — select one to include it as a scan target. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/discovery.html#mesh-beacon",
    
    "relUrl": "/pt-rPT/user/discovery.html#mesh-beacon"
  },"1314": {
    "doc": "Local Mesh Discovery",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traçar rota . 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 . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | 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 Response — The traceroute got nothing back. 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. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Informações da vizinhança . 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 . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 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. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. 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 nodes. | . 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 LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/discovery.html#manual-exploration",
    
    "relUrl": "/pt-rPT/user/discovery.html#manual-exploration"
  },"1315": {
    "doc": "Local Mesh Discovery",
    "title": "Tips for Mesh exploration",
    "content": ". | 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 combined with signal data help you understand why some links are strong and others are weak. | Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly. | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/pt-rPT/user/discovery.html#tips-for-mesh-exploration"
  },"1316": {
    "doc": "Local Mesh Discovery",
    "title": "Related Topics",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/discovery.html#related-topics",
    
    "relUrl": "/pt-rPT/user/discovery.html#related-topics"
  },"1317": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery",
    "content": "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. The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Manual exploration — traceroute, Neighbor Info, and the node list, which you can use at any time to investigate specific paths and topology. | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/discovery.html",
    
    "relUrl": "/pl-rPL/user/discovery.html"
  },"1318": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery (Scanner)",
    "content": "Local Mesh Discovery is a dedicated scanning mode that helps you find the best LoRa modem preset for your location and see which nodes are active on each preset. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Before starting, configure these controls: . | Control | Opis | . | LoRa preset picker | Select one or more presets to scan. Discovery dwells on each selected preset in turn. | . | Dwell time | Time to listen on each preset. Choose from 1, 5, 15, 30, 45, 60, 90, 120, or 180 minutes. Longer dwell times collect more packets and give a clearer picture, but take longer. | . | Keep screen awake | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The node is not connected. | No presets have been selected to scan. | The selected preset uses 2.4 GHz, which your hardware doesn’t support. | . Live progress . While a scan runs, Discovery shows its current stage: . | Stage | What’s happening | . | Preparing scan | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Re-establishing the connection after the preset change. | . | Dwelling on <preset> | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analyzing results | Processing the collected packets and ranking the presets. | . | Restoring home preset | Putting your original LoRa configuration back. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. Metrics include: . | Metric | What it tells you | . | RF health | Overall quality of the radio environment on that preset. | . | Wykorzystanie kanału | How busy the airwaves were during the dwell. | . | Czas nadawania | Transmission time observed. | . | Direct vs. relayed nodes | How many mesh nodes were heard directly versus via a relay. | . | Bad / duplicate packets | Counts of corrupt and repeated packets, indicating congestion or interference. | . Additional features available from the results: . | Scan History — saved sessions you can revisit; view or delete past scans. | Discovery Map — a map of the nodes found during the scan. | Report export — export a report as a PDF on Android, or as text on other platforms. | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/discovery.html#local-mesh-discovery-scanner",
    
    "relUrl": "/pl-rPL/user/discovery.html#local-mesh-discovery-scanner"
  },"1319": {
    "doc": "Local Mesh Discovery",
    "title": "Mesh Beacon",
    "content": "Mesh Beacon lets nodes invite others to join their mesh. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Received invitations appear as Mesh invitations cards on the Discovery screen. Each card shows the sender’s message plus the offered channel, region, preset, and signal quality, with these actions: . | Join — switch to the offered channel and preset (retunes the node and reboots). When the offer matches your current frequency slot, an Add channel action adds it without a reboot. | Discover — seed a Discovery scan with the offered preset so you can survey that mesh before joining (shown only when the beacon offers a preset). | Dismiss — ignore the invitation. | . Channels advertised by beacons also show up in the scan setup as Beacon channels — select one to include it as a scan target. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/discovery.html#mesh-beacon",
    
    "relUrl": "/pl-rPL/user/discovery.html#mesh-beacon"
  },"1320": {
    "doc": "Local Mesh Discovery",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Pokaż trasę . 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 . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | 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 Response — The traceroute got nothing back. 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. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Informacje o sąsiadze . 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 . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 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. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. 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 nodes. | . 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 LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/discovery.html#manual-exploration",
    
    "relUrl": "/pl-rPL/user/discovery.html#manual-exploration"
  },"1321": {
    "doc": "Local Mesh Discovery",
    "title": "Tips for Mesh exploration",
    "content": ". | 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 combined with signal data help you understand why some links are strong and others are weak. | Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly. | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/pl-rPL/user/discovery.html#tips-for-mesh-exploration"
  },"1322": {
    "doc": "Local Mesh Discovery",
    "title": "Related Topics",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/discovery.html#related-topics",
    
    "relUrl": "/pl-rPL/user/discovery.html#related-topics"
  },"1323": {
    "doc": "本地网状网络发现",
    "title": "本地网状网络发现",
    "content": "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. The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Manual exploration — traceroute, Neighbor Info, and the node list, which you can use at any time to investigate specific paths and topology. | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/discovery.html",
    
    "relUrl": "/zh-rCN/user/discovery.html"
  },"1324": {
    "doc": "本地网状网络发现",
    "title": "Local Mesh Discovery (Scanner)",
    "content": "Local Mesh Discovery is a dedicated scanning mode that helps you find the best LoRa modem preset for your location and see which nodes are active on each preset. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Before starting, configure these controls: . | Control | 说明 | . | LoRa preset picker | Select one or more presets to scan. Discovery dwells on each selected preset in turn. | . | Dwell time | Time to listen on each preset. Choose from 1, 5, 15, 30, 45, 60, 90, 120, or 180 minutes. Longer dwell times collect more packets and give a clearer picture, but take longer. | . | Keep screen awake | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The node is not connected. | No presets have been selected to scan. | The selected preset uses 2.4 GHz, which your hardware doesn’t support. | . Live progress . While a scan runs, Discovery shows its current stage: . | Stage | What’s happening | . | Preparing scan | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Re-establishing the connection after the preset change. | . | Dwelling on <preset> | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analyzing results | Processing the collected packets and ranking the presets. | . | Restoring home preset | Putting your original LoRa configuration back. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. Metrics include: . | 公制 | What it tells you | . | RF health | Overall quality of the radio environment on that preset. | . | 频道使用 | How busy the airwaves were during the dwell. | . | 广播时间 | Transmission time observed. | . | Direct vs. relayed nodes | How many mesh nodes were heard directly versus via a relay. | . | Bad / duplicate packets | Counts of corrupt and repeated packets, indicating congestion or interference. | . Additional features available from the results: . | Scan History — saved sessions you can revisit; view or delete past scans. | Discovery Map — a map of the nodes found during the scan. | Report export — export a report as a PDF on Android, or as text on other platforms. | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/discovery.html#local-mesh-discovery-scanner",
    
    "relUrl": "/zh-rCN/user/discovery.html#local-mesh-discovery-scanner"
  },"1325": {
    "doc": "本地网状网络发现",
    "title": "Mesh 信标",
    "content": "Mesh Beacon lets nodes invite others to join their mesh. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Received invitations appear as Mesh invitations cards on the Discovery screen. Each card shows the sender’s message plus the offered channel, region, preset, and signal quality, with these actions: . | Join — switch to the offered channel and preset (retunes the node and reboots). When the offer matches your current frequency slot, an Add channel action adds it without a reboot. | Discover — seed a Discovery scan with the offered preset so you can survey that mesh before joining (shown only when the beacon offers a preset). | Dismiss — ignore the invitation. | . Channels advertised by beacons also show up in the scan setup as Beacon channels — select one to include it as a scan target. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/discovery.html#mesh-%E4%BF%A1%E6%A0%87",
    
    "relUrl": "/zh-rCN/user/discovery.html#mesh-信标"
  },"1326": {
    "doc": "本地网状网络发现",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. 追踪器 . 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 . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | 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 Response — The traceroute got nothing back. 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. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . 邻居信息 . 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 . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 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. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. 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 nodes. | . 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 LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/discovery.html#manual-exploration",
    
    "relUrl": "/zh-rCN/user/discovery.html#manual-exploration"
  },"1327": {
    "doc": "本地网状网络发现",
    "title": "Tips for Mesh exploration",
    "content": ". | 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 combined with signal data help you understand why some links are strong and others are weak. | Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly. | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/zh-rCN/user/discovery.html#tips-for-mesh-exploration"
  },"1328": {
    "doc": "本地网状网络发现",
    "title": "Related Topics",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/discovery.html#related-topics",
    
    "relUrl": "/zh-rCN/user/discovery.html#related-topics"
  },"1329": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery",
    "content": "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. The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Manual exploration — traceroute, Neighbor Info, and the node list, which you can use at any time to investigate specific paths and topology. | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/discovery.html",
    
    "relUrl": "/sq-rAL/user/discovery.html"
  },"1330": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery (Scanner)",
    "content": "Local Mesh Discovery is a dedicated scanning mode that helps you find the best LoRa modem preset for your location and see which nodes are active on each preset. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Before starting, configure these controls: . | Control | Përshkrimi | . | LoRa preset picker | Select one or more presets to scan. Discovery dwells on each selected preset in turn. | . | Dwell time | Time to listen on each preset. Choose from 1, 5, 15, 30, 45, 60, 90, 120, or 180 minutes. Longer dwell times collect more packets and give a clearer picture, but take longer. | . | Keep screen awake | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The node is not connected. | No presets have been selected to scan. | The selected preset uses 2.4 GHz, which your hardware doesn’t support. | . Live progress . While a scan runs, Discovery shows its current stage: . | Stage | What’s happening | . | Preparing scan | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Re-establishing the connection after the preset change. | . | Dwelling on <preset> | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analyzing results | Processing the collected packets and ranking the presets. | . | Restoring home preset | Putting your original LoRa configuration back. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. Metrics include: . | Metric | What it tells you | . | RF health | Overall quality of the radio environment on that preset. | . | Channel utilization | How busy the airwaves were during the dwell. | . | Airtime | Transmission time observed. | . | Direct vs. relayed nodes | How many mesh nodes were heard directly versus via a relay. | . | Bad / duplicate packets | Counts of corrupt and repeated packets, indicating congestion or interference. | . Additional features available from the results: . | Scan History — saved sessions you can revisit; view or delete past scans. | Discovery Map — a map of the nodes found during the scan. | Report export — export a report as a PDF on Android, or as text on other platforms. | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/discovery.html#local-mesh-discovery-scanner",
    
    "relUrl": "/sq-rAL/user/discovery.html#local-mesh-discovery-scanner"
  },"1331": {
    "doc": "Local Mesh Discovery",
    "title": "Mesh Beacon",
    "content": "Mesh Beacon lets nodes invite others to join their mesh. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Received invitations appear as Mesh invitations cards on the Discovery screen. Each card shows the sender’s message plus the offered channel, region, preset, and signal quality, with these actions: . | Join — switch to the offered channel and preset (retunes the node and reboots). When the offer matches your current frequency slot, an Add channel action adds it without a reboot. | Discover — seed a Discovery scan with the offered preset so you can survey that mesh before joining (shown only when the beacon offers a preset). | Dismiss — ignore the invitation. | . Channels advertised by beacons also show up in the scan setup as Beacon channels — select one to include it as a scan target. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/discovery.html#mesh-beacon",
    
    "relUrl": "/sq-rAL/user/discovery.html#mesh-beacon"
  },"1332": {
    "doc": "Local Mesh Discovery",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. 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 . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | 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 Response — The traceroute got nothing back. 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. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t 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 . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 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. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. 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 nodes. | . 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 LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/discovery.html#manual-exploration",
    
    "relUrl": "/sq-rAL/user/discovery.html#manual-exploration"
  },"1333": {
    "doc": "Local Mesh Discovery",
    "title": "Tips for Mesh exploration",
    "content": ". | 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 combined with signal data help you understand why some links are strong and others are weak. | Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly. | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/sq-rAL/user/discovery.html#tips-for-mesh-exploration"
  },"1334": {
    "doc": "Local Mesh Discovery",
    "title": "Related Topics",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/discovery.html#related-topics",
    
    "relUrl": "/sq-rAL/user/discovery.html#related-topics"
  },"1335": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery",
    "content": "探索工具可協助您了解 mesh 網路的連線方式——哪些節點彼此可以收到訊號、訊息所經過的路徑，以及哪裡存在瓶頸或訊號薄弱的連結。 . The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Manual exploration — traceroute, Neighbor Info, and the node list, which you can use at any time to investigate specific paths and topology. | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/discovery.html",
    
    "relUrl": "/zh-rTW/user/discovery.html"
  },"1336": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery (Scanner)",
    "content": "Local Mesh Discovery is a dedicated scanning mode that helps you find the best LoRa modem preset for your location and see which nodes are active on each preset. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Before starting, configure these controls: . | Control | 描述說明 | . | LoRa preset picker | Select one or more presets to scan. Discovery dwells on each selected preset in turn. | . | Dwell time | Time to listen on each preset. Choose from 1, 5, 15, 30, 45, 60, 90, 120, or 180 minutes. Longer dwell times collect more packets and give a clearer picture, but take longer. | . | Keep screen awake | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The node is not connected. | No presets have been selected to scan. | The selected preset uses 2.4 GHz, which your hardware doesn’t support. | . Live progress . While a scan runs, Discovery shows its current stage: . | Stage | What’s happening | . | Preparing scan | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Re-establishing the connection after the preset change. | . | Dwelling on <preset> | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analyzing results | Processing the collected packets and ranking the presets. | . | Restoring home preset | Putting your original LoRa configuration back. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. Metrics include: . | 公制（公里/公尺） | What it tells you | . | RF health | Overall quality of the radio environment on that preset. | . | 頻道使用率 | How busy the airwaves were during the dwell. | . | Airtime | Transmission time observed. | . | Direct vs. relayed nodes | How many mesh nodes were heard directly versus via a relay. | . | Bad / duplicate packets | Counts of corrupt and repeated packets, indicating congestion or interference. | . Additional features available from the results: . | Scan History — saved sessions you can revisit; view or delete past scans. | Discovery Map — a map of the nodes found during the scan. | Report export — export a report as a PDF on Android, or as text on other platforms. | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/discovery.html#local-mesh-discovery-scanner",
    
    "relUrl": "/zh-rTW/user/discovery.html#local-mesh-discovery-scanner"
  },"1337": {
    "doc": "Local Mesh Discovery",
    "title": "Mesh Beacon",
    "content": "Mesh Beacon lets nodes invite others to join their mesh. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Received invitations appear as Mesh invitations cards on the Discovery screen. Each card shows the sender’s message plus the offered channel, region, preset, and signal quality, with these actions: . | Join — switch to the offered channel and preset (retunes the node and reboots). When the offer matches your current frequency slot, an Add channel action adds it without a reboot. | Discover — seed a Discovery scan with the offered preset so you can survey that mesh before joining (shown only when the beacon offers a preset). | Dismiss — ignore the invitation. | . Channels advertised by beacons also show up in the scan setup as Beacon channels — select one to include it as a scan target. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/discovery.html#mesh-beacon",
    
    "relUrl": "/zh-rTW/user/discovery.html#mesh-beacon"
  },"1338": {
    "doc": "Local Mesh Discovery",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. 路由追蹤 . 路由追蹤可顯示訊息從您的節點到 mesh 網路上任一節點所經過的確切路徑。這是診斷連線問題最有效的工具。 . 執行路由追蹤 . | 前往「節點」，並點選您要追蹤的節點。 | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . 路由追蹤結果的顯示方式如下： . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | 判讀重點 | 代表意義 | . | All hops show Good SNR (green) | 路徑狀況良好 — 訊息可穩定傳送 | . | One hop shows a poor SNR (orange or red) | 訊號薄弱 — 此中繼路段不穩定 | . | 跳躍點過多（4 個以上） | 路徑過長 — 建議調整節點位置以縮短路徑 | . | 重試時走不同路徑 | Mesh 網路正在自動調整 — 存在多條路由（這是好現象！） | . 💡 提示：請在幾分鐘內多次執行路由追蹤。若路徑發生變化，代表您的 mesh 網路具備備援路由 — 這是網路連線良好的象徵。 . 使用路由追蹤進行疑難排解 . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. 請確認兩個節點至少共用一個使用相同加密金鑰的頻道。 | 「路由追蹤逾時」— 路徑可能過長（超過跳躍限制），或某中繼節點發生壅塞。 Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | 非對稱路徑 — 從 A → B 的路由追蹤路徑，可能與 B → A 不同。 This is normal — radio propagation isn’t always symmetric. | . 鄰近節點資訊 . 鄰近節點資訊模組可讓每個節點廣播其可直接收到訊號的節點清單（單跳躍）。當多個節點共享各自的鄰近節點清單時，您便可拼湊出整個 mesh 網路的拓撲圖。 . 啟用鄰近節點資訊 . | Navigate to Settings → Module configuration → Neighbor Info. | 啟用此模組。 | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. 其他已啟用鄰近節點資訊的節點也會執行相同動作。 . Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 每筆鄰近節點記錄會顯示可直接收到訊號的節點及其訊號品質。 | 結合多個節點的鄰近節點資料，以了解完整的 mesh 網路拓撲。 | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . 善用節點清單的篩選與排序功能，即可將其作為強大的探索工具。 . Finding new nodes . | 依「最後收到訊號」排序，可將最近有活動的節點顯示於頂部。 | 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 nodes. | . Assessing connectivity . | 依「跳躍距離」排序，可區分可直接到達的節點（0 個跳躍點）與需中繼轉送的節點。 | 依「距離」排序，可找出附近的節點並確認是否可到達。 | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | 檢查其訊號品質與最後收到訊號的時間，以確認基礎架構節點運作正常。 | . 請參閱〔節點〕(nodes) 以了解完整的篩選與排序選項說明。 . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/discovery.html#manual-exploration",
    
    "relUrl": "/zh-rTW/user/discovery.html#manual-exploration"
  },"1339": {
    "doc": "Local Mesh Discovery",
    "title": "Tips for Mesh exploration",
    "content": ". | 從路由追蹤開始 — 可立即取得特定路徑的具體可行資訊。 | 在關鍵節點上啟用鄰近節點資訊 — 尤其是路由器與中繼器，以建立骨幹網路的整體概況。 | 查看地圖 —〔地圖〕(map-and-waypoints) 上的節點位置結合訊號資料，有助於了解為何某些連結訊號強，而其他連結訊號弱。 | 比較訊號變化趨勢 — 請參閱〔訊號儀表〕(signal-meter) 指南，以正確解讀 SNR 與 RSSI 數值。 | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/zh-rTW/user/discovery.html#tips-for-mesh-exploration"
  },"1340": {
    "doc": "Local Mesh Discovery",
    "title": "相關主題",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/discovery.html#%E7%9B%B8%E9%97%9C%E4%B8%BB%E9%A1%8C",
    
    "relUrl": "/zh-rTW/user/discovery.html#相關主題"
  },"1341": {
    "doc": "Kohalik kärgvõrgu avastaja",
    "title": "Kohalik kärgvõrgu avastaja",
    "content": "Avastamistööriistad aitavad mõista, kuidas kärgvõrk on ühendatud – millised sõlmed üksteist kuulevad, milliseid teid sõnumid läbivad ja kus esinevad kitsaskohad või nõrgad lülid. The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Manuaalne uurimine – traceroute, naabri info ja sõlmede loend, mida saate igal ajal kasutada konkreetsete teede ja topoloogia uurimiseks. | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/discovery.html",
    
    "relUrl": "/et-rEE/user/discovery.html"
  },"1342": {
    "doc": "Kohalik kärgvõrgu avastaja",
    "title": "Kohalik kärgvõrgu avastaja (skanner)",
    "content": "Kohalik kärgvõrdu avastaja on spetsiaalne skaneerimisrežiim, mis aitab leida oma asukoha jaoks parima LoRa modemi eelseadistuse ja näha, millised sõlmed on igal eelseadistusel aktiivsed. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Before starting, configure these controls: . | Control | Kirjeldus | . | LoRa preset picker | Vali skannimiseks üks või mitu eelseadistust. Otsing peatub kordamööda iga valitud eelseadistuse juures, et kuulata liiklust. | . | Kuulamisaeg | Time to listen on each preset. Vali 1, 5, 15, 30, 45, 60, 90, 120 või 180 minutit. Pikemad kuulamisajad koguvad rohkem pakette ja annavad selgema pildi, kuid võtavad kauem aega. | . | Keep screen awake | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The node is not connected. | Skannimiseks pole ühtegi eelseadet valitud. | Valitud eelseadistus kasutab 2,4 GHz sagedust, mida sinu riistvara ei toeta. | . Live progress . Skanni ajal näitab Discovery selle praegust etappi: . | Stage | What’s happening | . | Preparing scan | Praeguste sätete salvestamine ja skannimiseks valmistumine. | . | Shifting to <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Re-establishing the connection after the preset change. | . | Dwelling on <preset> | Kuulatakse praegust eelseadistust pakettide kogumiseks ja järgmise sammuni on oodata loendurit. | . | Analyzing results | Kogutud pakettide töötlemine ja eelseadete järjestamine. | . | Restoring home preset | Algsete LoRa seadete taastamine. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . Kui skann on lõppenud, kuvab Discovery iga testitud eelseadistuse kohta tulemuste kaardi ja üldise kokkuvõtte. Metrics include: . | Meetriline | What it tells you | . | RF health | Overall quality of the radio environment on that preset. | . | Kanali kasutus | Kui hõivatud olid eetrisagedused kuulamise ajal. | . | Airtime | Transmission time observed. | . | Otse- ja vahendussõlmed | Kui mitu võrgusõlme kuuldi otse, võrreldes vahendaja kaudu. | . | Halvad / duplikaatpaketid | Rikutud ja korduvate pakettide arv, mis näitab ummikuid või häireid. | . Tulemustest saadaolevad lisafunktsioonid: . | Scan History — saved sessions you can revisit; view or delete past scans. | Avastuskaart – skanni käigus leitud sõlmede kaart. | Aruande eksport – ekspordi aruanne PDF-failina Androidis või tekstina muudel platvormidel. | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/discovery.html#kohalik-k%C3%A4rgv%C3%B5rgu-avastaja-skanner",
    
    "relUrl": "/et-rEE/user/discovery.html#kohalik-kärgvõrgu-avastaja-skanner"
  },"1343": {
    "doc": "Kohalik kärgvõrgu avastaja",
    "title": "Kärgvõrgu majakas",
    "content": "Kärgvõrgu majakas võimaldab sõlmedel kutsuda teisi oma võrguga liituma. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Kuula majakaid — võta vastu teiste sõlmede edastatud kutseid. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Received invitations appear as Mesh invitations cards on the Discovery screen. Igal kaardil kuvatakse saatja sõnum koos pakutava kanali, piirkonna, eelseadistuse ja signaali kvaliteedi ning järgmiste toimingutega: . | Join — switch to the offered channel and preset (retunes the node and reboots). Kui pakkumine sobib praeguse sageduspesaga, lisab toiming Lisa kanal selle taaskäivituseta. | Avasta – sisesta pakutud eelseadistusega avastusskannimisskeem, et saaksid enne liitumist seda võrku uurida (kuvatakse ainult siis, kui majakas pakub eelseadistust). | Dismiss — ignore the invitation. | . Majakate poolt reklaamitud kanalid kuvatakse skannimise seadistuses ka Majakakanalitena – valige üks, et see skannimise sihtmärgina lisada. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/discovery.html#k%C3%A4rgv%C3%B5rgu-majakas",
    
    "relUrl": "/et-rEE/user/discovery.html#kärgvõrgu-majakas"
  },"1344": {
    "doc": "Kohalik kärgvõrgu avastaja",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Marsruudi . Traceroute näitab täpset teed, mida sõnum sõlmest mis tahes teise kärgvõrgu sõlme kulgeb. See on kõige kasulikum tööriist ühenduvusprobleemide tõrkeotsinguks. Traceroute’i käivitamine . | Mine valikuni Sõlmed ja puuduta sõlme, mida soovid jälgida. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . Traceroute’i tulemus näeb välja selline: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | Kehv ühendus – see releesegment on habras | . | Mitu hüppet (4+) | Pikk tee – kaalu sõlme ümberpaigutamist selle lühendamiseks | . | Different path on retry | Mesh is adapting — multiple routes exist (this is good!) | . 💡 Vihje: Käivita traceroute’i mitu korda mõne minuti tagant. If the path changes, your mesh has redundant routes — a sign of a well-connected network. Veaotsing koos Traceroute . | No Response — The traceroute got nothing back. The target node may be offline, out of range, or on a different channel. Kontrolli, et mõlemad sõlmed jagaksid vähemalt ühte kanalit sama krüpteerimisvõtmega. | Traceroute aegus — Tee võib olla liiga pikk (ületab hüppete limiidi) või on vahendussõlm ülekoormatud. Try increasing the hop limit in Settings → LoRa. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asümmeetrilised teed – Jälgimismarsruut teelt A→B võib minna teist teed kui teelt B→A. This is normal — radio propagation isn’t always symmetric. | . Naabruse teave . Naabriinfo moodul võimaldab igal sõlmel levitada nimekirja sõlmedest, mida see otse kuuleb (üksik-hüpe). Kui mitu sõlme jagavad oma naaberloendeid, saate kokku panna kogu võrgu topoloogiakaardi. Naabriinfo lubamine . | Navigate to Settings → Module configuration → Neighbor Info. | Luba moodul. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Teised sõlmed, millel on naabriinfo lubatud, teevad sama. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | Iga naabri-kirje näitab otse kuuldud sõlme ja selle signaali kvaliteeti. | Kogu kärgvõrgu topoloogia mõistmiseks kombineerige mitme sõlme naaberandmeid. | . ℹ️ Note: Neighbor Info increases airtime usage because every enabled node periodically broadcasts its neighbor list. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. Node list as a discovery tool . Sõlmede loend ise on võimas avastusvahend, kui kasutada selle filtreerimis- ja sortimisfunktsioone tõhusalt. Finding new nodes . | Sorteeri Viimati kuuldud järgi, et näha kõige hiljutisemaid aktiivseid sõlmi ülaosas. | 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 nodes. | . Assessing connectivity . | Sorteeri Hüpete arvu järgi, et näha, millised sõlmed on otse kättesaadavad (0 hüpet) ja millised vahendatavate sõlmedega. | Sort by Distance to find nearby nodes and verify they’re reachable. | Use Exclude MQTT to focus on nodes reachable over LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Kontrolli nende signaali kvaliteeti ja viimase kuulmise aegu, et veenduda oma infrastruktuuri sõlmede töökorras olekus. | . Filtreerimis- ja sortimisvalikute kohta leiate lisateavet jaotisest Nodes. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/discovery.html#manual-exploration",
    
    "relUrl": "/et-rEE/user/discovery.html#manual-exploration"
  },"1345": {
    "doc": "Kohalik kärgvõrgu avastaja",
    "title": "Tips for Mesh exploration",
    "content": ". | Alusta traceroute’ist — see annab sulle kohest ja praktilist teavet konkreetse tee kohta. | Luba naabriinfo funktsioon võtmesõlmedes – eriti ruuterites ja repiiterites, et saada ülevaade magistraalvõrgust. | Kontrolli kaarti — sõlmede asukohad [Kaart] (map-and-waypoints) koos signaaliandmetega aitavad sul mõista, miks mõned ühendused on tugevad ja teised nõrgad. | Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly. | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/et-rEE/user/discovery.html#tips-for-mesh-exploration"
  },"1346": {
    "doc": "Kohalik kärgvõrgu avastaja",
    "title": "Seotud teemad",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/discovery.html#seotud-teemad",
    
    "relUrl": "/et-rEE/user/discovery.html#seotud-teemad"
  },"1347": {
    "doc": "Découverte de maille locale",
    "title": "Découverte de maille locale",
    "content": "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. The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Manual exploration — traceroute, Neighbor Info, and the node list, which you can use at any time to investigate specific paths and topology. | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/discovery.html",
    
    "relUrl": "/fr-rFR/user/discovery.html"
  },"1348": {
    "doc": "Découverte de maille locale",
    "title": "Local Mesh Discovery (Scanner)",
    "content": "Local Mesh Discovery is a dedicated scanning mode that helps you find the best LoRa modem preset for your location and see which nodes are active on each preset. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Before starting, configure these controls: . | Control | Description | . | LoRa preset picker | Select one or more presets to scan. Discovery dwells on each selected preset in turn. | . | Dwell time | Time to listen on each preset. Choose from 1, 5, 15, 30, 45, 60, 90, 120, or 180 minutes. Longer dwell times collect more packets and give a clearer picture, but take longer. | . | Keep screen awake | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The node is not connected. | No presets have been selected to scan. | The selected preset uses 2.4 GHz, which your hardware doesn’t support. | . Live progress . While a scan runs, Discovery shows its current stage: . | Stage | What’s happening | . | Preparing scan | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Re-establishing the connection after the preset change. | . | Dwelling on <preset> | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analyzing results | Processing the collected packets and ranking the presets. | . | Restoring home preset | Putting your original LoRa configuration back. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. Metrics include: . | Métrique | What it tells you | . | RF health | Overall quality of the radio environment on that preset. | . | Utilisation du canal | How busy the airwaves were during the dwell. | . | Temps d’émission | Transmission time observed. | . | Direct vs. relayed nodes | How many mesh nodes were heard directly versus via a relay. | . | Bad / duplicate packets | Counts of corrupt and repeated packets, indicating congestion or interference. | . Additional features available from the results: . | Scan History — saved sessions you can revisit; view or delete past scans. | Discovery Map — a map of the nodes found during the scan. | Report export — export a report as a PDF on Android, or as text on other platforms. | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/discovery.html#local-mesh-discovery-scanner",
    
    "relUrl": "/fr-rFR/user/discovery.html#local-mesh-discovery-scanner"
  },"1349": {
    "doc": "Découverte de maille locale",
    "title": "Mesh Beacon",
    "content": "Mesh Beacon lets nodes invite others to join their mesh. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Received invitations appear as Mesh invitations cards on the Discovery screen. Each card shows the sender’s message plus the offered channel, region, preset, and signal quality, with these actions: . | Join — switch to the offered channel and preset (retunes the node and reboots). When the offer matches your current frequency slot, an Add channel action adds it without a reboot. | Discover — seed a Discovery scan with the offered preset so you can survey that mesh before joining (shown only when the beacon offers a preset). | Dismiss — ignore the invitation. | . Channels advertised by beacons also show up in the scan setup as Beacon channels — select one to include it as a scan target. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/discovery.html#mesh-beacon",
    
    "relUrl": "/fr-rFR/user/discovery.html#mesh-beacon"
  },"1350": {
    "doc": "Découverte de maille locale",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. 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 . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | 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 Response — The traceroute got nothing back. 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. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Informations sur les voisins . 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 . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 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. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. 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 nodes. | . 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 LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/discovery.html#manual-exploration",
    
    "relUrl": "/fr-rFR/user/discovery.html#manual-exploration"
  },"1351": {
    "doc": "Découverte de maille locale",
    "title": "Tips for Mesh exploration",
    "content": ". | 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 combined with signal data help you understand why some links are strong and others are weak. | Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly. | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/fr-rFR/user/discovery.html#tips-for-mesh-exploration"
  },"1352": {
    "doc": "Découverte de maille locale",
    "title": "Related Topics",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/discovery.html#related-topics",
    
    "relUrl": "/fr-rFR/user/discovery.html#related-topics"
  },"1353": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery",
    "content": "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. The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Manual exploration — traceroute, Neighbor Info, and the node list, which you can use at any time to investigate specific paths and topology. | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/discovery.html",
    
    "relUrl": "/tr-rTR/user/discovery.html"
  },"1354": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery (Scanner)",
    "content": "Local Mesh Discovery is a dedicated scanning mode that helps you find the best LoRa modem preset for your location and see which nodes are active on each preset. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Before starting, configure these controls: . | Control | Açıklaması | . | LoRa preset picker | Select one or more presets to scan. Discovery dwells on each selected preset in turn. | . | Dwell time | Time to listen on each preset. Choose from 1, 5, 15, 30, 45, 60, 90, 120, or 180 minutes. Longer dwell times collect more packets and give a clearer picture, but take longer. | . | Keep screen awake | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The node is not connected. | No presets have been selected to scan. | The selected preset uses 2.4 GHz, which your hardware doesn’t support. | . Live progress . While a scan runs, Discovery shows its current stage: . | Stage | What’s happening | . | Preparing scan | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Re-establishing the connection after the preset change. | . | Dwelling on <preset> | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analyzing results | Processing the collected packets and ranking the presets. | . | Restoring home preset | Putting your original LoRa configuration back. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. Metrics include: . | Metric | What it tells you | . | RF health | Overall quality of the radio environment on that preset. | . | Channel utilization | How busy the airwaves were during the dwell. | . | Airtime | Transmission time observed. | . | Direct vs. relayed nodes | How many mesh nodes were heard directly versus via a relay. | . | Bad / duplicate packets | Counts of corrupt and repeated packets, indicating congestion or interference. | . Additional features available from the results: . | Scan History — saved sessions you can revisit; view or delete past scans. | Discovery Map — a map of the nodes found during the scan. | Report export — export a report as a PDF on Android, or as text on other platforms. | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/discovery.html#local-mesh-discovery-scanner",
    
    "relUrl": "/tr-rTR/user/discovery.html#local-mesh-discovery-scanner"
  },"1355": {
    "doc": "Local Mesh Discovery",
    "title": "Mesh Beacon",
    "content": "Mesh Beacon lets nodes invite others to join their mesh. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Received invitations appear as Mesh invitations cards on the Discovery screen. Each card shows the sender’s message plus the offered channel, region, preset, and signal quality, with these actions: . | Join — switch to the offered channel and preset (retunes the node and reboots). When the offer matches your current frequency slot, an Add channel action adds it without a reboot. | Discover — seed a Discovery scan with the offered preset so you can survey that mesh before joining (shown only when the beacon offers a preset). | Dismiss — ignore the invitation. | . Channels advertised by beacons also show up in the scan setup as Beacon channels — select one to include it as a scan target. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/discovery.html#mesh-beacon",
    
    "relUrl": "/tr-rTR/user/discovery.html#mesh-beacon"
  },"1356": {
    "doc": "Local Mesh Discovery",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Yol izle . 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 . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | 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 Response — The traceroute got nothing back. 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. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Komşu Bilgisi . 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 . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 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. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. 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 nodes. | . 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 LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/discovery.html#manual-exploration",
    
    "relUrl": "/tr-rTR/user/discovery.html#manual-exploration"
  },"1357": {
    "doc": "Local Mesh Discovery",
    "title": "Tips for Mesh exploration",
    "content": ". | 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 combined with signal data help you understand why some links are strong and others are weak. | Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly. | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/tr-rTR/user/discovery.html#tips-for-mesh-exploration"
  },"1358": {
    "doc": "Local Mesh Discovery",
    "title": "Related Topics",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/discovery.html#related-topics",
    
    "relUrl": "/tr-rTR/user/discovery.html#related-topics"
  },"1359": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery",
    "content": "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. The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Manual exploration — traceroute, Neighbor Info, and the node list, which you can use at any time to investigate specific paths and topology. | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/discovery.html",
    
    "relUrl": "/el-rGR/user/discovery.html"
  },"1360": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery (Scanner)",
    "content": "Local Mesh Discovery is a dedicated scanning mode that helps you find the best LoRa modem preset for your location and see which nodes are active on each preset. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Before starting, configure these controls: . | Control | Περιγραφή | . | LoRa preset picker | Select one or more presets to scan. Discovery dwells on each selected preset in turn. | . | Dwell time | Time to listen on each preset. Choose from 1, 5, 15, 30, 45, 60, 90, 120, or 180 minutes. Longer dwell times collect more packets and give a clearer picture, but take longer. | . | Keep screen awake | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The node is not connected. | No presets have been selected to scan. | The selected preset uses 2.4 GHz, which your hardware doesn’t support. | . Live progress . While a scan runs, Discovery shows its current stage: . | Stage | What’s happening | . | Preparing scan | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Re-establishing the connection after the preset change. | . | Dwelling on <preset> | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analyzing results | Processing the collected packets and ranking the presets. | . | Restoring home preset | Putting your original LoRa configuration back. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. Metrics include: . | Metric | What it tells you | . | RF health | Overall quality of the radio environment on that preset. | . | Channel utilization | How busy the airwaves were during the dwell. | . | Airtime | Transmission time observed. | . | Direct vs. relayed nodes | How many mesh nodes were heard directly versus via a relay. | . | Bad / duplicate packets | Counts of corrupt and repeated packets, indicating congestion or interference. | . Additional features available from the results: . | Scan History — saved sessions you can revisit; view or delete past scans. | Discovery Map — a map of the nodes found during the scan. | Report export — export a report as a PDF on Android, or as text on other platforms. | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/discovery.html#local-mesh-discovery-scanner",
    
    "relUrl": "/el-rGR/user/discovery.html#local-mesh-discovery-scanner"
  },"1361": {
    "doc": "Local Mesh Discovery",
    "title": "Mesh Beacon",
    "content": "Mesh Beacon lets nodes invite others to join their mesh. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Received invitations appear as Mesh invitations cards on the Discovery screen. Each card shows the sender’s message plus the offered channel, region, preset, and signal quality, with these actions: . | Join — switch to the offered channel and preset (retunes the node and reboots). When the offer matches your current frequency slot, an Add channel action adds it without a reboot. | Discover — seed a Discovery scan with the offered preset so you can survey that mesh before joining (shown only when the beacon offers a preset). | Dismiss — ignore the invitation. | . Channels advertised by beacons also show up in the scan setup as Beacon channels — select one to include it as a scan target. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/discovery.html#mesh-beacon",
    
    "relUrl": "/el-rGR/user/discovery.html#mesh-beacon"
  },"1362": {
    "doc": "Local Mesh Discovery",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. 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 . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | 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 Response — The traceroute got nothing back. 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. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t 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 . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 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. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. 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 nodes. | . 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 LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/discovery.html#manual-exploration",
    
    "relUrl": "/el-rGR/user/discovery.html#manual-exploration"
  },"1363": {
    "doc": "Local Mesh Discovery",
    "title": "Tips for Mesh exploration",
    "content": ". | 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 combined with signal data help you understand why some links are strong and others are weak. | Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly. | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/el-rGR/user/discovery.html#tips-for-mesh-exploration"
  },"1364": {
    "doc": "Local Mesh Discovery",
    "title": "Related Topics",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/discovery.html#related-topics",
    
    "relUrl": "/el-rGR/user/discovery.html#related-topics"
  },"1365": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery",
    "content": "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. The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Manual exploration — traceroute, Neighbor Info, and the node list, which you can use at any time to investigate specific paths and topology. | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/discovery.html",
    
    "relUrl": "/ro-rRO/user/discovery.html"
  },"1366": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery (Scanner)",
    "content": "Local Mesh Discovery is a dedicated scanning mode that helps you find the best LoRa modem preset for your location and see which nodes are active on each preset. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Before starting, configure these controls: . | Control | Descriere | . | LoRa preset picker | Select one or more presets to scan. Discovery dwells on each selected preset in turn. | . | Dwell time | Time to listen on each preset. Choose from 1, 5, 15, 30, 45, 60, 90, 120, or 180 minutes. Longer dwell times collect more packets and give a clearer picture, but take longer. | . | Keep screen awake | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The node is not connected. | No presets have been selected to scan. | The selected preset uses 2.4 GHz, which your hardware doesn’t support. | . Live progress . While a scan runs, Discovery shows its current stage: . | Stage | What’s happening | . | Preparing scan | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Re-establishing the connection after the preset change. | . | Dwelling on <preset> | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analyzing results | Processing the collected packets and ranking the presets. | . | Restoring home preset | Putting your original LoRa configuration back. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. Metrics include: . | Metric | What it tells you | . | RF health | Overall quality of the radio environment on that preset. | . | Channel utilization | How busy the airwaves were during the dwell. | . | Airtime | Transmission time observed. | . | Direct vs. relayed nodes | How many mesh nodes were heard directly versus via a relay. | . | Bad / duplicate packets | Counts of corrupt and repeated packets, indicating congestion or interference. | . Additional features available from the results: . | Scan History — saved sessions you can revisit; view or delete past scans. | Discovery Map — a map of the nodes found during the scan. | Report export — export a report as a PDF on Android, or as text on other platforms. | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/discovery.html#local-mesh-discovery-scanner",
    
    "relUrl": "/ro-rRO/user/discovery.html#local-mesh-discovery-scanner"
  },"1367": {
    "doc": "Local Mesh Discovery",
    "title": "Mesh Beacon",
    "content": "Mesh Beacon lets nodes invite others to join their mesh. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Received invitations appear as Mesh invitations cards on the Discovery screen. Each card shows the sender’s message plus the offered channel, region, preset, and signal quality, with these actions: . | Join — switch to the offered channel and preset (retunes the node and reboots). When the offer matches your current frequency slot, an Add channel action adds it without a reboot. | Discover — seed a Discovery scan with the offered preset so you can survey that mesh before joining (shown only when the beacon offers a preset). | Dismiss — ignore the invitation. | . Channels advertised by beacons also show up in the scan setup as Beacon channels — select one to include it as a scan target. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/discovery.html#mesh-beacon",
    
    "relUrl": "/ro-rRO/user/discovery.html#mesh-beacon"
  },"1368": {
    "doc": "Local Mesh Discovery",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Trasare traseu . 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 . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | 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 Response — The traceroute got nothing back. 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. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Informații vecin . 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 . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 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. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. 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 nodes. | . 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 LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/discovery.html#manual-exploration",
    
    "relUrl": "/ro-rRO/user/discovery.html#manual-exploration"
  },"1369": {
    "doc": "Local Mesh Discovery",
    "title": "Tips for Mesh exploration",
    "content": ". | 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 combined with signal data help you understand why some links are strong and others are weak. | Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly. | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/ro-rRO/user/discovery.html#tips-for-mesh-exploration"
  },"1370": {
    "doc": "Local Mesh Discovery",
    "title": "Related Topics",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/discovery.html#related-topics",
    
    "relUrl": "/ro-rRO/user/discovery.html#related-topics"
  },"1371": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery",
    "content": "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. The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Manual exploration — traceroute, Neighbor Info, and the node list, which you can use at any time to investigate specific paths and topology. | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/discovery.html",
    
    "relUrl": "/iw-rIL/user/discovery.html"
  },"1372": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery (Scanner)",
    "content": "Local Mesh Discovery is a dedicated scanning mode that helps you find the best LoRa modem preset for your location and see which nodes are active on each preset. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Before starting, configure these controls: . | Control | תיאור | . | LoRa preset picker | Select one or more presets to scan. Discovery dwells on each selected preset in turn. | . | Dwell time | Time to listen on each preset. Choose from 1, 5, 15, 30, 45, 60, 90, 120, or 180 minutes. Longer dwell times collect more packets and give a clearer picture, but take longer. | . | Keep screen awake | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The node is not connected. | No presets have been selected to scan. | The selected preset uses 2.4 GHz, which your hardware doesn’t support. | . Live progress . While a scan runs, Discovery shows its current stage: . | Stage | What’s happening | . | Preparing scan | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Re-establishing the connection after the preset change. | . | Dwelling on <preset> | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analyzing results | Processing the collected packets and ranking the presets. | . | Restoring home preset | Putting your original LoRa configuration back. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. Metrics include: . | Metric | What it tells you | . | RF health | Overall quality of the radio environment on that preset. | . | Channel utilization | How busy the airwaves were during the dwell. | . | Airtime | Transmission time observed. | . | Direct vs. relayed nodes | How many mesh nodes were heard directly versus via a relay. | . | Bad / duplicate packets | Counts of corrupt and repeated packets, indicating congestion or interference. | . Additional features available from the results: . | Scan History — saved sessions you can revisit; view or delete past scans. | Discovery Map — a map of the nodes found during the scan. | Report export — export a report as a PDF on Android, or as text on other platforms. | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/discovery.html#local-mesh-discovery-scanner",
    
    "relUrl": "/iw-rIL/user/discovery.html#local-mesh-discovery-scanner"
  },"1373": {
    "doc": "Local Mesh Discovery",
    "title": "Mesh Beacon",
    "content": "Mesh Beacon lets nodes invite others to join their mesh. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Received invitations appear as Mesh invitations cards on the Discovery screen. Each card shows the sender’s message plus the offered channel, region, preset, and signal quality, with these actions: . | Join — switch to the offered channel and preset (retunes the node and reboots). When the offer matches your current frequency slot, an Add channel action adds it without a reboot. | Discover — seed a Discovery scan with the offered preset so you can survey that mesh before joining (shown only when the beacon offers a preset). | Dismiss — ignore the invitation. | . Channels advertised by beacons also show up in the scan setup as Beacon channels — select one to include it as a scan target. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/discovery.html#mesh-beacon",
    
    "relUrl": "/iw-rIL/user/discovery.html#mesh-beacon"
  },"1374": {
    "doc": "Local Mesh Discovery",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. בדיקת מסלול . 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 . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | 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 Response — The traceroute got nothing back. 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. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t 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 . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 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. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. 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 nodes. | . 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 LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/discovery.html#manual-exploration",
    
    "relUrl": "/iw-rIL/user/discovery.html#manual-exploration"
  },"1375": {
    "doc": "Local Mesh Discovery",
    "title": "Tips for Mesh exploration",
    "content": ". | 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 combined with signal data help you understand why some links are strong and others are weak. | Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly. | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/iw-rIL/user/discovery.html#tips-for-mesh-exploration"
  },"1376": {
    "doc": "Local Mesh Discovery",
    "title": "Related Topics",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/discovery.html#related-topics",
    
    "relUrl": "/iw-rIL/user/discovery.html#related-topics"
  },"1377": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery",
    "content": "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. The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Manual exploration — traceroute, Neighbor Info, and the node list, which you can use at any time to investigate specific paths and topology. | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/discovery.html",
    
    "relUrl": "/pt-rBR/user/discovery.html"
  },"1378": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery (Scanner)",
    "content": "Local Mesh Discovery is a dedicated scanning mode that helps you find the best LoRa modem preset for your location and see which nodes are active on each preset. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Before starting, configure these controls: . | Control | Descrição | . | LoRa preset picker | Select one or more presets to scan. Discovery dwells on each selected preset in turn. | . | Dwell time | Time to listen on each preset. Choose from 1, 5, 15, 30, 45, 60, 90, 120, or 180 minutes. Longer dwell times collect more packets and give a clearer picture, but take longer. | . | Keep screen awake | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The node is not connected. | No presets have been selected to scan. | The selected preset uses 2.4 GHz, which your hardware doesn’t support. | . Live progress . While a scan runs, Discovery shows its current stage: . | Stage | What’s happening | . | Preparing scan | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Re-establishing the connection after the preset change. | . | Dwelling on <preset> | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analyzing results | Processing the collected packets and ranking the presets. | . | Restoring home preset | Putting your original LoRa configuration back. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. Metrics include: . | Metric | What it tells you | . | RF health | Overall quality of the radio environment on that preset. | . | Channel utilization | How busy the airwaves were during the dwell. | . | Airtime | Transmission time observed. | . | Direct vs. relayed nodes | How many mesh nodes were heard directly versus via a relay. | . | Bad / duplicate packets | Counts of corrupt and repeated packets, indicating congestion or interference. | . Additional features available from the results: . | Scan History — saved sessions you can revisit; view or delete past scans. | Discovery Map — a map of the nodes found during the scan. | Report export — export a report as a PDF on Android, or as text on other platforms. | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/discovery.html#local-mesh-discovery-scanner",
    
    "relUrl": "/pt-rBR/user/discovery.html#local-mesh-discovery-scanner"
  },"1379": {
    "doc": "Local Mesh Discovery",
    "title": "Mesh Beacon",
    "content": "Mesh Beacon lets nodes invite others to join their mesh. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Received invitations appear as Mesh invitations cards on the Discovery screen. Each card shows the sender’s message plus the offered channel, region, preset, and signal quality, with these actions: . | Join — switch to the offered channel and preset (retunes the node and reboots). When the offer matches your current frequency slot, an Add channel action adds it without a reboot. | Discover — seed a Discovery scan with the offered preset so you can survey that mesh before joining (shown only when the beacon offers a preset). | Dismiss — ignore the invitation. | . Channels advertised by beacons also show up in the scan setup as Beacon channels — select one to include it as a scan target. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/discovery.html#mesh-beacon",
    
    "relUrl": "/pt-rBR/user/discovery.html#mesh-beacon"
  },"1380": {
    "doc": "Local Mesh Discovery",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. Traçar rota . 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 . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | 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 Response — The traceroute got nothing back. 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. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t always symmetric. | . Informações do Vizinho . 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 . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 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. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. 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 nodes. | . 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 LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/discovery.html#manual-exploration",
    
    "relUrl": "/pt-rBR/user/discovery.html#manual-exploration"
  },"1381": {
    "doc": "Local Mesh Discovery",
    "title": "Tips for Mesh exploration",
    "content": ". | 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 combined with signal data help you understand why some links are strong and others are weak. | Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly. | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/pt-rBR/user/discovery.html#tips-for-mesh-exploration"
  },"1382": {
    "doc": "Local Mesh Discovery",
    "title": "Related Topics",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/discovery.html#related-topics",
    
    "relUrl": "/pt-rBR/user/discovery.html#related-topics"
  },"1383": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery",
    "content": "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. The app offers two complementary approaches: . | Local Mesh Discovery (Scanner) — an automated mode that cycles your connected node through different LoRa presets, listens on each, and ranks which preset performs best at your location. | Manual exploration — traceroute, Neighbor Info, and the node list, which you can use at any time to investigate specific paths and topology. | . ",
    "url": "/Meshtastic-Android/main/en/user/discovery.html",
    
    "relUrl": "/en/user/discovery.html"
  },"1384": {
    "doc": "Local Mesh Discovery",
    "title": "Local Mesh Discovery (Scanner)",
    "content": "Local Mesh Discovery is a dedicated scanning mode that helps you find the best LoRa modem preset for your location and see which nodes are active on each preset. It cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results. Connect your node, then open Settings → Advanced → Local Mesh Discovery. On Android the Advanced section appears only for a locally connected node, never over remote admin, and stays grayed out until the app has finished reading the node’s configuration. On a managed device its entries are disabled, except Debug Panel, which reads app-local logs and stays available. On desktop, Local Mesh Discovery has its own entry on the Settings screen, with no such gate. ℹ️ Note: Discovery temporarily changes your node’s LoRa settings while it scans, then restores your original configuration when it finishes. Setting up a scan . Before starting, configure these controls: . | Control | Description | . | LoRa preset picker | Select one or more presets to scan. Discovery dwells on each selected preset in turn. | . | Dwell time | Time to listen on each preset. Choose from 1, 5, 15, 30, 45, 60, 90, 120, or 180 minutes. Longer dwell times collect more packets and give a clearer picture, but take longer. | . | Keep screen awake | Keeps the display on for the scan. The scan itself holds a CPU wake lock for its whole run and posts a Scanning LoRa presets… notification, so it keeps collecting with the screen off or the app in the background. | . The Start Scan button stays disabled — with an explanation of why — until the scan can run. Common reasons it’s disabled: . | The node is not connected. | No presets have been selected to scan. | The selected preset uses 2.4 GHz, which your hardware doesn’t support. | . Live progress . While a scan runs, Discovery shows its current stage: . | Stage | What’s happening | . | Preparing scan | Saving your current configuration and getting ready to scan. | . | Shifting to <preset> | Switching the node to the next preset to test. | . | Reconnecting on <preset> | Re-establishing the connection after the preset change. | . | Dwelling on <preset> | Listening on the current preset to collect packets, with a countdown to the next step. | . | Analyzing results | Processing the collected packets and ranking the presets. | . | Restoring home preset | Putting your original LoRa configuration back. | . | Cancelling scan | You tapped Stop Scan; partial results are saved before the original preset is restored. | . | Scan failed: <reason> | The scan could not continue — most often the node didn’t come back within a minute of a preset change. The results collected so far are saved, and the original preset is restored automatically. | . If a scan is interrupted — the app is closed, or the node goes away — the app restores your original preset the next time it reconnects to that node, and tells you it has done so. Reconnect the same node to let that happen; until you do, the node stays on whichever preset the scan left it on. Reading the results . When the scan completes, Discovery presents a per-preset result card for each preset it tested, plus an overall summary. Metrics include: . | Metric | What it tells you | . | RF health | Overall quality of the radio environment on that preset. | . | Channel utilization | How busy the airwaves were during the dwell. | . | Airtime | Transmission time observed. | . | Direct vs. relayed nodes | How many mesh nodes were heard directly versus via a relay. | . | Bad / duplicate packets | Counts of corrupt and repeated packets, indicating congestion or interference. | . Additional features available from the results: . | Scan History — saved sessions you can revisit; view or delete past scans. | Discovery Map — a map of the nodes found during the scan. | Report export — export a report as a PDF on Android, or as text on other platforms. | . 💡 Tip: On Google Play builds, Discovery can generate an on-device AI summary (Gemini Nano) of your results. F-Droid builds always use the algorithmic summary — the proprietary ML Kit dependency is deliberately excluded from that flavor — so you get a readable interpretation of the scan either way. ",
    "url": "/Meshtastic-Android/main/en/user/discovery.html#local-mesh-discovery-scanner",
    
    "relUrl": "/en/user/discovery.html#local-mesh-discovery-scanner"
  },"1385": {
    "doc": "Local Mesh Discovery",
    "title": "Mesh Beacon",
    "content": "Mesh Beacon lets nodes invite others to join their mesh. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby nodes can hear even before they share a configuration. Configure it under Settings → Module configuration → Mesh Beacon. The entry appears only on nodes running firmware 2.8.0 or newer. A read-only Region row at the top of the screen shows the region the beacon advertises: that region, and the preset, are always the ones the node itself uses, so a beacon can’t invite anyone onto settings your node isn’t running. | Listen for beacons — receive invitations broadcast by other nodes. | Broadcast a beacon — periodically advertise this mesh to nearby nodes, with an optional Beacon message of up to 100 bytes, a Broadcast interval picked from fixed intervals between 1 hour and 72 hours, and an Offered channel chosen from your node’s own channels. The offered channel is required, and defaults to your primary channel. Over remote admin the picker offers the primary channel only. | Broadcast targets — where the beacon actually transmits. The list always holds at least one row: the first is the beacon’s own transmission, not an extra. Each row picks a Channel and a Transmit preset. Add target appends a row, and Remove target deletes one — removing the last row replaces it with a fresh default rather than emptying the list. | . Two conditions block beacon setup: . | The node has no region set. The screen shows nothing but Set your node’s region before setting up a beacon. Set the region on Settings → LoRa first. | The node uses custom LoRa settings. A beacon advertises a modem preset for others to join, so a node with Use Preset turned off has no standard preset to offer. In that state Broadcast a beacon can be turned off but not on, and the broadcast settings are read-only. Listening for beacons is unaffected. | . Received invitations appear as Mesh invitations cards on the Discovery screen. Each card shows the sender’s message plus the offered channel, region, preset, and signal quality, with these actions: . | Join — switch to the offered channel and preset (retunes the node and reboots). When the offer matches your current frequency slot, an Add channel action adds it without a reboot. | Discover — seed a Discovery scan with the offered preset so you can survey that mesh before joining (shown only when the beacon offers a preset). | Dismiss — ignore the invitation. | . Channels advertised by beacons also show up in the scan setup as Beacon channels — select one to include it as a scan target. An invitation to a mesh your node is already on is suppressed: no card, no notification, and no Beacon channels entry. A channel counts as one you already have only when both its name and its key match a channel on your node — the same name with a different key is a different mesh, so that invitation still reaches you. ",
    "url": "/Meshtastic-Android/main/en/user/discovery.html#mesh-beacon",
    
    "relUrl": "/en/user/discovery.html#mesh-beacon"
  },"1386": {
    "doc": "Local Mesh Discovery",
    "title": "Manual exploration",
    "content": "The following tools are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan. 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 . | Navigate to Nodes and tap the node you want to trace. | On the node detail screen, find Traceroute in the Telemetry section and tap its request button. Once a result arrives, a second button on the same row opens the traceroute log, where each hop is listed with its signal quality. | . Reading the results . A traceroute result looks like this: . Route traced toward destination: ■ Your Node (YOUR) ⇊ 8.5 dB ■ Relay Node (RLAY) ⇊ -8.75 dB ■ Target Node (TGT1) . Each ⇊ line between two nodes is one relay hop, and the SNR on that line is the quality of that segment alone. The app colors it against the demodulation floor of the preset in use, not a fixed number: green above the floor, yellow within 5.5 dB below it, orange within 7.5 dB, and red beyond that. The floor is −7.5 dB on Short Fast and improves 2.5 dB per spreading-factor step, so it is −17.5 dB on Long Fast — the same SNR reads differently on different presets. See Signal Meter. A request that also gets a reply adds a second block under Route traced back to us:. | What to look for | What it means | . | All hops show Good SNR (green) | Healthy path — messages flow reliably | . | One hop shows a poor SNR (orange or red) | 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 Response — The traceroute got nothing back. 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. | Cannot show traceroute map because the start or destination node has no position information — The path was traced, but one end has never shared a position. | Asymmetric paths — A traceroute from A→B may take a different path than B→A. This is normal — radio propagation isn’t 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 . | Navigate to Settings → Module configuration → Neighbor Info. | Enable the module. | Set Update interval (seconds). The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it. | Turn on Transmit over LoRa. Without it, your neighbor list goes only to MQTT and to this app, never over the air. | . Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same. Viewing neighbor data . | Open a node’s detail screen and find Neighbor Info in the Telemetry section. The request button asks the node for its current neighbor list; once the app has received one, a second button on the same row opens the log of everything that node has reported. The row appears only on nodes that can answer a neighbor request, or that have already reported neighbors. | 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. The firmware doesn’t accept an interval shorter than 14400 seconds (4 hours) for this reason; on busy meshes, leave it at the 21600-second default or raise it further. 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 nodes. | . 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 LoRa (not via internet bridge). | . Infrastructure audit . | Disable Exclude infrastructure to see Router, Router Late, and Client Base nodes. | Check their signal quality and last-heard times to verify your infrastructure nodes are healthy. | . See Nodes for full details on filtering and sorting options. ",
    "url": "/Meshtastic-Android/main/en/user/discovery.html#manual-exploration",
    
    "relUrl": "/en/user/discovery.html#manual-exploration"
  },"1387": {
    "doc": "Local Mesh Discovery",
    "title": "Tips for Mesh exploration",
    "content": ". | 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 combined with signal data help you understand why some links are strong and others are weak. | Compare signal over time — use the Signal Meter guide to interpret SNR and RSSI values correctly. | . ",
    "url": "/Meshtastic-Android/main/en/user/discovery.html#tips-for-mesh-exploration",
    
    "relUrl": "/en/user/discovery.html#tips-for-mesh-exploration"
  },"1388": {
    "doc": "Local Mesh Discovery",
    "title": "Related Topics",
    "content": ". | Nodes — the node list these scans populate | Map & Waypoints — see discovered nodes geographically | Signal Meter — interpret the SNR and RSSI a scan reports | Settings — Modules & Admin — configure the Mesh Beacon and Neighbor Info modules | Messages & Channels — join a mesh you found and start talking | . ",
    "url": "/Meshtastic-Android/main/en/user/discovery.html#related-topics",
    
    "relUrl": "/en/user/discovery.html#related-topics"
  },"1389": {
    "doc": "Documentation Style",
    "title": "Documentation Style",
    "content": "Section 11 of the Meshtastic Client Design Standards is the style guide for everything under docs/en/. Read it first. It decides voice, plain language, terminology, page structure, instructions, cross-platform coverage, code and CLI examples, media, accessibility, admonition use, units, translation, versioning, and in-product text, and it closes with a checklist of the rules a reviewer can check without judgment. This page carries what Section 11 doesn’t: how documentation works in this repository, two forms that differ here, and the one prose rule the standards leave open. Where the two ever disagree on something not listed here, Section 11 wins and this page is wrong. Pages under docs/en/ ship to three places — the in-app docs browser, the GitHub Pages site, and meshtastic.org — so one page has to read well in all of them, and its English source is the translation base for 40+ locales on Crowdin. Section 11.1 describes the sync: user pages land in docs/software/android/ on the documentation site weekly, taken from the latest release, and pull requests against those paths there are reverted. Rules keep the IDs they had so review feedback and audit findings can still cite them. Rules that Section 11 now covers are retired, and their IDs aren’t reused. ",
    "url": "/Meshtastic-Android/main/en/developer/documentation-style.html",
    
    "relUrl": "/en/developer/documentation-style.html"
  },"1390": {
    "doc": "Documentation Style",
    "title": "In transition",
    "content": "Two rules changed when Section 11 landed. Neither is a sweep. | Headings are sentence case (11.5, and a quick check in 11.16). Existing Title Case headings stay until the page is edited for another reason. Re-casing a heading invalidates its translation memory across 40+ locales, so it happens as pages are touched and never as a pass of its own. Frontmatter title values are the nav labels the in-app browser and the site share, so they change with the rest of the nav rather than one page at a time. | The hardware is a node (11.4). This repo used radio to disambiguate the hardware from the phone, and roughly 300 uses of it remain. Prefer node in new writing and drop radio when you edit a page. Phone still means the Android handset the app runs on, which Section 11 has no word for. | . ",
    "url": "/Meshtastic-Android/main/en/developer/documentation-style.html#in-transition",
    
    "relUrl": "/en/developer/documentation-style.html#in-transition"
  },"1391": {
    "doc": "Documentation Style",
    "title": "Repository mechanics",
    "content": ". | STRUCT-1 — Complete frontmatter on every page, user and developer: title, parent, nav_order, last_updated (bump it whenever content changes — CI checks freshness), description (one sentence, ~160 characters, used by search and link previews), and aliases (search terms the in-app browser resolves). | HEAD-2 — One # H1 per page, and it matches the frontmatter title exactly. The in-app index is built from the frontmatter, so a mismatch shows the reader two different titles for one page. | STRUCT-3 — User pages end with a ## Related Topics section: bulleted links, each with an em-dash clause saying why you’d go there. The heading is a fixed section name shared by 22 pages, so like a frontmatter title it stays Title Case until they all change together. | STRUCT-4 — No horizontal rules (---) in page bodies, and especially not at the end of the file — the site layout adds its own footer rule, so a trailing --- renders as a doubled line. | STRUCT-5 — New pages must be registered in DocBundleLoader.kt (the in-app index) — CI fails in both directions if the page and the index disagree. | STRUCT-6 — Notable page changes get a What’s New entry at the top of user.md or developer.md, in the format the HTML comment there specifies. | IMG-1 — Reference screenshots by relative path from docs/assets/screenshots/: ../../assets/screenshots/<page>_<subject>.png. Both the Docusaurus sync and the in-app renderer anchor on the assets/ segment, so this one form works in all three consumers. | LINK-2 — Sibling pages link by bare slug (connections), cross-section by relative path (../developer/testing). scripts/validate-doc-links.js enforces resolvability. | LINK-3 — Node-side concepts (LoRa presets, firmware regions, MQTT topics) link out to the meshtastic.org docs rather than being re-explained here. One source drifts less than two. | CODE-1 — Code font for module paths (core:ble), Gradle tasks, class and function names, and setting keys, alongside the cases 11.8 covers. | DEV-1 — Developer pages assume Kotlin, Gradle, and Android fluency and skip the reassurance, but every rule on this page and in Section 11 still applies. Terse is good; cryptic is not. | DEV-3 — Structural or procedural changes get a What’s New for Developers entry in developer.md. | . ",
    "url": "/Meshtastic-Android/main/en/developer/documentation-style.html#repository-mechanics",
    
    "relUrl": "/en/developer/documentation-style.html#repository-mechanics"
  },"1392": {
    "doc": "Documentation Style",
    "title": "Local forms",
    "content": "Two forms differ from Section 11. The first is a renderer requirement. The second is the entrenched house form, kept because changing it would touch every page for no reader benefit. | ADMON-1 — Admonitions are a blockquote starting with an emoji and a bold label, from this closed set. The in-app renderer has no admonition component, so :::note would reach the reader as literal text. Section 11.11 exempts synced client documentation for exactly this reason and leaves the form to this guide; its rules on when to use one still apply in full, including at most one per H2 section. | Admonition | Use for | . | > 💡 **Tip:** | An optional shortcut or non-obvious alternative. The reader loses nothing by skipping it. | . | > ℹ️ **Note:** | Supplementary information worth knowing but not required for the task. | . | > ⚠️ **Important:** | Information essential to completing the task correctly, without danger of loss. | . | > ⚠️ **Warning:** | Risk of data loss, lockout, or hardware damage. Must come before the action it applies to. | . | > 🔒 **Privacy:** | What data leaves the phone, who on the mesh can see it, and how to limit it. | . | > 🔒 **Security:** | Cryptographic caveats — key handling, unencrypted channels, admin access. | . Privacy and Security are house labels with no equivalent upstream. They exist because the app’s constitution makes privacy a core principle, and they shouldn’t be flattened into Note. | PROC-2 — Menu paths use a spaced arrow between bold labels: Settings → Permissions. Never > or ›. Section 11.6 writes the separator as > in its example; the arrow is this corpus’s established form, unambiguous in Markdown, and it reads naturally in the in-app renderer. | . ",
    "url": "/Meshtastic-Android/main/en/developer/documentation-style.html#local-forms",
    
    "relUrl": "/en/developer/documentation-style.html#local-forms"
  },"1393": {
    "doc": "Documentation Style",
    "title": "Prose rules Section 11 leaves open",
    "content": "One rule. design#154 moved the rest into Section 11, where they read the same, so nothing about how you write changes — the rules have one home rather than two that can drift apart. | LANG-7 — Em dashes are spaced — like this — matching the entire existing corpus. Section 11 doesn’t mention them. | . These are retired, with the section that owns each. Their IDs aren’t reused. | Retired rule | Section | . | VOICE-2 — contractions, and do not in warnings | 11.2 | . | LANG-3 — requirement words | 11.3 | . | LANG-4 — e.g. and i.e. | 11.3 | . | LANG-6 — inclusive, literal language | 11.3 | . | LANG-7 — the Oxford comma half; the em dash stays | 11.3 | . | LANG-1 — American spelling | 11.4 | . | LANG-9 — above and below | 11.5 | . | LANG-8 — number style | 11.12 | . ",
    "url": "/Meshtastic-Android/main/en/developer/documentation-style.html#prose-rules-section-11-leaves-open",
    
    "relUrl": "/en/developer/documentation-style.html#prose-rules-section-11-leaves-open"
  },"1394": {
    "doc": "Documentation Style",
    "title": "Word list",
    "content": "Terms this repository needs that the Section 11 tables don’t cover. Section 11.4 decides the rest. | Term | Rule | . | email | No hyphen. | . | internet | Lowercase. | . | phone | The Android handset the app runs on. Use phone even when a tablet also works, unless the distinction matters. | . | set up / setup | Verb two words, noun/adjective one word. | . | sign in | Verb; sign-in as adjective. Not log in or login. | . | tap | The interaction verb for the app’s touch UI. These pages are mobile-specific, so tap stands where 11.7 would prefer select. Never tap on. | . | touch & hold | Exactly this form (Google’s Android convention). Not long press, not tap and hold. | . ",
    "url": "/Meshtastic-Android/main/en/developer/documentation-style.html#word-list",
    
    "relUrl": "/en/developer/documentation-style.html#word-list"
  },"1395": {
    "doc": "Documentation Style",
    "title": "New page checklist",
    "content": ". | Create docs/en/user/<slug>.md or docs/en/developer/<slug>.md with complete frontmatter (STRUCT-1). | Register the page in feature/docs/.../data/DocBundleLoader.kt with keywords and aliases. | Put screenshots in docs/assets/screenshots/, referenced per IMG-1. | Add a What’s New entry (STRUCT-6). | Validate locally: node scripts/validate-doc-links.js docs/en, node scripts/check-doc-coverage.js ., node scripts/check-doc-aliases.js . (every alias in step 1’s frontmatter must also be in step 2’s loader entry — only the loader’s list reaches in-app search), and the docs bundle Gradle checks in Contributing. | Run the Section 11.16 quick checks over the page before you open the pull request. | . ",
    "url": "/Meshtastic-Android/main/en/developer/documentation-style.html#new-page-checklist",
    
    "relUrl": "/en/developer/documentation-style.html#new-page-checklist"
  },"1396": {
    "doc": "Documentation Style",
    "title": "Related Topics",
    "content": ". | Contributing — branch naming, PR workflow, and the verification gates docs changes run through | Test Builds & Obtainium — where prerelease docs snapshots are published | . ",
    "url": "/Meshtastic-Android/main/en/developer/documentation-style.html#related-topics",
    
    "relUrl": "/en/developer/documentation-style.html#related-topics"
  },"1397": {
    "doc": "Firmware Updates",
    "title": "Firmware Updates",
    "content": "Keep your Meshtastic radio up to date with the latest firmware for new features, bug fixes, and security improvements. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/firmware.html",
    
    "relUrl": "/sk-rSK/user/firmware.html"
  },"1398": {
    "doc": "Firmware Updates",
    "title": "Checking for Updates",
    "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable radios. | The app checks for available firmware versions. | Available updates show the version number and changelog summary. | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/firmware.html#checking-for-updates",
    
    "relUrl": "/sk-rSK/user/firmware.html#checking-for-updates"
  },"1399": {
    "doc": "Firmware Updates",
    "title": "Update Methods",
    "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | Wait for the update to complete — do not disconnect during the update. | . Erase device during update . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Wipes the device’s flash completely, then installs the selected firmware from scratch. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. In-App USB Update . When your radio is connected over USB/serial (rather than Bluetooth), the Firmware Update screen offers USB File Transfer. The app reboots the device into DFU mode, then prompts you to save the .uf2 file to the device’s DFU drive using the system file picker. This option appears only on a USB/serial connection — it is not available over Bluetooth. ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. A bootloader supplied as an update-....uf2 can be installed by copying it to the drive; that is how the app’s own bootloader upgrade works. The app surfaces a hint when the serial-only route applies. Factory Erase and Bootloader Upgrade . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. The app reads INFO_UF2.TXT from the drive you select to confirm it really is the device’s update drive and to identify the board before writing anything. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Other Flashing Options . For recovery or when neither OTA nor in-app USB is available: . | Use the Meshtastic Web Flasher | Or the Meshtastic CLI tool on desktop | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/firmware.html#update-methods",
    
    "relUrl": "/sk-rSK/user/firmware.html#update-methods"
  },"1400": {
    "doc": "Firmware Updates",
    "title": "Version Channels",
    "content": "| Kanál | Popis | . | Stable | Recommended for most users; tested releases | . | Alpha | Preview releases; may contain bugs | . | Local File | Flash a firmware file you select yourself, instead of a downloaded release | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/firmware.html#version-channels",
    
    "relUrl": "/sk-rSK/user/firmware.html#version-channels"
  },"1401": {
    "doc": "Firmware Updates",
    "title": "Pre-Update Checklist",
    "content": "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 | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/firmware.html#pre-update-checklist",
    
    "relUrl": "/sk-rSK/user/firmware.html#pre-update-checklist"
  },"1402": {
    "doc": "Firmware Updates",
    "title": "Post-Update",
    "content": "After the firmware is written, the app verifies the update and waits for the device to come back online: . Once the update succeeds: . | The radio reboots automatically | The Bluetooth connection re-establishes | Verify your settings are intact | Confirm the new version under Currently Installed on the Firmware Update screen — it’s also shown on the node’s detail page and the Connections screen | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/firmware.html#post-update",
    
    "relUrl": "/sk-rSK/user/firmware.html#post-update"
  },"1403": {
    "doc": "Firmware Updates",
    "title": "Troubleshooting",
    "content": "Update Stuck . If the update appears frozen: . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | Try connecting via USB to a computer | Use the web flasher in recovery/DFU mode | Flash a known-good firmware version | Check the Meshtastic Discord for device-specific recovery steps | . Compatibility Warnings . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | Firmware version | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/firmware.html#troubleshooting",
    
    "relUrl": "/sk-rSK/user/firmware.html#troubleshooting"
  },"1404": {
    "doc": "Firmware Updates",
    "title": "Related Topics",
    "content": ". | Connections — reconnecting after a firmware update | Flashing firmware guide — full firmware flashing walkthrough on meshtastic.org | Supported devices — check firmware compatibility by device | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/firmware.html#related-topics",
    
    "relUrl": "/sk-rSK/user/firmware.html#related-topics"
  },"1405": {
    "doc": "Firmware Updates",
    "title": "Firmware Updates",
    "content": "Keep your Meshtastic radio up to date with the latest firmware for new features, bug fixes, and security improvements. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/firmware.html",
    
    "relUrl": "/be-rBY/user/firmware.html"
  },"1406": {
    "doc": "Firmware Updates",
    "title": "Checking for Updates",
    "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable radios. | The app checks for available firmware versions. | Available updates show the version number and changelog summary. | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/firmware.html#checking-for-updates",
    
    "relUrl": "/be-rBY/user/firmware.html#checking-for-updates"
  },"1407": {
    "doc": "Firmware Updates",
    "title": "Update Methods",
    "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | Wait for the update to complete — do not disconnect during the update. | . Erase device during update . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Wipes the device’s flash completely, then installs the selected firmware from scratch. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. In-App USB Update . When your radio is connected over USB/serial (rather than Bluetooth), the Firmware Update screen offers USB File Transfer. The app reboots the device into DFU mode, then prompts you to save the .uf2 file to the device’s DFU drive using the system file picker. This option appears only on a USB/serial connection — it is not available over Bluetooth. ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. A bootloader supplied as an update-....uf2 can be installed by copying it to the drive; that is how the app’s own bootloader upgrade works. The app surfaces a hint when the serial-only route applies. Factory Erase and Bootloader Upgrade . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. The app reads INFO_UF2.TXT from the drive you select to confirm it really is the device’s update drive and to identify the board before writing anything. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Other Flashing Options . For recovery or when neither OTA nor in-app USB is available: . | Use the Meshtastic Web Flasher | Or the Meshtastic CLI tool on desktop | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/firmware.html#update-methods",
    
    "relUrl": "/be-rBY/user/firmware.html#update-methods"
  },"1408": {
    "doc": "Firmware Updates",
    "title": "Version Channels",
    "content": "| Канал | Апісанне | . | Stable | Recommended for most users; tested releases | . | Alpha | Preview releases; may contain bugs | . | Local File | Flash a firmware file you select yourself, instead of a downloaded release | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/firmware.html#version-channels",
    
    "relUrl": "/be-rBY/user/firmware.html#version-channels"
  },"1409": {
    "doc": "Firmware Updates",
    "title": "Pre-Update Checklist",
    "content": "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 | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/firmware.html#pre-update-checklist",
    
    "relUrl": "/be-rBY/user/firmware.html#pre-update-checklist"
  },"1410": {
    "doc": "Firmware Updates",
    "title": "Post-Update",
    "content": "After the firmware is written, the app verifies the update and waits for the device to come back online: . Once the update succeeds: . | The radio reboots automatically | The Bluetooth connection re-establishes | Verify your settings are intact | Confirm the new version under Currently Installed on the Firmware Update screen — it’s also shown on the node’s detail page and the Connections screen | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/firmware.html#post-update",
    
    "relUrl": "/be-rBY/user/firmware.html#post-update"
  },"1411": {
    "doc": "Firmware Updates",
    "title": "Troubleshooting",
    "content": "Update Stuck . If the update appears frozen: . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | Try connecting via USB to a computer | Use the web flasher in recovery/DFU mode | Flash a known-good firmware version | Check the Meshtastic Discord for device-specific recovery steps | . Compatibility Warnings . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | Firmware version | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/firmware.html#troubleshooting",
    
    "relUrl": "/be-rBY/user/firmware.html#troubleshooting"
  },"1412": {
    "doc": "Firmware Updates",
    "title": "Related Topics",
    "content": ". | Connections — reconnecting after a firmware update | Flashing firmware guide — full firmware flashing walkthrough on meshtastic.org | Supported devices — check firmware compatibility by device | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/firmware.html#related-topics",
    
    "relUrl": "/be-rBY/user/firmware.html#related-topics"
  },"1413": {
    "doc": "Firmware Updates",
    "title": "Firmware Updates",
    "content": "Keep your Meshtastic radio up to date with the latest firmware for new features, bug fixes, and security improvements. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/firmware.html",
    
    "relUrl": "/it-rIT/user/firmware.html"
  },"1414": {
    "doc": "Firmware Updates",
    "title": "Checking for Updates",
    "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable radios. | The app checks for available firmware versions. | Available updates show the version number and changelog summary. | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/firmware.html#checking-for-updates",
    
    "relUrl": "/it-rIT/user/firmware.html#checking-for-updates"
  },"1415": {
    "doc": "Firmware Updates",
    "title": "Update Methods",
    "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | Wait for the update to complete — do not disconnect during the update. | . Erase device during update . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Wipes the device’s flash completely, then installs the selected firmware from scratch. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. In-App USB Update . When your radio is connected over USB/serial (rather than Bluetooth), the Firmware Update screen offers USB File Transfer. The app reboots the device into DFU mode, then prompts you to save the .uf2 file to the device’s DFU drive using the system file picker. This option appears only on a USB/serial connection — it is not available over Bluetooth. ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. A bootloader supplied as an update-....uf2 can be installed by copying it to the drive; that is how the app’s own bootloader upgrade works. The app surfaces a hint when the serial-only route applies. Factory Erase and Bootloader Upgrade . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. The app reads INFO_UF2.TXT from the drive you select to confirm it really is the device’s update drive and to identify the board before writing anything. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Other Flashing Options . For recovery or when neither OTA nor in-app USB is available: . | Use the Meshtastic Web Flasher | Or the Meshtastic CLI tool on desktop | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/firmware.html#update-methods",
    
    "relUrl": "/it-rIT/user/firmware.html#update-methods"
  },"1416": {
    "doc": "Firmware Updates",
    "title": "Version Channels",
    "content": "| Canale | Descrizione | . | Stabile | Recommended for most users; tested releases | . | Alfa | Preview releases; may contain bugs | . | Local File | Flash a firmware file you select yourself, instead of a downloaded release | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/firmware.html#version-channels",
    
    "relUrl": "/it-rIT/user/firmware.html#version-channels"
  },"1417": {
    "doc": "Firmware Updates",
    "title": "Pre-Update Checklist",
    "content": "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 | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/firmware.html#pre-update-checklist",
    
    "relUrl": "/it-rIT/user/firmware.html#pre-update-checklist"
  },"1418": {
    "doc": "Firmware Updates",
    "title": "Post-Update",
    "content": "After the firmware is written, the app verifies the update and waits for the device to come back online: . Once the update succeeds: . | The radio reboots automatically | The Bluetooth connection re-establishes | Verify your settings are intact | Confirm the new version under Currently Installed on the Firmware Update screen — it’s also shown on the node’s detail page and the Connections screen | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/firmware.html#post-update",
    
    "relUrl": "/it-rIT/user/firmware.html#post-update"
  },"1419": {
    "doc": "Firmware Updates",
    "title": "Risoluzione problemi",
    "content": "Update Stuck . If the update appears frozen: . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | Try connecting via USB to a computer | Use the web flasher in recovery/DFU mode | Flash a known-good firmware version | Check the Meshtastic Discord for device-specific recovery steps | . Compatibility Warnings . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | Versione firmware | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/firmware.html#risoluzione-problemi",
    
    "relUrl": "/it-rIT/user/firmware.html#risoluzione-problemi"
  },"1420": {
    "doc": "Firmware Updates",
    "title": "Related Topics",
    "content": ". | Connections — reconnecting after a firmware update | Flashing firmware guide — full firmware flashing walkthrough on meshtastic.org | Supported devices — check firmware compatibility by device | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/firmware.html#related-topics",
    
    "relUrl": "/it-rIT/user/firmware.html#related-topics"
  },"1421": {
    "doc": "Firmware Updates",
    "title": "Firmware Updates",
    "content": "Keep your Meshtastic radio up to date with the latest firmware for new features, bug fixes, and security improvements. ",
    "url": "/Meshtastic-Android/main/es-rES/user/firmware.html",
    
    "relUrl": "/es-rES/user/firmware.html"
  },"1422": {
    "doc": "Firmware Updates",
    "title": "Checking for Updates",
    "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable radios. | The app checks for available firmware versions. | Available updates show the version number and changelog summary. | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/firmware.html#checking-for-updates",
    
    "relUrl": "/es-rES/user/firmware.html#checking-for-updates"
  },"1423": {
    "doc": "Firmware Updates",
    "title": "Update Methods",
    "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | Wait for the update to complete — do not disconnect during the update. | . Erase device during update . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Wipes the device’s flash completely, then installs the selected firmware from scratch. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. In-App USB Update . When your radio is connected over USB/serial (rather than Bluetooth), the Firmware Update screen offers USB File Transfer. The app reboots the device into DFU mode, then prompts you to save the .uf2 file to the device’s DFU drive using the system file picker. This option appears only on a USB/serial connection — it is not available over Bluetooth. ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. A bootloader supplied as an update-....uf2 can be installed by copying it to the drive; that is how the app’s own bootloader upgrade works. The app surfaces a hint when the serial-only route applies. Factory Erase and Bootloader Upgrade . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. The app reads INFO_UF2.TXT from the drive you select to confirm it really is the device’s update drive and to identify the board before writing anything. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Other Flashing Options . For recovery or when neither OTA nor in-app USB is available: . | Use the Meshtastic Web Flasher | Or the Meshtastic CLI tool on desktop | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/firmware.html#update-methods",
    
    "relUrl": "/es-rES/user/firmware.html#update-methods"
  },"1424": {
    "doc": "Firmware Updates",
    "title": "Version Channels",
    "content": "| Canal | Descripción | . | Estable | Recommended for most users; tested releases | . | Alpha | Preview releases; may contain bugs | . | Local File | Flash a firmware file you select yourself, instead of a downloaded release | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/firmware.html#version-channels",
    
    "relUrl": "/es-rES/user/firmware.html#version-channels"
  },"1425": {
    "doc": "Firmware Updates",
    "title": "Pre-Update Checklist",
    "content": "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 | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/firmware.html#pre-update-checklist",
    
    "relUrl": "/es-rES/user/firmware.html#pre-update-checklist"
  },"1426": {
    "doc": "Firmware Updates",
    "title": "Post-Update",
    "content": "After the firmware is written, the app verifies the update and waits for the device to come back online: . Once the update succeeds: . | The radio reboots automatically | The Bluetooth connection re-establishes | Verify your settings are intact | Confirm the new version under Currently Installed on the Firmware Update screen — it’s also shown on the node’s detail page and the Connections screen | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/firmware.html#post-update",
    
    "relUrl": "/es-rES/user/firmware.html#post-update"
  },"1427": {
    "doc": "Firmware Updates",
    "title": "Troubleshooting",
    "content": "Update Stuck . If the update appears frozen: . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | Try connecting via USB to a computer | Use the web flasher in recovery/DFU mode | Flash a known-good firmware version | Check the Meshtastic Discord for device-specific recovery steps | . Compatibility Warnings . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | Versión del software | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/es-rES/user/firmware.html#troubleshooting",
    
    "relUrl": "/es-rES/user/firmware.html#troubleshooting"
  },"1428": {
    "doc": "Firmware Updates",
    "title": "Related Topics",
    "content": ". | Connections — reconnecting after a firmware update | Flashing firmware guide — full firmware flashing walkthrough on meshtastic.org | Supported devices — check firmware compatibility by device | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/firmware.html#related-topics",
    
    "relUrl": "/es-rES/user/firmware.html#related-topics"
  },"1429": {
    "doc": "Firmware Updates",
    "title": "Firmware Updates",
    "content": "Keep your Meshtastic radio up to date with the latest firmware for new features, bug fixes, and security improvements. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/firmware.html",
    
    "relUrl": "/sl-rSI/user/firmware.html"
  },"1430": {
    "doc": "Firmware Updates",
    "title": "Checking for Updates",
    "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable radios. | The app checks for available firmware versions. | Available updates show the version number and changelog summary. | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/firmware.html#checking-for-updates",
    
    "relUrl": "/sl-rSI/user/firmware.html#checking-for-updates"
  },"1431": {
    "doc": "Firmware Updates",
    "title": "Update Methods",
    "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | Wait for the update to complete — do not disconnect during the update. | . Erase device during update . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Wipes the device’s flash completely, then installs the selected firmware from scratch. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. In-App USB Update . When your radio is connected over USB/serial (rather than Bluetooth), the Firmware Update screen offers USB File Transfer. The app reboots the device into DFU mode, then prompts you to save the .uf2 file to the device’s DFU drive using the system file picker. This option appears only on a USB/serial connection — it is not available over Bluetooth. ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. A bootloader supplied as an update-....uf2 can be installed by copying it to the drive; that is how the app’s own bootloader upgrade works. The app surfaces a hint when the serial-only route applies. Factory Erase and Bootloader Upgrade . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. The app reads INFO_UF2.TXT from the drive you select to confirm it really is the device’s update drive and to identify the board before writing anything. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Other Flashing Options . For recovery or when neither OTA nor in-app USB is available: . | Use the Meshtastic Web Flasher | Or the Meshtastic CLI tool on desktop | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/firmware.html#update-methods",
    
    "relUrl": "/sl-rSI/user/firmware.html#update-methods"
  },"1432": {
    "doc": "Firmware Updates",
    "title": "Version Channels",
    "content": "| Kanal | Opis | . | Stable | Recommended for most users; tested releases | . | Alpha | Preview releases; may contain bugs | . | Local File | Flash a firmware file you select yourself, instead of a downloaded release | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/firmware.html#version-channels",
    
    "relUrl": "/sl-rSI/user/firmware.html#version-channels"
  },"1433": {
    "doc": "Firmware Updates",
    "title": "Pre-Update Checklist",
    "content": "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 | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/firmware.html#pre-update-checklist",
    
    "relUrl": "/sl-rSI/user/firmware.html#pre-update-checklist"
  },"1434": {
    "doc": "Firmware Updates",
    "title": "Post-Update",
    "content": "After the firmware is written, the app verifies the update and waits for the device to come back online: . Once the update succeeds: . | The radio reboots automatically | The Bluetooth connection re-establishes | Verify your settings are intact | Confirm the new version under Currently Installed on the Firmware Update screen — it’s also shown on the node’s detail page and the Connections screen | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/firmware.html#post-update",
    
    "relUrl": "/sl-rSI/user/firmware.html#post-update"
  },"1435": {
    "doc": "Firmware Updates",
    "title": "Troubleshooting",
    "content": "Update Stuck . If the update appears frozen: . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | Try connecting via USB to a computer | Use the web flasher in recovery/DFU mode | Flash a known-good firmware version | Check the Meshtastic Discord for device-specific recovery steps | . Compatibility Warnings . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | Firmware version | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/firmware.html#troubleshooting",
    
    "relUrl": "/sl-rSI/user/firmware.html#troubleshooting"
  },"1436": {
    "doc": "Firmware Updates",
    "title": "Related Topics",
    "content": ". | Connections — reconnecting after a firmware update | Flashing firmware guide — full firmware flashing walkthrough on meshtastic.org | Supported devices — check firmware compatibility by device | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/firmware.html#related-topics",
    
    "relUrl": "/sl-rSI/user/firmware.html#related-topics"
  },"1437": {
    "doc": "Firmware Updates",
    "title": "Firmware Updates",
    "content": "Keep your Meshtastic radio up to date with the latest firmware for new features, bug fixes, and security improvements. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/firmware.html",
    
    "relUrl": "/no-rNO/user/firmware.html"
  },"1438": {
    "doc": "Firmware Updates",
    "title": "Checking for Updates",
    "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable radios. | The app checks for available firmware versions. | Available updates show the version number and changelog summary. | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/firmware.html#checking-for-updates",
    
    "relUrl": "/no-rNO/user/firmware.html#checking-for-updates"
  },"1439": {
    "doc": "Firmware Updates",
    "title": "Update Methods",
    "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | Wait for the update to complete — do not disconnect during the update. | . Erase device during update . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Wipes the device’s flash completely, then installs the selected firmware from scratch. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. In-App USB Update . When your radio is connected over USB/serial (rather than Bluetooth), the Firmware Update screen offers USB File Transfer. The app reboots the device into DFU mode, then prompts you to save the .uf2 file to the device’s DFU drive using the system file picker. This option appears only on a USB/serial connection — it is not available over Bluetooth. ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. A bootloader supplied as an update-....uf2 can be installed by copying it to the drive; that is how the app’s own bootloader upgrade works. The app surfaces a hint when the serial-only route applies. Factory Erase and Bootloader Upgrade . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. The app reads INFO_UF2.TXT from the drive you select to confirm it really is the device’s update drive and to identify the board before writing anything. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Other Flashing Options . For recovery or when neither OTA nor in-app USB is available: . | Use the Meshtastic Web Flasher | Or the Meshtastic CLI tool on desktop | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/firmware.html#update-methods",
    
    "relUrl": "/no-rNO/user/firmware.html#update-methods"
  },"1440": {
    "doc": "Firmware Updates",
    "title": "Version Channels",
    "content": "| Kanal | Beskrivelse | . | Stable | Recommended for most users; tested releases | . | Alpha | Preview releases; may contain bugs | . | Local File | Flash a firmware file you select yourself, instead of a downloaded release | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/firmware.html#version-channels",
    
    "relUrl": "/no-rNO/user/firmware.html#version-channels"
  },"1441": {
    "doc": "Firmware Updates",
    "title": "Pre-Update Checklist",
    "content": "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 | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/firmware.html#pre-update-checklist",
    
    "relUrl": "/no-rNO/user/firmware.html#pre-update-checklist"
  },"1442": {
    "doc": "Firmware Updates",
    "title": "Post-Update",
    "content": "After the firmware is written, the app verifies the update and waits for the device to come back online: . Once the update succeeds: . | The radio reboots automatically | The Bluetooth connection re-establishes | Verify your settings are intact | Confirm the new version under Currently Installed on the Firmware Update screen — it’s also shown on the node’s detail page and the Connections screen | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/firmware.html#post-update",
    
    "relUrl": "/no-rNO/user/firmware.html#post-update"
  },"1443": {
    "doc": "Firmware Updates",
    "title": "Troubleshooting",
    "content": "Update Stuck . If the update appears frozen: . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | Try connecting via USB to a computer | Use the web flasher in recovery/DFU mode | Flash a known-good firmware version | Check the Meshtastic Discord for device-specific recovery steps | . Compatibility Warnings . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | Firmware version | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/firmware.html#troubleshooting",
    
    "relUrl": "/no-rNO/user/firmware.html#troubleshooting"
  },"1444": {
    "doc": "Firmware Updates",
    "title": "Related Topics",
    "content": ". | Connections — reconnecting after a firmware update | Flashing firmware guide — full firmware flashing walkthrough on meshtastic.org | Supported devices — check firmware compatibility by device | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/firmware.html#related-topics",
    
    "relUrl": "/no-rNO/user/firmware.html#related-topics"
  },"1445": {
    "doc": "Firmware Updates",
    "title": "Firmware Updates",
    "content": "Keep your Meshtastic radio up to date with the latest firmware for new features, bug fixes, and security improvements. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/firmware.html",
    
    "relUrl": "/hu-rHU/user/firmware.html"
  },"1446": {
    "doc": "Firmware Updates",
    "title": "Checking for Updates",
    "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable radios. | The app checks for available firmware versions. | Available updates show the version number and changelog summary. | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/firmware.html#checking-for-updates",
    
    "relUrl": "/hu-rHU/user/firmware.html#checking-for-updates"
  },"1447": {
    "doc": "Firmware Updates",
    "title": "Update Methods",
    "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | Wait for the update to complete — do not disconnect during the update. | . Erase device during update . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Wipes the device’s flash completely, then installs the selected firmware from scratch. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. In-App USB Update . When your radio is connected over USB/serial (rather than Bluetooth), the Firmware Update screen offers USB File Transfer. The app reboots the device into DFU mode, then prompts you to save the .uf2 file to the device’s DFU drive using the system file picker. This option appears only on a USB/serial connection — it is not available over Bluetooth. ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. A bootloader supplied as an update-....uf2 can be installed by copying it to the drive; that is how the app’s own bootloader upgrade works. The app surfaces a hint when the serial-only route applies. Factory Erase and Bootloader Upgrade . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. The app reads INFO_UF2.TXT from the drive you select to confirm it really is the device’s update drive and to identify the board before writing anything. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Other Flashing Options . For recovery or when neither OTA nor in-app USB is available: . | Use the Meshtastic Web Flasher | Or the Meshtastic CLI tool on desktop | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/firmware.html#update-methods",
    
    "relUrl": "/hu-rHU/user/firmware.html#update-methods"
  },"1448": {
    "doc": "Firmware Updates",
    "title": "Version Channels",
    "content": "| Csatorna | Leírás | . | Stable | Recommended for most users; tested releases | . | Alpha | Preview releases; may contain bugs | . | Local File | Flash a firmware file you select yourself, instead of a downloaded release | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/firmware.html#version-channels",
    
    "relUrl": "/hu-rHU/user/firmware.html#version-channels"
  },"1449": {
    "doc": "Firmware Updates",
    "title": "Pre-Update Checklist",
    "content": "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 | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/firmware.html#pre-update-checklist",
    
    "relUrl": "/hu-rHU/user/firmware.html#pre-update-checklist"
  },"1450": {
    "doc": "Firmware Updates",
    "title": "Post-Update",
    "content": "After the firmware is written, the app verifies the update and waits for the device to come back online: . Once the update succeeds: . | The radio reboots automatically | The Bluetooth connection re-establishes | Verify your settings are intact | Confirm the new version under Currently Installed on the Firmware Update screen — it’s also shown on the node’s detail page and the Connections screen | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/firmware.html#post-update",
    
    "relUrl": "/hu-rHU/user/firmware.html#post-update"
  },"1451": {
    "doc": "Firmware Updates",
    "title": "Troubleshooting",
    "content": "Update Stuck . If the update appears frozen: . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | Try connecting via USB to a computer | Use the web flasher in recovery/DFU mode | Flash a known-good firmware version | Check the Meshtastic Discord for device-specific recovery steps | . Compatibility Warnings . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | Firmware version | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/firmware.html#troubleshooting",
    
    "relUrl": "/hu-rHU/user/firmware.html#troubleshooting"
  },"1452": {
    "doc": "Firmware Updates",
    "title": "Related Topics",
    "content": ". | Connections — reconnecting after a firmware update | Flashing firmware guide — full firmware flashing walkthrough on meshtastic.org | Supported devices — check firmware compatibility by device | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/firmware.html#related-topics",
    
    "relUrl": "/hu-rHU/user/firmware.html#related-topics"
  },"1453": {
    "doc": "Обновления прошивки",
    "title": "Обновления прошивки",
    "content": "Поддерживайте своё радио Meshtastic в актуальном состоянии с помощью последней прошивки для получения новых функций, исправлений ошибок и улучшений безопасности. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/firmware.html",
    
    "relUrl": "/ru-rRU/user/firmware.html"
  },"1454": {
    "doc": "Обновления прошивки",
    "title": "Проверка обновлений",
    "content": ". | Откройте конфигурацию подключённого радио и в разделе “Дополнительно” нажмите “Обновление прошивки”. The entry appears only for OTA-capable radios. | Приложение проверяет доступные версии прошивки. | Доступные обновления показывают номер версии и сводку изменений. | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/firmware.html#%D0%BF%D1%80%D0%BE%D0%B2%D0%B5%D1%80%D0%BA%D0%B0-%D0%BE%D0%B1%D0%BD%D0%BE%D0%B2%D0%BB%D0%B5%D0%BD%D0%B8%D0%B9",
    
    "relUrl": "/ru-rRU/user/firmware.html#проверка-обновлений"
  },"1455": {
    "doc": "Обновления прошивки",
    "title": "Методы обновления",
    "content": "OTA (беспроводное обновление) через Bluetooth . Наиболее распространённый способ обновления для пользователей Android: . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | Убедитесь, что твоё радио подключено по Bluetooth. | Перейдите на экран “Обновление прошивки”. | Выберите нужную версию прошивки. | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | Дождитесь завершения обновления — не отключайте устройство во время обновления. | . Очистить устройство при обновлении . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Полностью стирает флэш-память устройства, а затем устанавливает выбранную прошивку с нуля. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. Обновление внутри приложения по USB . Когда твоё радио подключено по USB/serial (а не по Bluetooth), на экране обновления прошивки появляется опция “Передача файла по USB”. Приложение перезагружает устройство в режим DFU, а затем предлагает сохранить файл .uf2 на DFU-диск устройства с помощью системного выбора файлов. Эта опция появляется только при подключении по USB/serial — она недоступна по Bluetooth. ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. Загрузчик, поставляемый в виде update-....uf2, можно установить, скопировав его на диск; именно так работает обновление загрузчика из самого приложения. Приложение показывает подсказку, когда требуется использование последовательного способа. Полное стирание и обновление загрузчика . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. Приложение считывает INFO_UF2.TXT с выбранного тобою диска, чтобы убедиться, что это действительно диск обновления устройства, и определить плату до записи чего-либо. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Другие способы прошивки . Для восстановления или когда ни OTA, ни внутри приложение USB недоступны: . | Используйте Meshtastic Web Flasher | Или инструмент командной строки Meshtastic CLI на компьютере | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/firmware.html#%D0%BC%D0%B5%D1%82%D0%BE%D0%B4%D1%8B-%D0%BE%D0%B1%D0%BD%D0%BE%D0%B2%D0%BB%D0%B5%D0%BD%D0%B8%D1%8F",
    
    "relUrl": "/ru-rRU/user/firmware.html#методы-обновления"
  },"1456": {
    "doc": "Обновления прошивки",
    "title": "Каналы версий",
    "content": "| Канал | Описание | . | Стабильная | Рекомендуется для большинства пользователей; протестированные релизы | . | Альфа | Предварительные релизы; могут содержать ошибки | . | Локальный файл | Прошить файл прошивки, который ты выбираешь сам, вместо загруженного релиза | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/firmware.html#%D0%BA%D0%B0%D0%BD%D0%B0%D0%BB%D1%8B-%D0%B2%D0%B5%D1%80%D1%81%D0%B8%D0%B9",
    
    "relUrl": "/ru-rRU/user/firmware.html#каналы-версий"
  },"1457": {
    "doc": "Обновления прошивки",
    "title": "Предполётная проверка",
    "content": "Перед обновлением: . | Заряд батареи > 50% | Стабильное соединение Bluetooth | Запишите свои текущие настройки (они могут сброситься при смене мажорной версии) | Проверьте примечания к релизу на наличие критических изменений | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/firmware.html#%D0%BF%D1%80%D0%B5%D0%B4%D0%BF%D0%BE%D0%BB%D1%91%D1%82%D0%BD%D0%B0%D1%8F-%D0%BF%D1%80%D0%BE%D0%B2%D0%B5%D1%80%D0%BA%D0%B0",
    
    "relUrl": "/ru-rRU/user/firmware.html#предполётная-проверка"
  },"1458": {
    "doc": "Обновления прошивки",
    "title": "После обновления",
    "content": "После записи прошивки приложение проверяет обновление и ждёт, пока устройство снова станет доступным: . После успешного обновления: . | The radio reboots automatically | The Bluetooth connection re-establishes | Убедись, что твои настройки сохранились | Проверьте новую версию в разделе “Установленная версия” на экране обновления прошивки — она также отображается на странице сведений о ноде и на экране “Подключения” | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/firmware.html#%D0%BF%D0%BE%D1%81%D0%BB%D0%B5-%D0%BE%D0%B1%D0%BD%D0%BE%D0%B2%D0%BB%D0%B5%D0%BD%D0%B8%D1%8F",
    
    "relUrl": "/ru-rRU/user/firmware.html#после-обновления"
  },"1459": {
    "doc": "Обновления прошивки",
    "title": "Устранение неполадок",
    "content": "Обновление зависло . Если обновление кажется зависшим: . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | Попробуйте подключиться по USB к компьютеру | Используйте Web Flasher в режиме восстановления/DFU | Прошивайте заведомо рабочую версию прошивки | Обратитесь к Discord-серверу Meshtastic для получения инструкций по восстановлению, специфичных для твоего устройства | . Предупреждения о совместимости . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | Версия прошивки | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/firmware.html#%D1%83%D1%81%D1%82%D1%80%D0%B0%D0%BD%D0%B5%D0%BD%D0%B8%D0%B5-%D0%BD%D0%B5%D0%BF%D0%BE%D0%BB%D0%B0%D0%B4%D0%BE%D0%BA",
    
    "relUrl": "/ru-rRU/user/firmware.html#устранение-неполадок"
  },"1460": {
    "doc": "Обновления прошивки",
    "title": "Связанные темы",
    "content": ". | Подключения — восстановление соединения после обновления прошивки | Руководство по прошивке— полное пошаговое руководство по полной прошивке на meshtastic.org | Поддерживаемые устройства — проверьте совместимость прошивки с устройством | FAQ — общие вопросы на meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/firmware.html#%D1%81%D0%B2%D1%8F%D0%B7%D0%B0%D0%BD%D0%BD%D1%8B%D0%B5-%D1%82%D0%B5%D0%BC%D1%8B",
    
    "relUrl": "/ru-rRU/user/firmware.html#связанные-темы"
  },"1461": {
    "doc": "Aktualizace firmware",
    "title": "Aktualizace firmware",
    "content": "Keep your Meshtastic radio up to date with the latest firmware for new features, bug fixes, and security improvements. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/firmware.html",
    
    "relUrl": "/cs-rCZ/user/firmware.html"
  },"1462": {
    "doc": "Aktualizace firmware",
    "title": "Checking for Updates",
    "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable radios. | The app checks for available firmware versions. | Available updates show the version number and changelog summary. | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/firmware.html#checking-for-updates",
    
    "relUrl": "/cs-rCZ/user/firmware.html#checking-for-updates"
  },"1463": {
    "doc": "Aktualizace firmware",
    "title": "Update Methods",
    "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | Wait for the update to complete — do not disconnect during the update. | . Vymazat zařízení během aktualizace . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Úplně vymaže paměť zařízení a poté od začátku nainstaluje vybraný firmware. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. In-App USB Update . When your radio is connected over USB/serial (rather than Bluetooth), the Firmware Update screen offers USB File Transfer. The app reboots the device into DFU mode, then prompts you to save the .uf2 file to the device’s DFU drive using the system file picker. This option appears only on a USB/serial connection — it is not available over Bluetooth. ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. A bootloader supplied as an update-....uf2 can be installed by copying it to the drive; that is how the app’s own bootloader upgrade works. The app surfaces a hint when the serial-only route applies. Factory Erase and Bootloader Upgrade . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. The app reads INFO_UF2.TXT from the drive you select to confirm it really is the device’s update drive and to identify the board before writing anything. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Other Flashing Options . For recovery or when neither OTA nor in-app USB is available: . | Use the Meshtastic Web Flasher | Or the Meshtastic CLI tool on desktop | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/firmware.html#update-methods",
    
    "relUrl": "/cs-rCZ/user/firmware.html#update-methods"
  },"1464": {
    "doc": "Aktualizace firmware",
    "title": "Version Channels",
    "content": "| Kanál | Popis | . | Stabilní | Recommended for most users; tested releases | . | Alfa | Preview releases; may contain bugs | . | Lokální soubor | Flash a firmware file you select yourself, instead of a downloaded release | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/firmware.html#version-channels",
    
    "relUrl": "/cs-rCZ/user/firmware.html#version-channels"
  },"1465": {
    "doc": "Aktualizace firmware",
    "title": "Pre-Update Checklist",
    "content": "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 | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/firmware.html#pre-update-checklist",
    
    "relUrl": "/cs-rCZ/user/firmware.html#pre-update-checklist"
  },"1466": {
    "doc": "Aktualizace firmware",
    "title": "Post-Update",
    "content": "After the firmware is written, the app verifies the update and waits for the device to come back online: . Once the update succeeds: . | The radio reboots automatically | The Bluetooth connection re-establishes | Verify your settings are intact | Confirm the new version under Currently Installed on the Firmware Update screen — it’s also shown on the node’s detail page and the Connections screen | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/firmware.html#post-update",
    
    "relUrl": "/cs-rCZ/user/firmware.html#post-update"
  },"1467": {
    "doc": "Aktualizace firmware",
    "title": "Troubleshooting",
    "content": "Update Stuck . If the update appears frozen: . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | Try connecting via USB to a computer | Use the web flasher in recovery/DFU mode | Flash a known-good firmware version | Check the Meshtastic Discord for device-specific recovery steps | . Compatibility Warnings . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | Verze firmwaru | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/firmware.html#troubleshooting",
    
    "relUrl": "/cs-rCZ/user/firmware.html#troubleshooting"
  },"1468": {
    "doc": "Aktualizace firmware",
    "title": "Související témata",
    "content": ". | Connections — reconnecting after a firmware update | Flashing firmware guide — full firmware flashing walkthrough on meshtastic.org | Supported devices — check firmware compatibility by device | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/firmware.html#souvisej%C3%ADc%C3%AD-t%C3%A9mata",
    
    "relUrl": "/cs-rCZ/user/firmware.html#související-témata"
  },"1469": {
    "doc": "Актуализации на фърмуера",
    "title": "Актуализации на фърмуера",
    "content": "Поддържайте вашето Meshtastic радио актуално с най-новия фърмуер за нови функции, корекции на грешки и подобрения в сигурността. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/firmware.html",
    
    "relUrl": "/bg-rBG/user/firmware.html"
  },"1470": {
    "doc": "Актуализации на фърмуера",
    "title": "Проверка за актуализации",
    "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable radios. | Приложението проверява за налични версии на фърмуера. | Available updates show the version number and changelog summary. | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/firmware.html#%D0%BF%D1%80%D0%BE%D0%B2%D0%B5%D1%80%D0%BA%D0%B0-%D0%B7%D0%B0-%D0%B0%D0%BA%D1%82%D1%83%D0%B0%D0%BB%D0%B8%D0%B7%D0%B0%D1%86%D0%B8%D0%B8",
    
    "relUrl": "/bg-rBG/user/firmware.html#проверка-за-актуализации"
  },"1471": {
    "doc": "Актуализации на фърмуера",
    "title": "Методи за актуализиране",
    "content": "OTA (Over-The-Air) чрез Bluetooth . Най-често срещаният метод за актуализиране за потребителите на Android: . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | Уверете се, че радиото ви е свързано чрез Bluetooth. | Отидете до екрана за актуализация на фърмуера. | Изберете желаната версия на фърмуера. | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | Wait for the update to complete — do not disconnect during the update. | . Erase device during update . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Wipes the device’s flash completely, then installs the selected firmware from scratch. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. In-App USB Update . When your radio is connected over USB/serial (rather than Bluetooth), the Firmware Update screen offers USB File Transfer. The app reboots the device into DFU mode, then prompts you to save the .uf2 file to the device’s DFU drive using the system file picker. This option appears only on a USB/serial connection — it is not available over Bluetooth. ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. A bootloader supplied as an update-....uf2 can be installed by copying it to the drive; that is how the app’s own bootloader upgrade works. The app surfaces a hint when the serial-only route applies. Factory Erase and Bootloader Upgrade . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. The app reads INFO_UF2.TXT from the drive you select to confirm it really is the device’s update drive and to identify the board before writing anything. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Other Flashing Options . For recovery or when neither OTA nor in-app USB is available: . | Use the Meshtastic Web Flasher | Or the Meshtastic CLI tool on desktop | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/firmware.html#%D0%BC%D0%B5%D1%82%D0%BE%D0%B4%D0%B8-%D0%B7%D0%B0-%D0%B0%D0%BA%D1%82%D1%83%D0%B0%D0%BB%D0%B8%D0%B7%D0%B8%D1%80%D0%B0%D0%BD%D0%B5",
    
    "relUrl": "/bg-rBG/user/firmware.html#методи-за-актуализиране"
  },"1472": {
    "doc": "Актуализации на фърмуера",
    "title": "Канали на версиите",
    "content": "| Канал | Описание | . | Стабилен | Препоръчва се за повечето потребители; тествани версии | . | Алфа | Предварителни издания; може да съдържат грешки | . | Локален файл | Flash a firmware file you select yourself, instead of a downloaded release | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/firmware.html#%D0%BA%D0%B0%D0%BD%D0%B0%D0%BB%D0%B8-%D0%BD%D0%B0-%D0%B2%D0%B5%D1%80%D1%81%D0%B8%D0%B8%D1%82%D0%B5",
    
    "relUrl": "/bg-rBG/user/firmware.html#канали-на-версиите"
  },"1473": {
    "doc": "Актуализации на фърмуера",
    "title": "Контролен списък преди актуализация",
    "content": "Преди актуализиране: . | Батерия > 50% | Стабилна Bluetooth връзка | Запишете текущите си настройки (те могат да се нулират при големи промени във версията) | Проверете бележките към изданието за важни промени | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/firmware.html#%D0%BA%D0%BE%D0%BD%D1%82%D1%80%D0%BE%D0%BB%D0%B5%D0%BD-%D1%81%D0%BF%D0%B8%D1%81%D1%8A%D0%BA-%D0%BF%D1%80%D0%B5%D0%B4%D0%B8-%D0%B0%D0%BA%D1%82%D1%83%D0%B0%D0%BB%D0%B8%D0%B7%D0%B0%D1%86%D0%B8%D1%8F",
    
    "relUrl": "/bg-rBG/user/firmware.html#контролен-списък-преди-актуализация"
  },"1474": {
    "doc": "Актуализации на фърмуера",
    "title": "След актуализация",
    "content": "After the firmware is written, the app verifies the update and waits for the device to come back online: . След като актуализацията е успешна: . | The radio reboots automatically | The Bluetooth connection re-establishes | Проверете дали настройките ви са непокътнати | Confirm the new version under Currently Installed on the Firmware Update screen — it’s also shown on the node’s detail page and the Connections screen | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/firmware.html#%D1%81%D0%BB%D0%B5%D0%B4-%D0%B0%D0%BA%D1%82%D1%83%D0%B0%D0%BB%D0%B8%D0%B7%D0%B0%D1%86%D0%B8%D1%8F",
    
    "relUrl": "/bg-rBG/user/firmware.html#след-актуализация"
  },"1475": {
    "doc": "Актуализации на фърмуера",
    "title": "Отстраняване на неизправности",
    "content": "Update Stuck . If the update appears frozen: . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | Try connecting via USB to a computer | Use the web flasher in recovery/DFU mode | Flash a known-good firmware version | Check the Meshtastic Discord for device-specific recovery steps | . Предупреждения за съвместимост . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | Версия на фърмуера | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/firmware.html#%D0%BE%D1%82%D1%81%D1%82%D1%80%D0%B0%D0%BD%D1%8F%D0%B2%D0%B0%D0%BD%D0%B5-%D0%BD%D0%B0-%D0%BD%D0%B5%D0%B8%D0%B7%D0%BF%D1%80%D0%B0%D0%B2%D0%BD%D0%BE%D1%81%D1%82%D0%B8",
    
    "relUrl": "/bg-rBG/user/firmware.html#отстраняване-на-неизправности"
  },"1476": {
    "doc": "Актуализации на фърмуера",
    "title": "Свързани теми",
    "content": ". | Connections — reconnecting after a firmware update | Flashing firmware guide — full firmware flashing walkthrough on meshtastic.org | Supported devices — check firmware compatibility by device | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/firmware.html#%D1%81%D0%B2%D1%8A%D1%80%D0%B7%D0%B0%D0%BD%D0%B8-%D1%82%D0%B5%D0%BC%D0%B8",
    
    "relUrl": "/bg-rBG/user/firmware.html#свързани-теми"
  },"1477": {
    "doc": "Firmware Updates",
    "title": "Firmware Updates",
    "content": "Keep your Meshtastic radio up to date with the latest firmware for new features, bug fixes, and security improvements. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/firmware.html",
    
    "relUrl": "/ga-rIE/user/firmware.html"
  },"1478": {
    "doc": "Firmware Updates",
    "title": "Checking for Updates",
    "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable radios. | The app checks for available firmware versions. | Available updates show the version number and changelog summary. | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/firmware.html#checking-for-updates",
    
    "relUrl": "/ga-rIE/user/firmware.html#checking-for-updates"
  },"1479": {
    "doc": "Firmware Updates",
    "title": "Update Methods",
    "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | Wait for the update to complete — do not disconnect during the update. | . Erase device during update . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Wipes the device’s flash completely, then installs the selected firmware from scratch. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. In-App USB Update . When your radio is connected over USB/serial (rather than Bluetooth), the Firmware Update screen offers USB File Transfer. The app reboots the device into DFU mode, then prompts you to save the .uf2 file to the device’s DFU drive using the system file picker. This option appears only on a USB/serial connection — it is not available over Bluetooth. ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. A bootloader supplied as an update-....uf2 can be installed by copying it to the drive; that is how the app’s own bootloader upgrade works. The app surfaces a hint when the serial-only route applies. Factory Erase and Bootloader Upgrade . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. The app reads INFO_UF2.TXT from the drive you select to confirm it really is the device’s update drive and to identify the board before writing anything. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Other Flashing Options . For recovery or when neither OTA nor in-app USB is available: . | Use the Meshtastic Web Flasher | Or the Meshtastic CLI tool on desktop | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/firmware.html#update-methods",
    
    "relUrl": "/ga-rIE/user/firmware.html#update-methods"
  },"1480": {
    "doc": "Firmware Updates",
    "title": "Version Channels",
    "content": "| Cainéal | Cur síos | . | Stable | Recommended for most users; tested releases | . | Alpha | Preview releases; may contain bugs | . | Local File | Flash a firmware file you select yourself, instead of a downloaded release | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/firmware.html#version-channels",
    
    "relUrl": "/ga-rIE/user/firmware.html#version-channels"
  },"1481": {
    "doc": "Firmware Updates",
    "title": "Pre-Update Checklist",
    "content": "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 | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/firmware.html#pre-update-checklist",
    
    "relUrl": "/ga-rIE/user/firmware.html#pre-update-checklist"
  },"1482": {
    "doc": "Firmware Updates",
    "title": "Post-Update",
    "content": "After the firmware is written, the app verifies the update and waits for the device to come back online: . Once the update succeeds: . | The radio reboots automatically | The Bluetooth connection re-establishes | Verify your settings are intact | Confirm the new version under Currently Installed on the Firmware Update screen — it’s also shown on the node’s detail page and the Connections screen | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/firmware.html#post-update",
    
    "relUrl": "/ga-rIE/user/firmware.html#post-update"
  },"1483": {
    "doc": "Firmware Updates",
    "title": "Troubleshooting",
    "content": "Update Stuck . If the update appears frozen: . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | Try connecting via USB to a computer | Use the web flasher in recovery/DFU mode | Flash a known-good firmware version | Check the Meshtastic Discord for device-specific recovery steps | . Compatibility Warnings . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | Firmware version | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/firmware.html#troubleshooting",
    
    "relUrl": "/ga-rIE/user/firmware.html#troubleshooting"
  },"1484": {
    "doc": "Firmware Updates",
    "title": "Related Topics",
    "content": ". | Connections — reconnecting after a firmware update | Flashing firmware guide — full firmware flashing walkthrough on meshtastic.org | Supported devices — check firmware compatibility by device | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/firmware.html#related-topics",
    
    "relUrl": "/ga-rIE/user/firmware.html#related-topics"
  },"1485": {
    "doc": "Firmware Updates",
    "title": "Firmware Updates",
    "content": "Keep your Meshtastic radio up to date with the latest firmware for new features, bug fixes, and security improvements. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/firmware.html",
    
    "relUrl": "/fr-rCA/user/firmware.html"
  },"1486": {
    "doc": "Firmware Updates",
    "title": "Checking for Updates",
    "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable radios. | The app checks for available firmware versions. | Available updates show the version number and changelog summary. | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/firmware.html#checking-for-updates",
    
    "relUrl": "/fr-rCA/user/firmware.html#checking-for-updates"
  },"1487": {
    "doc": "Firmware Updates",
    "title": "Update Methods",
    "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | Wait for the update to complete — do not disconnect during the update. | . Erase device during update . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Wipes the device’s flash completely, then installs the selected firmware from scratch. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. In-App USB Update . When your radio is connected over USB/serial (rather than Bluetooth), the Firmware Update screen offers USB File Transfer. The app reboots the device into DFU mode, then prompts you to save the .uf2 file to the device’s DFU drive using the system file picker. This option appears only on a USB/serial connection — it is not available over Bluetooth. ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. A bootloader supplied as an update-....uf2 can be installed by copying it to the drive; that is how the app’s own bootloader upgrade works. The app surfaces a hint when the serial-only route applies. Factory Erase and Bootloader Upgrade . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. The app reads INFO_UF2.TXT from the drive you select to confirm it really is the device’s update drive and to identify the board before writing anything. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Other Flashing Options . For recovery or when neither OTA nor in-app USB is available: . | Use the Meshtastic Web Flasher | Or the Meshtastic CLI tool on desktop | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/firmware.html#update-methods",
    
    "relUrl": "/fr-rCA/user/firmware.html#update-methods"
  },"1488": {
    "doc": "Firmware Updates",
    "title": "Version Channels",
    "content": "| Canal | Description | . | Stable | Recommended for most users; tested releases | . | Alpha | Preview releases; may contain bugs | . | Fichier local | Flash a firmware file you select yourself, instead of a downloaded release | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/firmware.html#version-channels",
    
    "relUrl": "/fr-rCA/user/firmware.html#version-channels"
  },"1489": {
    "doc": "Firmware Updates",
    "title": "Pre-Update Checklist",
    "content": "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 | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/firmware.html#pre-update-checklist",
    
    "relUrl": "/fr-rCA/user/firmware.html#pre-update-checklist"
  },"1490": {
    "doc": "Firmware Updates",
    "title": "Post-Update",
    "content": "After the firmware is written, the app verifies the update and waits for the device to come back online: . Once the update succeeds: . | The radio reboots automatically | The Bluetooth connection re-establishes | Verify your settings are intact | Confirm the new version under Currently Installed on the Firmware Update screen — it’s also shown on the node’s detail page and the Connections screen | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/firmware.html#post-update",
    
    "relUrl": "/fr-rCA/user/firmware.html#post-update"
  },"1491": {
    "doc": "Firmware Updates",
    "title": "Troubleshooting",
    "content": "Update Stuck . If the update appears frozen: . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | Try connecting via USB to a computer | Use the web flasher in recovery/DFU mode | Flash a known-good firmware version | Check the Meshtastic Discord for device-specific recovery steps | . Compatibility Warnings . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | Version du microprogramme | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/firmware.html#troubleshooting",
    
    "relUrl": "/fr-rCA/user/firmware.html#troubleshooting"
  },"1492": {
    "doc": "Firmware Updates",
    "title": "Related Topics",
    "content": ". | Connections — reconnecting after a firmware update | Flashing firmware guide — full firmware flashing walkthrough on meshtastic.org | Supported devices — check firmware compatibility by device | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/firmware.html#related-topics",
    
    "relUrl": "/fr-rCA/user/firmware.html#related-topics"
  },"1493": {
    "doc": "Ажурирања фирмвера",
    "title": "Ажурирања фирмвера",
    "content": "Keep your Meshtastic radio up to date with the latest firmware for new features, bug fixes, and security improvements. ",
    "url": "/Meshtastic-Android/main/srp/user/firmware.html",
    
    "relUrl": "/srp/user/firmware.html"
  },"1494": {
    "doc": "Ажурирања фирмвера",
    "title": "Checking for Updates",
    "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable radios. | The app checks for available firmware versions. | Available updates show the version number and changelog summary. | . ",
    "url": "/Meshtastic-Android/main/srp/user/firmware.html#checking-for-updates",
    
    "relUrl": "/srp/user/firmware.html#checking-for-updates"
  },"1495": {
    "doc": "Ажурирања фирмвера",
    "title": "Update Methods",
    "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | Wait for the update to complete — do not disconnect during the update. | . Erase device during update . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Wipes the device’s flash completely, then installs the selected firmware from scratch. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. In-App USB Update . When your radio is connected over USB/serial (rather than Bluetooth), the Firmware Update screen offers USB File Transfer. The app reboots the device into DFU mode, then prompts you to save the .uf2 file to the device’s DFU drive using the system file picker. This option appears only on a USB/serial connection — it is not available over Bluetooth. ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. A bootloader supplied as an update-....uf2 can be installed by copying it to the drive; that is how the app’s own bootloader upgrade works. The app surfaces a hint when the serial-only route applies. Factory Erase and Bootloader Upgrade . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. The app reads INFO_UF2.TXT from the drive you select to confirm it really is the device’s update drive and to identify the board before writing anything. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Other Flashing Options . For recovery or when neither OTA nor in-app USB is available: . | Use the Meshtastic Web Flasher | Or the Meshtastic CLI tool on desktop | . ",
    "url": "/Meshtastic-Android/main/srp/user/firmware.html#update-methods",
    
    "relUrl": "/srp/user/firmware.html#update-methods"
  },"1496": {
    "doc": "Ажурирања фирмвера",
    "title": "Version Channels",
    "content": "| Канал | Опис | . | Stable | Recommended for most users; tested releases | . | Alpha | Preview releases; may contain bugs | . | Local File | Flash a firmware file you select yourself, instead of a downloaded release | . ",
    "url": "/Meshtastic-Android/main/srp/user/firmware.html#version-channels",
    
    "relUrl": "/srp/user/firmware.html#version-channels"
  },"1497": {
    "doc": "Ажурирања фирмвера",
    "title": "Pre-Update Checklist",
    "content": "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 | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/srp/user/firmware.html#pre-update-checklist",
    
    "relUrl": "/srp/user/firmware.html#pre-update-checklist"
  },"1498": {
    "doc": "Ажурирања фирмвера",
    "title": "Post-Update",
    "content": "After the firmware is written, the app verifies the update and waits for the device to come back online: . Once the update succeeds: . | The radio reboots automatically | The Bluetooth connection re-establishes | Verify your settings are intact | Confirm the new version under Currently Installed on the Firmware Update screen — it’s also shown on the node’s detail page and the Connections screen | . ",
    "url": "/Meshtastic-Android/main/srp/user/firmware.html#post-update",
    
    "relUrl": "/srp/user/firmware.html#post-update"
  },"1499": {
    "doc": "Ажурирања фирмвера",
    "title": "Troubleshooting",
    "content": "Update Stuck . If the update appears frozen: . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | Try connecting via USB to a computer | Use the web flasher in recovery/DFU mode | Flash a known-good firmware version | Check the Meshtastic Discord for device-specific recovery steps | . Compatibility Warnings . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | Firmware version | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/srp/user/firmware.html#troubleshooting",
    
    "relUrl": "/srp/user/firmware.html#troubleshooting"
  },"1500": {
    "doc": "Ажурирања фирмвера",
    "title": "Related Topics",
    "content": ". | Connections — reconnecting after a firmware update | Flashing firmware guide — full firmware flashing walkthrough on meshtastic.org | Supported devices — check firmware compatibility by device | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/srp/user/firmware.html#related-topics",
    
    "relUrl": "/srp/user/firmware.html#related-topics"
  },"1501": {
    "doc": "Firmware Updates",
    "title": "Firmware Updates",
    "content": "Keep your Meshtastic radio up to date with the latest firmware for new features, bug fixes, and security improvements. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/firmware.html",
    
    "relUrl": "/ca-rES/user/firmware.html"
  },"1502": {
    "doc": "Firmware Updates",
    "title": "Checking for Updates",
    "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable radios. | The app checks for available firmware versions. | Available updates show the version number and changelog summary. | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/firmware.html#checking-for-updates",
    
    "relUrl": "/ca-rES/user/firmware.html#checking-for-updates"
  },"1503": {
    "doc": "Firmware Updates",
    "title": "Update Methods",
    "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | Wait for the update to complete — do not disconnect during the update. | . Erase device during update . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Wipes the device’s flash completely, then installs the selected firmware from scratch. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. In-App USB Update . When your radio is connected over USB/serial (rather than Bluetooth), the Firmware Update screen offers USB File Transfer. The app reboots the device into DFU mode, then prompts you to save the .uf2 file to the device’s DFU drive using the system file picker. This option appears only on a USB/serial connection — it is not available over Bluetooth. ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. A bootloader supplied as an update-....uf2 can be installed by copying it to the drive; that is how the app’s own bootloader upgrade works. The app surfaces a hint when the serial-only route applies. Factory Erase and Bootloader Upgrade . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. The app reads INFO_UF2.TXT from the drive you select to confirm it really is the device’s update drive and to identify the board before writing anything. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Other Flashing Options . For recovery or when neither OTA nor in-app USB is available: . | Use the Meshtastic Web Flasher | Or the Meshtastic CLI tool on desktop | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/firmware.html#update-methods",
    
    "relUrl": "/ca-rES/user/firmware.html#update-methods"
  },"1504": {
    "doc": "Firmware Updates",
    "title": "Version Channels",
    "content": "| Canal | Descripció | . | Stable | Recommended for most users; tested releases | . | Alpha | Preview releases; may contain bugs | . | Local File | Flash a firmware file you select yourself, instead of a downloaded release | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/firmware.html#version-channels",
    
    "relUrl": "/ca-rES/user/firmware.html#version-channels"
  },"1505": {
    "doc": "Firmware Updates",
    "title": "Pre-Update Checklist",
    "content": "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 | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/firmware.html#pre-update-checklist",
    
    "relUrl": "/ca-rES/user/firmware.html#pre-update-checklist"
  },"1506": {
    "doc": "Firmware Updates",
    "title": "Post-Update",
    "content": "After the firmware is written, the app verifies the update and waits for the device to come back online: . Once the update succeeds: . | The radio reboots automatically | The Bluetooth connection re-establishes | Verify your settings are intact | Confirm the new version under Currently Installed on the Firmware Update screen — it’s also shown on the node’s detail page and the Connections screen | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/firmware.html#post-update",
    
    "relUrl": "/ca-rES/user/firmware.html#post-update"
  },"1507": {
    "doc": "Firmware Updates",
    "title": "Troubleshooting",
    "content": "Update Stuck . If the update appears frozen: . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | Try connecting via USB to a computer | Use the web flasher in recovery/DFU mode | Flash a known-good firmware version | Check the Meshtastic Discord for device-specific recovery steps | . Compatibility Warnings . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | Firmware version | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/firmware.html#troubleshooting",
    
    "relUrl": "/ca-rES/user/firmware.html#troubleshooting"
  },"1508": {
    "doc": "Firmware Updates",
    "title": "Related Topics",
    "content": ". | Connections — reconnecting after a firmware update | Flashing firmware guide — full firmware flashing walkthrough on meshtastic.org | Supported devices — check firmware compatibility by device | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/firmware.html#related-topics",
    
    "relUrl": "/ca-rES/user/firmware.html#related-topics"
  },"1509": {
    "doc": "Firmware Updates",
    "title": "Firmware Updates",
    "content": "Keep your Meshtastic radio up to date with the latest firmware for new features, bug fixes, and security improvements. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/firmware.html",
    
    "relUrl": "/ko-rKR/user/firmware.html"
  },"1510": {
    "doc": "Firmware Updates",
    "title": "Checking for Updates",
    "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable radios. | The app checks for available firmware versions. | Available updates show the version number and changelog summary. | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/firmware.html#checking-for-updates",
    
    "relUrl": "/ko-rKR/user/firmware.html#checking-for-updates"
  },"1511": {
    "doc": "Firmware Updates",
    "title": "Update Methods",
    "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | Wait for the update to complete — do not disconnect during the update. | . Erase device during update . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Wipes the device’s flash completely, then installs the selected firmware from scratch. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. In-App USB Update . When your radio is connected over USB/serial (rather than Bluetooth), the Firmware Update screen offers USB File Transfer. The app reboots the device into DFU mode, then prompts you to save the .uf2 file to the device’s DFU drive using the system file picker. This option appears only on a USB/serial connection — it is not available over Bluetooth. ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. A bootloader supplied as an update-....uf2 can be installed by copying it to the drive; that is how the app’s own bootloader upgrade works. The app surfaces a hint when the serial-only route applies. Factory Erase and Bootloader Upgrade . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. The app reads INFO_UF2.TXT from the drive you select to confirm it really is the device’s update drive and to identify the board before writing anything. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Other Flashing Options . For recovery or when neither OTA nor in-app USB is available: . | Use the Meshtastic Web Flasher | Or the Meshtastic CLI tool on desktop | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/firmware.html#update-methods",
    
    "relUrl": "/ko-rKR/user/firmware.html#update-methods"
  },"1512": {
    "doc": "Firmware Updates",
    "title": "Version Channels",
    "content": "| 채널 | 설명 | . | Stable | Recommended for most users; tested releases | . | Alpha | Preview releases; may contain bugs | . | Local File | Flash a firmware file you select yourself, instead of a downloaded release | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/firmware.html#version-channels",
    
    "relUrl": "/ko-rKR/user/firmware.html#version-channels"
  },"1513": {
    "doc": "Firmware Updates",
    "title": "Pre-Update Checklist",
    "content": "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 | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/firmware.html#pre-update-checklist",
    
    "relUrl": "/ko-rKR/user/firmware.html#pre-update-checklist"
  },"1514": {
    "doc": "Firmware Updates",
    "title": "Post-Update",
    "content": "After the firmware is written, the app verifies the update and waits for the device to come back online: . Once the update succeeds: . | The radio reboots automatically | The Bluetooth connection re-establishes | Verify your settings are intact | Confirm the new version under Currently Installed on the Firmware Update screen — it’s also shown on the node’s detail page and the Connections screen | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/firmware.html#post-update",
    
    "relUrl": "/ko-rKR/user/firmware.html#post-update"
  },"1515": {
    "doc": "Firmware Updates",
    "title": "Troubleshooting",
    "content": "Update Stuck . If the update appears frozen: . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | Try connecting via USB to a computer | Use the web flasher in recovery/DFU mode | Flash a known-good firmware version | Check the Meshtastic Discord for device-specific recovery steps | . Compatibility Warnings . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | 펌웨어 버전 | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/firmware.html#troubleshooting",
    
    "relUrl": "/ko-rKR/user/firmware.html#troubleshooting"
  },"1516": {
    "doc": "Firmware Updates",
    "title": "Related Topics",
    "content": ". | Connections — reconnecting after a firmware update | Flashing firmware guide — full firmware flashing walkthrough on meshtastic.org | Supported devices — check firmware compatibility by device | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/firmware.html#related-topics",
    
    "relUrl": "/ko-rKR/user/firmware.html#related-topics"
  },"1517": {
    "doc": "Firmware Updates",
    "title": "Firmware Updates",
    "content": "Keep your Meshtastic radio up to date with the latest firmware for new features, bug fixes, and security improvements. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/firmware.html",
    
    "relUrl": "/sv-rSE/user/firmware.html"
  },"1518": {
    "doc": "Firmware Updates",
    "title": "Checking for Updates",
    "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable radios. | The app checks for available firmware versions. | Available updates show the version number and changelog summary. | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/firmware.html#checking-for-updates",
    
    "relUrl": "/sv-rSE/user/firmware.html#checking-for-updates"
  },"1519": {
    "doc": "Firmware Updates",
    "title": "Update Methods",
    "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | Wait for the update to complete — do not disconnect during the update. | . Erase device during update . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Wipes the device’s flash completely, then installs the selected firmware from scratch. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. In-App USB Update . When your radio is connected over USB/serial (rather than Bluetooth), the Firmware Update screen offers USB File Transfer. The app reboots the device into DFU mode, then prompts you to save the .uf2 file to the device’s DFU drive using the system file picker. This option appears only on a USB/serial connection — it is not available over Bluetooth. ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. A bootloader supplied as an update-....uf2 can be installed by copying it to the drive; that is how the app’s own bootloader upgrade works. The app surfaces a hint when the serial-only route applies. Factory Erase and Bootloader Upgrade . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. The app reads INFO_UF2.TXT from the drive you select to confirm it really is the device’s update drive and to identify the board before writing anything. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Other Flashing Options . For recovery or when neither OTA nor in-app USB is available: . | Use the Meshtastic Web Flasher | Or the Meshtastic CLI tool on desktop | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/firmware.html#update-methods",
    
    "relUrl": "/sv-rSE/user/firmware.html#update-methods"
  },"1520": {
    "doc": "Firmware Updates",
    "title": "Version Channels",
    "content": "| Kanal | Beskrivning | . | Stabil version | Recommended for most users; tested releases | . | Alfa | Preview releases; may contain bugs | . | Lokal fil | Flash a firmware file you select yourself, instead of a downloaded release | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/firmware.html#version-channels",
    
    "relUrl": "/sv-rSE/user/firmware.html#version-channels"
  },"1521": {
    "doc": "Firmware Updates",
    "title": "Pre-Update Checklist",
    "content": "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 | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/firmware.html#pre-update-checklist",
    
    "relUrl": "/sv-rSE/user/firmware.html#pre-update-checklist"
  },"1522": {
    "doc": "Firmware Updates",
    "title": "Post-Update",
    "content": "After the firmware is written, the app verifies the update and waits for the device to come back online: . Once the update succeeds: . | The radio reboots automatically | The Bluetooth connection re-establishes | Verify your settings are intact | Confirm the new version under Currently Installed on the Firmware Update screen — it’s also shown on the node’s detail page and the Connections screen | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/firmware.html#post-update",
    
    "relUrl": "/sv-rSE/user/firmware.html#post-update"
  },"1523": {
    "doc": "Firmware Updates",
    "title": "Felsökning",
    "content": "Update Stuck . If the update appears frozen: . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | Try connecting via USB to a computer | Use the web flasher in recovery/DFU mode | Flash a known-good firmware version | Check the Meshtastic Discord for device-specific recovery steps | . Compatibility Warnings . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | Firmware version | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/firmware.html#fels%C3%B6kning",
    
    "relUrl": "/sv-rSE/user/firmware.html#felsökning"
  },"1524": {
    "doc": "Firmware Updates",
    "title": "Related Topics",
    "content": ". | Connections — reconnecting after a firmware update | Flashing firmware guide — full firmware flashing walkthrough on meshtastic.org | Supported devices — check firmware compatibility by device | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/firmware.html#related-topics",
    
    "relUrl": "/sv-rSE/user/firmware.html#related-topics"
  },"1525": {
    "doc": "Firmware Updates",
    "title": "Firmware Updates",
    "content": "Keep your Meshtastic radio up to date with the latest firmware for new features, bug fixes, and security improvements. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/firmware.html",
    
    "relUrl": "/ht-rHT/user/firmware.html"
  },"1526": {
    "doc": "Firmware Updates",
    "title": "Checking for Updates",
    "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable radios. | The app checks for available firmware versions. | Available updates show the version number and changelog summary. | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/firmware.html#checking-for-updates",
    
    "relUrl": "/ht-rHT/user/firmware.html#checking-for-updates"
  },"1527": {
    "doc": "Firmware Updates",
    "title": "Update Methods",
    "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | Wait for the update to complete — do not disconnect during the update. | . Erase device during update . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Wipes the device’s flash completely, then installs the selected firmware from scratch. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. In-App USB Update . When your radio is connected over USB/serial (rather than Bluetooth), the Firmware Update screen offers USB File Transfer. The app reboots the device into DFU mode, then prompts you to save the .uf2 file to the device’s DFU drive using the system file picker. This option appears only on a USB/serial connection — it is not available over Bluetooth. ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. A bootloader supplied as an update-....uf2 can be installed by copying it to the drive; that is how the app’s own bootloader upgrade works. The app surfaces a hint when the serial-only route applies. Factory Erase and Bootloader Upgrade . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. The app reads INFO_UF2.TXT from the drive you select to confirm it really is the device’s update drive and to identify the board before writing anything. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Other Flashing Options . For recovery or when neither OTA nor in-app USB is available: . | Use the Meshtastic Web Flasher | Or the Meshtastic CLI tool on desktop | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/firmware.html#update-methods",
    
    "relUrl": "/ht-rHT/user/firmware.html#update-methods"
  },"1528": {
    "doc": "Firmware Updates",
    "title": "Version Channels",
    "content": "| kanal | Deskripsyon | . | Stable | Recommended for most users; tested releases | . | Alpha | Preview releases; may contain bugs | . | Local File | Flash a firmware file you select yourself, instead of a downloaded release | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/firmware.html#version-channels",
    
    "relUrl": "/ht-rHT/user/firmware.html#version-channels"
  },"1529": {
    "doc": "Firmware Updates",
    "title": "Pre-Update Checklist",
    "content": "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 | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/firmware.html#pre-update-checklist",
    
    "relUrl": "/ht-rHT/user/firmware.html#pre-update-checklist"
  },"1530": {
    "doc": "Firmware Updates",
    "title": "Post-Update",
    "content": "After the firmware is written, the app verifies the update and waits for the device to come back online: . Once the update succeeds: . | The radio reboots automatically | The Bluetooth connection re-establishes | Verify your settings are intact | Confirm the new version under Currently Installed on the Firmware Update screen — it’s also shown on the node’s detail page and the Connections screen | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/firmware.html#post-update",
    
    "relUrl": "/ht-rHT/user/firmware.html#post-update"
  },"1531": {
    "doc": "Firmware Updates",
    "title": "Troubleshooting",
    "content": "Update Stuck . If the update appears frozen: . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | Try connecting via USB to a computer | Use the web flasher in recovery/DFU mode | Flash a known-good firmware version | Check the Meshtastic Discord for device-specific recovery steps | . Compatibility Warnings . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | Firmware version | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/firmware.html#troubleshooting",
    
    "relUrl": "/ht-rHT/user/firmware.html#troubleshooting"
  },"1532": {
    "doc": "Firmware Updates",
    "title": "Related Topics",
    "content": ". | Connections — reconnecting after a firmware update | Flashing firmware guide — full firmware flashing walkthrough on meshtastic.org | Supported devices — check firmware compatibility by device | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/firmware.html#related-topics",
    
    "relUrl": "/ht-rHT/user/firmware.html#related-topics"
  },"1533": {
    "doc": "Ажурирања фирмвера",
    "title": "Ажурирања фирмвера",
    "content": "Keep your Meshtastic radio up to date with the latest firmware for new features, bug fixes, and security improvements. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/firmware.html",
    
    "relUrl": "/sr-rLatn/user/firmware.html"
  },"1534": {
    "doc": "Ажурирања фирмвера",
    "title": "Checking for Updates",
    "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable radios. | The app checks for available firmware versions. | Available updates show the version number and changelog summary. | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/firmware.html#checking-for-updates",
    
    "relUrl": "/sr-rLatn/user/firmware.html#checking-for-updates"
  },"1535": {
    "doc": "Ажурирања фирмвера",
    "title": "Update Methods",
    "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | Wait for the update to complete — do not disconnect during the update. | . Erase device during update . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Wipes the device’s flash completely, then installs the selected firmware from scratch. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. In-App USB Update . When your radio is connected over USB/serial (rather than Bluetooth), the Firmware Update screen offers USB File Transfer. The app reboots the device into DFU mode, then prompts you to save the .uf2 file to the device’s DFU drive using the system file picker. This option appears only on a USB/serial connection — it is not available over Bluetooth. ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. A bootloader supplied as an update-....uf2 can be installed by copying it to the drive; that is how the app’s own bootloader upgrade works. The app surfaces a hint when the serial-only route applies. Factory Erase and Bootloader Upgrade . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. The app reads INFO_UF2.TXT from the drive you select to confirm it really is the device’s update drive and to identify the board before writing anything. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Other Flashing Options . For recovery or when neither OTA nor in-app USB is available: . | Use the Meshtastic Web Flasher | Or the Meshtastic CLI tool on desktop | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/firmware.html#update-methods",
    
    "relUrl": "/sr-rLatn/user/firmware.html#update-methods"
  },"1536": {
    "doc": "Ажурирања фирмвера",
    "title": "Version Channels",
    "content": "| Kanal | Опис | . | Stable | Recommended for most users; tested releases | . | Alpha | Preview releases; may contain bugs | . | Local File | Flash a firmware file you select yourself, instead of a downloaded release | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/firmware.html#version-channels",
    
    "relUrl": "/sr-rLatn/user/firmware.html#version-channels"
  },"1537": {
    "doc": "Ажурирања фирмвера",
    "title": "Pre-Update Checklist",
    "content": "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 | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/firmware.html#pre-update-checklist",
    
    "relUrl": "/sr-rLatn/user/firmware.html#pre-update-checklist"
  },"1538": {
    "doc": "Ажурирања фирмвера",
    "title": "Post-Update",
    "content": "After the firmware is written, the app verifies the update and waits for the device to come back online: . Once the update succeeds: . | The radio reboots automatically | The Bluetooth connection re-establishes | Verify your settings are intact | Confirm the new version under Currently Installed on the Firmware Update screen — it’s also shown on the node’s detail page and the Connections screen | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/firmware.html#post-update",
    
    "relUrl": "/sr-rLatn/user/firmware.html#post-update"
  },"1539": {
    "doc": "Ажурирања фирмвера",
    "title": "Troubleshooting",
    "content": "Update Stuck . If the update appears frozen: . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | Try connecting via USB to a computer | Use the web flasher in recovery/DFU mode | Flash a known-good firmware version | Check the Meshtastic Discord for device-specific recovery steps | . Compatibility Warnings . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | Firmware version | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/firmware.html#troubleshooting",
    
    "relUrl": "/sr-rLatn/user/firmware.html#troubleshooting"
  },"1540": {
    "doc": "Ажурирања фирмвера",
    "title": "Related Topics",
    "content": ". | Connections — reconnecting after a firmware update | Flashing firmware guide — full firmware flashing walkthrough on meshtastic.org | Supported devices — check firmware compatibility by device | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/firmware.html#related-topics",
    
    "relUrl": "/sr-rLatn/user/firmware.html#related-topics"
  },"1541": {
    "doc": "Firmware Updates",
    "title": "Firmware Updates",
    "content": "Keep your Meshtastic radio up to date with the latest firmware for new features, bug fixes, and security improvements. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/firmware.html",
    
    "relUrl": "/nl-rNL/user/firmware.html"
  },"1542": {
    "doc": "Firmware Updates",
    "title": "Checking for Updates",
    "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable radios. | The app checks for available firmware versions. | Available updates show the version number and changelog summary. | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/firmware.html#checking-for-updates",
    
    "relUrl": "/nl-rNL/user/firmware.html#checking-for-updates"
  },"1543": {
    "doc": "Firmware Updates",
    "title": "Update Methods",
    "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | Wait for the update to complete — do not disconnect during the update. | . Erase device during update . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Wipes the device’s flash completely, then installs the selected firmware from scratch. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. In-App USB Update . When your radio is connected over USB/serial (rather than Bluetooth), the Firmware Update screen offers USB File Transfer. The app reboots the device into DFU mode, then prompts you to save the .uf2 file to the device’s DFU drive using the system file picker. This option appears only on a USB/serial connection — it is not available over Bluetooth. ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. A bootloader supplied as an update-....uf2 can be installed by copying it to the drive; that is how the app’s own bootloader upgrade works. The app surfaces a hint when the serial-only route applies. Factory Erase and Bootloader Upgrade . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. The app reads INFO_UF2.TXT from the drive you select to confirm it really is the device’s update drive and to identify the board before writing anything. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Other Flashing Options . For recovery or when neither OTA nor in-app USB is available: . | Use the Meshtastic Web Flasher | Or the Meshtastic CLI tool on desktop | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/firmware.html#update-methods",
    
    "relUrl": "/nl-rNL/user/firmware.html#update-methods"
  },"1544": {
    "doc": "Firmware Updates",
    "title": "Version Channels",
    "content": "| Kanaal | Beschrijving | . | Stable | Recommended for most users; tested releases | . | Alpha | Preview releases; may contain bugs | . | Local File | Flash a firmware file you select yourself, instead of a downloaded release | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/firmware.html#version-channels",
    
    "relUrl": "/nl-rNL/user/firmware.html#version-channels"
  },"1545": {
    "doc": "Firmware Updates",
    "title": "Pre-Update Checklist",
    "content": "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 | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/firmware.html#pre-update-checklist",
    
    "relUrl": "/nl-rNL/user/firmware.html#pre-update-checklist"
  },"1546": {
    "doc": "Firmware Updates",
    "title": "Post-Update",
    "content": "After the firmware is written, the app verifies the update and waits for the device to come back online: . Once the update succeeds: . | The radio reboots automatically | The Bluetooth connection re-establishes | Verify your settings are intact | Confirm the new version under Currently Installed on the Firmware Update screen — it’s also shown on the node’s detail page and the Connections screen | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/firmware.html#post-update",
    
    "relUrl": "/nl-rNL/user/firmware.html#post-update"
  },"1547": {
    "doc": "Firmware Updates",
    "title": "Troubleshooting",
    "content": "Update Stuck . If the update appears frozen: . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | Try connecting via USB to a computer | Use the web flasher in recovery/DFU mode | Flash a known-good firmware version | Check the Meshtastic Discord for device-specific recovery steps | . Compatibility Warnings . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | Firmware-versie | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/firmware.html#troubleshooting",
    
    "relUrl": "/nl-rNL/user/firmware.html#troubleshooting"
  },"1548": {
    "doc": "Firmware Updates",
    "title": "Related Topics",
    "content": ". | Connections — reconnecting after a firmware update | Flashing firmware guide — full firmware flashing walkthrough on meshtastic.org | Supported devices — check firmware compatibility by device | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/firmware.html#related-topics",
    
    "relUrl": "/nl-rNL/user/firmware.html#related-topics"
  },"1549": {
    "doc": "Firmware Updates",
    "title": "Firmware Updates",
    "content": "Keep your Meshtastic radio up to date with the latest firmware for new features, bug fixes, and security improvements. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/firmware.html",
    
    "relUrl": "/uk-rUA/user/firmware.html"
  },"1550": {
    "doc": "Firmware Updates",
    "title": "Checking for Updates",
    "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable radios. | The app checks for available firmware versions. | Available updates show the version number and changelog summary. | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/firmware.html#checking-for-updates",
    
    "relUrl": "/uk-rUA/user/firmware.html#checking-for-updates"
  },"1551": {
    "doc": "Firmware Updates",
    "title": "Update Methods",
    "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | Wait for the update to complete — do not disconnect during the update. | . Erase device during update . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Wipes the device’s flash completely, then installs the selected firmware from scratch. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. In-App USB Update . When your radio is connected over USB/serial (rather than Bluetooth), the Firmware Update screen offers USB File Transfer. The app reboots the device into DFU mode, then prompts you to save the .uf2 file to the device’s DFU drive using the system file picker. This option appears only on a USB/serial connection — it is not available over Bluetooth. ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. A bootloader supplied as an update-....uf2 can be installed by copying it to the drive; that is how the app’s own bootloader upgrade works. The app surfaces a hint when the serial-only route applies. Factory Erase and Bootloader Upgrade . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. The app reads INFO_UF2.TXT from the drive you select to confirm it really is the device’s update drive and to identify the board before writing anything. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Other Flashing Options . For recovery or when neither OTA nor in-app USB is available: . | Use the Meshtastic Web Flasher | Or the Meshtastic CLI tool on desktop | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/firmware.html#update-methods",
    
    "relUrl": "/uk-rUA/user/firmware.html#update-methods"
  },"1552": {
    "doc": "Firmware Updates",
    "title": "Version Channels",
    "content": "| Канал | Опис | . | Стабільна | Recommended for most users; tested releases | . | Альфа | Preview releases; may contain bugs | . | Файл | Flash a firmware file you select yourself, instead of a downloaded release | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/firmware.html#version-channels",
    
    "relUrl": "/uk-rUA/user/firmware.html#version-channels"
  },"1553": {
    "doc": "Firmware Updates",
    "title": "Pre-Update Checklist",
    "content": "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 | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/firmware.html#pre-update-checklist",
    
    "relUrl": "/uk-rUA/user/firmware.html#pre-update-checklist"
  },"1554": {
    "doc": "Firmware Updates",
    "title": "Post-Update",
    "content": "After the firmware is written, the app verifies the update and waits for the device to come back online: . Once the update succeeds: . | The radio reboots automatically | The Bluetooth connection re-establishes | Verify your settings are intact | Confirm the new version under Currently Installed on the Firmware Update screen — it’s also shown on the node’s detail page and the Connections screen | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/firmware.html#post-update",
    
    "relUrl": "/uk-rUA/user/firmware.html#post-update"
  },"1555": {
    "doc": "Firmware Updates",
    "title": "Troubleshooting",
    "content": "Update Stuck . If the update appears frozen: . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | Try connecting via USB to a computer | Use the web flasher in recovery/DFU mode | Flash a known-good firmware version | Check the Meshtastic Discord for device-specific recovery steps | . Compatibility Warnings . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | Версія прошивки | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/firmware.html#troubleshooting",
    
    "relUrl": "/uk-rUA/user/firmware.html#troubleshooting"
  },"1556": {
    "doc": "Firmware Updates",
    "title": "Related Topics",
    "content": ". | Connections — reconnecting after a firmware update | Flashing firmware guide — full firmware flashing walkthrough on meshtastic.org | Supported devices — check firmware compatibility by device | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/firmware.html#related-topics",
    
    "relUrl": "/uk-rUA/user/firmware.html#related-topics"
  },"1557": {
    "doc": "Laiteohjelmiston päivitykset",
    "title": "Laiteohjelmiston päivitykset",
    "content": "Pidä Meshtastic-radiosi ajan tasalla uusimmalla firmwarella, jossa on uusia ominaisuuksia, virhekorjauksia ja tietoturvaparannuksia. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/firmware.html",
    
    "relUrl": "/fi-rFI/user/firmware.html"
  },"1558": {
    "doc": "Laiteohjelmiston päivitykset",
    "title": "Päivitysten tarkistaminen",
    "content": ". | Avaa yhdistetyn radion asetukset ja valitse Lisäasetukset → Laiteohjelmiston päivitys. Kohta näkyy vain OTA-päivitystä tukeville radioille. | Sovellus tarkistaa saatavilla olevat firmware-versiot. | Saatavilla olevat päivitykset näyttävät versionumeron ja muutoslokin yhteenvedon. | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/firmware.html#p%C3%A4ivitysten-tarkistaminen",
    
    "relUrl": "/fi-rFI/user/firmware.html#päivitysten-tarkistaminen"
  },"1559": {
    "doc": "Laiteohjelmiston päivitykset",
    "title": "Päivitysmenetelmät",
    "content": "OTA (Over-The-Air) Bluetooth-yhteyden kautta . Yleisin päivitystapa Android-käyttäjille: . ⚠️ Varoitus: Laiteohjelmistopäivityksen keskeyttäminen voi estää radion käynnistymisen. Pidä puhelin lähellä ja molemmat laitteet käynnissä, kunnes päivitys on valmis. | Varmista, että radiosi on yhdistetty Bluetoothilla. | Siirry Firmware-päivitys -näkymään. | Valitse haluamasi firmware-versio. | Napauta Päivitä. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | Odota, että päivitys valmistuu — älä katkaise yhteyttä päivityksen aikana. | . Tyhjennä laite päivityksen aikana . Jos sovellus tukee sitä, päivityspainikkeen vieressä näkyy Tyhjennä laite päivityksen aikana -valintaruutu. Asetus koskee vain tätä päivitystä eikä sitä muisteta myöhemmin. | Menetelmä | Mitä tyhjennys tekee | . | BLE / WiFi OTA | Laite palautetaan tehdasasetuksiin, kun päivitys on vahvistettu. Kaikki asetukset ja Bluetooth-pariliitokset poistetaan. | . | USB | Tyhjentää laitteen flash-muistin kokonaan ja asentaa sen jälkeen valitun laiteohjelmiston alusta alkaen. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Tämän jälkeen laite on määritettävä uudelleen ja pariliitos muodostettava uudelleen. OTA WiFi:n kautta (verkkoon yhdistetty ESP32) . Kun ESP32-radio on yhdistetty verkkoon Bluetoothin sijaan, sovellus tarjoaa WiFi OTA -vaihtoehdon, joka siirtää saman päivityksen TCP-yhteyden kautta. | Muodosta yhteys radioon verkon kautta (katso Yhteydet). | Avaa Laiteohjelmiston päivitys -näkymä ja valitse versio. | Napauta Päivitä. Pidä radio ja puhelin samassa verkossa koko siirron ajan. | . WiFi OTA käyttää ESP32:n update.bin-tiedostoa USB-päivityksen .uf2-tiedoston sijaan. Sovellus valitsee oikean tiedoston automaattisesti. USB-päivitys sovelluksesta . Kun radio on yhdistetty USB:n tai sarjayhteyden kautta (bluetoothin sijaan), laiteohjelmiston päivitys -näkymässä on käytettävissä USB-tiedostonsiirto. Sovellus käynnistää laitteen uudelleen DFU-tilaan ja pyytää sitten tallentamaan .uf2-tiedoston laitteen DFU-asemaan järjestelmän tiedostonvalitsimen avulla. Tämä vaihtoehto näkyy vain USB tai sarjayhteydellä — sitä ei voi käyttää bluetoothin kautta. ℹ️ Huomautus: Valmistajan nRF-käynnistyslatain, joka toimitetaan .zip-tiedostona (esim. RAK WisBlock RAK4631), on asennettava sarjaliitäntäisen DFU-työkalun, kuten adafruit-nrfutil-ohjelman avulla — .zip-tiedoston kopioiminen asemalle ei toimi. Päivitysmuotoinen .uf2-käynnistyslatain voidaan asentaa kopioimalla se asemalle. Näin myös tämän sovelluksen käynnistyslataimen päivitystoiminto toimii. Sovellus näyttää huomautuksen, kun käytettävissä on vain sarjaliitäntäinen menetelmä. Tyhjennys tehdasasetuksiin ja käynnistyslataimen päivitys . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. Sovellus lukee valitsemaltasi asemalta tiedoston INFO_UF2.TXT varmistaakseen, että kyseessä on todella laitteen päivitysasema, sekä tunnistaakseen laitteen ennen kuin mitään kirjoitetaan. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. Web Flasherissa väärän Bluetooth-pinon valitseminen voi johtaa siihen, että radion palauttaminen onnistuu vain laitteisto-ohjelmoijan avulla. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Muut päivitysvaihtoehdot . Käytä näitä palautukseen tai silloin, kun OTA- tai sovelluksen USB-päivitys ei ole käytettävissä: . | Käytä Meshtastic Web Flasheriä | Tai Meshtastic CLI -työkalua työpöytäympäristössä | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/firmware.html#p%C3%A4ivitysmenetelm%C3%A4t",
    
    "relUrl": "/fi-rFI/user/firmware.html#päivitysmenetelmät"
  },"1560": {
    "doc": "Laiteohjelmiston päivitykset",
    "title": "Versiokanavat",
    "content": "| Kanava | Kuvaus | . | Vakaa | Suositeltu useimmille käyttäjille: testatut julkaisut | . | Alpha | Esijulkaisut voivat sisältää virheitä | . | Paikallinen tiedosto | Asenna itse valitsemasi laiteohjelmistotiedosto ladatun julkaisun sijaan | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/firmware.html#versiokanavat",
    
    "relUrl": "/fi-rFI/user/firmware.html#versiokanavat"
  },"1561": {
    "doc": "Laiteohjelmiston päivitykset",
    "title": "Päivitystä edeltävä tarkistuslista",
    "content": "Ennen päivityksen aloitamista: . | Akku > 50 % | Vakaa Bluetooth-yhteys | Kirjaa ylös nykyiset asetuksesi (ne voivat nollautua suurissa versiomuutoksissa) | Tarkista julkaisumuistiinpanot mahdollista yhteensopivuutta rikkovien muutosten varalta | Päivitä myös Meshtastic-sovellus joko ennen laiteohjelmiston päivitystä tai sen yhteydessä yhteensopivuuden varmistamiseksi | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/firmware.html#p%C3%A4ivityst%C3%A4-edelt%C3%A4v%C3%A4-tarkistuslista",
    
    "relUrl": "/fi-rFI/user/firmware.html#päivitystä-edeltävä-tarkistuslista"
  },"1562": {
    "doc": "Laiteohjelmiston päivitykset",
    "title": "Päivityksen jälkeen",
    "content": "Kun laiteohjelmisto on kirjoitettu, sovellus varmistaa päivityksen ja odottaa laitteen palaavan takaisin verkkoon: . Kun päivitys onnistuu: . | Radio käynnistyy uudelleen automaattisesti | Bluetooth-yhteys muodostetaan uudelleen | Varmista, että asetuksesi ovat säilyneet | Vahvista uusi versio Asennettu tällä hetkellä -kohdasta Laiteohjelmiston päivitys -näkymässä — sama tieto näkyy myös radion tiedoissa ja Yhteydet-näkymässä | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/firmware.html#p%C3%A4ivityksen-j%C3%A4lkeen",
    
    "relUrl": "/fi-rFI/user/firmware.html#päivityksen-jälkeen"
  },"1563": {
    "doc": "Laiteohjelmiston päivitykset",
    "title": "Vianetsintä",
    "content": "Päivitys jumissa . Jos päivitys näyttää jumiutuneen: . | Anna sille hetki aikaa. Kun tiedosto on kirjoitettu, sovellus odottaa enintään 60 sekuntia, että radio käynnistyy uudelleen ja ilmoittaa uuden versionsa. Lyhyt odotus vahvistusvaiheessa on siis normaalia. | Jos radio on tämän jälkeen edelleen jumissa, käynnistä se uudelleen katkaisemalla virta. | Yritä päivitystä uudelleen. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio ei käynnisty päivityksen jälkeen . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | Kokeile yhdistää USB:llä tietokoneeseen | Käytä web-flasheria palautus tai DFU-tilassa | Asenna tunnetusti toimiva firmware-versio | Tarkista Meshtastic Discordista laitekohtaiset palautusohjeet | . Yhteensopivuutta koskevat varoitukset . Yhteyden muodostamisen yhteydessä sovellus vertaa radion laiteohjelmistoversiota kahteen rajaan ja toimii niiden perusteella eri tavoin: . | Laiteohjelmistoversio | Näet seuraavan | Mitä tapahtuu | . | Alle 2.3.15 | Laiteohjelmiston päivitys vaaditaan. | Sovellus katkaisee yhteyden radioon. Se ei toimi näin vanhan laiteohjelmiston kanssa. | . | 2.3.15 tai uudempi, mutta alle 2.5.14 | Laiteohjelmiston päivitystä suositellaan. | Vain suositus – voit ohittaa sen ja jatkaa. Valintaikkunassa kerrotaan uusin vakaa julkaisu. | . | 2.5.14 tai uudempi | Ei mitään | — | . Jos sovellus ei pysty tulkitsemaan versionumeroa, se ohitetaan sen sijaan, että sitä pidettäisiin liian vanhana. Näin tilapäinen lukuvirhe ei katkaise yhteyttä toimivaan radioon. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/firmware.html#vianetsint%C3%A4",
    
    "relUrl": "/fi-rFI/user/firmware.html#vianetsintä"
  },"1564": {
    "doc": "Laiteohjelmiston päivitykset",
    "title": "Aiheeseen liittyvät aiheet",
    "content": ". | Yhteydet — yhdistetään uudelleen laiteohjelmiston päivityksen jälkeen | Laiteohjelmiston päivitysopas — täydellinen firmware-päivityksen ohjeistus meshtastic.org -sivustolla | Tuetut laitteet — tarkista firmware-yhteensopivuus laitekohtaisesti | UKK – usein kysytyt kysymykset meshtastic.org -sivustolla | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/firmware.html#aiheeseen-liittyv%C3%A4t-aiheet",
    
    "relUrl": "/fi-rFI/user/firmware.html#aiheeseen-liittyvät-aiheet"
  },"1565": {
    "doc": "Firmware Updates",
    "title": "Firmware Updates",
    "content": "Keep your Meshtastic radio up to date with the latest firmware for new features, bug fixes, and security improvements. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/firmware.html",
    
    "relUrl": "/is-rIS/user/firmware.html"
  },"1566": {
    "doc": "Firmware Updates",
    "title": "Checking for Updates",
    "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable radios. | The app checks for available firmware versions. | Available updates show the version number and changelog summary. | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/firmware.html#checking-for-updates",
    
    "relUrl": "/is-rIS/user/firmware.html#checking-for-updates"
  },"1567": {
    "doc": "Firmware Updates",
    "title": "Update Methods",
    "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | Wait for the update to complete — do not disconnect during the update. | . Erase device during update . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Wipes the device’s flash completely, then installs the selected firmware from scratch. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. In-App USB Update . When your radio is connected over USB/serial (rather than Bluetooth), the Firmware Update screen offers USB File Transfer. The app reboots the device into DFU mode, then prompts you to save the .uf2 file to the device’s DFU drive using the system file picker. This option appears only on a USB/serial connection — it is not available over Bluetooth. ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. A bootloader supplied as an update-....uf2 can be installed by copying it to the drive; that is how the app’s own bootloader upgrade works. The app surfaces a hint when the serial-only route applies. Factory Erase and Bootloader Upgrade . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. The app reads INFO_UF2.TXT from the drive you select to confirm it really is the device’s update drive and to identify the board before writing anything. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Other Flashing Options . For recovery or when neither OTA nor in-app USB is available: . | Use the Meshtastic Web Flasher | Or the Meshtastic CLI tool on desktop | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/firmware.html#update-methods",
    
    "relUrl": "/is-rIS/user/firmware.html#update-methods"
  },"1568": {
    "doc": "Firmware Updates",
    "title": "Version Channels",
    "content": "| Channel | Lýsing | . | Stable | Recommended for most users; tested releases | . | Alpha | Preview releases; may contain bugs | . | Local File | Flash a firmware file you select yourself, instead of a downloaded release | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/firmware.html#version-channels",
    
    "relUrl": "/is-rIS/user/firmware.html#version-channels"
  },"1569": {
    "doc": "Firmware Updates",
    "title": "Pre-Update Checklist",
    "content": "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 | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/firmware.html#pre-update-checklist",
    
    "relUrl": "/is-rIS/user/firmware.html#pre-update-checklist"
  },"1570": {
    "doc": "Firmware Updates",
    "title": "Post-Update",
    "content": "After the firmware is written, the app verifies the update and waits for the device to come back online: . Once the update succeeds: . | The radio reboots automatically | The Bluetooth connection re-establishes | Verify your settings are intact | Confirm the new version under Currently Installed on the Firmware Update screen — it’s also shown on the node’s detail page and the Connections screen | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/firmware.html#post-update",
    
    "relUrl": "/is-rIS/user/firmware.html#post-update"
  },"1571": {
    "doc": "Firmware Updates",
    "title": "Troubleshooting",
    "content": "Update Stuck . If the update appears frozen: . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | Try connecting via USB to a computer | Use the web flasher in recovery/DFU mode | Flash a known-good firmware version | Check the Meshtastic Discord for device-specific recovery steps | . Compatibility Warnings . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | Firmware version | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/firmware.html#troubleshooting",
    
    "relUrl": "/is-rIS/user/firmware.html#troubleshooting"
  },"1572": {
    "doc": "Firmware Updates",
    "title": "Related Topics",
    "content": ". | Connections — reconnecting after a firmware update | Flashing firmware guide — full firmware flashing walkthrough on meshtastic.org | Supported devices — check firmware compatibility by device | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/firmware.html#related-topics",
    
    "relUrl": "/is-rIS/user/firmware.html#related-topics"
  },"1573": {
    "doc": "Firmware Updates",
    "title": "Firmware Updates",
    "content": "Keep your Meshtastic radio up to date with the latest firmware for new features, bug fixes, and security improvements. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/firmware.html",
    
    "relUrl": "/lt-rLT/user/firmware.html"
  },"1574": {
    "doc": "Firmware Updates",
    "title": "Checking for Updates",
    "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable radios. | The app checks for available firmware versions. | Available updates show the version number and changelog summary. | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/firmware.html#checking-for-updates",
    
    "relUrl": "/lt-rLT/user/firmware.html#checking-for-updates"
  },"1575": {
    "doc": "Firmware Updates",
    "title": "Update Methods",
    "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | Wait for the update to complete — do not disconnect during the update. | . Erase device during update . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Wipes the device’s flash completely, then installs the selected firmware from scratch. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. In-App USB Update . When your radio is connected over USB/serial (rather than Bluetooth), the Firmware Update screen offers USB File Transfer. The app reboots the device into DFU mode, then prompts you to save the .uf2 file to the device’s DFU drive using the system file picker. This option appears only on a USB/serial connection — it is not available over Bluetooth. ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. A bootloader supplied as an update-....uf2 can be installed by copying it to the drive; that is how the app’s own bootloader upgrade works. The app surfaces a hint when the serial-only route applies. Factory Erase and Bootloader Upgrade . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. The app reads INFO_UF2.TXT from the drive you select to confirm it really is the device’s update drive and to identify the board before writing anything. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Other Flashing Options . For recovery or when neither OTA nor in-app USB is available: . | Use the Meshtastic Web Flasher | Or the Meshtastic CLI tool on desktop | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/firmware.html#update-methods",
    
    "relUrl": "/lt-rLT/user/firmware.html#update-methods"
  },"1576": {
    "doc": "Firmware Updates",
    "title": "Version Channels",
    "content": "| Kanalas | Aprašymas | . | Stable | Recommended for most users; tested releases | . | Alpha | Preview releases; may contain bugs | . | Local File | Flash a firmware file you select yourself, instead of a downloaded release | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/firmware.html#version-channels",
    
    "relUrl": "/lt-rLT/user/firmware.html#version-channels"
  },"1577": {
    "doc": "Firmware Updates",
    "title": "Pre-Update Checklist",
    "content": "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 | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/firmware.html#pre-update-checklist",
    
    "relUrl": "/lt-rLT/user/firmware.html#pre-update-checklist"
  },"1578": {
    "doc": "Firmware Updates",
    "title": "Post-Update",
    "content": "After the firmware is written, the app verifies the update and waits for the device to come back online: . Once the update succeeds: . | The radio reboots automatically | The Bluetooth connection re-establishes | Verify your settings are intact | Confirm the new version under Currently Installed on the Firmware Update screen — it’s also shown on the node’s detail page and the Connections screen | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/firmware.html#post-update",
    
    "relUrl": "/lt-rLT/user/firmware.html#post-update"
  },"1579": {
    "doc": "Firmware Updates",
    "title": "Troubleshooting",
    "content": "Update Stuck . If the update appears frozen: . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | Try connecting via USB to a computer | Use the web flasher in recovery/DFU mode | Flash a known-good firmware version | Check the Meshtastic Discord for device-specific recovery steps | . Compatibility Warnings . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | Firmware version | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/firmware.html#troubleshooting",
    
    "relUrl": "/lt-rLT/user/firmware.html#troubleshooting"
  },"1580": {
    "doc": "Firmware Updates",
    "title": "Related Topics",
    "content": ". | Connections — reconnecting after a firmware update | Flashing firmware guide — full firmware flashing walkthrough on meshtastic.org | Supported devices — check firmware compatibility by device | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/firmware.html#related-topics",
    
    "relUrl": "/lt-rLT/user/firmware.html#related-topics"
  },"1581": {
    "doc": "Firmware Updates",
    "title": "Firmware Updates",
    "content": "Keep your Meshtastic radio up to date with the latest firmware for new features, bug fixes, and security improvements. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/firmware.html",
    
    "relUrl": "/gl-rES/user/firmware.html"
  },"1582": {
    "doc": "Firmware Updates",
    "title": "Checking for Updates",
    "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable radios. | The app checks for available firmware versions. | Available updates show the version number and changelog summary. | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/firmware.html#checking-for-updates",
    
    "relUrl": "/gl-rES/user/firmware.html#checking-for-updates"
  },"1583": {
    "doc": "Firmware Updates",
    "title": "Update Methods",
    "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | Wait for the update to complete — do not disconnect during the update. | . Erase device during update . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Wipes the device’s flash completely, then installs the selected firmware from scratch. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. In-App USB Update . When your radio is connected over USB/serial (rather than Bluetooth), the Firmware Update screen offers USB File Transfer. The app reboots the device into DFU mode, then prompts you to save the .uf2 file to the device’s DFU drive using the system file picker. This option appears only on a USB/serial connection — it is not available over Bluetooth. ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. A bootloader supplied as an update-....uf2 can be installed by copying it to the drive; that is how the app’s own bootloader upgrade works. The app surfaces a hint when the serial-only route applies. Factory Erase and Bootloader Upgrade . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. The app reads INFO_UF2.TXT from the drive you select to confirm it really is the device’s update drive and to identify the board before writing anything. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Other Flashing Options . For recovery or when neither OTA nor in-app USB is available: . | Use the Meshtastic Web Flasher | Or the Meshtastic CLI tool on desktop | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/firmware.html#update-methods",
    
    "relUrl": "/gl-rES/user/firmware.html#update-methods"
  },"1584": {
    "doc": "Firmware Updates",
    "title": "Version Channels",
    "content": "| Canle | Descrición | . | Stable | Recommended for most users; tested releases | . | Alpha | Preview releases; may contain bugs | . | Local File | Flash a firmware file you select yourself, instead of a downloaded release | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/firmware.html#version-channels",
    
    "relUrl": "/gl-rES/user/firmware.html#version-channels"
  },"1585": {
    "doc": "Firmware Updates",
    "title": "Pre-Update Checklist",
    "content": "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 | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/firmware.html#pre-update-checklist",
    
    "relUrl": "/gl-rES/user/firmware.html#pre-update-checklist"
  },"1586": {
    "doc": "Firmware Updates",
    "title": "Post-Update",
    "content": "After the firmware is written, the app verifies the update and waits for the device to come back online: . Once the update succeeds: . | The radio reboots automatically | The Bluetooth connection re-establishes | Verify your settings are intact | Confirm the new version under Currently Installed on the Firmware Update screen — it’s also shown on the node’s detail page and the Connections screen | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/firmware.html#post-update",
    
    "relUrl": "/gl-rES/user/firmware.html#post-update"
  },"1587": {
    "doc": "Firmware Updates",
    "title": "Troubleshooting",
    "content": "Update Stuck . If the update appears frozen: . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | Try connecting via USB to a computer | Use the web flasher in recovery/DFU mode | Flash a known-good firmware version | Check the Meshtastic Discord for device-specific recovery steps | . Compatibility Warnings . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | Firmware version | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/firmware.html#troubleshooting",
    
    "relUrl": "/gl-rES/user/firmware.html#troubleshooting"
  },"1588": {
    "doc": "Firmware Updates",
    "title": "Related Topics",
    "content": ". | Connections — reconnecting after a firmware update | Flashing firmware guide — full firmware flashing walkthrough on meshtastic.org | Supported devices — check firmware compatibility by device | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/firmware.html#related-topics",
    
    "relUrl": "/gl-rES/user/firmware.html#related-topics"
  },"1589": {
    "doc": "ファームウェア更新",
    "title": "ファームウェア更新",
    "content": "新機能、バグ修正、セキュリティ改善のために、Meshtastic 無線機を最新のファームウェアに保ちましょう。 . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/firmware.html",
    
    "relUrl": "/ja-rJP/user/firmware.html"
  },"1590": {
    "doc": "ファームウェア更新",
    "title": "更新を確認する",
    "content": ". | 接続中の無線機の設定を開き、「詳細設定」で「ファームウェア更新」をタップします。 The entry appears only for OTA-capable radios. | アプリが、利用可能なファームウェアバージョンを確認します。 | 利用可能な更新には、バージョン番号と変更履歴の概要が表示されます。 | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/firmware.html#%E6%9B%B4%E6%96%B0%E3%82%92%E7%A2%BA%E8%AA%8D%E3%81%99%E3%82%8B",
    
    "relUrl": "/ja-rJP/user/firmware.html#更新を確認する"
  },"1591": {
    "doc": "ファームウェア更新",
    "title": "更新方法",
    "content": "Bluetooth 経由の OTA（無線更新） . Android ユーザーにとって最も一般的な更新方法です： . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | 無線機が Bluetooth で接続されていることを確認します。 | ファームウェア更新画面に移動します。 | 希望するファームウェアバージョンを選択します。 | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | 更新が完了するまで待ちます。更新中は接続を切断しないでください。 | . Erase device during update . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Wipes the device’s flash completely, then installs the selected firmware from scratch. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. アプリ内での USB 更新 . 無線機が（Bluetooth ではなく）USB／シリアルで接続されている場合、ファームウェア更新画面に「USB ファイル転送」が表示されます。アプリはデバイスを DFU モードで再起動し、システムのファイル選択画面を使って .uf2 ファイルをデバイスの DFU ドライブに保存するよう促します。このオプションは USB／シリアル接続でのみ表示され、Bluetooth では利用できません。 . ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. A bootloader supplied as an update-....uf2 can be installed by copying it to the drive; that is how the app’s own bootloader upgrade works. The app surfaces a hint when the serial-only route applies. Factory Erase and Bootloader Upgrade . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. The app reads INFO_UF2.TXT from the drive you select to confirm it really is the device’s update drive and to identify the board before writing anything. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. その他の書き込み方法 . 復旧時、または OTA とアプリ内 USB のどちらも使えない場合： . | Meshtastic Web Flasher を使用する | または、デスクトップで Meshtastic CLI ツール を使用する | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/firmware.html#%E6%9B%B4%E6%96%B0%E6%96%B9%E6%B3%95",
    
    "relUrl": "/ja-rJP/user/firmware.html#更新方法"
  },"1592": {
    "doc": "ファームウェア更新",
    "title": "バージョンチャンネル",
    "content": "| チャンネル | 説明 | . | 安定版 | ほとんどのユーザーに推奨。テスト済みのリリース | . | アルファ版 | プレビューリリース。バグを含む場合があります | . | ローカルファイル | ダウンロードしたリリースではなく、自分で選んだファームウェアファイルを書き込む | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/firmware.html#%E3%83%90%E3%83%BC%E3%82%B8%E3%83%A7%E3%83%B3%E3%83%81%E3%83%A3%E3%83%B3%E3%83%8D%E3%83%AB",
    
    "relUrl": "/ja-rJP/user/firmware.html#バージョンチャンネル"
  },"1593": {
    "doc": "ファームウェア更新",
    "title": "更新前のチェックリスト",
    "content": "更新する前に： . | バッテリー 50% 以上 | 安定した Bluetooth 接続 | 現在の設定を控えておく（メジャーバージョンの変更時にリセットされることがあります） | 破壊的変更がないか、リリースノートを確認する | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/firmware.html#%E6%9B%B4%E6%96%B0%E5%89%8D%E3%81%AE%E3%83%81%E3%82%A7%E3%83%83%E3%82%AF%E3%83%AA%E3%82%B9%E3%83%88",
    
    "relUrl": "/ja-rJP/user/firmware.html#更新前のチェックリスト"
  },"1594": {
    "doc": "ファームウェア更新",
    "title": "更新後",
    "content": "ファームウェアの書き込み後、アプリは更新を検証し、デバイスが再びオンラインになるのを待ちます： . 更新が成功すると： . | The radio reboots automatically | The Bluetooth connection re-establishes | 設定が保持されているか確認します | ファームウェア更新画面の「現在インストール済み」で新しいバージョンを確認します。バージョンは、ノードの詳細ページや接続画面にも表示されます | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/firmware.html#%E6%9B%B4%E6%96%B0%E5%BE%8C",
    
    "relUrl": "/ja-rJP/user/firmware.html#更新後"
  },"1595": {
    "doc": "ファームウェア更新",
    "title": "トラブルシューティング",
    "content": "更新が止まる . 更新が固まったように見える場合： . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | USB でコンピューターに接続してみる | リカバリー／DFU モードで Web Flasher を使用する | 動作確認済みのファームウェアバージョンを書き込む | デバイス固有の復旧手順については、Meshtastic の Discord を確認する | . 互換性の警告 . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | ファームウェアバージョン | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/firmware.html#%E3%83%88%E3%83%A9%E3%83%96%E3%83%AB%E3%82%B7%E3%83%A5%E3%83%BC%E3%83%86%E3%82%A3%E3%83%B3%E3%82%B0",
    
    "relUrl": "/ja-rJP/user/firmware.html#トラブルシューティング"
  },"1596": {
    "doc": "ファームウェア更新",
    "title": "関連トピック",
    "content": ". | コネクション：ファームウェア更新後の再接続 | ファームウェア書き込みガイド：meshtastic.org にあるファームウェア書き込みの完全な手順 | 対応デバイス：デバイスごとのファームウェア互換性を確認 | FAQ：meshtastic.org のよくある質問 | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/firmware.html#%E9%96%A2%E9%80%A3%E3%83%88%E3%83%94%E3%83%83%E3%82%AF",
    
    "relUrl": "/ja-rJP/user/firmware.html#関連トピック"
  },"1597": {
    "doc": "Firmwareaktualisierungen",
    "title": "Firmwareaktualisierungen",
    "content": "Keep your Meshtastic radio up to date with the latest firmware for new features, bug fixes, and security improvements. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/firmware.html",
    
    "relUrl": "/de-rDE/user/firmware.html"
  },"1598": {
    "doc": "Firmwareaktualisierungen",
    "title": "Checking for Updates",
    "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable radios. | The app checks for available firmware versions. | Available updates show the version number and changelog summary. | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/firmware.html#checking-for-updates",
    
    "relUrl": "/de-rDE/user/firmware.html#checking-for-updates"
  },"1599": {
    "doc": "Firmwareaktualisierungen",
    "title": "Update Methods",
    "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | Wait for the update to complete — do not disconnect during the update. | . Erase device during update . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Wipes the device’s flash completely, then installs the selected firmware from scratch. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. In-App USB Update . When your radio is connected over USB/serial (rather than Bluetooth), the Firmware Update screen offers USB File Transfer. The app reboots the device into DFU mode, then prompts you to save the .uf2 file to the device’s DFU drive using the system file picker. This option appears only on a USB/serial connection — it is not available over Bluetooth. ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. A bootloader supplied as an update-....uf2 can be installed by copying it to the drive; that is how the app’s own bootloader upgrade works. The app surfaces a hint when the serial-only route applies. Factory Erase and Bootloader Upgrade . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. The app reads INFO_UF2.TXT from the drive you select to confirm it really is the device’s update drive and to identify the board before writing anything. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Other Flashing Options . For recovery or when neither OTA nor in-app USB is available: . | Use the Meshtastic Web Flasher | Or the Meshtastic CLI tool on desktop | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/firmware.html#update-methods",
    
    "relUrl": "/de-rDE/user/firmware.html#update-methods"
  },"1600": {
    "doc": "Firmwareaktualisierungen",
    "title": "Version Channels",
    "content": "| Kanal | Beschreibung | . | Stabil | Recommended for most users; tested releases | . | Alpha | Preview releases; may contain bugs | . | Lokale Datei | Flash a firmware file you select yourself, instead of a downloaded release | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/firmware.html#version-channels",
    
    "relUrl": "/de-rDE/user/firmware.html#version-channels"
  },"1601": {
    "doc": "Firmwareaktualisierungen",
    "title": "Pre-Update Checklist",
    "content": "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 | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/firmware.html#pre-update-checklist",
    
    "relUrl": "/de-rDE/user/firmware.html#pre-update-checklist"
  },"1602": {
    "doc": "Firmwareaktualisierungen",
    "title": "Post-Update",
    "content": "After the firmware is written, the app verifies the update and waits for the device to come back online: . Once the update succeeds: . | The radio reboots automatically | The Bluetooth connection re-establishes | Verify your settings are intact | Confirm the new version under Currently Installed on the Firmware Update screen — it’s also shown on the node’s detail page and the Connections screen | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/firmware.html#post-update",
    
    "relUrl": "/de-rDE/user/firmware.html#post-update"
  },"1603": {
    "doc": "Firmwareaktualisierungen",
    "title": "Fehlerbehebung",
    "content": "Update Stuck . If the update appears frozen: . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | Try connecting via USB to a computer | Use the web flasher in recovery/DFU mode | Flash a known-good firmware version | Check the Meshtastic Discord for device-specific recovery steps | . Compatibility Warnings . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | Firmwareversion | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/firmware.html#fehlerbehebung",
    
    "relUrl": "/de-rDE/user/firmware.html#fehlerbehebung"
  },"1604": {
    "doc": "Firmwareaktualisierungen",
    "title": "Verwandte Themen",
    "content": ". | Connections — reconnecting after a firmware update | Flashing firmware guide — full firmware flashing walkthrough on meshtastic.org | Supported devices — check firmware compatibility by device | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/firmware.html#verwandte-themen",
    
    "relUrl": "/de-rDE/user/firmware.html#verwandte-themen"
  },"1605": {
    "doc": "Firmware Updates",
    "title": "Firmware Updates",
    "content": "Keep your Meshtastic radio up to date with the latest firmware for new features, bug fixes, and security improvements. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/firmware.html",
    
    "relUrl": "/ar-rSA/user/firmware.html"
  },"1606": {
    "doc": "Firmware Updates",
    "title": "Checking for Updates",
    "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable radios. | The app checks for available firmware versions. | Available updates show the version number and changelog summary. | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/firmware.html#checking-for-updates",
    
    "relUrl": "/ar-rSA/user/firmware.html#checking-for-updates"
  },"1607": {
    "doc": "Firmware Updates",
    "title": "Update Methods",
    "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | Wait for the update to complete — do not disconnect during the update. | . Erase device during update . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Wipes the device’s flash completely, then installs the selected firmware from scratch. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. In-App USB Update . When your radio is connected over USB/serial (rather than Bluetooth), the Firmware Update screen offers USB File Transfer. The app reboots the device into DFU mode, then prompts you to save the .uf2 file to the device’s DFU drive using the system file picker. This option appears only on a USB/serial connection — it is not available over Bluetooth. ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. A bootloader supplied as an update-....uf2 can be installed by copying it to the drive; that is how the app’s own bootloader upgrade works. The app surfaces a hint when the serial-only route applies. Factory Erase and Bootloader Upgrade . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. The app reads INFO_UF2.TXT from the drive you select to confirm it really is the device’s update drive and to identify the board before writing anything. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Other Flashing Options . For recovery or when neither OTA nor in-app USB is available: . | Use the Meshtastic Web Flasher | Or the Meshtastic CLI tool on desktop | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/firmware.html#update-methods",
    
    "relUrl": "/ar-rSA/user/firmware.html#update-methods"
  },"1608": {
    "doc": "Firmware Updates",
    "title": "Version Channels",
    "content": "| عربي | الوصف | . | Stable | Recommended for most users; tested releases | . | Alpha | Preview releases; may contain bugs | . | Local File | Flash a firmware file you select yourself, instead of a downloaded release | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/firmware.html#version-channels",
    
    "relUrl": "/ar-rSA/user/firmware.html#version-channels"
  },"1609": {
    "doc": "Firmware Updates",
    "title": "Pre-Update Checklist",
    "content": "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 | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/firmware.html#pre-update-checklist",
    
    "relUrl": "/ar-rSA/user/firmware.html#pre-update-checklist"
  },"1610": {
    "doc": "Firmware Updates",
    "title": "Post-Update",
    "content": "After the firmware is written, the app verifies the update and waits for the device to come back online: . Once the update succeeds: . | The radio reboots automatically | The Bluetooth connection re-establishes | Verify your settings are intact | Confirm the new version under Currently Installed on the Firmware Update screen — it’s also shown on the node’s detail page and the Connections screen | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/firmware.html#post-update",
    
    "relUrl": "/ar-rSA/user/firmware.html#post-update"
  },"1611": {
    "doc": "Firmware Updates",
    "title": "Troubleshooting",
    "content": "Update Stuck . If the update appears frozen: . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | Try connecting via USB to a computer | Use the web flasher in recovery/DFU mode | Flash a known-good firmware version | Check the Meshtastic Discord for device-specific recovery steps | . Compatibility Warnings . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | Firmware version | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/firmware.html#troubleshooting",
    
    "relUrl": "/ar-rSA/user/firmware.html#troubleshooting"
  },"1612": {
    "doc": "Firmware Updates",
    "title": "Related Topics",
    "content": ". | Connections — reconnecting after a firmware update | Flashing firmware guide — full firmware flashing walkthrough on meshtastic.org | Supported devices — check firmware compatibility by device | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/firmware.html#related-topics",
    
    "relUrl": "/ar-rSA/user/firmware.html#related-topics"
  },"1613": {
    "doc": "Firmware Updates",
    "title": "Firmware Updates",
    "content": "Keep your Meshtastic radio up to date with the latest firmware for new features, bug fixes, and security improvements. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/firmware.html",
    
    "relUrl": "/hr-rHR/user/firmware.html"
  },"1614": {
    "doc": "Firmware Updates",
    "title": "Checking for Updates",
    "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable radios. | The app checks for available firmware versions. | Available updates show the version number and changelog summary. | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/firmware.html#checking-for-updates",
    
    "relUrl": "/hr-rHR/user/firmware.html#checking-for-updates"
  },"1615": {
    "doc": "Firmware Updates",
    "title": "Update Methods",
    "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | Wait for the update to complete — do not disconnect during the update. | . Erase device during update . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Wipes the device’s flash completely, then installs the selected firmware from scratch. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. In-App USB Update . When your radio is connected over USB/serial (rather than Bluetooth), the Firmware Update screen offers USB File Transfer. The app reboots the device into DFU mode, then prompts you to save the .uf2 file to the device’s DFU drive using the system file picker. This option appears only on a USB/serial connection — it is not available over Bluetooth. ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. A bootloader supplied as an update-....uf2 can be installed by copying it to the drive; that is how the app’s own bootloader upgrade works. The app surfaces a hint when the serial-only route applies. Factory Erase and Bootloader Upgrade . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. The app reads INFO_UF2.TXT from the drive you select to confirm it really is the device’s update drive and to identify the board before writing anything. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Other Flashing Options . For recovery or when neither OTA nor in-app USB is available: . | Use the Meshtastic Web Flasher | Or the Meshtastic CLI tool on desktop | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/firmware.html#update-methods",
    
    "relUrl": "/hr-rHR/user/firmware.html#update-methods"
  },"1616": {
    "doc": "Firmware Updates",
    "title": "Version Channels",
    "content": "| Kanal | Opis | . | Stable | Recommended for most users; tested releases | . | Alpha | Preview releases; may contain bugs | . | Local File | Flash a firmware file you select yourself, instead of a downloaded release | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/firmware.html#version-channels",
    
    "relUrl": "/hr-rHR/user/firmware.html#version-channels"
  },"1617": {
    "doc": "Firmware Updates",
    "title": "Pre-Update Checklist",
    "content": "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 | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/firmware.html#pre-update-checklist",
    
    "relUrl": "/hr-rHR/user/firmware.html#pre-update-checklist"
  },"1618": {
    "doc": "Firmware Updates",
    "title": "Post-Update",
    "content": "After the firmware is written, the app verifies the update and waits for the device to come back online: . Once the update succeeds: . | The radio reboots automatically | The Bluetooth connection re-establishes | Verify your settings are intact | Confirm the new version under Currently Installed on the Firmware Update screen — it’s also shown on the node’s detail page and the Connections screen | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/firmware.html#post-update",
    
    "relUrl": "/hr-rHR/user/firmware.html#post-update"
  },"1619": {
    "doc": "Firmware Updates",
    "title": "Troubleshooting",
    "content": "Update Stuck . If the update appears frozen: . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | Try connecting via USB to a computer | Use the web flasher in recovery/DFU mode | Flash a known-good firmware version | Check the Meshtastic Discord for device-specific recovery steps | . Compatibility Warnings . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | Firmware version | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/firmware.html#troubleshooting",
    
    "relUrl": "/hr-rHR/user/firmware.html#troubleshooting"
  },"1620": {
    "doc": "Firmware Updates",
    "title": "Related Topics",
    "content": ". | Connections — reconnecting after a firmware update | Flashing firmware guide — full firmware flashing walkthrough on meshtastic.org | Supported devices — check firmware compatibility by device | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/firmware.html#related-topics",
    
    "relUrl": "/hr-rHR/user/firmware.html#related-topics"
  },"1621": {
    "doc": "Firmware Updates",
    "title": "Firmware Updates",
    "content": "Keep your Meshtastic radio up to date with the latest firmware for new features, bug fixes, and security improvements. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/firmware.html",
    
    "relUrl": "/pt-rPT/user/firmware.html"
  },"1622": {
    "doc": "Firmware Updates",
    "title": "Checking for Updates",
    "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable radios. | The app checks for available firmware versions. | Available updates show the version number and changelog summary. | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/firmware.html#checking-for-updates",
    
    "relUrl": "/pt-rPT/user/firmware.html#checking-for-updates"
  },"1623": {
    "doc": "Firmware Updates",
    "title": "Update Methods",
    "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | Wait for the update to complete — do not disconnect during the update. | . Erase device during update . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Wipes the device’s flash completely, then installs the selected firmware from scratch. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. In-App USB Update . When your radio is connected over USB/serial (rather than Bluetooth), the Firmware Update screen offers USB File Transfer. The app reboots the device into DFU mode, then prompts you to save the .uf2 file to the device’s DFU drive using the system file picker. This option appears only on a USB/serial connection — it is not available over Bluetooth. ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. A bootloader supplied as an update-....uf2 can be installed by copying it to the drive; that is how the app’s own bootloader upgrade works. The app surfaces a hint when the serial-only route applies. Factory Erase and Bootloader Upgrade . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. The app reads INFO_UF2.TXT from the drive you select to confirm it really is the device’s update drive and to identify the board before writing anything. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Other Flashing Options . For recovery or when neither OTA nor in-app USB is available: . | Use the Meshtastic Web Flasher | Or the Meshtastic CLI tool on desktop | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/firmware.html#update-methods",
    
    "relUrl": "/pt-rPT/user/firmware.html#update-methods"
  },"1624": {
    "doc": "Firmware Updates",
    "title": "Version Channels",
    "content": "| Canal | Descrição | . | Stable | Recommended for most users; tested releases | . | Alpha | Preview releases; may contain bugs | . | Local File | Flash a firmware file you select yourself, instead of a downloaded release | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/firmware.html#version-channels",
    
    "relUrl": "/pt-rPT/user/firmware.html#version-channels"
  },"1625": {
    "doc": "Firmware Updates",
    "title": "Pre-Update Checklist",
    "content": "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 | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/firmware.html#pre-update-checklist",
    
    "relUrl": "/pt-rPT/user/firmware.html#pre-update-checklist"
  },"1626": {
    "doc": "Firmware Updates",
    "title": "Post-Update",
    "content": "After the firmware is written, the app verifies the update and waits for the device to come back online: . Once the update succeeds: . | The radio reboots automatically | The Bluetooth connection re-establishes | Verify your settings are intact | Confirm the new version under Currently Installed on the Firmware Update screen — it’s also shown on the node’s detail page and the Connections screen | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/firmware.html#post-update",
    
    "relUrl": "/pt-rPT/user/firmware.html#post-update"
  },"1627": {
    "doc": "Firmware Updates",
    "title": "Troubleshooting",
    "content": "Update Stuck . If the update appears frozen: . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | Try connecting via USB to a computer | Use the web flasher in recovery/DFU mode | Flash a known-good firmware version | Check the Meshtastic Discord for device-specific recovery steps | . Compatibility Warnings . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | Versão do firmware | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/firmware.html#troubleshooting",
    
    "relUrl": "/pt-rPT/user/firmware.html#troubleshooting"
  },"1628": {
    "doc": "Firmware Updates",
    "title": "Related Topics",
    "content": ". | Connections — reconnecting after a firmware update | Flashing firmware guide — full firmware flashing walkthrough on meshtastic.org | Supported devices — check firmware compatibility by device | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/firmware.html#related-topics",
    
    "relUrl": "/pt-rPT/user/firmware.html#related-topics"
  },"1629": {
    "doc": "Firmware Updates",
    "title": "Firmware Updates",
    "content": "Keep your Meshtastic radio up to date with the latest firmware for new features, bug fixes, and security improvements. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/firmware.html",
    
    "relUrl": "/pl-rPL/user/firmware.html"
  },"1630": {
    "doc": "Firmware Updates",
    "title": "Checking for Updates",
    "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable radios. | The app checks for available firmware versions. | Available updates show the version number and changelog summary. | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/firmware.html#checking-for-updates",
    
    "relUrl": "/pl-rPL/user/firmware.html#checking-for-updates"
  },"1631": {
    "doc": "Firmware Updates",
    "title": "Update Methods",
    "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | Wait for the update to complete — do not disconnect during the update. | . Erase device during update . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Wipes the device’s flash completely, then installs the selected firmware from scratch. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. In-App USB Update . When your radio is connected over USB/serial (rather than Bluetooth), the Firmware Update screen offers USB File Transfer. The app reboots the device into DFU mode, then prompts you to save the .uf2 file to the device’s DFU drive using the system file picker. This option appears only on a USB/serial connection — it is not available over Bluetooth. ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. A bootloader supplied as an update-....uf2 can be installed by copying it to the drive; that is how the app’s own bootloader upgrade works. The app surfaces a hint when the serial-only route applies. Factory Erase and Bootloader Upgrade . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. The app reads INFO_UF2.TXT from the drive you select to confirm it really is the device’s update drive and to identify the board before writing anything. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Other Flashing Options . For recovery or when neither OTA nor in-app USB is available: . | Use the Meshtastic Web Flasher | Or the Meshtastic CLI tool on desktop | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/firmware.html#update-methods",
    
    "relUrl": "/pl-rPL/user/firmware.html#update-methods"
  },"1632": {
    "doc": "Firmware Updates",
    "title": "Version Channels",
    "content": "| Kanał | Opis | . | Stabilna | Recommended for most users; tested releases | . | Alpha | Preview releases; may contain bugs | . | Local File | Flash a firmware file you select yourself, instead of a downloaded release | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/firmware.html#version-channels",
    
    "relUrl": "/pl-rPL/user/firmware.html#version-channels"
  },"1633": {
    "doc": "Firmware Updates",
    "title": "Pre-Update Checklist",
    "content": "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 | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/firmware.html#pre-update-checklist",
    
    "relUrl": "/pl-rPL/user/firmware.html#pre-update-checklist"
  },"1634": {
    "doc": "Firmware Updates",
    "title": "Post-Update",
    "content": "After the firmware is written, the app verifies the update and waits for the device to come back online: . Once the update succeeds: . | The radio reboots automatically | The Bluetooth connection re-establishes | Verify your settings are intact | Confirm the new version under Currently Installed on the Firmware Update screen — it’s also shown on the node’s detail page and the Connections screen | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/firmware.html#post-update",
    
    "relUrl": "/pl-rPL/user/firmware.html#post-update"
  },"1635": {
    "doc": "Firmware Updates",
    "title": "Troubleshooting",
    "content": "Update Stuck . If the update appears frozen: . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | Try connecting via USB to a computer | Use the web flasher in recovery/DFU mode | Flash a known-good firmware version | Check the Meshtastic Discord for device-specific recovery steps | . Compatibility Warnings . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | Wersja firmware | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/firmware.html#troubleshooting",
    
    "relUrl": "/pl-rPL/user/firmware.html#troubleshooting"
  },"1636": {
    "doc": "Firmware Updates",
    "title": "Related Topics",
    "content": ". | Connections — reconnecting after a firmware update | Flashing firmware guide — full firmware flashing walkthrough on meshtastic.org | Supported devices — check firmware compatibility by device | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/firmware.html#related-topics",
    
    "relUrl": "/pl-rPL/user/firmware.html#related-topics"
  },"1637": {
    "doc": "固件升级",
    "title": "固件升级",
    "content": "Keep your Meshtastic radio up to date with the latest firmware for new features, bug fixes, and security improvements. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/firmware.html",
    
    "relUrl": "/zh-rCN/user/firmware.html"
  },"1638": {
    "doc": "固件升级",
    "title": "Checking for Updates",
    "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable radios. | The app checks for available firmware versions. | Available updates show the version number and changelog summary. | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/firmware.html#checking-for-updates",
    
    "relUrl": "/zh-rCN/user/firmware.html#checking-for-updates"
  },"1639": {
    "doc": "固件升级",
    "title": "Update Methods",
    "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | Wait for the update to complete — do not disconnect during the update. | . Erase device during update . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Wipes the device’s flash completely, then installs the selected firmware from scratch. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. In-App USB Update . When your radio is connected over USB/serial (rather than Bluetooth), the Firmware Update screen offers USB File Transfer. The app reboots the device into DFU mode, then prompts you to save the .uf2 file to the device’s DFU drive using the system file picker. This option appears only on a USB/serial connection — it is not available over Bluetooth. ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. A bootloader supplied as an update-....uf2 can be installed by copying it to the drive; that is how the app’s own bootloader upgrade works. The app surfaces a hint when the serial-only route applies. Factory Erase and Bootloader Upgrade . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. The app reads INFO_UF2.TXT from the drive you select to confirm it really is the device’s update drive and to identify the board before writing anything. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Other Flashing Options . For recovery or when neither OTA nor in-app USB is available: . | Use the Meshtastic Web Flasher | Or the Meshtastic CLI tool on desktop | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/firmware.html#update-methods",
    
    "relUrl": "/zh-rCN/user/firmware.html#update-methods"
  },"1640": {
    "doc": "固件升级",
    "title": "Version Channels",
    "content": "| 频道 | 说明 | . | 稳定版本 | Recommended for most users; tested releases | . | 开发版本 | Preview releases; may contain bugs | . | 本地文件 | Flash a firmware file you select yourself, instead of a downloaded release | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/firmware.html#version-channels",
    
    "relUrl": "/zh-rCN/user/firmware.html#version-channels"
  },"1641": {
    "doc": "固件升级",
    "title": "Pre-Update Checklist",
    "content": "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 | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/firmware.html#pre-update-checklist",
    
    "relUrl": "/zh-rCN/user/firmware.html#pre-update-checklist"
  },"1642": {
    "doc": "固件升级",
    "title": "Post-Update",
    "content": "After the firmware is written, the app verifies the update and waits for the device to come back online: . Once the update succeeds: . | The radio reboots automatically | The Bluetooth connection re-establishes | Verify your settings are intact | Confirm the new version under Currently Installed on the Firmware Update screen — it’s also shown on the node’s detail page and the Connections screen | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/firmware.html#post-update",
    
    "relUrl": "/zh-rCN/user/firmware.html#post-update"
  },"1643": {
    "doc": "固件升级",
    "title": "问题排查",
    "content": "Update Stuck . If the update appears frozen: . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | Try connecting via USB to a computer | Use the web flasher in recovery/DFU mode | Flash a known-good firmware version | Check the Meshtastic Discord for device-specific recovery steps | . Compatibility Warnings . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | 固件版本 | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/firmware.html#%E9%97%AE%E9%A2%98%E6%8E%92%E6%9F%A5",
    
    "relUrl": "/zh-rCN/user/firmware.html#问题排查"
  },"1644": {
    "doc": "固件升级",
    "title": "Related Topics",
    "content": ". | Connections — reconnecting after a firmware update | Flashing firmware guide — full firmware flashing walkthrough on meshtastic.org | Supported devices — check firmware compatibility by device | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/firmware.html#related-topics",
    
    "relUrl": "/zh-rCN/user/firmware.html#related-topics"
  },"1645": {
    "doc": "Firmware Updates",
    "title": "Firmware Updates",
    "content": "Keep your Meshtastic radio up to date with the latest firmware for new features, bug fixes, and security improvements. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/firmware.html",
    
    "relUrl": "/sq-rAL/user/firmware.html"
  },"1646": {
    "doc": "Firmware Updates",
    "title": "Checking for Updates",
    "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable radios. | The app checks for available firmware versions. | Available updates show the version number and changelog summary. | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/firmware.html#checking-for-updates",
    
    "relUrl": "/sq-rAL/user/firmware.html#checking-for-updates"
  },"1647": {
    "doc": "Firmware Updates",
    "title": "Update Methods",
    "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | Wait for the update to complete — do not disconnect during the update. | . Erase device during update . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Wipes the device’s flash completely, then installs the selected firmware from scratch. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. In-App USB Update . When your radio is connected over USB/serial (rather than Bluetooth), the Firmware Update screen offers USB File Transfer. The app reboots the device into DFU mode, then prompts you to save the .uf2 file to the device’s DFU drive using the system file picker. This option appears only on a USB/serial connection — it is not available over Bluetooth. ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. A bootloader supplied as an update-....uf2 can be installed by copying it to the drive; that is how the app’s own bootloader upgrade works. The app surfaces a hint when the serial-only route applies. Factory Erase and Bootloader Upgrade . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. The app reads INFO_UF2.TXT from the drive you select to confirm it really is the device’s update drive and to identify the board before writing anything. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Other Flashing Options . For recovery or when neither OTA nor in-app USB is available: . | Use the Meshtastic Web Flasher | Or the Meshtastic CLI tool on desktop | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/firmware.html#update-methods",
    
    "relUrl": "/sq-rAL/user/firmware.html#update-methods"
  },"1648": {
    "doc": "Firmware Updates",
    "title": "Version Channels",
    "content": "| Kanal | Përshkrimi | . | Stable | Recommended for most users; tested releases | . | Alpha | Preview releases; may contain bugs | . | Local File | Flash a firmware file you select yourself, instead of a downloaded release | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/firmware.html#version-channels",
    
    "relUrl": "/sq-rAL/user/firmware.html#version-channels"
  },"1649": {
    "doc": "Firmware Updates",
    "title": "Pre-Update Checklist",
    "content": "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 | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/firmware.html#pre-update-checklist",
    
    "relUrl": "/sq-rAL/user/firmware.html#pre-update-checklist"
  },"1650": {
    "doc": "Firmware Updates",
    "title": "Post-Update",
    "content": "After the firmware is written, the app verifies the update and waits for the device to come back online: . Once the update succeeds: . | The radio reboots automatically | The Bluetooth connection re-establishes | Verify your settings are intact | Confirm the new version under Currently Installed on the Firmware Update screen — it’s also shown on the node’s detail page and the Connections screen | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/firmware.html#post-update",
    
    "relUrl": "/sq-rAL/user/firmware.html#post-update"
  },"1651": {
    "doc": "Firmware Updates",
    "title": "Troubleshooting",
    "content": "Update Stuck . If the update appears frozen: . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | Try connecting via USB to a computer | Use the web flasher in recovery/DFU mode | Flash a known-good firmware version | Check the Meshtastic Discord for device-specific recovery steps | . Compatibility Warnings . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | Firmware version | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/firmware.html#troubleshooting",
    
    "relUrl": "/sq-rAL/user/firmware.html#troubleshooting"
  },"1652": {
    "doc": "Firmware Updates",
    "title": "Related Topics",
    "content": ". | Connections — reconnecting after a firmware update | Flashing firmware guide — full firmware flashing walkthrough on meshtastic.org | Supported devices — check firmware compatibility by device | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/firmware.html#related-topics",
    
    "relUrl": "/sq-rAL/user/firmware.html#related-topics"
  },"1653": {
    "doc": "韌體更新",
    "title": "韌體更新",
    "content": "保持 Meshtastic 無線電裝置的韌體為最新版本，以取得新功能、錯誤修正與安全性改善。 . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/firmware.html",
    
    "relUrl": "/zh-rTW/user/firmware.html"
  },"1654": {
    "doc": "韌體更新",
    "title": "檢查更新",
    "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable radios. | 應用程式將檢查可用的韌體版本。 | 如有可用更新將顯示版本號碼與更新記錄摘要。 | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/firmware.html#%E6%AA%A2%E6%9F%A5%E6%9B%B4%E6%96%B0",
    
    "relUrl": "/zh-rTW/user/firmware.html#檢查更新"
  },"1655": {
    "doc": "韌體更新",
    "title": "更新方式",
    "content": "OTA（無線空中下載）透過藍牙 . Android 使用者最常用的更新方式： . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | 請確認您的無線電裝置已透過藍牙連線。 | 前往韌體更新畫面。 | 選取所需的韌體版本。 | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | 請等待更新完成 — 更新期間請勿中斷連線。 | . Erase device during update . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Wipes the device’s flash completely, then installs the selected firmware from scratch. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. In-App USB Update . When your radio is connected over USB/serial (rather than Bluetooth), the Firmware Update screen offers USB File Transfer. The app reboots the device into DFU mode, then prompts you to save the .uf2 file to the device’s DFU drive using the system file picker. This option appears only on a USB/serial connection — it is not available over Bluetooth. ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. A bootloader supplied as an update-....uf2 can be installed by copying it to the drive; that is how the app’s own bootloader upgrade works. The app surfaces a hint when the serial-only route applies. Factory Erase and Bootloader Upgrade . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. The app reads INFO_UF2.TXT from the drive you select to confirm it really is the device’s update drive and to identify the board before writing anything. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Other Flashing Options . For recovery or when neither OTA nor in-app USB is available: . | 請使用〔Meshtastic 網頁燒錄工具〕(https://flasher.meshtastic.org) | 或在桌面版使用〔Meshtastic CLI 工具〕(https://meshtastic.org/docs/getting-started/flashing-firmware) | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/firmware.html#%E6%9B%B4%E6%96%B0%E6%96%B9%E5%BC%8F",
    
    "relUrl": "/zh-rTW/user/firmware.html#更新方式"
  },"1656": {
    "doc": "韌體更新",
    "title": "版本頻道",
    "content": "| 頻道 | 描述說明 | . | 穩定版 | 建議大多數使用者採用；已測試的正式版本 | . | Alpha 測試版 | 預覽版本；可能包含錯誤 | . | 本機檔案 | Flash a firmware file you select yourself, instead of a downloaded release | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/firmware.html#%E7%89%88%E6%9C%AC%E9%A0%BB%E9%81%93",
    
    "relUrl": "/zh-rTW/user/firmware.html#版本頻道"
  },"1657": {
    "doc": "韌體更新",
    "title": "更新前檢查清單",
    "content": "更新前請確認： . | 電量 > 50% | 藍牙連線穩定 | 記錄目前的設定（主要版本更新時可能會重設） | 查看版本說明中是否有重大變更 | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/firmware.html#%E6%9B%B4%E6%96%B0%E5%89%8D%E6%AA%A2%E6%9F%A5%E6%B8%85%E5%96%AE",
    
    "relUrl": "/zh-rTW/user/firmware.html#更新前檢查清單"
  },"1658": {
    "doc": "韌體更新",
    "title": "更新後",
    "content": "After the firmware is written, the app verifies the update and waits for the device to come back online: . Once the update succeeds: . | The radio reboots automatically | The Bluetooth connection re-establishes | 確認您的設定完整無缺 | Confirm the new version under Currently Installed on the Firmware Update screen — it’s also shown on the node’s detail page and the Connections screen | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/firmware.html#%E6%9B%B4%E6%96%B0%E5%BE%8C",
    
    "relUrl": "/zh-rTW/user/firmware.html#更新後"
  },"1659": {
    "doc": "韌體更新",
    "title": "故障排除",
    "content": "更新卡住 . 若更新似乎停滯不動： . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | 請嘗試透過 USB 連接至電腦 | 在復原／DFU 模式下使用網頁燒錄工具 | 燒錄已知可正常運作的韌體版本 | 前往 Meshtastic Discord 查詢特定裝置的復原步驟 | . 相容性警告 . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | 韌體版本 | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/firmware.html#%E6%95%85%E9%9A%9C%E6%8E%92%E9%99%A4",
    
    "relUrl": "/zh-rTW/user/firmware.html#故障排除"
  },"1660": {
    "doc": "韌體更新",
    "title": "相關主題",
    "content": ". | 〔連線〕(connections)——韌體更新後重新連線 | (https://meshtastic.org/docs/getting-started/flashing-firmware) — meshtastic.org 上的完整韌體燒錄操作說明 | 〔支援的裝置〕(https://meshtastic.org/docs/hardware/devices) https://meshtastic.org/docs/hardware/devices — 依裝置查詢韌體相容性 | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/firmware.html#%E7%9B%B8%E9%97%9C%E4%B8%BB%E9%A1%8C",
    
    "relUrl": "/zh-rTW/user/firmware.html#相關主題"
  },"1661": {
    "doc": "Püsivara värskendus",
    "title": "Püsivara värskendus",
    "content": "Hoia oma Meshtastic raadio ajakohasena uusima püsivaraga, et saada uusi funktsioone, veaparandusi ja turvalisuse täiustusi. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/firmware.html",
    
    "relUrl": "/et-rEE/user/firmware.html"
  },"1662": {
    "doc": "Püsivara värskendus",
    "title": "Kontrollin värskendust",
    "content": ". | Ava ühendatud raadio konfiguratsioon ja puuduta jaotises Täpsemalt valikut Püsivara värskendus. The entry appears only for OTA-capable radios. | Rakendus kontrollib saadaolevaid püsivara versioone. | Saadaval olevad värskendused näitavad versiooninumbrit ja muudatuste logi kokkuvõtet. | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/firmware.html#kontrollin-v%C3%A4rskendust",
    
    "relUrl": "/et-rEE/user/firmware.html#kontrollin-värskendust"
  },"1663": {
    "doc": "Püsivara värskendus",
    "title": "Värskendamise meetod",
    "content": "OTA (Over-The-Air) sinihamba abil . Kõige levinum värskendamisviis Androidi kasutajate seas: . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | Veendu, et raadio on sinihamba ​​kaudu ühendatud. | Mine püsivara värskenduse lehele. | Vali soovitud püsivara versioon. | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | Oota, kuni värskendus on lõppenud – ära katkesta ühendust värskenduse ajal. | . Tühjendada seade uuendamise käigus . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Puhastab seadme välkmälu täielikult ja paigaldab seejärel valitud püsivara nullist. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. Rakendusesisene USB värskendus . Kui raadio on ühendatud USB/jadaühenduse (mitte sinihamba) kaudu, pakub püsivara värskendamise ekraan USB failiedastust. Rakendus taaskäivitab seadme DFU-režiimis ja seejärel palub süsteemifailide valija abil salvestada .uf2-fail seadme DFU kettale. See valik kuvatakse ainult USB/jadaühenduse korral – see pole sinihamba ​​kaudu saadaval. ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. Failina pakutavat alglaadur update-....uf2 saab installida selle kettale kopeerimise teel; nii töötabki rakenduse enda alglaaduri uuendamine. The app surfaces a hint when the serial-only route applies. Factory Erase and Bootloader Upgrade . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. Rakendus loeb valitud kettalt faili INFO_UF2.TXT, et veenduda, kas see on tõepoolest seadme uuendusketas ja enne millegi kirjutamist plaat tuvastada. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Muud püsivarauuenduse valikud . For recovery or when neither OTA nor in-app USB is available: . | Kasuta Meshtastic Web Flasherit | Või arvutil Meshtastic CLI tööriist | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/firmware.html#v%C3%A4rskendamise-meetod",
    
    "relUrl": "/et-rEE/user/firmware.html#värskendamise-meetod"
  },"1664": {
    "doc": "Püsivara värskendus",
    "title": "Versioonikanalid",
    "content": "| Kanal | Kirjeldus | . | Stabiilne | Soovitatav enamusele kasutajatele; testitud versioonid | . | Alfa | Eelvaateversioonid; võivad sisaldada vigu | . | Lokaalne | Püsivarauuenda ise valitud püsivara failga, allalaetud versiooni asemel | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/firmware.html#versioonikanalid",
    
    "relUrl": "/et-rEE/user/firmware.html#versioonikanalid"
  },"1665": {
    "doc": "Püsivara värskendus",
    "title": "Eelvärskenduse kontrollnimekiri",
    "content": "Enne uuendamist: . | Aku > 50% | Stabiilne sinihamba ühendus | Pane tähele oma praeguseid seadeid (need võivad oluliste versioonimuudatuste korral lähtestuda) | Check the release notes for breaking changes | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/firmware.html#eelv%C3%A4rskenduse-kontrollnimekiri",
    
    "relUrl": "/et-rEE/user/firmware.html#eelvärskenduse-kontrollnimekiri"
  },"1666": {
    "doc": "Püsivara värskendus",
    "title": "Eelvärskendus",
    "content": "Pärast püsivara kirjutamist kontrollib rakendus värskendust ja ootab, kuni seade taas võrku lülitub: . Kui värskendus õnnestub: . | The radio reboots automatically | The Bluetooth connection re-establishes | Veendu, et seaded on puutumatud | Kontrolli uut versiooni püsivara värskenduse ekraanil jaotises Praegu paigaldatud – see kuvatakse ka sõlme üksikasjade lehel ja ühenduste ekraanil | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/firmware.html#eelv%C3%A4rskendus",
    
    "relUrl": "/et-rEE/user/firmware.html#eelvärskendus"
  },"1667": {
    "doc": "Püsivara värskendus",
    "title": "Veaotsing",
    "content": "Värskendus on ummikus . Kui värskendus näib olevat hangunud: . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | Try connecting via USB to a computer | Kasuta veebi püsivarauuendust taaste/DFU režiimis | Püsivarauuenda teadaolevalt toimiva püsivara versiooniga | Seadmepõhiste taastamissammude kohta vaata Meshtastic Discordist | . Compatibility Warnings . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | Püsivara versioon | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/firmware.html#veaotsing",
    
    "relUrl": "/et-rEE/user/firmware.html#veaotsing"
  },"1668": {
    "doc": "Püsivara värskendus",
    "title": "Seotud teemad",
    "content": ". | Ühendused — ühenduse loomine pärast püsivara värskendamist | Püsivara uuendamise juhend — täielik püsivara uuendamise juhend meshtastic.org lehel | Toetatud seadmed — ühilduvate raadiote täielik loetelu on leitav aadressilt meshtastic.org | KKK — meshtastic.org sageli esitatavad küsimused | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/firmware.html#seotud-teemad",
    
    "relUrl": "/et-rEE/user/firmware.html#seotud-teemad"
  },"1669": {
    "doc": "Firmware Updates",
    "title": "Firmware Updates",
    "content": "Keep your Meshtastic radio up to date with the latest firmware for new features, bug fixes, and security improvements. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/firmware.html",
    
    "relUrl": "/fr-rFR/user/firmware.html"
  },"1670": {
    "doc": "Firmware Updates",
    "title": "Checking for Updates",
    "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable radios. | The app checks for available firmware versions. | Available updates show the version number and changelog summary. | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/firmware.html#checking-for-updates",
    
    "relUrl": "/fr-rFR/user/firmware.html#checking-for-updates"
  },"1671": {
    "doc": "Firmware Updates",
    "title": "Update Methods",
    "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | Wait for the update to complete — do not disconnect during the update. | . Erase device during update . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Wipes the device’s flash completely, then installs the selected firmware from scratch. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. In-App USB Update . When your radio is connected over USB/serial (rather than Bluetooth), the Firmware Update screen offers USB File Transfer. The app reboots the device into DFU mode, then prompts you to save the .uf2 file to the device’s DFU drive using the system file picker. This option appears only on a USB/serial connection — it is not available over Bluetooth. ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. A bootloader supplied as an update-....uf2 can be installed by copying it to the drive; that is how the app’s own bootloader upgrade works. The app surfaces a hint when the serial-only route applies. Factory Erase and Bootloader Upgrade . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. The app reads INFO_UF2.TXT from the drive you select to confirm it really is the device’s update drive and to identify the board before writing anything. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Other Flashing Options . For recovery or when neither OTA nor in-app USB is available: . | Use the Meshtastic Web Flasher | Or the Meshtastic CLI tool on desktop | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/firmware.html#update-methods",
    
    "relUrl": "/fr-rFR/user/firmware.html#update-methods"
  },"1672": {
    "doc": "Firmware Updates",
    "title": "Version Channels",
    "content": "| Canal | Description | . | Stable | Recommended for most users; tested releases | . | Alpha | Preview releases; may contain bugs | . | Fichier local | Flash a firmware file you select yourself, instead of a downloaded release | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/firmware.html#version-channels",
    
    "relUrl": "/fr-rFR/user/firmware.html#version-channels"
  },"1673": {
    "doc": "Firmware Updates",
    "title": "Pre-Update Checklist",
    "content": "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 | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/firmware.html#pre-update-checklist",
    
    "relUrl": "/fr-rFR/user/firmware.html#pre-update-checklist"
  },"1674": {
    "doc": "Firmware Updates",
    "title": "Post-Update",
    "content": "After the firmware is written, the app verifies the update and waits for the device to come back online: . Once the update succeeds: . | The radio reboots automatically | The Bluetooth connection re-establishes | Verify your settings are intact | Confirm the new version under Currently Installed on the Firmware Update screen — it’s also shown on the node’s detail page and the Connections screen | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/firmware.html#post-update",
    
    "relUrl": "/fr-rFR/user/firmware.html#post-update"
  },"1675": {
    "doc": "Firmware Updates",
    "title": "Troubleshooting",
    "content": "Update Stuck . If the update appears frozen: . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | Try connecting via USB to a computer | Use the web flasher in recovery/DFU mode | Flash a known-good firmware version | Check the Meshtastic Discord for device-specific recovery steps | . Compatibility Warnings . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | Version du microprogramme | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/firmware.html#troubleshooting",
    
    "relUrl": "/fr-rFR/user/firmware.html#troubleshooting"
  },"1676": {
    "doc": "Firmware Updates",
    "title": "Related Topics",
    "content": ". | Connections — reconnecting after a firmware update | Flashing firmware guide — full firmware flashing walkthrough on meshtastic.org | Supported devices — check firmware compatibility by device | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/firmware.html#related-topics",
    
    "relUrl": "/fr-rFR/user/firmware.html#related-topics"
  },"1677": {
    "doc": "Firmware Updates",
    "title": "Firmware Updates",
    "content": "Keep your Meshtastic radio up to date with the latest firmware for new features, bug fixes, and security improvements. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/firmware.html",
    
    "relUrl": "/tr-rTR/user/firmware.html"
  },"1678": {
    "doc": "Firmware Updates",
    "title": "Checking for Updates",
    "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable radios. | The app checks for available firmware versions. | Available updates show the version number and changelog summary. | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/firmware.html#checking-for-updates",
    
    "relUrl": "/tr-rTR/user/firmware.html#checking-for-updates"
  },"1679": {
    "doc": "Firmware Updates",
    "title": "Update Methods",
    "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | Wait for the update to complete — do not disconnect during the update. | . Erase device during update . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Wipes the device’s flash completely, then installs the selected firmware from scratch. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. In-App USB Update . When your radio is connected over USB/serial (rather than Bluetooth), the Firmware Update screen offers USB File Transfer. The app reboots the device into DFU mode, then prompts you to save the .uf2 file to the device’s DFU drive using the system file picker. This option appears only on a USB/serial connection — it is not available over Bluetooth. ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. A bootloader supplied as an update-....uf2 can be installed by copying it to the drive; that is how the app’s own bootloader upgrade works. The app surfaces a hint when the serial-only route applies. Factory Erase and Bootloader Upgrade . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. The app reads INFO_UF2.TXT from the drive you select to confirm it really is the device’s update drive and to identify the board before writing anything. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Other Flashing Options . For recovery or when neither OTA nor in-app USB is available: . | Use the Meshtastic Web Flasher | Or the Meshtastic CLI tool on desktop | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/firmware.html#update-methods",
    
    "relUrl": "/tr-rTR/user/firmware.html#update-methods"
  },"1680": {
    "doc": "Firmware Updates",
    "title": "Version Channels",
    "content": "| Kanal | Açıklaması | . | Stable | Recommended for most users; tested releases | . | Alpha | Preview releases; may contain bugs | . | Local File | Flash a firmware file you select yourself, instead of a downloaded release | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/firmware.html#version-channels",
    
    "relUrl": "/tr-rTR/user/firmware.html#version-channels"
  },"1681": {
    "doc": "Firmware Updates",
    "title": "Pre-Update Checklist",
    "content": "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 | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/firmware.html#pre-update-checklist",
    
    "relUrl": "/tr-rTR/user/firmware.html#pre-update-checklist"
  },"1682": {
    "doc": "Firmware Updates",
    "title": "Post-Update",
    "content": "After the firmware is written, the app verifies the update and waits for the device to come back online: . Once the update succeeds: . | The radio reboots automatically | The Bluetooth connection re-establishes | Verify your settings are intact | Confirm the new version under Currently Installed on the Firmware Update screen — it’s also shown on the node’s detail page and the Connections screen | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/firmware.html#post-update",
    
    "relUrl": "/tr-rTR/user/firmware.html#post-update"
  },"1683": {
    "doc": "Firmware Updates",
    "title": "Troubleshooting",
    "content": "Update Stuck . If the update appears frozen: . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | Try connecting via USB to a computer | Use the web flasher in recovery/DFU mode | Flash a known-good firmware version | Check the Meshtastic Discord for device-specific recovery steps | . Compatibility Warnings . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | Yazılım sürümü | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/firmware.html#troubleshooting",
    
    "relUrl": "/tr-rTR/user/firmware.html#troubleshooting"
  },"1684": {
    "doc": "Firmware Updates",
    "title": "Related Topics",
    "content": ". | Connections — reconnecting after a firmware update | Flashing firmware guide — full firmware flashing walkthrough on meshtastic.org | Supported devices — check firmware compatibility by device | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/firmware.html#related-topics",
    
    "relUrl": "/tr-rTR/user/firmware.html#related-topics"
  },"1685": {
    "doc": "Firmware Updates",
    "title": "Firmware Updates",
    "content": "Keep your Meshtastic radio up to date with the latest firmware for new features, bug fixes, and security improvements. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/firmware.html",
    
    "relUrl": "/el-rGR/user/firmware.html"
  },"1686": {
    "doc": "Firmware Updates",
    "title": "Checking for Updates",
    "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable radios. | The app checks for available firmware versions. | Available updates show the version number and changelog summary. | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/firmware.html#checking-for-updates",
    
    "relUrl": "/el-rGR/user/firmware.html#checking-for-updates"
  },"1687": {
    "doc": "Firmware Updates",
    "title": "Update Methods",
    "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | Wait for the update to complete — do not disconnect during the update. | . Erase device during update . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Wipes the device’s flash completely, then installs the selected firmware from scratch. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. In-App USB Update . When your radio is connected over USB/serial (rather than Bluetooth), the Firmware Update screen offers USB File Transfer. The app reboots the device into DFU mode, then prompts you to save the .uf2 file to the device’s DFU drive using the system file picker. This option appears only on a USB/serial connection — it is not available over Bluetooth. ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. A bootloader supplied as an update-....uf2 can be installed by copying it to the drive; that is how the app’s own bootloader upgrade works. The app surfaces a hint when the serial-only route applies. Factory Erase and Bootloader Upgrade . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. The app reads INFO_UF2.TXT from the drive you select to confirm it really is the device’s update drive and to identify the board before writing anything. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Other Flashing Options . For recovery or when neither OTA nor in-app USB is available: . | Use the Meshtastic Web Flasher | Or the Meshtastic CLI tool on desktop | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/firmware.html#update-methods",
    
    "relUrl": "/el-rGR/user/firmware.html#update-methods"
  },"1688": {
    "doc": "Firmware Updates",
    "title": "Version Channels",
    "content": "| Κανάλι | Περιγραφή | . | Stable | Recommended for most users; tested releases | . | Alpha | Preview releases; may contain bugs | . | Local File | Flash a firmware file you select yourself, instead of a downloaded release | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/firmware.html#version-channels",
    
    "relUrl": "/el-rGR/user/firmware.html#version-channels"
  },"1689": {
    "doc": "Firmware Updates",
    "title": "Pre-Update Checklist",
    "content": "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 | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/firmware.html#pre-update-checklist",
    
    "relUrl": "/el-rGR/user/firmware.html#pre-update-checklist"
  },"1690": {
    "doc": "Firmware Updates",
    "title": "Post-Update",
    "content": "After the firmware is written, the app verifies the update and waits for the device to come back online: . Once the update succeeds: . | The radio reboots automatically | The Bluetooth connection re-establishes | Verify your settings are intact | Confirm the new version under Currently Installed on the Firmware Update screen — it’s also shown on the node’s detail page and the Connections screen | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/firmware.html#post-update",
    
    "relUrl": "/el-rGR/user/firmware.html#post-update"
  },"1691": {
    "doc": "Firmware Updates",
    "title": "Troubleshooting",
    "content": "Update Stuck . If the update appears frozen: . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | Try connecting via USB to a computer | Use the web flasher in recovery/DFU mode | Flash a known-good firmware version | Check the Meshtastic Discord for device-specific recovery steps | . Compatibility Warnings . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | Firmware version | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/firmware.html#troubleshooting",
    
    "relUrl": "/el-rGR/user/firmware.html#troubleshooting"
  },"1692": {
    "doc": "Firmware Updates",
    "title": "Related Topics",
    "content": ". | Connections — reconnecting after a firmware update | Flashing firmware guide — full firmware flashing walkthrough on meshtastic.org | Supported devices — check firmware compatibility by device | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/firmware.html#related-topics",
    
    "relUrl": "/el-rGR/user/firmware.html#related-topics"
  },"1693": {
    "doc": "Firmware Updates",
    "title": "Firmware Updates",
    "content": "Keep your Meshtastic radio up to date with the latest firmware for new features, bug fixes, and security improvements. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/firmware.html",
    
    "relUrl": "/ro-rRO/user/firmware.html"
  },"1694": {
    "doc": "Firmware Updates",
    "title": "Checking for Updates",
    "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable radios. | The app checks for available firmware versions. | Available updates show the version number and changelog summary. | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/firmware.html#checking-for-updates",
    
    "relUrl": "/ro-rRO/user/firmware.html#checking-for-updates"
  },"1695": {
    "doc": "Firmware Updates",
    "title": "Update Methods",
    "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | Wait for the update to complete — do not disconnect during the update. | . Erase device during update . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Wipes the device’s flash completely, then installs the selected firmware from scratch. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. In-App USB Update . When your radio is connected over USB/serial (rather than Bluetooth), the Firmware Update screen offers USB File Transfer. The app reboots the device into DFU mode, then prompts you to save the .uf2 file to the device’s DFU drive using the system file picker. This option appears only on a USB/serial connection — it is not available over Bluetooth. ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. A bootloader supplied as an update-....uf2 can be installed by copying it to the drive; that is how the app’s own bootloader upgrade works. The app surfaces a hint when the serial-only route applies. Factory Erase and Bootloader Upgrade . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. The app reads INFO_UF2.TXT from the drive you select to confirm it really is the device’s update drive and to identify the board before writing anything. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Other Flashing Options . For recovery or when neither OTA nor in-app USB is available: . | Use the Meshtastic Web Flasher | Or the Meshtastic CLI tool on desktop | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/firmware.html#update-methods",
    
    "relUrl": "/ro-rRO/user/firmware.html#update-methods"
  },"1696": {
    "doc": "Firmware Updates",
    "title": "Version Channels",
    "content": "| Canal | Descriere | . | Stabil | Recommended for most users; tested releases | . | Alpha | Preview releases; may contain bugs | . | Fișier local | Flash a firmware file you select yourself, instead of a downloaded release | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/firmware.html#version-channels",
    
    "relUrl": "/ro-rRO/user/firmware.html#version-channels"
  },"1697": {
    "doc": "Firmware Updates",
    "title": "Pre-Update Checklist",
    "content": "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 | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/firmware.html#pre-update-checklist",
    
    "relUrl": "/ro-rRO/user/firmware.html#pre-update-checklist"
  },"1698": {
    "doc": "Firmware Updates",
    "title": "Post-Update",
    "content": "After the firmware is written, the app verifies the update and waits for the device to come back online: . Once the update succeeds: . | The radio reboots automatically | The Bluetooth connection re-establishes | Verify your settings are intact | Confirm the new version under Currently Installed on the Firmware Update screen — it’s also shown on the node’s detail page and the Connections screen | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/firmware.html#post-update",
    
    "relUrl": "/ro-rRO/user/firmware.html#post-update"
  },"1699": {
    "doc": "Firmware Updates",
    "title": "Troubleshooting",
    "content": "Update Stuck . If the update appears frozen: . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | Try connecting via USB to a computer | Use the web flasher in recovery/DFU mode | Flash a known-good firmware version | Check the Meshtastic Discord for device-specific recovery steps | . Compatibility Warnings . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | Firmware version | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/firmware.html#troubleshooting",
    
    "relUrl": "/ro-rRO/user/firmware.html#troubleshooting"
  },"1700": {
    "doc": "Firmware Updates",
    "title": "Related Topics",
    "content": ". | Connections — reconnecting after a firmware update | Flashing firmware guide — full firmware flashing walkthrough on meshtastic.org | Supported devices — check firmware compatibility by device | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/firmware.html#related-topics",
    
    "relUrl": "/ro-rRO/user/firmware.html#related-topics"
  },"1701": {
    "doc": "Firmware Updates",
    "title": "Firmware Updates",
    "content": "Keep your Meshtastic radio up to date with the latest firmware for new features, bug fixes, and security improvements. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/firmware.html",
    
    "relUrl": "/iw-rIL/user/firmware.html"
  },"1702": {
    "doc": "Firmware Updates",
    "title": "Checking for Updates",
    "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable radios. | The app checks for available firmware versions. | Available updates show the version number and changelog summary. | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/firmware.html#checking-for-updates",
    
    "relUrl": "/iw-rIL/user/firmware.html#checking-for-updates"
  },"1703": {
    "doc": "Firmware Updates",
    "title": "Update Methods",
    "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | Wait for the update to complete — do not disconnect during the update. | . Erase device during update . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Wipes the device’s flash completely, then installs the selected firmware from scratch. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. In-App USB Update . When your radio is connected over USB/serial (rather than Bluetooth), the Firmware Update screen offers USB File Transfer. The app reboots the device into DFU mode, then prompts you to save the .uf2 file to the device’s DFU drive using the system file picker. This option appears only on a USB/serial connection — it is not available over Bluetooth. ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. A bootloader supplied as an update-....uf2 can be installed by copying it to the drive; that is how the app’s own bootloader upgrade works. The app surfaces a hint when the serial-only route applies. Factory Erase and Bootloader Upgrade . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. The app reads INFO_UF2.TXT from the drive you select to confirm it really is the device’s update drive and to identify the board before writing anything. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Other Flashing Options . For recovery or when neither OTA nor in-app USB is available: . | Use the Meshtastic Web Flasher | Or the Meshtastic CLI tool on desktop | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/firmware.html#update-methods",
    
    "relUrl": "/iw-rIL/user/firmware.html#update-methods"
  },"1704": {
    "doc": "Firmware Updates",
    "title": "Version Channels",
    "content": "| ערוץ | תיאור | . | Stable | Recommended for most users; tested releases | . | Alpha | Preview releases; may contain bugs | . | Local File | Flash a firmware file you select yourself, instead of a downloaded release | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/firmware.html#version-channels",
    
    "relUrl": "/iw-rIL/user/firmware.html#version-channels"
  },"1705": {
    "doc": "Firmware Updates",
    "title": "Pre-Update Checklist",
    "content": "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 | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/firmware.html#pre-update-checklist",
    
    "relUrl": "/iw-rIL/user/firmware.html#pre-update-checklist"
  },"1706": {
    "doc": "Firmware Updates",
    "title": "Post-Update",
    "content": "After the firmware is written, the app verifies the update and waits for the device to come back online: . Once the update succeeds: . | The radio reboots automatically | The Bluetooth connection re-establishes | Verify your settings are intact | Confirm the new version under Currently Installed on the Firmware Update screen — it’s also shown on the node’s detail page and the Connections screen | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/firmware.html#post-update",
    
    "relUrl": "/iw-rIL/user/firmware.html#post-update"
  },"1707": {
    "doc": "Firmware Updates",
    "title": "Troubleshooting",
    "content": "Update Stuck . If the update appears frozen: . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | Try connecting via USB to a computer | Use the web flasher in recovery/DFU mode | Flash a known-good firmware version | Check the Meshtastic Discord for device-specific recovery steps | . Compatibility Warnings . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | Firmware version | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/firmware.html#troubleshooting",
    
    "relUrl": "/iw-rIL/user/firmware.html#troubleshooting"
  },"1708": {
    "doc": "Firmware Updates",
    "title": "Related Topics",
    "content": ". | Connections — reconnecting after a firmware update | Flashing firmware guide — full firmware flashing walkthrough on meshtastic.org | Supported devices — check firmware compatibility by device | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/firmware.html#related-topics",
    
    "relUrl": "/iw-rIL/user/firmware.html#related-topics"
  },"1709": {
    "doc": "Firmware Updates",
    "title": "Firmware Updates",
    "content": "Keep your Meshtastic radio up to date with the latest firmware for new features, bug fixes, and security improvements. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/firmware.html",
    
    "relUrl": "/pt-rBR/user/firmware.html"
  },"1710": {
    "doc": "Firmware Updates",
    "title": "Checking for Updates",
    "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable radios. | The app checks for available firmware versions. | Available updates show the version number and changelog summary. | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/firmware.html#checking-for-updates",
    
    "relUrl": "/pt-rBR/user/firmware.html#checking-for-updates"
  },"1711": {
    "doc": "Firmware Updates",
    "title": "Update Methods",
    "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | Wait for the update to complete — do not disconnect during the update. | . Erase device during update . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Wipes the device’s flash completely, then installs the selected firmware from scratch. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. In-App USB Update . When your radio is connected over USB/serial (rather than Bluetooth), the Firmware Update screen offers USB File Transfer. The app reboots the device into DFU mode, then prompts you to save the .uf2 file to the device’s DFU drive using the system file picker. This option appears only on a USB/serial connection — it is not available over Bluetooth. ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. A bootloader supplied as an update-....uf2 can be installed by copying it to the drive; that is how the app’s own bootloader upgrade works. The app surfaces a hint when the serial-only route applies. Factory Erase and Bootloader Upgrade . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. The app reads INFO_UF2.TXT from the drive you select to confirm it really is the device’s update drive and to identify the board before writing anything. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Other Flashing Options . For recovery or when neither OTA nor in-app USB is available: . | Use the Meshtastic Web Flasher | Or the Meshtastic CLI tool on desktop | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/firmware.html#update-methods",
    
    "relUrl": "/pt-rBR/user/firmware.html#update-methods"
  },"1712": {
    "doc": "Firmware Updates",
    "title": "Version Channels",
    "content": "| Canal | Descrição | . | Stable | Recommended for most users; tested releases | . | Alpha | Preview releases; may contain bugs | . | Local File | Flash a firmware file you select yourself, instead of a downloaded release | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/firmware.html#version-channels",
    
    "relUrl": "/pt-rBR/user/firmware.html#version-channels"
  },"1713": {
    "doc": "Firmware Updates",
    "title": "Pre-Update Checklist",
    "content": "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 | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/firmware.html#pre-update-checklist",
    
    "relUrl": "/pt-rBR/user/firmware.html#pre-update-checklist"
  },"1714": {
    "doc": "Firmware Updates",
    "title": "Post-Update",
    "content": "After the firmware is written, the app verifies the update and waits for the device to come back online: . Once the update succeeds: . | The radio reboots automatically | The Bluetooth connection re-establishes | Verify your settings are intact | Confirm the new version under Currently Installed on the Firmware Update screen — it’s also shown on the node’s detail page and the Connections screen | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/firmware.html#post-update",
    
    "relUrl": "/pt-rBR/user/firmware.html#post-update"
  },"1715": {
    "doc": "Firmware Updates",
    "title": "Troubleshooting",
    "content": "Update Stuck . If the update appears frozen: . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | Try connecting via USB to a computer | Use the web flasher in recovery/DFU mode | Flash a known-good firmware version | Check the Meshtastic Discord for device-specific recovery steps | . Compatibility Warnings . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | Versão do firmware | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/firmware.html#troubleshooting",
    
    "relUrl": "/pt-rBR/user/firmware.html#troubleshooting"
  },"1716": {
    "doc": "Firmware Updates",
    "title": "Related Topics",
    "content": ". | Connections — reconnecting after a firmware update | Flashing firmware guide — full firmware flashing walkthrough on meshtastic.org | Supported devices — check firmware compatibility by device | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/firmware.html#related-topics",
    
    "relUrl": "/pt-rBR/user/firmware.html#related-topics"
  },"1717": {
    "doc": "Firmware Updates",
    "title": "Firmware Updates",
    "content": "Keep your Meshtastic radio up to date with the latest firmware for new features, bug fixes, and security improvements. ",
    "url": "/Meshtastic-Android/main/en/user/firmware.html",
    
    "relUrl": "/en/user/firmware.html"
  },"1718": {
    "doc": "Firmware Updates",
    "title": "Checking for Updates",
    "content": ". | Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable radios. | The app checks for available firmware versions. | Available updates show the version number and changelog summary. | . ",
    "url": "/Meshtastic-Android/main/en/user/firmware.html#checking-for-updates",
    
    "relUrl": "/en/user/firmware.html#checking-for-updates"
  },"1719": {
    "doc": "Firmware Updates",
    "title": "Update Methods",
    "content": "OTA (Over-The-Air) via Bluetooth . The most common update method for Android users: . ⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes. | Ensure your radio is connected via Bluetooth. | Navigate to the Firmware Update screen. | Select the desired firmware version. | Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file. | Wait for the update to complete — do not disconnect during the update. | . Erase device during update . Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered. | Method | What erasing does | . | BLE / Wi-Fi OTA | Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed. | . | USB | Wipes the device’s flash completely, then installs the selected firmware from scratch. | . It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again. OTA via Wi-Fi (network-connected ESP32) . When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP: . | Connect to the radio over the network (see Connections). | Open the Firmware Update screen and pick a version. | Tap Update. Keep the radio and phone on the same network for the whole transfer. | . Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you. In-App USB Update . When your radio is connected over USB/serial (rather than Bluetooth), the Firmware Update screen offers USB File Transfer. The app reboots the device into DFU mode, then prompts you to save the .uf2 file to the device’s DFU drive using the system file picker. This option appears only on a USB/serial connection — it is not available over Bluetooth. ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. A bootloader supplied as an update-....uf2 can be installed by copying it to the drive; that is how the app’s own bootloader upgrade works. The app surfaces a hint when the serial-only route applies. Factory Erase and Bootloader Upgrade . On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it. Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead. Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written. Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware. The app reads INFO_UF2.TXT from the drive you select to confirm it really is the device’s update drive and to identify the board before writing anything. On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer. Once the drive is readable, how an nRF52 device is erased depends on its bootloader: . | Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path. | Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing. | . The app picks the path from what the drive reports; you don’t choose it. Other Flashing Options . For recovery or when neither OTA nor in-app USB is available: . | Use the Meshtastic Web Flasher | Or the Meshtastic CLI tool on desktop | . ",
    "url": "/Meshtastic-Android/main/en/user/firmware.html#update-methods",
    
    "relUrl": "/en/user/firmware.html#update-methods"
  },"1720": {
    "doc": "Firmware Updates",
    "title": "Version Channels",
    "content": "| Channel | Description | . | Stable | Recommended for most users; tested releases | . | Alpha | Preview releases; may contain bugs | . | Local File | Flash a firmware file you select yourself, instead of a downloaded release | . ",
    "url": "/Meshtastic-Android/main/en/user/firmware.html#version-channels",
    
    "relUrl": "/en/user/firmware.html#version-channels"
  },"1721": {
    "doc": "Firmware Updates",
    "title": "Pre-Update Checklist",
    "content": "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 | Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility | . ",
    "url": "/Meshtastic-Android/main/en/user/firmware.html#pre-update-checklist",
    
    "relUrl": "/en/user/firmware.html#pre-update-checklist"
  },"1722": {
    "doc": "Firmware Updates",
    "title": "Post-Update",
    "content": "After the firmware is written, the app verifies the update and waits for the device to come back online: . Once the update succeeds: . | The radio reboots automatically | The Bluetooth connection re-establishes | Verify your settings are intact | Confirm the new version under Currently Installed on the Firmware Update screen — it’s also shown on the node’s detail page and the Connections screen | . ",
    "url": "/Meshtastic-Android/main/en/user/firmware.html#post-update",
    
    "relUrl": "/en/user/firmware.html#post-update"
  },"1723": {
    "doc": "Firmware Updates",
    "title": "Troubleshooting",
    "content": "Update Stuck . If the update appears frozen: . | Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected. | If it is still stuck after that, power-cycle the radio. | Attempt the update again. | . The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update. Radio Won’t Boot After Update . If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update. Otherwise, if your radio fails to boot: . | Try connecting via USB to a computer | Use the web flasher in recovery/DFU mode | Flash a known-good firmware version | Check the Meshtastic Discord for device-specific recovery steps | . Compatibility Warnings . On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each: . | Firmware version | What you see | What happens | . | Below 2.3.15 | Firmware update required. | The app disconnects from the radio. It does not operate against firmware this old. | . | 2.3.15 up to, but not including, 2.5.14 | Firmware Update Recommended. | Advisory only — dismiss it and carry on. The dialog names the latest stable release. | . | 2.5.14 or newer | Nothing | — | . A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio. ",
    "url": "/Meshtastic-Android/main/en/user/firmware.html#troubleshooting",
    
    "relUrl": "/en/user/firmware.html#troubleshooting"
  },"1724": {
    "doc": "Firmware Updates",
    "title": "Related Topics",
    "content": ". | Connections — reconnecting after a firmware update | Flashing firmware guide — full firmware flashing walkthrough on meshtastic.org | Supported devices — check firmware compatibility by device | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/en/user/firmware.html#related-topics",
    
    "relUrl": "/en/user/firmware.html#related-topics"
  },"1725": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": "This same user documentation ships inside the app, so you can read it offline without leaving Meshtastic. Open it from Settings → Help & Documentation. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/help-and-docs.html#help--in-app-docs",
    
    "relUrl": "/sk-rSK/user/help-and-docs.html#help--in-app-docs"
  },"1726": {
    "doc": "Help & In-App Docs",
    "title": "Browsing",
    "content": "The docs browser lists every user-guide page. Tap a page to read it; images and cross-links work just like they do here. Search . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. A page open in the browser: . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/help-and-docs.html#browsing",
    
    "relUrl": "/sk-rSK/user/help-and-docs.html#browsing"
  },"1727": {
    "doc": "Help & In-App Docs",
    "title": "Chirpy — the AI Assistant",
    "content": "Chirpy answers plain-language questions about Meshtastic using this bundled documentation as its source. Tap the Chirpy button in the docs browser, type a question, and it replies with an answer and links to the relevant pages. Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/help-and-docs.html#chirpy--the-ai-assistant",
    
    "relUrl": "/sk-rSK/user/help-and-docs.html#chirpy--the-ai-assistant"
  },"1728": {
    "doc": "Help & In-App Docs",
    "title": "Related Topics",
    "content": ". | Translate the App — how these pages get localized into other languages | App Functions — the separate system-AI integration (distinct from Chirpy) | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/help-and-docs.html#related-topics",
    
    "relUrl": "/sk-rSK/user/help-and-docs.html#related-topics"
  },"1729": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": " ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/help-and-docs.html",
    
    "relUrl": "/sk-rSK/user/help-and-docs.html"
  },"1730": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": "This same user documentation ships inside the app, so you can read it offline without leaving Meshtastic. Open it from Settings → Help & Documentation. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/help-and-docs.html#help--in-app-docs",
    
    "relUrl": "/be-rBY/user/help-and-docs.html#help--in-app-docs"
  },"1731": {
    "doc": "Help & In-App Docs",
    "title": "Browsing",
    "content": "The docs browser lists every user-guide page. Tap a page to read it; images and cross-links work just like they do here. Поиск . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. A page open in the browser: . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/help-and-docs.html#browsing",
    
    "relUrl": "/be-rBY/user/help-and-docs.html#browsing"
  },"1732": {
    "doc": "Help & In-App Docs",
    "title": "Chirpy — the AI Assistant",
    "content": "Chirpy answers plain-language questions about Meshtastic using this bundled documentation as its source. Tap the Chirpy button in the docs browser, type a question, and it replies with an answer and links to the relevant pages. Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/help-and-docs.html#chirpy--the-ai-assistant",
    
    "relUrl": "/be-rBY/user/help-and-docs.html#chirpy--the-ai-assistant"
  },"1733": {
    "doc": "Help & In-App Docs",
    "title": "Related Topics",
    "content": ". | Translate the App — how these pages get localized into other languages | App Functions — the separate system-AI integration (distinct from Chirpy) | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/help-and-docs.html#related-topics",
    
    "relUrl": "/be-rBY/user/help-and-docs.html#related-topics"
  },"1734": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": " ",
    "url": "/Meshtastic-Android/main/be-rBY/user/help-and-docs.html",
    
    "relUrl": "/be-rBY/user/help-and-docs.html"
  },"1735": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": "This same user documentation ships inside the app, so you can read it offline without leaving Meshtastic. Open it from Settings → Help & Documentation. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/help-and-docs.html#help--in-app-docs",
    
    "relUrl": "/it-rIT/user/help-and-docs.html#help--in-app-docs"
  },"1736": {
    "doc": "Help & In-App Docs",
    "title": "Browsing",
    "content": "The docs browser lists every user-guide page. Tap a page to read it; images and cross-links work just like they do here. Search . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. A page open in the browser: . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/help-and-docs.html#browsing",
    
    "relUrl": "/it-rIT/user/help-and-docs.html#browsing"
  },"1737": {
    "doc": "Help & In-App Docs",
    "title": "Chirpy — the AI Assistant",
    "content": "Chirpy answers plain-language questions about Meshtastic using this bundled documentation as its source. Tap the Chirpy button in the docs browser, type a question, and it replies with an answer and links to the relevant pages. Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/help-and-docs.html#chirpy--the-ai-assistant",
    
    "relUrl": "/it-rIT/user/help-and-docs.html#chirpy--the-ai-assistant"
  },"1738": {
    "doc": "Help & In-App Docs",
    "title": "Related Topics",
    "content": ". | Translate the App — how these pages get localized into other languages | App Functions — the separate system-AI integration (distinct from Chirpy) | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/help-and-docs.html#related-topics",
    
    "relUrl": "/it-rIT/user/help-and-docs.html#related-topics"
  },"1739": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": " ",
    "url": "/Meshtastic-Android/main/it-rIT/user/help-and-docs.html",
    
    "relUrl": "/it-rIT/user/help-and-docs.html"
  },"1740": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": "This same user documentation ships inside the app, so you can read it offline without leaving Meshtastic. Open it from Settings → Help & Documentation. ",
    "url": "/Meshtastic-Android/main/es-rES/user/help-and-docs.html#help--in-app-docs",
    
    "relUrl": "/es-rES/user/help-and-docs.html#help--in-app-docs"
  },"1741": {
    "doc": "Help & In-App Docs",
    "title": "Browsing",
    "content": "The docs browser lists every user-guide page. Tap a page to read it; images and cross-links work just like they do here. Search . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. A page open in the browser: . ",
    "url": "/Meshtastic-Android/main/es-rES/user/help-and-docs.html#browsing",
    
    "relUrl": "/es-rES/user/help-and-docs.html#browsing"
  },"1742": {
    "doc": "Help & In-App Docs",
    "title": "Chirpy — the AI Assistant",
    "content": "Chirpy answers plain-language questions about Meshtastic using this bundled documentation as its source. Tap the Chirpy button in the docs browser, type a question, and it replies with an answer and links to the relevant pages. Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ",
    "url": "/Meshtastic-Android/main/es-rES/user/help-and-docs.html#chirpy--the-ai-assistant",
    
    "relUrl": "/es-rES/user/help-and-docs.html#chirpy--the-ai-assistant"
  },"1743": {
    "doc": "Help & In-App Docs",
    "title": "Related Topics",
    "content": ". | Translate the App — how these pages get localized into other languages | App Functions — the separate system-AI integration (distinct from Chirpy) | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/help-and-docs.html#related-topics",
    
    "relUrl": "/es-rES/user/help-and-docs.html#related-topics"
  },"1744": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": " ",
    "url": "/Meshtastic-Android/main/es-rES/user/help-and-docs.html",
    
    "relUrl": "/es-rES/user/help-and-docs.html"
  },"1745": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": "This same user documentation ships inside the app, so you can read it offline without leaving Meshtastic. Open it from Settings → Help & Documentation. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/help-and-docs.html#help--in-app-docs",
    
    "relUrl": "/sl-rSI/user/help-and-docs.html#help--in-app-docs"
  },"1746": {
    "doc": "Help & In-App Docs",
    "title": "Browsing",
    "content": "The docs browser lists every user-guide page. Tap a page to read it; images and cross-links work just like they do here. Search . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. A page open in the browser: . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/help-and-docs.html#browsing",
    
    "relUrl": "/sl-rSI/user/help-and-docs.html#browsing"
  },"1747": {
    "doc": "Help & In-App Docs",
    "title": "Chirpy — the AI Assistant",
    "content": "Chirpy answers plain-language questions about Meshtastic using this bundled documentation as its source. Tap the Chirpy button in the docs browser, type a question, and it replies with an answer and links to the relevant pages. Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/help-and-docs.html#chirpy--the-ai-assistant",
    
    "relUrl": "/sl-rSI/user/help-and-docs.html#chirpy--the-ai-assistant"
  },"1748": {
    "doc": "Help & In-App Docs",
    "title": "Related Topics",
    "content": ". | Translate the App — how these pages get localized into other languages | App Functions — the separate system-AI integration (distinct from Chirpy) | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/help-and-docs.html#related-topics",
    
    "relUrl": "/sl-rSI/user/help-and-docs.html#related-topics"
  },"1749": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": " ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/help-and-docs.html",
    
    "relUrl": "/sl-rSI/user/help-and-docs.html"
  },"1750": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": "This same user documentation ships inside the app, so you can read it offline without leaving Meshtastic. Open it from Settings → Help & Documentation. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/help-and-docs.html#help--in-app-docs",
    
    "relUrl": "/no-rNO/user/help-and-docs.html#help--in-app-docs"
  },"1751": {
    "doc": "Help & In-App Docs",
    "title": "Browsing",
    "content": "The docs browser lists every user-guide page. Tap a page to read it; images and cross-links work just like they do here. Search . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. A page open in the browser: . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/help-and-docs.html#browsing",
    
    "relUrl": "/no-rNO/user/help-and-docs.html#browsing"
  },"1752": {
    "doc": "Help & In-App Docs",
    "title": "Chirpy — the AI Assistant",
    "content": "Chirpy answers plain-language questions about Meshtastic using this bundled documentation as its source. Tap the Chirpy button in the docs browser, type a question, and it replies with an answer and links to the relevant pages. Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/help-and-docs.html#chirpy--the-ai-assistant",
    
    "relUrl": "/no-rNO/user/help-and-docs.html#chirpy--the-ai-assistant"
  },"1753": {
    "doc": "Help & In-App Docs",
    "title": "Related Topics",
    "content": ". | Translate the App — how these pages get localized into other languages | App Functions — the separate system-AI integration (distinct from Chirpy) | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/help-and-docs.html#related-topics",
    
    "relUrl": "/no-rNO/user/help-and-docs.html#related-topics"
  },"1754": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": " ",
    "url": "/Meshtastic-Android/main/no-rNO/user/help-and-docs.html",
    
    "relUrl": "/no-rNO/user/help-and-docs.html"
  },"1755": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": "This same user documentation ships inside the app, so you can read it offline without leaving Meshtastic. Open it from Settings → Help & Documentation. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/help-and-docs.html#help--in-app-docs",
    
    "relUrl": "/hu-rHU/user/help-and-docs.html#help--in-app-docs"
  },"1756": {
    "doc": "Help & In-App Docs",
    "title": "Browsing",
    "content": "The docs browser lists every user-guide page. Tap a page to read it; images and cross-links work just like they do here. Search . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. A page open in the browser: . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/help-and-docs.html#browsing",
    
    "relUrl": "/hu-rHU/user/help-and-docs.html#browsing"
  },"1757": {
    "doc": "Help & In-App Docs",
    "title": "Chirpy — the AI Assistant",
    "content": "Chirpy answers plain-language questions about Meshtastic using this bundled documentation as its source. Tap the Chirpy button in the docs browser, type a question, and it replies with an answer and links to the relevant pages. Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/help-and-docs.html#chirpy--the-ai-assistant",
    
    "relUrl": "/hu-rHU/user/help-and-docs.html#chirpy--the-ai-assistant"
  },"1758": {
    "doc": "Help & In-App Docs",
    "title": "Related Topics",
    "content": ". | Translate the App — how these pages get localized into other languages | App Functions — the separate system-AI integration (distinct from Chirpy) | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/help-and-docs.html#related-topics",
    
    "relUrl": "/hu-rHU/user/help-and-docs.html#related-topics"
  },"1759": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": " ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/help-and-docs.html",
    
    "relUrl": "/hu-rHU/user/help-and-docs.html"
  },"1760": {
    "doc": "Справка и встроенная документация",
    "title": "Справка и встроенная документация",
    "content": "Эта же пользовательская документация поставляется внутри приложения, поэтому вы можете читать её офлайн, не покидая Meshtastic. Откройте её через Настройки → Справка и документация. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/help-and-docs.html",
    
    "relUrl": "/ru-rRU/user/help-and-docs.html"
  },"1761": {
    "doc": "Справка и встроенная документация",
    "title": "Просмотр",
    "content": "Браузер документации отображает список всех страниц руководства пользователя. Нажмите на страницу, чтобы прочитать её; изображения и перекрёстные ссылки работают точно так же, как здесь. Поиск . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. Страница, открытая в браузере: . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/help-and-docs.html#%D0%BF%D1%80%D0%BE%D1%81%D0%BC%D0%BE%D1%82%D1%80",
    
    "relUrl": "/ru-rRU/user/help-and-docs.html#просмотр"
  },"1762": {
    "doc": "Справка и встроенная документация",
    "title": "Chirpy — ИИ-ассистент",
    "content": "Chirpy отвечает на вопросы о Meshtastic на естественном языке, используя в качестве источника эту встроенную документацию. Нажмите кнопку Chirpy в браузере документации, введите вопрос — и он ответит, предложив ответ и ссылки на соответствующие страницы. Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. Небольшая модель загружается при первом использовании. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/help-and-docs.html#chirpy--%D0%B8%D0%B8-%D0%B0%D1%81%D1%81%D0%B8%D1%81%D1%82%D0%B5%D0%BD%D1%82",
    
    "relUrl": "/ru-rRU/user/help-and-docs.html#chirpy--ии-ассистент"
  },"1763": {
    "doc": "Справка и встроенная документация",
    "title": "Связанные темы",
    "content": ". | Перевод приложения — как эти страницы локализуются на другие языки | Функции приложения — отдельная интеграция с системным ИИ (отличается от Chirpy) | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/help-and-docs.html#%D1%81%D0%B2%D1%8F%D0%B7%D0%B0%D0%BD%D0%BD%D1%8B%D0%B5-%D1%82%D0%B5%D0%BC%D1%8B",
    
    "relUrl": "/ru-rRU/user/help-and-docs.html#связанные-темы"
  },"1764": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": "This same user documentation ships inside the app, so you can read it offline without leaving Meshtastic. Open it from Settings → Help & Documentation. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/help-and-docs.html#help--in-app-docs",
    
    "relUrl": "/cs-rCZ/user/help-and-docs.html#help--in-app-docs"
  },"1765": {
    "doc": "Help & In-App Docs",
    "title": "Browsing",
    "content": "The docs browser lists every user-guide page. Tap a page to read it; images and cross-links work just like they do here. Search . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. A page open in the browser: . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/help-and-docs.html#browsing",
    
    "relUrl": "/cs-rCZ/user/help-and-docs.html#browsing"
  },"1766": {
    "doc": "Help & In-App Docs",
    "title": "Chirpy — the AI Assistant",
    "content": "Chirpy answers plain-language questions about Meshtastic using this bundled documentation as its source. Tap the Chirpy button in the docs browser, type a question, and it replies with an answer and links to the relevant pages. Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/help-and-docs.html#chirpy--the-ai-assistant",
    
    "relUrl": "/cs-rCZ/user/help-and-docs.html#chirpy--the-ai-assistant"
  },"1767": {
    "doc": "Help & In-App Docs",
    "title": "Related Topics",
    "content": ". | Translate the App — how these pages get localized into other languages | App Functions — the separate system-AI integration (distinct from Chirpy) | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/help-and-docs.html#related-topics",
    
    "relUrl": "/cs-rCZ/user/help-and-docs.html#related-topics"
  },"1768": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": " ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/help-and-docs.html",
    
    "relUrl": "/cs-rCZ/user/help-and-docs.html"
  },"1769": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": "This same user documentation ships inside the app, so you can read it offline without leaving Meshtastic. Open it from Settings → Help & Documentation. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/help-and-docs.html#help--in-app-docs",
    
    "relUrl": "/bg-rBG/user/help-and-docs.html#help--in-app-docs"
  },"1770": {
    "doc": "Help & In-App Docs",
    "title": "Browsing",
    "content": "The docs browser lists every user-guide page. Tap a page to read it; images and cross-links work just like they do here. Търсене . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. A page open in the browser: . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/help-and-docs.html#browsing",
    
    "relUrl": "/bg-rBG/user/help-and-docs.html#browsing"
  },"1771": {
    "doc": "Help & In-App Docs",
    "title": "Chirpy — the AI Assistant",
    "content": "Chirpy answers plain-language questions about Meshtastic using this bundled documentation as its source. Tap the Chirpy button in the docs browser, type a question, and it replies with an answer and links to the relevant pages. Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/help-and-docs.html#chirpy--the-ai-assistant",
    
    "relUrl": "/bg-rBG/user/help-and-docs.html#chirpy--the-ai-assistant"
  },"1772": {
    "doc": "Help & In-App Docs",
    "title": "Свързани теми",
    "content": ". | Превод на приложението — как тези страници се локализират на други езици | App Functions — the separate system-AI integration (distinct from Chirpy) | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/help-and-docs.html#%D1%81%D0%B2%D1%8A%D1%80%D0%B7%D0%B0%D0%BD%D0%B8-%D1%82%D0%B5%D0%BC%D0%B8",
    
    "relUrl": "/bg-rBG/user/help-and-docs.html#свързани-теми"
  },"1773": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": " ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/help-and-docs.html",
    
    "relUrl": "/bg-rBG/user/help-and-docs.html"
  },"1774": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": "This same user documentation ships inside the app, so you can read it offline without leaving Meshtastic. Open it from Settings → Help & Documentation. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/help-and-docs.html#help--in-app-docs",
    
    "relUrl": "/ga-rIE/user/help-and-docs.html#help--in-app-docs"
  },"1775": {
    "doc": "Help & In-App Docs",
    "title": "Browsing",
    "content": "The docs browser lists every user-guide page. Tap a page to read it; images and cross-links work just like they do here. Search . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. A page open in the browser: . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/help-and-docs.html#browsing",
    
    "relUrl": "/ga-rIE/user/help-and-docs.html#browsing"
  },"1776": {
    "doc": "Help & In-App Docs",
    "title": "Chirpy — the AI Assistant",
    "content": "Chirpy answers plain-language questions about Meshtastic using this bundled documentation as its source. Tap the Chirpy button in the docs browser, type a question, and it replies with an answer and links to the relevant pages. Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/help-and-docs.html#chirpy--the-ai-assistant",
    
    "relUrl": "/ga-rIE/user/help-and-docs.html#chirpy--the-ai-assistant"
  },"1777": {
    "doc": "Help & In-App Docs",
    "title": "Related Topics",
    "content": ". | Translate the App — how these pages get localized into other languages | App Functions — the separate system-AI integration (distinct from Chirpy) | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/help-and-docs.html#related-topics",
    
    "relUrl": "/ga-rIE/user/help-and-docs.html#related-topics"
  },"1778": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": " ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/help-and-docs.html",
    
    "relUrl": "/ga-rIE/user/help-and-docs.html"
  },"1779": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": "This same user documentation ships inside the app, so you can read it offline without leaving Meshtastic. Open it from Settings → Help & Documentation. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/help-and-docs.html#help--in-app-docs",
    
    "relUrl": "/fr-rCA/user/help-and-docs.html#help--in-app-docs"
  },"1780": {
    "doc": "Help & In-App Docs",
    "title": "Browsing",
    "content": "The docs browser lists every user-guide page. Tap a page to read it; images and cross-links work just like they do here. Search . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. A page open in the browser: . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/help-and-docs.html#browsing",
    
    "relUrl": "/fr-rCA/user/help-and-docs.html#browsing"
  },"1781": {
    "doc": "Help & In-App Docs",
    "title": "Chirpy — the AI Assistant",
    "content": "Chirpy answers plain-language questions about Meshtastic using this bundled documentation as its source. Tap the Chirpy button in the docs browser, type a question, and it replies with an answer and links to the relevant pages. Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/help-and-docs.html#chirpy--the-ai-assistant",
    
    "relUrl": "/fr-rCA/user/help-and-docs.html#chirpy--the-ai-assistant"
  },"1782": {
    "doc": "Help & In-App Docs",
    "title": "Related Topics",
    "content": ". | Translate the App — how these pages get localized into other languages | App Functions — the separate system-AI integration (distinct from Chirpy) | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/help-and-docs.html#related-topics",
    
    "relUrl": "/fr-rCA/user/help-and-docs.html#related-topics"
  },"1783": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": " ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/help-and-docs.html",
    
    "relUrl": "/fr-rCA/user/help-and-docs.html"
  },"1784": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": "This same user documentation ships inside the app, so you can read it offline without leaving Meshtastic. Open it from Settings → Help & Documentation. ",
    "url": "/Meshtastic-Android/main/srp/user/help-and-docs.html#help--in-app-docs",
    
    "relUrl": "/srp/user/help-and-docs.html#help--in-app-docs"
  },"1785": {
    "doc": "Help & In-App Docs",
    "title": "Browsing",
    "content": "The docs browser lists every user-guide page. Tap a page to read it; images and cross-links work just like they do here. Претражи . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. A page open in the browser: . ",
    "url": "/Meshtastic-Android/main/srp/user/help-and-docs.html#browsing",
    
    "relUrl": "/srp/user/help-and-docs.html#browsing"
  },"1786": {
    "doc": "Help & In-App Docs",
    "title": "Chirpy — the AI Assistant",
    "content": "Chirpy answers plain-language questions about Meshtastic using this bundled documentation as its source. Tap the Chirpy button in the docs browser, type a question, and it replies with an answer and links to the relevant pages. Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ",
    "url": "/Meshtastic-Android/main/srp/user/help-and-docs.html#chirpy--the-ai-assistant",
    
    "relUrl": "/srp/user/help-and-docs.html#chirpy--the-ai-assistant"
  },"1787": {
    "doc": "Help & In-App Docs",
    "title": "Related Topics",
    "content": ". | Translate the App — how these pages get localized into other languages | App Functions — the separate system-AI integration (distinct from Chirpy) | . ",
    "url": "/Meshtastic-Android/main/srp/user/help-and-docs.html#related-topics",
    
    "relUrl": "/srp/user/help-and-docs.html#related-topics"
  },"1788": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": " ",
    "url": "/Meshtastic-Android/main/srp/user/help-and-docs.html",
    
    "relUrl": "/srp/user/help-and-docs.html"
  },"1789": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": "This same user documentation ships inside the app, so you can read it offline without leaving Meshtastic. Open it from Settings → Help & Documentation. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/help-and-docs.html#help--in-app-docs",
    
    "relUrl": "/ca-rES/user/help-and-docs.html#help--in-app-docs"
  },"1790": {
    "doc": "Help & In-App Docs",
    "title": "Browsing",
    "content": "The docs browser lists every user-guide page. Tap a page to read it; images and cross-links work just like they do here. Search . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. A page open in the browser: . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/help-and-docs.html#browsing",
    
    "relUrl": "/ca-rES/user/help-and-docs.html#browsing"
  },"1791": {
    "doc": "Help & In-App Docs",
    "title": "Chirpy — the AI Assistant",
    "content": "Chirpy answers plain-language questions about Meshtastic using this bundled documentation as its source. Tap the Chirpy button in the docs browser, type a question, and it replies with an answer and links to the relevant pages. Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/help-and-docs.html#chirpy--the-ai-assistant",
    
    "relUrl": "/ca-rES/user/help-and-docs.html#chirpy--the-ai-assistant"
  },"1792": {
    "doc": "Help & In-App Docs",
    "title": "Related Topics",
    "content": ". | Translate the App — how these pages get localized into other languages | App Functions — the separate system-AI integration (distinct from Chirpy) | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/help-and-docs.html#related-topics",
    
    "relUrl": "/ca-rES/user/help-and-docs.html#related-topics"
  },"1793": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": " ",
    "url": "/Meshtastic-Android/main/ca-rES/user/help-and-docs.html",
    
    "relUrl": "/ca-rES/user/help-and-docs.html"
  },"1794": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": "This same user documentation ships inside the app, so you can read it offline without leaving Meshtastic. Open it from Settings → Help & Documentation. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/help-and-docs.html#help--in-app-docs",
    
    "relUrl": "/ko-rKR/user/help-and-docs.html#help--in-app-docs"
  },"1795": {
    "doc": "Help & In-App Docs",
    "title": "Browsing",
    "content": "The docs browser lists every user-guide page. Tap a page to read it; images and cross-links work just like they do here. Search . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. A page open in the browser: . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/help-and-docs.html#browsing",
    
    "relUrl": "/ko-rKR/user/help-and-docs.html#browsing"
  },"1796": {
    "doc": "Help & In-App Docs",
    "title": "Chirpy — the AI Assistant",
    "content": "Chirpy answers plain-language questions about Meshtastic using this bundled documentation as its source. Tap the Chirpy button in the docs browser, type a question, and it replies with an answer and links to the relevant pages. Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/help-and-docs.html#chirpy--the-ai-assistant",
    
    "relUrl": "/ko-rKR/user/help-and-docs.html#chirpy--the-ai-assistant"
  },"1797": {
    "doc": "Help & In-App Docs",
    "title": "Related Topics",
    "content": ". | Translate the App — how these pages get localized into other languages | App Functions — the separate system-AI integration (distinct from Chirpy) | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/help-and-docs.html#related-topics",
    
    "relUrl": "/ko-rKR/user/help-and-docs.html#related-topics"
  },"1798": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": " ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/help-and-docs.html",
    
    "relUrl": "/ko-rKR/user/help-and-docs.html"
  },"1799": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": "This same user documentation ships inside the app, so you can read it offline without leaving Meshtastic. Open it from Settings → Help & Documentation. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/help-and-docs.html#help--in-app-docs",
    
    "relUrl": "/sv-rSE/user/help-and-docs.html#help--in-app-docs"
  },"1800": {
    "doc": "Help & In-App Docs",
    "title": "Browsing",
    "content": "The docs browser lists every user-guide page. Tap a page to read it; images and cross-links work just like they do here. Search . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. A page open in the browser: . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/help-and-docs.html#browsing",
    
    "relUrl": "/sv-rSE/user/help-and-docs.html#browsing"
  },"1801": {
    "doc": "Help & In-App Docs",
    "title": "Chirpy — the AI Assistant",
    "content": "Chirpy answers plain-language questions about Meshtastic using this bundled documentation as its source. Tap the Chirpy button in the docs browser, type a question, and it replies with an answer and links to the relevant pages. Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/help-and-docs.html#chirpy--the-ai-assistant",
    
    "relUrl": "/sv-rSE/user/help-and-docs.html#chirpy--the-ai-assistant"
  },"1802": {
    "doc": "Help & In-App Docs",
    "title": "Related Topics",
    "content": ". | Translate the App — how these pages get localized into other languages | App Functions — the separate system-AI integration (distinct from Chirpy) | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/help-and-docs.html#related-topics",
    
    "relUrl": "/sv-rSE/user/help-and-docs.html#related-topics"
  },"1803": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": " ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/help-and-docs.html",
    
    "relUrl": "/sv-rSE/user/help-and-docs.html"
  },"1804": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": "This same user documentation ships inside the app, so you can read it offline without leaving Meshtastic. Open it from Settings → Help & Documentation. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/help-and-docs.html#help--in-app-docs",
    
    "relUrl": "/ht-rHT/user/help-and-docs.html#help--in-app-docs"
  },"1805": {
    "doc": "Help & In-App Docs",
    "title": "Browsing",
    "content": "The docs browser lists every user-guide page. Tap a page to read it; images and cross-links work just like they do here. Search . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. A page open in the browser: . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/help-and-docs.html#browsing",
    
    "relUrl": "/ht-rHT/user/help-and-docs.html#browsing"
  },"1806": {
    "doc": "Help & In-App Docs",
    "title": "Chirpy — the AI Assistant",
    "content": "Chirpy answers plain-language questions about Meshtastic using this bundled documentation as its source. Tap the Chirpy button in the docs browser, type a question, and it replies with an answer and links to the relevant pages. Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/help-and-docs.html#chirpy--the-ai-assistant",
    
    "relUrl": "/ht-rHT/user/help-and-docs.html#chirpy--the-ai-assistant"
  },"1807": {
    "doc": "Help & In-App Docs",
    "title": "Related Topics",
    "content": ". | Translate the App — how these pages get localized into other languages | App Functions — the separate system-AI integration (distinct from Chirpy) | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/help-and-docs.html#related-topics",
    
    "relUrl": "/ht-rHT/user/help-and-docs.html#related-topics"
  },"1808": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": " ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/help-and-docs.html",
    
    "relUrl": "/ht-rHT/user/help-and-docs.html"
  },"1809": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": "This same user documentation ships inside the app, so you can read it offline without leaving Meshtastic. Open it from Settings → Help & Documentation. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/help-and-docs.html#help--in-app-docs",
    
    "relUrl": "/sr-rLatn/user/help-and-docs.html#help--in-app-docs"
  },"1810": {
    "doc": "Help & In-App Docs",
    "title": "Browsing",
    "content": "The docs browser lists every user-guide page. Tap a page to read it; images and cross-links work just like they do here. Претражи . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. A page open in the browser: . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/help-and-docs.html#browsing",
    
    "relUrl": "/sr-rLatn/user/help-and-docs.html#browsing"
  },"1811": {
    "doc": "Help & In-App Docs",
    "title": "Chirpy — the AI Assistant",
    "content": "Chirpy answers plain-language questions about Meshtastic using this bundled documentation as its source. Tap the Chirpy button in the docs browser, type a question, and it replies with an answer and links to the relevant pages. Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/help-and-docs.html#chirpy--the-ai-assistant",
    
    "relUrl": "/sr-rLatn/user/help-and-docs.html#chirpy--the-ai-assistant"
  },"1812": {
    "doc": "Help & In-App Docs",
    "title": "Related Topics",
    "content": ". | Translate the App — how these pages get localized into other languages | App Functions — the separate system-AI integration (distinct from Chirpy) | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/help-and-docs.html#related-topics",
    
    "relUrl": "/sr-rLatn/user/help-and-docs.html#related-topics"
  },"1813": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": " ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/help-and-docs.html",
    
    "relUrl": "/sr-rLatn/user/help-and-docs.html"
  },"1814": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": "This same user documentation ships inside the app, so you can read it offline without leaving Meshtastic. Open it from Settings → Help & Documentation. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/help-and-docs.html#help--in-app-docs",
    
    "relUrl": "/nl-rNL/user/help-and-docs.html#help--in-app-docs"
  },"1815": {
    "doc": "Help & In-App Docs",
    "title": "Browsing",
    "content": "The docs browser lists every user-guide page. Tap a page to read it; images and cross-links work just like they do here. Search . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. A page open in the browser: . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/help-and-docs.html#browsing",
    
    "relUrl": "/nl-rNL/user/help-and-docs.html#browsing"
  },"1816": {
    "doc": "Help & In-App Docs",
    "title": "Chirpy — the AI Assistant",
    "content": "Chirpy answers plain-language questions about Meshtastic using this bundled documentation as its source. Tap the Chirpy button in the docs browser, type a question, and it replies with an answer and links to the relevant pages. Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/help-and-docs.html#chirpy--the-ai-assistant",
    
    "relUrl": "/nl-rNL/user/help-and-docs.html#chirpy--the-ai-assistant"
  },"1817": {
    "doc": "Help & In-App Docs",
    "title": "Related Topics",
    "content": ". | Translate the App — how these pages get localized into other languages | App Functions — the separate system-AI integration (distinct from Chirpy) | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/help-and-docs.html#related-topics",
    
    "relUrl": "/nl-rNL/user/help-and-docs.html#related-topics"
  },"1818": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": " ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/help-and-docs.html",
    
    "relUrl": "/nl-rNL/user/help-and-docs.html"
  },"1819": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": "This same user documentation ships inside the app, so you can read it offline without leaving Meshtastic. Open it from Settings → Help & Documentation. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/help-and-docs.html#help--in-app-docs",
    
    "relUrl": "/uk-rUA/user/help-and-docs.html#help--in-app-docs"
  },"1820": {
    "doc": "Help & In-App Docs",
    "title": "Browsing",
    "content": "The docs browser lists every user-guide page. Tap a page to read it; images and cross-links work just like they do here. Search . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. A page open in the browser: . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/help-and-docs.html#browsing",
    
    "relUrl": "/uk-rUA/user/help-and-docs.html#browsing"
  },"1821": {
    "doc": "Help & In-App Docs",
    "title": "Chirpy — the AI Assistant",
    "content": "Chirpy answers plain-language questions about Meshtastic using this bundled documentation as its source. Tap the Chirpy button in the docs browser, type a question, and it replies with an answer and links to the relevant pages. Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/help-and-docs.html#chirpy--the-ai-assistant",
    
    "relUrl": "/uk-rUA/user/help-and-docs.html#chirpy--the-ai-assistant"
  },"1822": {
    "doc": "Help & In-App Docs",
    "title": "Related Topics",
    "content": ". | Translate the App — how these pages get localized into other languages | App Functions — the separate system-AI integration (distinct from Chirpy) | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/help-and-docs.html#related-topics",
    
    "relUrl": "/uk-rUA/user/help-and-docs.html#related-topics"
  },"1823": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": " ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/help-and-docs.html",
    
    "relUrl": "/uk-rUA/user/help-and-docs.html"
  },"1824": {
    "doc": "Ohjeet jasovelluksen sisäinen dokumentaatio",
    "title": "Ohjeet ja sovelluksen sisäinen dokumentaatio",
    "content": "Sama käyttöohje sisältyy myös sovellukseen, joten voit lukea sitä offline-tilassa poistumatta Meshtasticista. Avaa se kohdasta Asetukset → Ohjeet & dokumentaatio. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/help-and-docs.html#ohjeet-ja-sovelluksen-sis%C3%A4inen-dokumentaatio",
    
    "relUrl": "/fi-rFI/user/help-and-docs.html#ohjeet-ja-sovelluksen-sisäinen-dokumentaatio"
  },"1825": {
    "doc": "Ohjeet jasovelluksen sisäinen dokumentaatio",
    "title": "Selaaminen",
    "content": "Dokumentaation selain näyttää kaikki käyttöohjeen sivut. Avaa sivu napauttamalla sitä. Kuvat ja ristiviittaukset toimivat samalla tavalla kuin tässä dokumentaatiossa. Haku . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. Dokumentaatiosivu avattuna selaimessa: . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/help-and-docs.html#selaaminen",
    
    "relUrl": "/fi-rFI/user/help-and-docs.html#selaaminen"
  },"1826": {
    "doc": "Ohjeet jasovelluksen sisäinen dokumentaatio",
    "title": "Chirpy — tekoälyn avustaja",
    "content": "Chirpy vastaa Meshtasticia koskeviin luonnollisella kielellä esitettyihin kysymyksiin käyttäen lähteenään tätä sovellukseen sisältyvää dokumentaatiota. Napauta Chirpy-painiketta dokumentaatioselaimessa, kirjoita kysymyksesi, niin se vastaa ja linkittää aiheeseen liittyville sivuille. Chirpy on käytettävissä vain Androidin Google-versiossa. F-Droid-, Työpöytä- ja iOS-versioissa avustajapainiketta ei näytetä lainkaan — sama koskee puhelimia, joiden laitteisto ei pysty suorittamaan laitteella ajettavaa mallia. Selaaminen ja ohjeselaimen oma haku toimivat normaalisti kaikilla alustoilla. 🔒 Tietosuoja: Tuetuissa puhelimissa, joissa käytetään Google-versiota, Chirpy toimii laitteella Gemini Nanon avulla — kysymyksesi eivät koskaan poistu puhelimestasi. Pieni kielimalli ladataan ensimmäisellä käyttökerralla. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/help-and-docs.html#chirpy--teko%C3%A4lyn-avustaja",
    
    "relUrl": "/fi-rFI/user/help-and-docs.html#chirpy--tekoälyn-avustaja"
  },"1827": {
    "doc": "Ohjeet jasovelluksen sisäinen dokumentaatio",
    "title": "Aiheeseen liittyvät aiheet",
    "content": ". | Käännä sovellus — miten nämä sivut lokalisoidaan muille kielille | Sovelluksen toiminnot — erillinen järjestelmätekoälyintegraatio (ei sama kuin Chirpy) | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/help-and-docs.html#aiheeseen-liittyv%C3%A4t-aiheet",
    
    "relUrl": "/fi-rFI/user/help-and-docs.html#aiheeseen-liittyvät-aiheet"
  },"1828": {
    "doc": "Ohjeet jasovelluksen sisäinen dokumentaatio",
    "title": "Ohjeet jasovelluksen sisäinen dokumentaatio",
    "content": " ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/help-and-docs.html",
    
    "relUrl": "/fi-rFI/user/help-and-docs.html"
  },"1829": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": "This same user documentation ships inside the app, so you can read it offline without leaving Meshtastic. Open it from Settings → Help & Documentation. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/help-and-docs.html#help--in-app-docs",
    
    "relUrl": "/is-rIS/user/help-and-docs.html#help--in-app-docs"
  },"1830": {
    "doc": "Help & In-App Docs",
    "title": "Browsing",
    "content": "The docs browser lists every user-guide page. Tap a page to read it; images and cross-links work just like they do here. Search . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. A page open in the browser: . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/help-and-docs.html#browsing",
    
    "relUrl": "/is-rIS/user/help-and-docs.html#browsing"
  },"1831": {
    "doc": "Help & In-App Docs",
    "title": "Chirpy — the AI Assistant",
    "content": "Chirpy answers plain-language questions about Meshtastic using this bundled documentation as its source. Tap the Chirpy button in the docs browser, type a question, and it replies with an answer and links to the relevant pages. Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/help-and-docs.html#chirpy--the-ai-assistant",
    
    "relUrl": "/is-rIS/user/help-and-docs.html#chirpy--the-ai-assistant"
  },"1832": {
    "doc": "Help & In-App Docs",
    "title": "Related Topics",
    "content": ". | Translate the App — how these pages get localized into other languages | App Functions — the separate system-AI integration (distinct from Chirpy) | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/help-and-docs.html#related-topics",
    
    "relUrl": "/is-rIS/user/help-and-docs.html#related-topics"
  },"1833": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": " ",
    "url": "/Meshtastic-Android/main/is-rIS/user/help-and-docs.html",
    
    "relUrl": "/is-rIS/user/help-and-docs.html"
  },"1834": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": "This same user documentation ships inside the app, so you can read it offline without leaving Meshtastic. Open it from Settings → Help & Documentation. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/help-and-docs.html#help--in-app-docs",
    
    "relUrl": "/lt-rLT/user/help-and-docs.html#help--in-app-docs"
  },"1835": {
    "doc": "Help & In-App Docs",
    "title": "Browsing",
    "content": "The docs browser lists every user-guide page. Tap a page to read it; images and cross-links work just like they do here. Search . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. A page open in the browser: . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/help-and-docs.html#browsing",
    
    "relUrl": "/lt-rLT/user/help-and-docs.html#browsing"
  },"1836": {
    "doc": "Help & In-App Docs",
    "title": "Chirpy — the AI Assistant",
    "content": "Chirpy answers plain-language questions about Meshtastic using this bundled documentation as its source. Tap the Chirpy button in the docs browser, type a question, and it replies with an answer and links to the relevant pages. Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/help-and-docs.html#chirpy--the-ai-assistant",
    
    "relUrl": "/lt-rLT/user/help-and-docs.html#chirpy--the-ai-assistant"
  },"1837": {
    "doc": "Help & In-App Docs",
    "title": "Related Topics",
    "content": ". | Translate the App — how these pages get localized into other languages | App Functions — the separate system-AI integration (distinct from Chirpy) | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/help-and-docs.html#related-topics",
    
    "relUrl": "/lt-rLT/user/help-and-docs.html#related-topics"
  },"1838": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": " ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/help-and-docs.html",
    
    "relUrl": "/lt-rLT/user/help-and-docs.html"
  },"1839": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": "This same user documentation ships inside the app, so you can read it offline without leaving Meshtastic. Open it from Settings → Help & Documentation. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/help-and-docs.html#help--in-app-docs",
    
    "relUrl": "/gl-rES/user/help-and-docs.html#help--in-app-docs"
  },"1840": {
    "doc": "Help & In-App Docs",
    "title": "Browsing",
    "content": "The docs browser lists every user-guide page. Tap a page to read it; images and cross-links work just like they do here. Search . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. A page open in the browser: . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/help-and-docs.html#browsing",
    
    "relUrl": "/gl-rES/user/help-and-docs.html#browsing"
  },"1841": {
    "doc": "Help & In-App Docs",
    "title": "Chirpy — the AI Assistant",
    "content": "Chirpy answers plain-language questions about Meshtastic using this bundled documentation as its source. Tap the Chirpy button in the docs browser, type a question, and it replies with an answer and links to the relevant pages. Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/help-and-docs.html#chirpy--the-ai-assistant",
    
    "relUrl": "/gl-rES/user/help-and-docs.html#chirpy--the-ai-assistant"
  },"1842": {
    "doc": "Help & In-App Docs",
    "title": "Related Topics",
    "content": ". | Translate the App — how these pages get localized into other languages | App Functions — the separate system-AI integration (distinct from Chirpy) | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/help-and-docs.html#related-topics",
    
    "relUrl": "/gl-rES/user/help-and-docs.html#related-topics"
  },"1843": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": " ",
    "url": "/Meshtastic-Android/main/gl-rES/user/help-and-docs.html",
    
    "relUrl": "/gl-rES/user/help-and-docs.html"
  },"1844": {
    "doc": "ヘルプとアプリ内ドキュメント",
    "title": "ヘルプとアプリ内ドキュメント",
    "content": "このユーザードキュメントはアプリ内にも同梱されており、Meshtastic を離れることなくオフラインで読めます。「設定 → ヘルプとドキュメント」から開きます。 . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/help-and-docs.html",
    
    "relUrl": "/ja-rJP/user/help-and-docs.html"
  },"1845": {
    "doc": "ヘルプとアプリ内ドキュメント",
    "title": "閲覧する",
    "content": "ドキュメントブラウザーには、ユーザーガイドのすべてのページが一覧表示されます。ページをタップすると読めます。画像や相互リンクも、ここと同じように機能します。 . 検索 . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. ブラウザーで開いたページ： . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/help-and-docs.html#%E9%96%B2%E8%A6%A7%E3%81%99%E3%82%8B",
    
    "relUrl": "/ja-rJP/user/help-and-docs.html#閲覧する"
  },"1846": {
    "doc": "ヘルプとアプリ内ドキュメント",
    "title": "Chirpy：AI アシスタント",
    "content": "Chirpy は、この同梱ドキュメントを情報源として、Meshtastic に関する平易な質問に答えます。ドキュメントブラウザーで Chirpy ボタンをタップして質問を入力すると、回答と、関連ページへのリンクが返ってきます。 . Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. 初回使用時に、小さなモデルがダウンロードされます。 . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/help-and-docs.html#chirpyai-%E3%82%A2%E3%82%B7%E3%82%B9%E3%82%BF%E3%83%B3%E3%83%88",
    
    "relUrl": "/ja-rJP/user/help-and-docs.html#chirpyai-アシスタント"
  },"1847": {
    "doc": "ヘルプとアプリ内ドキュメント",
    "title": "関連トピック",
    "content": ". | アプリを翻訳する：これらのページが他の言語にどう翻訳されるか | アプリ機能：Chirpy とは別の、システム AI 連携 | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/help-and-docs.html#%E9%96%A2%E9%80%A3%E3%83%88%E3%83%94%E3%83%83%E3%82%AF",
    
    "relUrl": "/ja-rJP/user/help-and-docs.html#関連トピック"
  },"1848": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": "This same user documentation ships inside the app, so you can read it offline without leaving Meshtastic. Open it from Settings → Help & Documentation. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/help-and-docs.html#help--in-app-docs",
    
    "relUrl": "/de-rDE/user/help-and-docs.html#help--in-app-docs"
  },"1849": {
    "doc": "Help & In-App Docs",
    "title": "Browsing",
    "content": "The docs browser lists every user-guide page. Tap a page to read it; images and cross-links work just like they do here. Suchen . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. A page open in the browser: . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/help-and-docs.html#browsing",
    
    "relUrl": "/de-rDE/user/help-and-docs.html#browsing"
  },"1850": {
    "doc": "Help & In-App Docs",
    "title": "Chirpy — the AI Assistant",
    "content": "Chirpy answers plain-language questions about Meshtastic using this bundled documentation as its source. Tap the Chirpy button in the docs browser, type a question, and it replies with an answer and links to the relevant pages. Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/help-and-docs.html#chirpy--the-ai-assistant",
    
    "relUrl": "/de-rDE/user/help-and-docs.html#chirpy--the-ai-assistant"
  },"1851": {
    "doc": "Help & In-App Docs",
    "title": "Related Topics",
    "content": ". | Translate the App — how these pages get localized into other languages | App Functions — the separate system-AI integration (distinct from Chirpy) | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/help-and-docs.html#related-topics",
    
    "relUrl": "/de-rDE/user/help-and-docs.html#related-topics"
  },"1852": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": " ",
    "url": "/Meshtastic-Android/main/de-rDE/user/help-and-docs.html",
    
    "relUrl": "/de-rDE/user/help-and-docs.html"
  },"1853": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": "This same user documentation ships inside the app, so you can read it offline without leaving Meshtastic. Open it from Settings → Help & Documentation. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/help-and-docs.html#help--in-app-docs",
    
    "relUrl": "/ar-rSA/user/help-and-docs.html#help--in-app-docs"
  },"1854": {
    "doc": "Help & In-App Docs",
    "title": "Browsing",
    "content": "The docs browser lists every user-guide page. Tap a page to read it; images and cross-links work just like they do here. Search . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. A page open in the browser: . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/help-and-docs.html#browsing",
    
    "relUrl": "/ar-rSA/user/help-and-docs.html#browsing"
  },"1855": {
    "doc": "Help & In-App Docs",
    "title": "Chirpy — the AI Assistant",
    "content": "Chirpy answers plain-language questions about Meshtastic using this bundled documentation as its source. Tap the Chirpy button in the docs browser, type a question, and it replies with an answer and links to the relevant pages. Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/help-and-docs.html#chirpy--the-ai-assistant",
    
    "relUrl": "/ar-rSA/user/help-and-docs.html#chirpy--the-ai-assistant"
  },"1856": {
    "doc": "Help & In-App Docs",
    "title": "Related Topics",
    "content": ". | Translate the App — how these pages get localized into other languages | App Functions — the separate system-AI integration (distinct from Chirpy) | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/help-and-docs.html#related-topics",
    
    "relUrl": "/ar-rSA/user/help-and-docs.html#related-topics"
  },"1857": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": " ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/help-and-docs.html",
    
    "relUrl": "/ar-rSA/user/help-and-docs.html"
  },"1858": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": "This same user documentation ships inside the app, so you can read it offline without leaving Meshtastic. Open it from Settings → Help & Documentation. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/help-and-docs.html#help--in-app-docs",
    
    "relUrl": "/hr-rHR/user/help-and-docs.html#help--in-app-docs"
  },"1859": {
    "doc": "Help & In-App Docs",
    "title": "Browsing",
    "content": "The docs browser lists every user-guide page. Tap a page to read it; images and cross-links work just like they do here. Search . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. A page open in the browser: . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/help-and-docs.html#browsing",
    
    "relUrl": "/hr-rHR/user/help-and-docs.html#browsing"
  },"1860": {
    "doc": "Help & In-App Docs",
    "title": "Chirpy — the AI Assistant",
    "content": "Chirpy answers plain-language questions about Meshtastic using this bundled documentation as its source. Tap the Chirpy button in the docs browser, type a question, and it replies with an answer and links to the relevant pages. Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/help-and-docs.html#chirpy--the-ai-assistant",
    
    "relUrl": "/hr-rHR/user/help-and-docs.html#chirpy--the-ai-assistant"
  },"1861": {
    "doc": "Help & In-App Docs",
    "title": "Related Topics",
    "content": ". | Translate the App — how these pages get localized into other languages | App Functions — the separate system-AI integration (distinct from Chirpy) | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/help-and-docs.html#related-topics",
    
    "relUrl": "/hr-rHR/user/help-and-docs.html#related-topics"
  },"1862": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": " ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/help-and-docs.html",
    
    "relUrl": "/hr-rHR/user/help-and-docs.html"
  },"1863": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": "This same user documentation ships inside the app, so you can read it offline without leaving Meshtastic. Open it from Settings → Help & Documentation. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/help-and-docs.html#help--in-app-docs",
    
    "relUrl": "/pt-rPT/user/help-and-docs.html#help--in-app-docs"
  },"1864": {
    "doc": "Help & In-App Docs",
    "title": "Browsing",
    "content": "The docs browser lists every user-guide page. Tap a page to read it; images and cross-links work just like they do here. Search . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. A page open in the browser: . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/help-and-docs.html#browsing",
    
    "relUrl": "/pt-rPT/user/help-and-docs.html#browsing"
  },"1865": {
    "doc": "Help & In-App Docs",
    "title": "Chirpy — the AI Assistant",
    "content": "Chirpy answers plain-language questions about Meshtastic using this bundled documentation as its source. Tap the Chirpy button in the docs browser, type a question, and it replies with an answer and links to the relevant pages. Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/help-and-docs.html#chirpy--the-ai-assistant",
    
    "relUrl": "/pt-rPT/user/help-and-docs.html#chirpy--the-ai-assistant"
  },"1866": {
    "doc": "Help & In-App Docs",
    "title": "Related Topics",
    "content": ". | Translate the App — how these pages get localized into other languages | App Functions — the separate system-AI integration (distinct from Chirpy) | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/help-and-docs.html#related-topics",
    
    "relUrl": "/pt-rPT/user/help-and-docs.html#related-topics"
  },"1867": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": " ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/help-and-docs.html",
    
    "relUrl": "/pt-rPT/user/help-and-docs.html"
  },"1868": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": "This same user documentation ships inside the app, so you can read it offline without leaving Meshtastic. Open it from Settings → Help & Documentation. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/help-and-docs.html#help--in-app-docs",
    
    "relUrl": "/pl-rPL/user/help-and-docs.html#help--in-app-docs"
  },"1869": {
    "doc": "Help & In-App Docs",
    "title": "Browsing",
    "content": "The docs browser lists every user-guide page. Tap a page to read it; images and cross-links work just like they do here. Search . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. A page open in the browser: . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/help-and-docs.html#browsing",
    
    "relUrl": "/pl-rPL/user/help-and-docs.html#browsing"
  },"1870": {
    "doc": "Help & In-App Docs",
    "title": "Chirpy — the AI Assistant",
    "content": "Chirpy answers plain-language questions about Meshtastic using this bundled documentation as its source. Tap the Chirpy button in the docs browser, type a question, and it replies with an answer and links to the relevant pages. Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/help-and-docs.html#chirpy--the-ai-assistant",
    
    "relUrl": "/pl-rPL/user/help-and-docs.html#chirpy--the-ai-assistant"
  },"1871": {
    "doc": "Help & In-App Docs",
    "title": "Related Topics",
    "content": ". | Translate the App — how these pages get localized into other languages | App Functions — the separate system-AI integration (distinct from Chirpy) | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/help-and-docs.html#related-topics",
    
    "relUrl": "/pl-rPL/user/help-and-docs.html#related-topics"
  },"1872": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": " ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/help-and-docs.html",
    
    "relUrl": "/pl-rPL/user/help-and-docs.html"
  },"1873": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": "This same user documentation ships inside the app, so you can read it offline without leaving Meshtastic. Open it from Settings → Help & Documentation. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/help-and-docs.html#help--in-app-docs",
    
    "relUrl": "/zh-rCN/user/help-and-docs.html#help--in-app-docs"
  },"1874": {
    "doc": "Help & In-App Docs",
    "title": "Browsing",
    "content": "The docs browser lists every user-guide page. Tap a page to read it; images and cross-links work just like they do here. Search . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. A page open in the browser: . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/help-and-docs.html#browsing",
    
    "relUrl": "/zh-rCN/user/help-and-docs.html#browsing"
  },"1875": {
    "doc": "Help & In-App Docs",
    "title": "Chirpy — the AI Assistant",
    "content": "Chirpy answers plain-language questions about Meshtastic using this bundled documentation as its source. Tap the Chirpy button in the docs browser, type a question, and it replies with an answer and links to the relevant pages. Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/help-and-docs.html#chirpy--the-ai-assistant",
    
    "relUrl": "/zh-rCN/user/help-and-docs.html#chirpy--the-ai-assistant"
  },"1876": {
    "doc": "Help & In-App Docs",
    "title": "Related Topics",
    "content": ". | Translate the App — how these pages get localized into other languages | App Functions — the separate system-AI integration (distinct from Chirpy) | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/help-and-docs.html#related-topics",
    
    "relUrl": "/zh-rCN/user/help-and-docs.html#related-topics"
  },"1877": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": " ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/help-and-docs.html",
    
    "relUrl": "/zh-rCN/user/help-and-docs.html"
  },"1878": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": "This same user documentation ships inside the app, so you can read it offline without leaving Meshtastic. Open it from Settings → Help & Documentation. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/help-and-docs.html#help--in-app-docs",
    
    "relUrl": "/sq-rAL/user/help-and-docs.html#help--in-app-docs"
  },"1879": {
    "doc": "Help & In-App Docs",
    "title": "Browsing",
    "content": "The docs browser lists every user-guide page. Tap a page to read it; images and cross-links work just like they do here. Search . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. A page open in the browser: . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/help-and-docs.html#browsing",
    
    "relUrl": "/sq-rAL/user/help-and-docs.html#browsing"
  },"1880": {
    "doc": "Help & In-App Docs",
    "title": "Chirpy — the AI Assistant",
    "content": "Chirpy answers plain-language questions about Meshtastic using this bundled documentation as its source. Tap the Chirpy button in the docs browser, type a question, and it replies with an answer and links to the relevant pages. Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/help-and-docs.html#chirpy--the-ai-assistant",
    
    "relUrl": "/sq-rAL/user/help-and-docs.html#chirpy--the-ai-assistant"
  },"1881": {
    "doc": "Help & In-App Docs",
    "title": "Related Topics",
    "content": ". | Translate the App — how these pages get localized into other languages | App Functions — the separate system-AI integration (distinct from Chirpy) | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/help-and-docs.html#related-topics",
    
    "relUrl": "/sq-rAL/user/help-and-docs.html#related-topics"
  },"1882": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": " ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/help-and-docs.html",
    
    "relUrl": "/sq-rAL/user/help-and-docs.html"
  },"1883": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": "This same user documentation ships inside the app, so you can read it offline without leaving Meshtastic. Open it from Settings → Help & Documentation. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/help-and-docs.html#help--in-app-docs",
    
    "relUrl": "/zh-rTW/user/help-and-docs.html#help--in-app-docs"
  },"1884": {
    "doc": "Help & In-App Docs",
    "title": "Browsing",
    "content": "The docs browser lists every user-guide page. Tap a page to read it; images and cross-links work just like they do here. 搜尋 . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. A page open in the browser: . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/help-and-docs.html#browsing",
    
    "relUrl": "/zh-rTW/user/help-and-docs.html#browsing"
  },"1885": {
    "doc": "Help & In-App Docs",
    "title": "Chirpy — the AI Assistant",
    "content": "Chirpy answers plain-language questions about Meshtastic using this bundled documentation as its source. Tap the Chirpy button in the docs browser, type a question, and it replies with an answer and links to the relevant pages. Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/help-and-docs.html#chirpy--the-ai-assistant",
    
    "relUrl": "/zh-rTW/user/help-and-docs.html#chirpy--the-ai-assistant"
  },"1886": {
    "doc": "Help & In-App Docs",
    "title": "相關主題",
    "content": ". | Translate the App — how these pages get localized into other languages | App Functions — the separate system-AI integration (distinct from Chirpy) | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/help-and-docs.html#%E7%9B%B8%E9%97%9C%E4%B8%BB%E9%A1%8C",
    
    "relUrl": "/zh-rTW/user/help-and-docs.html#相關主題"
  },"1887": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": " ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/help-and-docs.html",
    
    "relUrl": "/zh-rTW/user/help-and-docs.html"
  },"1888": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": "Sama kasutajadokumentatsioon on rakenduse sees, nii et saate seda lugeda võrguühenduseta ilma Meshtasticust lahkumata. Ava see menüüst Seaded → Abi ja dokumentatsioon. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/help-and-docs.html#help--in-app-docs",
    
    "relUrl": "/et-rEE/user/help-and-docs.html#help--in-app-docs"
  },"1889": {
    "doc": "Help & In-App Docs",
    "title": "Browsing",
    "content": "Dokumendibrauser loetleb kõik kasutusjuhendi lehed. Selle lugemiseks klõpsa lehel; pildid ja ristlingid toimivad ka. Otsi . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. A page open in the browser: . ![Rakenduses kuvatav dokumentatsioonileht(../../assets/screenshots/docs-browser_page.png) . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/help-and-docs.html#browsing",
    
    "relUrl": "/et-rEE/user/help-and-docs.html#browsing"
  },"1890": {
    "doc": "Help & In-App Docs",
    "title": "Chirpy — TI assistent",
    "content": "Chirpy vastab Meshtasticu kohta käivatele lihtsatele küsimustele, kasutades allikana seda komplekti kuuluvat dokumentatsiooni. Klõpsai dokumendibrauseris nuppu Chirpy, sisesta küsimus ja see vastab vastuse ja linkidega asjakohastele lehtedele. Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. Väike mudel laetakse alla esmakordsel kasutamisel. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/help-and-docs.html#chirpy--ti-assistent",
    
    "relUrl": "/et-rEE/user/help-and-docs.html#chirpy--ti-assistent"
  },"1891": {
    "doc": "Help & In-App Docs",
    "title": "Seotud teemad",
    "content": ". | [Tõlgi rakendus] (translate) — kuidas need lehed teistesse keeltesse lokaliseeritakse | Rakenduse funktsioonid — eraldi süsteemi ja tehisintellekti integratsioon (erineb Chirpyst) | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/help-and-docs.html#seotud-teemad",
    
    "relUrl": "/et-rEE/user/help-and-docs.html#seotud-teemad"
  },"1892": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": " ",
    "url": "/Meshtastic-Android/main/et-rEE/user/help-and-docs.html",
    
    "relUrl": "/et-rEE/user/help-and-docs.html"
  },"1893": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": "This same user documentation ships inside the app, so you can read it offline without leaving Meshtastic. Open it from Settings → Help & Documentation. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/help-and-docs.html#help--in-app-docs",
    
    "relUrl": "/fr-rFR/user/help-and-docs.html#help--in-app-docs"
  },"1894": {
    "doc": "Help & In-App Docs",
    "title": "Browsing",
    "content": "The docs browser lists every user-guide page. Tap a page to read it; images and cross-links work just like they do here. Search . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. A page open in the browser: . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/help-and-docs.html#browsing",
    
    "relUrl": "/fr-rFR/user/help-and-docs.html#browsing"
  },"1895": {
    "doc": "Help & In-App Docs",
    "title": "Chirpy — the AI Assistant",
    "content": "Chirpy answers plain-language questions about Meshtastic using this bundled documentation as its source. Tap the Chirpy button in the docs browser, type a question, and it replies with an answer and links to the relevant pages. Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/help-and-docs.html#chirpy--the-ai-assistant",
    
    "relUrl": "/fr-rFR/user/help-and-docs.html#chirpy--the-ai-assistant"
  },"1896": {
    "doc": "Help & In-App Docs",
    "title": "Related Topics",
    "content": ". | Translate the App — how these pages get localized into other languages | App Functions — the separate system-AI integration (distinct from Chirpy) | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/help-and-docs.html#related-topics",
    
    "relUrl": "/fr-rFR/user/help-and-docs.html#related-topics"
  },"1897": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": " ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/help-and-docs.html",
    
    "relUrl": "/fr-rFR/user/help-and-docs.html"
  },"1898": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": "This same user documentation ships inside the app, so you can read it offline without leaving Meshtastic. Open it from Settings → Help & Documentation. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/help-and-docs.html#help--in-app-docs",
    
    "relUrl": "/tr-rTR/user/help-and-docs.html#help--in-app-docs"
  },"1899": {
    "doc": "Help & In-App Docs",
    "title": "Browsing",
    "content": "The docs browser lists every user-guide page. Tap a page to read it; images and cross-links work just like they do here. Search . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. A page open in the browser: . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/help-and-docs.html#browsing",
    
    "relUrl": "/tr-rTR/user/help-and-docs.html#browsing"
  },"1900": {
    "doc": "Help & In-App Docs",
    "title": "Chirpy — the AI Assistant",
    "content": "Chirpy answers plain-language questions about Meshtastic using this bundled documentation as its source. Tap the Chirpy button in the docs browser, type a question, and it replies with an answer and links to the relevant pages. Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/help-and-docs.html#chirpy--the-ai-assistant",
    
    "relUrl": "/tr-rTR/user/help-and-docs.html#chirpy--the-ai-assistant"
  },"1901": {
    "doc": "Help & In-App Docs",
    "title": "Related Topics",
    "content": ". | Translate the App — how these pages get localized into other languages | App Functions — the separate system-AI integration (distinct from Chirpy) | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/help-and-docs.html#related-topics",
    
    "relUrl": "/tr-rTR/user/help-and-docs.html#related-topics"
  },"1902": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": " ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/help-and-docs.html",
    
    "relUrl": "/tr-rTR/user/help-and-docs.html"
  },"1903": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": "This same user documentation ships inside the app, so you can read it offline without leaving Meshtastic. Open it from Settings → Help & Documentation. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/help-and-docs.html#help--in-app-docs",
    
    "relUrl": "/el-rGR/user/help-and-docs.html#help--in-app-docs"
  },"1904": {
    "doc": "Help & In-App Docs",
    "title": "Browsing",
    "content": "The docs browser lists every user-guide page. Tap a page to read it; images and cross-links work just like they do here. Search . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. A page open in the browser: . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/help-and-docs.html#browsing",
    
    "relUrl": "/el-rGR/user/help-and-docs.html#browsing"
  },"1905": {
    "doc": "Help & In-App Docs",
    "title": "Chirpy — the AI Assistant",
    "content": "Chirpy answers plain-language questions about Meshtastic using this bundled documentation as its source. Tap the Chirpy button in the docs browser, type a question, and it replies with an answer and links to the relevant pages. Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/help-and-docs.html#chirpy--the-ai-assistant",
    
    "relUrl": "/el-rGR/user/help-and-docs.html#chirpy--the-ai-assistant"
  },"1906": {
    "doc": "Help & In-App Docs",
    "title": "Related Topics",
    "content": ". | Translate the App — how these pages get localized into other languages | App Functions — the separate system-AI integration (distinct from Chirpy) | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/help-and-docs.html#related-topics",
    
    "relUrl": "/el-rGR/user/help-and-docs.html#related-topics"
  },"1907": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": " ",
    "url": "/Meshtastic-Android/main/el-rGR/user/help-and-docs.html",
    
    "relUrl": "/el-rGR/user/help-and-docs.html"
  },"1908": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": "This same user documentation ships inside the app, so you can read it offline without leaving Meshtastic. Open it from Settings → Help & Documentation. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/help-and-docs.html#help--in-app-docs",
    
    "relUrl": "/ro-rRO/user/help-and-docs.html#help--in-app-docs"
  },"1909": {
    "doc": "Help & In-App Docs",
    "title": "Browsing",
    "content": "The docs browser lists every user-guide page. Tap a page to read it; images and cross-links work just like they do here. Search . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. A page open in the browser: . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/help-and-docs.html#browsing",
    
    "relUrl": "/ro-rRO/user/help-and-docs.html#browsing"
  },"1910": {
    "doc": "Help & In-App Docs",
    "title": "Chirpy — the AI Assistant",
    "content": "Chirpy answers plain-language questions about Meshtastic using this bundled documentation as its source. Tap the Chirpy button in the docs browser, type a question, and it replies with an answer and links to the relevant pages. Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/help-and-docs.html#chirpy--the-ai-assistant",
    
    "relUrl": "/ro-rRO/user/help-and-docs.html#chirpy--the-ai-assistant"
  },"1911": {
    "doc": "Help & In-App Docs",
    "title": "Related Topics",
    "content": ". | Translate the App — how these pages get localized into other languages | App Functions — the separate system-AI integration (distinct from Chirpy) | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/help-and-docs.html#related-topics",
    
    "relUrl": "/ro-rRO/user/help-and-docs.html#related-topics"
  },"1912": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": " ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/help-and-docs.html",
    
    "relUrl": "/ro-rRO/user/help-and-docs.html"
  },"1913": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": "This same user documentation ships inside the app, so you can read it offline without leaving Meshtastic. Open it from Settings → Help & Documentation. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/help-and-docs.html#help--in-app-docs",
    
    "relUrl": "/iw-rIL/user/help-and-docs.html#help--in-app-docs"
  },"1914": {
    "doc": "Help & In-App Docs",
    "title": "Browsing",
    "content": "The docs browser lists every user-guide page. Tap a page to read it; images and cross-links work just like they do here. Search . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. A page open in the browser: . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/help-and-docs.html#browsing",
    
    "relUrl": "/iw-rIL/user/help-and-docs.html#browsing"
  },"1915": {
    "doc": "Help & In-App Docs",
    "title": "Chirpy — the AI Assistant",
    "content": "Chirpy answers plain-language questions about Meshtastic using this bundled documentation as its source. Tap the Chirpy button in the docs browser, type a question, and it replies with an answer and links to the relevant pages. Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/help-and-docs.html#chirpy--the-ai-assistant",
    
    "relUrl": "/iw-rIL/user/help-and-docs.html#chirpy--the-ai-assistant"
  },"1916": {
    "doc": "Help & In-App Docs",
    "title": "Related Topics",
    "content": ". | Translate the App — how these pages get localized into other languages | App Functions — the separate system-AI integration (distinct from Chirpy) | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/help-and-docs.html#related-topics",
    
    "relUrl": "/iw-rIL/user/help-and-docs.html#related-topics"
  },"1917": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": " ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/help-and-docs.html",
    
    "relUrl": "/iw-rIL/user/help-and-docs.html"
  },"1918": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": "This same user documentation ships inside the app, so you can read it offline without leaving Meshtastic. Open it from Settings → Help & Documentation. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/help-and-docs.html#help--in-app-docs",
    
    "relUrl": "/pt-rBR/user/help-and-docs.html#help--in-app-docs"
  },"1919": {
    "doc": "Help & In-App Docs",
    "title": "Browsing",
    "content": "The docs browser lists every user-guide page. Tap a page to read it; images and cross-links work just like they do here. Search . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. A page open in the browser: . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/help-and-docs.html#browsing",
    
    "relUrl": "/pt-rBR/user/help-and-docs.html#browsing"
  },"1920": {
    "doc": "Help & In-App Docs",
    "title": "Chirpy — the AI Assistant",
    "content": "Chirpy answers plain-language questions about Meshtastic using this bundled documentation as its source. Tap the Chirpy button in the docs browser, type a question, and it replies with an answer and links to the relevant pages. Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/help-and-docs.html#chirpy--the-ai-assistant",
    
    "relUrl": "/pt-rBR/user/help-and-docs.html#chirpy--the-ai-assistant"
  },"1921": {
    "doc": "Help & In-App Docs",
    "title": "Related Topics",
    "content": ". | Translate the App — how these pages get localized into other languages | App Functions — the separate system-AI integration (distinct from Chirpy) | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/help-and-docs.html#related-topics",
    
    "relUrl": "/pt-rBR/user/help-and-docs.html#related-topics"
  },"1922": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": " ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/help-and-docs.html",
    
    "relUrl": "/pt-rBR/user/help-and-docs.html"
  },"1923": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": "This same user documentation ships inside the app, so you can read it offline without leaving Meshtastic. Open it from Settings → Help & Documentation. ",
    "url": "/Meshtastic-Android/main/en/user/help-and-docs.html#help--in-app-docs",
    
    "relUrl": "/en/user/help-and-docs.html#help--in-app-docs"
  },"1924": {
    "doc": "Help & In-App Docs",
    "title": "Browsing",
    "content": "The docs browser lists every user-guide page. Tap a page to read it; images and cross-links work just like they do here. Search . Tap the search field at the top of the docs browser to open a full-screen search view. Type to filter pages by title and keywords — results update as you type, under the same field. The back arrow, or the keyboard’s search action, closes the view. The field hides while you scroll down the page list and comes back when you scroll up. A page open in the browser: . ",
    "url": "/Meshtastic-Android/main/en/user/help-and-docs.html#browsing",
    
    "relUrl": "/en/user/help-and-docs.html#browsing"
  },"1925": {
    "doc": "Help & In-App Docs",
    "title": "Chirpy — the AI Assistant",
    "content": "Chirpy answers plain-language questions about Meshtastic using this bundled documentation as its source. Tap the Chirpy button in the docs browser, type a question, and it replies with an answer and links to the relevant pages. Chirpy is Google-flavor Android only. On F-Droid, desktop and iOS builds the assistant button does not appear at all — the same is true on a phone whose hardware cannot run the on-device model. Browsing and the docs browser’s own search work normally on every platform. 🔒 Privacy: On supported phones running the Google-flavor build, Chirpy runs on-device using Gemini Nano — your questions never leave your phone. A small model downloads on first use. ",
    "url": "/Meshtastic-Android/main/en/user/help-and-docs.html#chirpy--the-ai-assistant",
    
    "relUrl": "/en/user/help-and-docs.html#chirpy--the-ai-assistant"
  },"1926": {
    "doc": "Help & In-App Docs",
    "title": "Related Topics",
    "content": ". | Translate the App — how these pages get localized into other languages | App Functions — the separate system-AI integration (distinct from Chirpy) | . ",
    "url": "/Meshtastic-Android/main/en/user/help-and-docs.html#related-topics",
    
    "relUrl": "/en/user/help-and-docs.html#related-topics"
  },"1927": {
    "doc": "Help & In-App Docs",
    "title": "Help & In-App Docs",
    "content": " ",
    "url": "/Meshtastic-Android/main/en/user/help-and-docs.html",
    
    "relUrl": "/en/user/help-and-docs.html"
  },"1928": {
    "doc": "Home",
    "title": "Meshtastic Android App Documentation",
    "content": "User and developer documentation for the Meshtastic Android and Desktop app, built with Kotlin Multiplatform. Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ",
    "url": "/Meshtastic-Android/main/sk-rSK/#meshtastic-android-app-documentation",
    
    "relUrl": "/sk-rSK/#meshtastic-android-app-documentation"
  },"1929": {
    "doc": "Home",
    "title": "Quick Links",
    "content": "| Guide | Popis | . | Getting Started | Connect your first radio and send a message | . | Messages & Channels | Channel broadcasts, direct messages, reactions, and encryption | . | Nodes | Understanding the mesh network node list | . | Signal Meter | How the LoRa signal quality meter works | . | Units & Locale | How temperatures, distances, and times adapt to your region | . | Desktop App | Linux, macOS, and Windows desktop usage | . | Architecture | App architecture overview for contributors | . | 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. ",
    "url": "/Meshtastic-Android/main/sk-rSK/#quick-links",
    
    "relUrl": "/sk-rSK/#quick-links"
  },"1930": {
    "doc": "Home",
    "title": "Home",
    "content": " ",
    "url": "/Meshtastic-Android/main/sk-rSK/",
    
    "relUrl": "/sk-rSK/"
  },"1931": {
    "doc": "Home",
    "title": "Meshtastic Android App Documentation",
    "content": "User and developer documentation for the Meshtastic Android and Desktop app, built with Kotlin Multiplatform. Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ",
    "url": "/Meshtastic-Android/main/be-rBY/#meshtastic-android-app-documentation",
    
    "relUrl": "/be-rBY/#meshtastic-android-app-documentation"
  },"1932": {
    "doc": "Home",
    "title": "Quick Links",
    "content": "| Guide | Апісанне | . | Getting Started | Connect your first radio and send a message | . | Messages & Channels | Channel broadcasts, direct messages, reactions, and encryption | . | Nodes | Understanding the mesh network node list | . | Signal Meter | How the LoRa signal quality meter works | . | Units & Locale | How temperatures, distances, and times adapt to your region | . | Desktop App | Linux, macOS, and Windows desktop usage | . | Architecture | App architecture overview for contributors | . | 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. ",
    "url": "/Meshtastic-Android/main/be-rBY/#quick-links",
    
    "relUrl": "/be-rBY/#quick-links"
  },"1933": {
    "doc": "Home",
    "title": "Home",
    "content": " ",
    "url": "/Meshtastic-Android/main/be-rBY/",
    
    "relUrl": "/be-rBY/"
  },"1934": {
    "doc": "Home",
    "title": "Meshtastic Android App Documentation",
    "content": "User and developer documentation for the Meshtastic Android and Desktop app, built with Kotlin Multiplatform. Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ",
    "url": "/Meshtastic-Android/main/it-rIT/#meshtastic-android-app-documentation",
    
    "relUrl": "/it-rIT/#meshtastic-android-app-documentation"
  },"1935": {
    "doc": "Home",
    "title": "Quick Links",
    "content": "| Guide | Descrizione | . | Getting Started | Connect your first radio and send a message | . | Messages & Channels | Channel broadcasts, direct messages, reactions, and encryption | . | Nodes | Understanding the mesh network node list | . | Signal Meter | How the LoRa signal quality meter works | . | Units & Locale | How temperatures, distances, and times adapt to your region | . | Desktop App | Linux, macOS, and Windows desktop usage | . | Architecture | App architecture overview for contributors | . | 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. ",
    "url": "/Meshtastic-Android/main/it-rIT/#quick-links",
    
    "relUrl": "/it-rIT/#quick-links"
  },"1936": {
    "doc": "Home",
    "title": "Home",
    "content": " ",
    "url": "/Meshtastic-Android/main/it-rIT/",
    
    "relUrl": "/it-rIT/"
  },"1937": {
    "doc": "Home",
    "title": "Meshtastic Android App Documentation",
    "content": "User and developer documentation for the Meshtastic Android and Desktop app, built with Kotlin Multiplatform. Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ",
    "url": "/Meshtastic-Android/main/es-rES/#meshtastic-android-app-documentation",
    
    "relUrl": "/es-rES/#meshtastic-android-app-documentation"
  },"1938": {
    "doc": "Home",
    "title": "Quick Links",
    "content": "| Guide | Descripción | . | Getting Started | Connect your first radio and send a message | . | Messages & Channels | Channel broadcasts, direct messages, reactions, and encryption | . | Nodes | Understanding the mesh network node list | . | Signal Meter | How the LoRa signal quality meter works | . | Units & Locale | How temperatures, distances, and times adapt to your region | . | Desktop App | Linux, macOS, and Windows desktop usage | . | Architecture | App architecture overview for contributors | . | 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. ",
    "url": "/Meshtastic-Android/main/es-rES/#quick-links",
    
    "relUrl": "/es-rES/#quick-links"
  },"1939": {
    "doc": "Home",
    "title": "Home",
    "content": " ",
    "url": "/Meshtastic-Android/main/es-rES/",
    
    "relUrl": "/es-rES/"
  },"1940": {
    "doc": "Home",
    "title": "Meshtastic Android App Documentation",
    "content": "User and developer documentation for the Meshtastic Android and Desktop app, built with Kotlin Multiplatform. Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ",
    "url": "/Meshtastic-Android/main/sl-rSI/#meshtastic-android-app-documentation",
    
    "relUrl": "/sl-rSI/#meshtastic-android-app-documentation"
  },"1941": {
    "doc": "Home",
    "title": "Quick Links",
    "content": "| Guide | Opis | . | Getting Started | Connect your first radio and send a message | . | Messages & Channels | Channel broadcasts, direct messages, reactions, and encryption | . | Nodes | Understanding the mesh network node list | . | Signal Meter | How the LoRa signal quality meter works | . | Units & Locale | How temperatures, distances, and times adapt to your region | . | Desktop App | Linux, macOS, and Windows desktop usage | . | Architecture | App architecture overview for contributors | . | 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. ",
    "url": "/Meshtastic-Android/main/sl-rSI/#quick-links",
    
    "relUrl": "/sl-rSI/#quick-links"
  },"1942": {
    "doc": "Home",
    "title": "Home",
    "content": " ",
    "url": "/Meshtastic-Android/main/sl-rSI/",
    
    "relUrl": "/sl-rSI/"
  },"1943": {
    "doc": "Home",
    "title": "Meshtastic Android App Documentation",
    "content": "User and developer documentation for the Meshtastic Android and Desktop app, built with Kotlin Multiplatform. Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ",
    "url": "/Meshtastic-Android/main/no-rNO/#meshtastic-android-app-documentation",
    
    "relUrl": "/no-rNO/#meshtastic-android-app-documentation"
  },"1944": {
    "doc": "Home",
    "title": "Quick Links",
    "content": "| Guide | Beskrivelse | . | Getting Started | Connect your first radio and send a message | . | Messages & Channels | Channel broadcasts, direct messages, reactions, and encryption | . | Nodes | Understanding the mesh network node list | . | Signal Meter | How the LoRa signal quality meter works | . | Units & Locale | How temperatures, distances, and times adapt to your region | . | Desktop App | Linux, macOS, and Windows desktop usage | . | Architecture | App architecture overview for contributors | . | 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. ",
    "url": "/Meshtastic-Android/main/no-rNO/#quick-links",
    
    "relUrl": "/no-rNO/#quick-links"
  },"1945": {
    "doc": "Home",
    "title": "Home",
    "content": " ",
    "url": "/Meshtastic-Android/main/no-rNO/",
    
    "relUrl": "/no-rNO/"
  },"1946": {
    "doc": "Home",
    "title": "Meshtastic Android App Documentation",
    "content": "User and developer documentation for the Meshtastic Android and Desktop app, built with Kotlin Multiplatform. Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ",
    "url": "/Meshtastic-Android/main/hu-rHU/#meshtastic-android-app-documentation",
    
    "relUrl": "/hu-rHU/#meshtastic-android-app-documentation"
  },"1947": {
    "doc": "Home",
    "title": "Quick Links",
    "content": "| Guide | Leírás | . | Getting Started | Connect your first radio and send a message | . | Messages & Channels | Channel broadcasts, direct messages, reactions, and encryption | . | Nodes | Understanding the mesh network node list | . | Signal Meter | How the LoRa signal quality meter works | . | Units & Locale | How temperatures, distances, and times adapt to your region | . | Desktop App | Linux, macOS, and Windows desktop usage | . | Architecture | App architecture overview for contributors | . | 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. ",
    "url": "/Meshtastic-Android/main/hu-rHU/#quick-links",
    
    "relUrl": "/hu-rHU/#quick-links"
  },"1948": {
    "doc": "Home",
    "title": "Home",
    "content": " ",
    "url": "/Meshtastic-Android/main/hu-rHU/",
    
    "relUrl": "/hu-rHU/"
  },"1949": {
    "doc": "Домой",
    "title": "Документация приложения Meshtastic Android",
    "content": "User and developer documentation for the Meshtastic Android and Desktop app, built with Kotlin Multiplatform. Используйте боковую панель навигации, чтобы просматривать Руководство пользователя по функциям приложения и Руководство разработчика по внесению вклада в проект. ",
    "url": "/Meshtastic-Android/main/ru-rRU/#%D0%B4%D0%BE%D0%BA%D1%83%D0%BC%D0%B5%D0%BD%D1%82%D0%B0%D1%86%D0%B8%D1%8F-%D0%BF%D1%80%D0%B8%D0%BB%D0%BE%D0%B6%D0%B5%D0%BD%D0%B8%D1%8F-meshtastic-android",
    
    "relUrl": "/ru-rRU/#документация-приложения-meshtastic-android"
  },"1950": {
    "doc": "Домой",
    "title": "Быстрые ссылки",
    "content": "| Руководство | Описание | . | Начало работы | Подключи свою первую радиостанцию и отправь сообщение | . | Сообщения и Каналы | Широковещательный канал, личные сообщения, реакции и шифрование | . | Ноды | Понимание списка нод mesh-сети | . | Индикатор сигнала | Как работает индикатор измерения качества сигнала LoRa | . | Ед.изм. и локализация | Как температуру, расстояние и время адаптировать к своему региону | . | Десктопное приложение | Использование десктопных систем Linux, macOS и Windows | . | Архитектура | Обзор архитектуры приложения для участников | . | Вклад | Именование веток, рабочий процесс PR и команды проверки | . Эта документация предоставляется из того же источника Markdown, который обеспечивает работу встроенного браузера Справка и документация. ",
    "url": "/Meshtastic-Android/main/ru-rRU/#%D0%B1%D1%8B%D1%81%D1%82%D1%80%D1%8B%D0%B5-%D1%81%D1%81%D1%8B%D0%BB%D0%BA%D0%B8",
    
    "relUrl": "/ru-rRU/#быстрые-ссылки"
  },"1951": {
    "doc": "Домой",
    "title": "Домой",
    "content": " ",
    "url": "/Meshtastic-Android/main/ru-rRU/",
    
    "relUrl": "/ru-rRU/"
  },"1952": {
    "doc": "Home",
    "title": "Dokumentace aplikace Meshtastic Android",
    "content": "Uživatelská a vývojářská dokumentace aplikace Meshtastic pro Android a Desktop, vytvořené pomocí Kotlin Multiplatform. Pomocí navigace v postranním panelu si můžete procházet Uživatelskou příručku s funkcemi aplikace a Vývojářskou příručku s informacemi o přispívání do projektu. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/#dokumentace-aplikace-meshtastic-android",
    
    "relUrl": "/cs-rCZ/#dokumentace-aplikace-meshtastic-android"
  },"1953": {
    "doc": "Home",
    "title": "Rychlé odkazy",
    "content": "| Příručka | Popis | . | Začínáme | Připojte své první rádio a pošlete zprávu | . | Zprávy a kanály | Vysílání kanálů, přímé zprávy, reakce a šifrování | . | Uzel | Porozumění seznamu uzlů mesh sítě | . | Měřič signálu | Jak funguje měřič kvality signálu LoRa | . | Jednotky a lokalizace | Jak se teploty, vzdálenosti a časy přizpůsobují vašemu regionu | . | Desktopová aplikace | Používání desktopové aplikace v Linuxu, macOS a Windows | . | Architektura | Přehled architektury aplikace pro přispěvatele | . | Přispívání do projektu | Pojmenování větví, postup práce s PR a příkazy pro ověření | . Tato dokumentace je generována ze stejného zdroje Markdownu, který používá prohlížeč Nápovědy a dokumentace přímo v aplikaci. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/#rychl%C3%A9-odkazy",
    
    "relUrl": "/cs-rCZ/#rychlé-odkazy"
  },"1954": {
    "doc": "Home",
    "title": "Home",
    "content": " ",
    "url": "/Meshtastic-Android/main/cs-rCZ/",
    
    "relUrl": "/cs-rCZ/"
  },"1955": {
    "doc": "Home",
    "title": "Документация за приложението Meshtastic за Android",
    "content": "User and developer documentation for the Meshtastic Android and Desktop app, built with Kotlin Multiplatform. Използвайте страничната лента за навигация, за да разгледате Ръководството за потребителя за функциите на приложението и Ръководството за разработчици за участие в проекта. ",
    "url": "/Meshtastic-Android/main/bg-rBG/#%D0%B4%D0%BE%D0%BA%D1%83%D0%BC%D0%B5%D0%BD%D1%82%D0%B0%D1%86%D0%B8%D1%8F-%D0%B7%D0%B0-%D0%BF%D1%80%D0%B8%D0%BB%D0%BE%D0%B6%D0%B5%D0%BD%D0%B8%D0%B5%D1%82%D0%BE-meshtastic-%D0%B7%D0%B0-android",
    
    "relUrl": "/bg-rBG/#документация-за-приложението-meshtastic-за-android"
  },"1956": {
    "doc": "Home",
    "title": "Бързи връзки",
    "content": "| Ръководство | Описание | . | Първи стъпки | Свържете първото си радио и изпратете съобщение | . | Съобщения & Канали | Channel broadcasts, direct messages, reactions, and encryption | . | Възли | Understanding the mesh network node list | . | Измервател на сигнала | Как работи измервателят на качеството на LoRa сигнала | . | Единици & Локация | How temperatures, distances, and times adapt to your region | . | Настолно приложение | Използване на настолни компютри на Linux, macOS и Windows | . | Архитектура | App architecture overview for contributors | . | Допринасяне | Branch naming, PR workflow, and verification commands | . This documentation is served from the same markdown source that powers the in-app Help & Documentation browser. ",
    "url": "/Meshtastic-Android/main/bg-rBG/#%D0%B1%D1%8A%D1%80%D0%B7%D0%B8-%D0%B2%D1%80%D1%8A%D0%B7%D0%BA%D0%B8",
    
    "relUrl": "/bg-rBG/#бързи-връзки"
  },"1957": {
    "doc": "Home",
    "title": "Home",
    "content": " ",
    "url": "/Meshtastic-Android/main/bg-rBG/",
    
    "relUrl": "/bg-rBG/"
  },"1958": {
    "doc": "Home",
    "title": "Meshtastic Android App Documentation",
    "content": "User and developer documentation for the Meshtastic Android and Desktop app, built with Kotlin Multiplatform. Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ",
    "url": "/Meshtastic-Android/main/ga-rIE/#meshtastic-android-app-documentation",
    
    "relUrl": "/ga-rIE/#meshtastic-android-app-documentation"
  },"1959": {
    "doc": "Home",
    "title": "Quick Links",
    "content": "| Guide | Cur síos | . | Getting Started | Connect your first radio and send a message | . | Messages & Channels | Channel broadcasts, direct messages, reactions, and encryption | . | Nodes | Understanding the mesh network node list | . | Signal Meter | How the LoRa signal quality meter works | . | Units & Locale | How temperatures, distances, and times adapt to your region | . | Desktop App | Linux, macOS, and Windows desktop usage | . | Architecture | App architecture overview for contributors | . | 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. ",
    "url": "/Meshtastic-Android/main/ga-rIE/#quick-links",
    
    "relUrl": "/ga-rIE/#quick-links"
  },"1960": {
    "doc": "Home",
    "title": "Home",
    "content": " ",
    "url": "/Meshtastic-Android/main/ga-rIE/",
    
    "relUrl": "/ga-rIE/"
  },"1961": {
    "doc": "Home",
    "title": "Meshtastic Android App Documentation",
    "content": "User and developer documentation for the Meshtastic Android and Desktop app, built with Kotlin Multiplatform. Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ",
    "url": "/Meshtastic-Android/main/fr-rCA/#meshtastic-android-app-documentation",
    
    "relUrl": "/fr-rCA/#meshtastic-android-app-documentation"
  },"1962": {
    "doc": "Home",
    "title": "Liens rapides",
    "content": "| Guide | Description | . | Démarrer | Connectez votre première radio et envoyez un message | . | Messages & Canaux | Diffusions de chaînes, messages directs, réactions et chiffrement | . | [Nœuds (user/nodes) | Comprendre la liste des nœuds du réseau de maillage | . | Mesure du Signal | Comment fonctionne le compteur de qualité du signal LoRa | . | Unités et Localisation | Comment les températures, les distances et le temps s’adaptent à votre région | . | Application de bureau | Utilisation de Linux, macOS et Windows | . | Architecture | Aperçu de l’architecture de l’application pour les contributeurs | . | Contribuer | Nommage des branches, flux de production PR et commandes de vérification | . Cette documentation est servie à partir de la même source markdown qui alimente le navigateur dans l’application Aide et Documentation. ",
    "url": "/Meshtastic-Android/main/fr-rCA/#liens-rapides",
    
    "relUrl": "/fr-rCA/#liens-rapides"
  },"1963": {
    "doc": "Home",
    "title": "Home",
    "content": " ",
    "url": "/Meshtastic-Android/main/fr-rCA/",
    
    "relUrl": "/fr-rCA/"
  },"1964": {
    "doc": "Home",
    "title": "Meshtastic Android App Documentation",
    "content": "User and developer documentation for the Meshtastic Android and Desktop app, built with Kotlin Multiplatform. Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ",
    "url": "/Meshtastic-Android/main/srp/#meshtastic-android-app-documentation",
    
    "relUrl": "/srp/#meshtastic-android-app-documentation"
  },"1965": {
    "doc": "Home",
    "title": "Quick Links",
    "content": "| Guide | Опис | . | Getting Started | Connect your first radio and send a message | . | Messages & Channels | Channel broadcasts, direct messages, reactions, and encryption | . | Nodes | Understanding the mesh network node list | . | Signal Meter | How the LoRa signal quality meter works | . | Units & Locale | How temperatures, distances, and times adapt to your region | . | Desktop App | Linux, macOS, and Windows desktop usage | . | Architecture | App architecture overview for contributors | . | 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. ",
    "url": "/Meshtastic-Android/main/srp/#quick-links",
    
    "relUrl": "/srp/#quick-links"
  },"1966": {
    "doc": "Home",
    "title": "Home",
    "content": " ",
    "url": "/Meshtastic-Android/main/srp/",
    
    "relUrl": "/srp/"
  },"1967": {
    "doc": "Home",
    "title": "Meshtastic Android App Documentation",
    "content": "User and developer documentation for the Meshtastic Android and Desktop app, built with Kotlin Multiplatform. Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ",
    "url": "/Meshtastic-Android/main/ca-rES/#meshtastic-android-app-documentation",
    
    "relUrl": "/ca-rES/#meshtastic-android-app-documentation"
  },"1968": {
    "doc": "Home",
    "title": "Quick Links",
    "content": "| Guide | Descripció | . | Getting Started | Connect your first radio and send a message | . | Messages & Channels | Channel broadcasts, direct messages, reactions, and encryption | . | Nodes | Understanding the mesh network node list | . | Signal Meter | How the LoRa signal quality meter works | . | Units & Locale | How temperatures, distances, and times adapt to your region | . | Desktop App | Linux, macOS, and Windows desktop usage | . | Architecture | App architecture overview for contributors | . | 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. ",
    "url": "/Meshtastic-Android/main/ca-rES/#quick-links",
    
    "relUrl": "/ca-rES/#quick-links"
  },"1969": {
    "doc": "Home",
    "title": "Home",
    "content": " ",
    "url": "/Meshtastic-Android/main/ca-rES/",
    
    "relUrl": "/ca-rES/"
  },"1970": {
    "doc": "Home",
    "title": "Meshtastic Android App Documentation",
    "content": "User and developer documentation for the Meshtastic Android and Desktop app, built with Kotlin Multiplatform. Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ",
    "url": "/Meshtastic-Android/main/ko-rKR/#meshtastic-android-app-documentation",
    
    "relUrl": "/ko-rKR/#meshtastic-android-app-documentation"
  },"1971": {
    "doc": "Home",
    "title": "Quick Links",
    "content": "| Guide | 설명 | . | Getting Started | Connect your first radio and send a message | . | Messages & Channels | Channel broadcasts, direct messages, reactions, and encryption | . | Nodes | Understanding the mesh network node list | . | Signal Meter | How the LoRa signal quality meter works | . | Units & Locale | How temperatures, distances, and times adapt to your region | . | Desktop App | Linux, macOS, and Windows desktop usage | . | Architecture | App architecture overview for contributors | . | 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. ",
    "url": "/Meshtastic-Android/main/ko-rKR/#quick-links",
    
    "relUrl": "/ko-rKR/#quick-links"
  },"1972": {
    "doc": "Home",
    "title": "Home",
    "content": " ",
    "url": "/Meshtastic-Android/main/ko-rKR/",
    
    "relUrl": "/ko-rKR/"
  },"1973": {
    "doc": "Home",
    "title": "Meshtastic Android App Documentation",
    "content": "User and developer documentation for the Meshtastic Android and Desktop app, built with Kotlin Multiplatform. Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ",
    "url": "/Meshtastic-Android/main/sv-rSE/#meshtastic-android-app-documentation",
    
    "relUrl": "/sv-rSE/#meshtastic-android-app-documentation"
  },"1974": {
    "doc": "Home",
    "title": "Quick Links",
    "content": "| Guide | Beskrivning | . | Getting Started | Connect your first radio and send a message | . | Messages & Channels | Channel broadcasts, direct messages, reactions, and encryption | . | Nodes | Understanding the mesh network node list | . | Signal Meter | How the LoRa signal quality meter works | . | Units & Locale | How temperatures, distances, and times adapt to your region | . | Desktop App | Linux, macOS, and Windows desktop usage | . | Architecture | App architecture overview for contributors | . | 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. ",
    "url": "/Meshtastic-Android/main/sv-rSE/#quick-links",
    
    "relUrl": "/sv-rSE/#quick-links"
  },"1975": {
    "doc": "Home",
    "title": "Home",
    "content": " ",
    "url": "/Meshtastic-Android/main/sv-rSE/",
    
    "relUrl": "/sv-rSE/"
  },"1976": {
    "doc": "Home",
    "title": "Meshtastic Android App Documentation",
    "content": "User and developer documentation for the Meshtastic Android and Desktop app, built with Kotlin Multiplatform. Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ",
    "url": "/Meshtastic-Android/main/ht-rHT/#meshtastic-android-app-documentation",
    
    "relUrl": "/ht-rHT/#meshtastic-android-app-documentation"
  },"1977": {
    "doc": "Home",
    "title": "Quick Links",
    "content": "| Guide | Deskripsyon | . | Getting Started | Connect your first radio and send a message | . | Messages & Channels | Channel broadcasts, direct messages, reactions, and encryption | . | Nodes | Understanding the mesh network node list | . | Signal Meter | How the LoRa signal quality meter works | . | Units & Locale | How temperatures, distances, and times adapt to your region | . | Desktop App | Linux, macOS, and Windows desktop usage | . | Architecture | App architecture overview for contributors | . | 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. ",
    "url": "/Meshtastic-Android/main/ht-rHT/#quick-links",
    
    "relUrl": "/ht-rHT/#quick-links"
  },"1978": {
    "doc": "Home",
    "title": "Home",
    "content": " ",
    "url": "/Meshtastic-Android/main/ht-rHT/",
    
    "relUrl": "/ht-rHT/"
  },"1979": {
    "doc": "Home",
    "title": "Meshtastic Android App Documentation",
    "content": "User and developer documentation for the Meshtastic Android and Desktop app, built with Kotlin Multiplatform. Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/#meshtastic-android-app-documentation",
    
    "relUrl": "/sr-rLatn/#meshtastic-android-app-documentation"
  },"1980": {
    "doc": "Home",
    "title": "Quick Links",
    "content": "| Guide | Опис | . | Getting Started | Connect your first radio and send a message | . | Messages & Channels | Channel broadcasts, direct messages, reactions, and encryption | . | Nodes | Understanding the mesh network node list | . | Signal Meter | How the LoRa signal quality meter works | . | Units & Locale | How temperatures, distances, and times adapt to your region | . | Desktop App | Linux, macOS, and Windows desktop usage | . | Architecture | App architecture overview for contributors | . | 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. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/#quick-links",
    
    "relUrl": "/sr-rLatn/#quick-links"
  },"1981": {
    "doc": "Home",
    "title": "Home",
    "content": " ",
    "url": "/Meshtastic-Android/main/sr-rLatn/",
    
    "relUrl": "/sr-rLatn/"
  },"1982": {
    "doc": "Home",
    "title": "Meshtastic Android App Documentation",
    "content": "User and developer documentation for the Meshtastic Android and Desktop app, built with Kotlin Multiplatform. Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ",
    "url": "/Meshtastic-Android/main/nl-rNL/#meshtastic-android-app-documentation",
    
    "relUrl": "/nl-rNL/#meshtastic-android-app-documentation"
  },"1983": {
    "doc": "Home",
    "title": "Quick Links",
    "content": "| Guide | Beschrijving | . | Getting Started | Connect your first radio and send a message | . | Messages & Channels | Channel broadcasts, direct messages, reactions, and encryption | . | Nodes | Understanding the mesh network node list | . | Signal Meter | How the LoRa signal quality meter works | . | Units & Locale | How temperatures, distances, and times adapt to your region | . | Desktop App | Linux, macOS, and Windows desktop usage | . | Architecture | App architecture overview for contributors | . | 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. ",
    "url": "/Meshtastic-Android/main/nl-rNL/#quick-links",
    
    "relUrl": "/nl-rNL/#quick-links"
  },"1984": {
    "doc": "Home",
    "title": "Home",
    "content": " ",
    "url": "/Meshtastic-Android/main/nl-rNL/",
    
    "relUrl": "/nl-rNL/"
  },"1985": {
    "doc": "Головна",
    "title": "Meshtastic Android App Documentation",
    "content": "User and developer documentation for the Meshtastic Android and Desktop app, built with Kotlin Multiplatform. Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ",
    "url": "/Meshtastic-Android/main/uk-rUA/#meshtastic-android-app-documentation",
    
    "relUrl": "/uk-rUA/#meshtastic-android-app-documentation"
  },"1986": {
    "doc": "Головна",
    "title": "Швидкі посилання",
    "content": "| Посібник | Опис | . | Getting Started | Connect your first radio and send a message | . | Messages & Channels | Channel broadcasts, direct messages, reactions, and encryption | . | Nodes | Understanding the mesh network node list | . | Signal Meter | How the LoRa signal quality meter works | . | Units & Locale | How temperatures, distances, and times adapt to your region | . | Desktop App | Linux, macOS, and Windows desktop usage | . | Architecture | App architecture overview for contributors | . | 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. ",
    "url": "/Meshtastic-Android/main/uk-rUA/#%D1%88%D0%B2%D0%B8%D0%B4%D0%BA%D1%96-%D0%BF%D0%BE%D1%81%D0%B8%D0%BB%D0%B0%D0%BD%D0%BD%D1%8F",
    
    "relUrl": "/uk-rUA/#швидкі-посилання"
  },"1987": {
    "doc": "Головна",
    "title": "Головна",
    "content": " ",
    "url": "/Meshtastic-Android/main/uk-rUA/",
    
    "relUrl": "/uk-rUA/"
  },"1988": {
    "doc": "Etusivu",
    "title": "Meshtastic Android -sovelluksen dokumentaatio",
    "content": "Meshtastic Android- ja Työpöytä-sovelluksen käyttäjä- ja kehittäjädokumentaatio, toteutettu Kotlin Multiplatformilla. Käytä sivupalkkia selataksesi käyttöopasta ja Kehittäjäopasta. Käyttöoppaasta löydät sovelluksen ominaisuudet ja kehittäjäoppaasta ohjeet projektin kehittämiseen osallistumiseen. ",
    "url": "/Meshtastic-Android/main/fi-rFI/#meshtastic-android--sovelluksen-dokumentaatio",
    
    "relUrl": "/fi-rFI/#meshtastic-android--sovelluksen-dokumentaatio"
  },"1989": {
    "doc": "Etusivu",
    "title": "Pikalinkit",
    "content": "| Opas | Kuvaus | . | Aloittaminen | Yhdistä radioon ja lähetä viesti | . | Viestit & kanavat | Kanavaviestit, yksityisviestit, reaktiot ja salaus | . | Radiot | Mesh-verkon radioluettelon ymmärtäminen | . | Signaalimittari | Miten LoRa-signaalin laatumittari toimii | . | Yksiköt & kielialue | Lämpötilojen, etäisyyksien ja aikaesitysten mukautuminen alueesi asetuksiin | . | Työpöytäsovellus | Työpöytäsovelluksen käyttö Linuxissa, macOS ja Windows käyttöjärjestelmissä | . | Arkkitehtuuri | Yleiskatsaus sovelluksen arkkitehtuuriin kehittäjille | . | Osallistuminen kehitystyöhön | Haarojen nimeäminen, PR-työnkulku ja tarkistuskomennot | . Tämä dokumentaatio perustuu samoihin Markdown-lähdetiedostoihin kuin sovelluksen sisäinen Ohje ja dokumentaatio -osio. ",
    "url": "/Meshtastic-Android/main/fi-rFI/#pikalinkit",
    
    "relUrl": "/fi-rFI/#pikalinkit"
  },"1990": {
    "doc": "Etusivu",
    "title": "Etusivu",
    "content": " ",
    "url": "/Meshtastic-Android/main/fi-rFI/",
    
    "relUrl": "/fi-rFI/"
  },"1991": {
    "doc": "Home",
    "title": "Meshtastic Android App Documentation",
    "content": "User and developer documentation for the Meshtastic Android and Desktop app, built with Kotlin Multiplatform. Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ",
    "url": "/Meshtastic-Android/main/is-rIS/#meshtastic-android-app-documentation",
    
    "relUrl": "/is-rIS/#meshtastic-android-app-documentation"
  },"1992": {
    "doc": "Home",
    "title": "Quick Links",
    "content": "| Guide | Lýsing | . | Getting Started | Connect your first radio and send a message | . | Messages & Channels | Channel broadcasts, direct messages, reactions, and encryption | . | Nodes | Understanding the mesh network node list | . | Signal Meter | How the LoRa signal quality meter works | . | Units & Locale | How temperatures, distances, and times adapt to your region | . | Desktop App | Linux, macOS, and Windows desktop usage | . | Architecture | App architecture overview for contributors | . | 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. ",
    "url": "/Meshtastic-Android/main/is-rIS/#quick-links",
    
    "relUrl": "/is-rIS/#quick-links"
  },"1993": {
    "doc": "Home",
    "title": "Home",
    "content": " ",
    "url": "/Meshtastic-Android/main/is-rIS/",
    
    "relUrl": "/is-rIS/"
  },"1994": {
    "doc": "Home",
    "title": "Meshtastic Android App Documentation",
    "content": "User and developer documentation for the Meshtastic Android and Desktop app, built with Kotlin Multiplatform. Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ",
    "url": "/Meshtastic-Android/main/lt-rLT/#meshtastic-android-app-documentation",
    
    "relUrl": "/lt-rLT/#meshtastic-android-app-documentation"
  },"1995": {
    "doc": "Home",
    "title": "Quick Links",
    "content": "| Guide | Aprašymas | . | Getting Started | Connect your first radio and send a message | . | Messages & Channels | Channel broadcasts, direct messages, reactions, and encryption | . | Nodes | Understanding the mesh network node list | . | Signal Meter | How the LoRa signal quality meter works | . | Units & Locale | How temperatures, distances, and times adapt to your region | . | Desktop App | Linux, macOS, and Windows desktop usage | . | Architecture | App architecture overview for contributors | . | 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. ",
    "url": "/Meshtastic-Android/main/lt-rLT/#quick-links",
    
    "relUrl": "/lt-rLT/#quick-links"
  },"1996": {
    "doc": "Home",
    "title": "Home",
    "content": " ",
    "url": "/Meshtastic-Android/main/lt-rLT/",
    
    "relUrl": "/lt-rLT/"
  },"1997": {
    "doc": "Home",
    "title": "Meshtastic Android App Documentation",
    "content": "User and developer documentation for the Meshtastic Android and Desktop app, built with Kotlin Multiplatform. Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ",
    "url": "/Meshtastic-Android/main/gl-rES/#meshtastic-android-app-documentation",
    
    "relUrl": "/gl-rES/#meshtastic-android-app-documentation"
  },"1998": {
    "doc": "Home",
    "title": "Quick Links",
    "content": "| Guide | Descrición | . | Getting Started | Connect your first radio and send a message | . | Messages & Channels | Channel broadcasts, direct messages, reactions, and encryption | . | Nodes | Understanding the mesh network node list | . | Signal Meter | How the LoRa signal quality meter works | . | Units & Locale | How temperatures, distances, and times adapt to your region | . | Desktop App | Linux, macOS, and Windows desktop usage | . | Architecture | App architecture overview for contributors | . | 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. ",
    "url": "/Meshtastic-Android/main/gl-rES/#quick-links",
    
    "relUrl": "/gl-rES/#quick-links"
  },"1999": {
    "doc": "Home",
    "title": "Home",
    "content": " ",
    "url": "/Meshtastic-Android/main/gl-rES/",
    
    "relUrl": "/gl-rES/"
  },"2000": {
    "doc": "ホーム",
    "title": "Meshtastic Android アプリのドキュメント",
    "content": "User and developer documentation for the Meshtastic Android and Desktop app, built with Kotlin Multiplatform. サイドバーのナビゲーションから、アプリの機能についてはユーザーガイドを、プロジェクトへの貢献については開発者ガイドをご覧ください。 . ",
    "url": "/Meshtastic-Android/main/ja-rJP/#meshtastic-android-%E3%82%A2%E3%83%97%E3%83%AA%E3%81%AE%E3%83%89%E3%82%AD%E3%83%A5%E3%83%A1%E3%83%B3%E3%83%88",
    
    "relUrl": "/ja-rJP/#meshtastic-android-アプリのドキュメント"
  },"2001": {
    "doc": "ホーム",
    "title": "クイックリンク",
    "content": "| ガイド | 説明 | . | はじめに | 最初の無線機を接続してメッセージを送信する | . | メッセージとチャンネル | チャンネルのブロードキャスト、ダイレクトメッセージ、リアクション、暗号化 | . | ノード | メッシュネットワークのノードリストを理解する | . | 信号メーター | LoRa の信号品質メーターの仕組み | . | 単位とロケール | 温度・距離・時刻が地域に合わせて変わる仕組み | . | デスクトップアプリ | Linux、macOS、Windows でのデスクトップ利用 | . | アーキテクチャ | コントリビューター向けのアプリアーキテクチャ概要 | . | コントリビューション | ブランチ命名、PR ワークフロー、検証コマンド | . このドキュメントは、アプリ内のヘルプとドキュメントブラウザと同じ Markdown ソースから提供されています。 . ",
    "url": "/Meshtastic-Android/main/ja-rJP/#%E3%82%AF%E3%82%A4%E3%83%83%E3%82%AF%E3%83%AA%E3%83%B3%E3%82%AF",
    
    "relUrl": "/ja-rJP/#クイックリンク"
  },"2002": {
    "doc": "ホーム",
    "title": "ホーム",
    "content": " ",
    "url": "/Meshtastic-Android/main/ja-rJP/",
    
    "relUrl": "/ja-rJP/"
  },"2003": {
    "doc": "Startseite",
    "title": "Meshtastic Android App Documentation",
    "content": "User and developer documentation for the Meshtastic Android and Desktop app, built with Kotlin Multiplatform. Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ",
    "url": "/Meshtastic-Android/main/de-rDE/#meshtastic-android-app-documentation",
    
    "relUrl": "/de-rDE/#meshtastic-android-app-documentation"
  },"2004": {
    "doc": "Startseite",
    "title": "Quick Links",
    "content": "| Anleitung | Beschreibung | . | Getting Started | Connect your first radio and send a message | . | Messages & Channels | Channel broadcasts, direct messages, reactions, and encryption | . | Nodes | Understanding the mesh network node list | . | Signal Meter | How the LoRa signal quality meter works | . | Units & Locale | How temperatures, distances, and times adapt to your region | . | Desktop App | Linux, macOS, and Windows desktop usage | . | Architecture | App architecture overview for contributors | . | 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. ",
    "url": "/Meshtastic-Android/main/de-rDE/#quick-links",
    
    "relUrl": "/de-rDE/#quick-links"
  },"2005": {
    "doc": "Startseite",
    "title": "Startseite",
    "content": " ",
    "url": "/Meshtastic-Android/main/de-rDE/",
    
    "relUrl": "/de-rDE/"
  },"2006": {
    "doc": "Home",
    "title": "Meshtastic Android App Documentation",
    "content": "User and developer documentation for the Meshtastic Android and Desktop app, built with Kotlin Multiplatform. Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ",
    "url": "/Meshtastic-Android/main/ar-rSA/#meshtastic-android-app-documentation",
    
    "relUrl": "/ar-rSA/#meshtastic-android-app-documentation"
  },"2007": {
    "doc": "Home",
    "title": "Quick Links",
    "content": "| Guide | الوصف | . | Getting Started | Connect your first radio and send a message | . | Messages & Channels | Channel broadcasts, direct messages, reactions, and encryption | . | Nodes | Understanding the mesh network node list | . | Signal Meter | How the LoRa signal quality meter works | . | Units & Locale | How temperatures, distances, and times adapt to your region | . | Desktop App | Linux, macOS, and Windows desktop usage | . | Architecture | App architecture overview for contributors | . | 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. ",
    "url": "/Meshtastic-Android/main/ar-rSA/#quick-links",
    
    "relUrl": "/ar-rSA/#quick-links"
  },"2008": {
    "doc": "Home",
    "title": "Home",
    "content": " ",
    "url": "/Meshtastic-Android/main/ar-rSA/",
    
    "relUrl": "/ar-rSA/"
  },"2009": {
    "doc": "Home",
    "title": "Meshtastic Android App Documentation",
    "content": "User and developer documentation for the Meshtastic Android and Desktop app, built with Kotlin Multiplatform. Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ",
    "url": "/Meshtastic-Android/main/hr-rHR/#meshtastic-android-app-documentation",
    
    "relUrl": "/hr-rHR/#meshtastic-android-app-documentation"
  },"2010": {
    "doc": "Home",
    "title": "Quick Links",
    "content": "| Guide | Opis | . | Getting Started | Connect your first radio and send a message | . | Messages & Channels | Channel broadcasts, direct messages, reactions, and encryption | . | Nodes | Understanding the mesh network node list | . | Signal Meter | How the LoRa signal quality meter works | . | Units & Locale | How temperatures, distances, and times adapt to your region | . | Desktop App | Linux, macOS, and Windows desktop usage | . | Architecture | App architecture overview for contributors | . | 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. ",
    "url": "/Meshtastic-Android/main/hr-rHR/#quick-links",
    
    "relUrl": "/hr-rHR/#quick-links"
  },"2011": {
    "doc": "Home",
    "title": "Home",
    "content": " ",
    "url": "/Meshtastic-Android/main/hr-rHR/",
    
    "relUrl": "/hr-rHR/"
  },"2012": {
    "doc": "Home",
    "title": "Meshtastic Android App Documentation",
    "content": "User and developer documentation for the Meshtastic Android and Desktop app, built with Kotlin Multiplatform. Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ",
    "url": "/Meshtastic-Android/main/pt-rPT/#meshtastic-android-app-documentation",
    
    "relUrl": "/pt-rPT/#meshtastic-android-app-documentation"
  },"2013": {
    "doc": "Home",
    "title": "Quick Links",
    "content": "| Guide | Descrição | . | Getting Started | Connect your first radio and send a message | . | Messages & Channels | Channel broadcasts, direct messages, reactions, and encryption | . | Nodes | Understanding the mesh network node list | . | Signal Meter | How the LoRa signal quality meter works | . | Units & Locale | How temperatures, distances, and times adapt to your region | . | Desktop App | Linux, macOS, and Windows desktop usage | . | Architecture | App architecture overview for contributors | . | 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. ",
    "url": "/Meshtastic-Android/main/pt-rPT/#quick-links",
    
    "relUrl": "/pt-rPT/#quick-links"
  },"2014": {
    "doc": "Home",
    "title": "Home",
    "content": " ",
    "url": "/Meshtastic-Android/main/pt-rPT/",
    
    "relUrl": "/pt-rPT/"
  },"2015": {
    "doc": "Home",
    "title": "Meshtastic Android App Documentation",
    "content": "User and developer documentation for the Meshtastic Android and Desktop app, built with Kotlin Multiplatform. Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ",
    "url": "/Meshtastic-Android/main/pl-rPL/#meshtastic-android-app-documentation",
    
    "relUrl": "/pl-rPL/#meshtastic-android-app-documentation"
  },"2016": {
    "doc": "Home",
    "title": "Quick Links",
    "content": "| Guide | Opis | . | Getting Started | Connect your first radio and send a message | . | Messages & Channels | Channel broadcasts, direct messages, reactions, and encryption | . | Nodes | Understanding the mesh network node list | . | Signal Meter | How the LoRa signal quality meter works | . | Units & Locale | How temperatures, distances, and times adapt to your region | . | Desktop App | Linux, macOS, and Windows desktop usage | . | Architecture | App architecture overview for contributors | . | 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. ",
    "url": "/Meshtastic-Android/main/pl-rPL/#quick-links",
    
    "relUrl": "/pl-rPL/#quick-links"
  },"2017": {
    "doc": "Home",
    "title": "Home",
    "content": " ",
    "url": "/Meshtastic-Android/main/pl-rPL/",
    
    "relUrl": "/pl-rPL/"
  },"2018": {
    "doc": "Home",
    "title": "Meshtastic Android App Documentation",
    "content": "User and developer documentation for the Meshtastic Android and Desktop app, built with Kotlin Multiplatform. Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ",
    "url": "/Meshtastic-Android/main/zh-rCN/#meshtastic-android-app-documentation",
    
    "relUrl": "/zh-rCN/#meshtastic-android-app-documentation"
  },"2019": {
    "doc": "Home",
    "title": "Quick Links",
    "content": "| Guide | 说明 | . | Getting Started | Connect your first radio and send a message | . | Messages & Channels | Channel broadcasts, direct messages, reactions, and encryption | . | Nodes | Understanding the mesh network node list | . | Signal Meter | How the LoRa signal quality meter works | . | Units & Locale | How temperatures, distances, and times adapt to your region | . | Desktop App | Linux, macOS, and Windows desktop usage | . | Architecture | App architecture overview for contributors | . | 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. ",
    "url": "/Meshtastic-Android/main/zh-rCN/#quick-links",
    
    "relUrl": "/zh-rCN/#quick-links"
  },"2020": {
    "doc": "Home",
    "title": "Home",
    "content": " ",
    "url": "/Meshtastic-Android/main/zh-rCN/",
    
    "relUrl": "/zh-rCN/"
  },"2021": {
    "doc": "Home",
    "title": "Meshtastic Android App Documentation",
    "content": "User and developer documentation for the Meshtastic Android and Desktop app, built with Kotlin Multiplatform. Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ",
    "url": "/Meshtastic-Android/main/sq-rAL/#meshtastic-android-app-documentation",
    
    "relUrl": "/sq-rAL/#meshtastic-android-app-documentation"
  },"2022": {
    "doc": "Home",
    "title": "Quick Links",
    "content": "| Guide | Përshkrimi | . | Getting Started | Connect your first radio and send a message | . | Messages & Channels | Channel broadcasts, direct messages, reactions, and encryption | . | Nodes | Understanding the mesh network node list | . | Signal Meter | How the LoRa signal quality meter works | . | Units & Locale | How temperatures, distances, and times adapt to your region | . | Desktop App | Linux, macOS, and Windows desktop usage | . | Architecture | App architecture overview for contributors | . | 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. ",
    "url": "/Meshtastic-Android/main/sq-rAL/#quick-links",
    
    "relUrl": "/sq-rAL/#quick-links"
  },"2023": {
    "doc": "Home",
    "title": "Home",
    "content": " ",
    "url": "/Meshtastic-Android/main/sq-rAL/",
    
    "relUrl": "/sq-rAL/"
  },"2024": {
    "doc": "Home",
    "title": "Meshtastic Android App Documentation",
    "content": "User and developer documentation for the Meshtastic Android and Desktop app, built with Kotlin Multiplatform. Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ",
    "url": "/Meshtastic-Android/main/zh-rTW/#meshtastic-android-app-documentation",
    
    "relUrl": "/zh-rTW/#meshtastic-android-app-documentation"
  },"2025": {
    "doc": "Home",
    "title": "快速連結",
    "content": "| 指南 | 描述說明 | . | 〔快速入門〕(user/onboarding) | 連接您的第一台無線電裝置並傳送訊息 | . | 〔訊息與頻道〕(user/messages-and-channels) | 頻道廣播、私訊、訊息回應與加密 | . | 〔節點〕(user/nodes) | 了解 mesh 網路節點清單 | . | 〔訊號儀表〕(user/signal-meter) | LoRa 訊號品質儀表的運作方式 | . | 〔單位與地區設定〕(user/units-and-locale) | 溫度、距離與時間如何依地區設定自動調整 | . | 〔桌面版應用程式〕(user/desktop) | Linux、macOS 及 Windows 桌面版使用說明 | . | 〔架構〕(developer/architecture) | 供貢獻者參考的應用程式架構概覽 | . | 〔貢獻指南〕(developer/contributing) | 分支命名規範、PR 工作流程與驗證指令 | . 本說明文件與應用程式內建的說明與文件瀏覽器使用相同的 Markdown 原始檔。 . ",
    "url": "/Meshtastic-Android/main/zh-rTW/#%E5%BF%AB%E9%80%9F%E9%80%A3%E7%B5%90",
    
    "relUrl": "/zh-rTW/#快速連結"
  },"2026": {
    "doc": "Home",
    "title": "Home",
    "content": " ",
    "url": "/Meshtastic-Android/main/zh-rTW/",
    
    "relUrl": "/zh-rTW/"
  },"2027": {
    "doc": "Kodu",
    "title": "Meshtastic Androidi rakenduse dokumentatsioon",
    "content": "User and developer documentation for the Meshtastic Android and Desktop app, built with Kotlin Multiplatform. Rakenduse funktsioonide vaatamiseks kasuta külgriba navigeerimisriba, et sirvida kasutusjuhendit ja projekti panustamiseks arendaja juhendit. ",
    "url": "/Meshtastic-Android/main/et-rEE/#meshtastic-androidi-rakenduse-dokumentatsioon",
    
    "relUrl": "/et-rEE/#meshtastic-androidi-rakenduse-dokumentatsioon"
  },"2028": {
    "doc": "Kodu",
    "title": "Kiir ühendus",
    "content": "| Juhend | Kirjeldus | . | Alustamine | Ühenda oma esimene raadio ja saada sõnum | . | Sõnumid ja kanalid | Kanali levitamine, otseteated, reaktsioonid ja krüptimine | . | Seadmed | Kärgvõrgu sõlmede loendi mõistmine | . | Signaalimõõtur | Kuidas Lora signaali kvaliteedi mõõdik toimib | . | Ühikud ja lokaat | Kuidas temperatuurid, vahemaad ja kellaajad piirkonnaga sobituvad | . | Arvuti rakendus | Linux, macOS ja Windows arvuti kasutus | . | Arhitektuur | Rakenduse arhitektuuri ülevaade kaastöölistele | . | Panustamine | Haarade nimetamine, PR töövoog ja kinnituskäsklused | . See dokumentatsioon pärineb samast Markdowni allikast, mis toetab rakendusesisest Abi ja dokumentatsioon brauserit. ",
    "url": "/Meshtastic-Android/main/et-rEE/#kiir-%C3%BChendus",
    
    "relUrl": "/et-rEE/#kiir-ühendus"
  },"2029": {
    "doc": "Kodu",
    "title": "Kodu",
    "content": " ",
    "url": "/Meshtastic-Android/main/et-rEE/",
    
    "relUrl": "/et-rEE/"
  },"2030": {
    "doc": "Home",
    "title": "Meshtastic Android App Documentation",
    "content": "User and developer documentation for the Meshtastic Android and Desktop app, built with Kotlin Multiplatform. Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ",
    "url": "/Meshtastic-Android/main/fr-rFR/#meshtastic-android-app-documentation",
    
    "relUrl": "/fr-rFR/#meshtastic-android-app-documentation"
  },"2031": {
    "doc": "Home",
    "title": "Liens rapides",
    "content": "| Guide | Description | . | Démarrer | Connectez votre première radio et envoyez un message | . | Messages & Canaux | Diffusions de chaînes, messages directs, réactions et chiffrement | . | [Nœuds (user/nodes) | Comprendre la liste des nœuds du réseau de maillage | . | Mesure du Signal | Comment fonctionne le compteur de qualité du signal LoRa | . | Unités et Localisation | Comment les températures, les distances et le temps s’adaptent à votre région | . | Application de bureau | Utilisation de Linux, macOS et Windows | . | Architecture | Aperçu de l’architecture de l’application pour les contributeurs | . | Contribuer | Nommage des branches, flux de production PR et commandes de vérification | . Cette documentation est servie à partir de la même source markdown qui alimente le navigateur dans l’application Aide et Documentation. ",
    "url": "/Meshtastic-Android/main/fr-rFR/#liens-rapides",
    
    "relUrl": "/fr-rFR/#liens-rapides"
  },"2032": {
    "doc": "Home",
    "title": "Home",
    "content": " ",
    "url": "/Meshtastic-Android/main/fr-rFR/",
    
    "relUrl": "/fr-rFR/"
  },"2033": {
    "doc": "Home",
    "title": "Meshtastic Android App Documentation",
    "content": "User and developer documentation for the Meshtastic Android and Desktop app, built with Kotlin Multiplatform. Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ",
    "url": "/Meshtastic-Android/main/tr-rTR/#meshtastic-android-app-documentation",
    
    "relUrl": "/tr-rTR/#meshtastic-android-app-documentation"
  },"2034": {
    "doc": "Home",
    "title": "Quick Links",
    "content": "| Guide | Açıklaması | . | Getting Started | Connect your first radio and send a message | . | Messages & Channels | Channel broadcasts, direct messages, reactions, and encryption | . | Nodes | Understanding the mesh network node list | . | Signal Meter | How the LoRa signal quality meter works | . | Units & Locale | How temperatures, distances, and times adapt to your region | . | Desktop App | Linux, macOS, and Windows desktop usage | . | Architecture | App architecture overview for contributors | . | 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. ",
    "url": "/Meshtastic-Android/main/tr-rTR/#quick-links",
    
    "relUrl": "/tr-rTR/#quick-links"
  },"2035": {
    "doc": "Home",
    "title": "Home",
    "content": " ",
    "url": "/Meshtastic-Android/main/tr-rTR/",
    
    "relUrl": "/tr-rTR/"
  },"2036": {
    "doc": "Home",
    "title": "Meshtastic Android App Documentation",
    "content": "User and developer documentation for the Meshtastic Android and Desktop app, built with Kotlin Multiplatform. Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ",
    "url": "/Meshtastic-Android/main/el-rGR/#meshtastic-android-app-documentation",
    
    "relUrl": "/el-rGR/#meshtastic-android-app-documentation"
  },"2037": {
    "doc": "Home",
    "title": "Quick Links",
    "content": "| Guide | Περιγραφή | . | Getting Started | Connect your first radio and send a message | . | Messages & Channels | Channel broadcasts, direct messages, reactions, and encryption | . | Nodes | Understanding the mesh network node list | . | Signal Meter | How the LoRa signal quality meter works | . | Units & Locale | How temperatures, distances, and times adapt to your region | . | Desktop App | Linux, macOS, and Windows desktop usage | . | Architecture | App architecture overview for contributors | . | 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. ",
    "url": "/Meshtastic-Android/main/el-rGR/#quick-links",
    
    "relUrl": "/el-rGR/#quick-links"
  },"2038": {
    "doc": "Home",
    "title": "Home",
    "content": " ",
    "url": "/Meshtastic-Android/main/el-rGR/",
    
    "relUrl": "/el-rGR/"
  },"2039": {
    "doc": "Home",
    "title": "Meshtastic Android App Documentation",
    "content": "User and developer documentation for the Meshtastic Android and Desktop app, built with Kotlin Multiplatform. Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ",
    "url": "/Meshtastic-Android/main/ro-rRO/#meshtastic-android-app-documentation",
    
    "relUrl": "/ro-rRO/#meshtastic-android-app-documentation"
  },"2040": {
    "doc": "Home",
    "title": "Quick Links",
    "content": "| Guide | Descriere | . | Getting Started | Connect your first radio and send a message | . | Messages & Channels | Channel broadcasts, direct messages, reactions, and encryption | . | Nodes | Understanding the mesh network node list | . | Signal Meter | How the LoRa signal quality meter works | . | Units & Locale | How temperatures, distances, and times adapt to your region | . | Desktop App | Linux, macOS, and Windows desktop usage | . | Architecture | App architecture overview for contributors | . | 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. ",
    "url": "/Meshtastic-Android/main/ro-rRO/#quick-links",
    
    "relUrl": "/ro-rRO/#quick-links"
  },"2041": {
    "doc": "Home",
    "title": "Home",
    "content": " ",
    "url": "/Meshtastic-Android/main/ro-rRO/",
    
    "relUrl": "/ro-rRO/"
  },"2042": {
    "doc": "Home",
    "title": "Meshtastic Android App Documentation",
    "content": "User and developer documentation for the Meshtastic Android and Desktop app, built with Kotlin Multiplatform. Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ",
    "url": "/Meshtastic-Android/main/iw-rIL/#meshtastic-android-app-documentation",
    
    "relUrl": "/iw-rIL/#meshtastic-android-app-documentation"
  },"2043": {
    "doc": "Home",
    "title": "Quick Links",
    "content": "| Guide | תיאור | . | Getting Started | Connect your first radio and send a message | . | Messages & Channels | Channel broadcasts, direct messages, reactions, and encryption | . | Nodes | Understanding the mesh network node list | . | Signal Meter | How the LoRa signal quality meter works | . | Units & Locale | How temperatures, distances, and times adapt to your region | . | Desktop App | Linux, macOS, and Windows desktop usage | . | Architecture | App architecture overview for contributors | . | 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. ",
    "url": "/Meshtastic-Android/main/iw-rIL/#quick-links",
    
    "relUrl": "/iw-rIL/#quick-links"
  },"2044": {
    "doc": "Home",
    "title": "Home",
    "content": " ",
    "url": "/Meshtastic-Android/main/iw-rIL/",
    
    "relUrl": "/iw-rIL/"
  },"2045": {
    "doc": "Home",
    "title": "Meshtastic Android App Documentation",
    "content": "User and developer documentation for the Meshtastic Android and Desktop app, built with Kotlin Multiplatform. Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ",
    "url": "/Meshtastic-Android/main/pt-rBR/#meshtastic-android-app-documentation",
    
    "relUrl": "/pt-rBR/#meshtastic-android-app-documentation"
  },"2046": {
    "doc": "Home",
    "title": "Quick Links",
    "content": "| Guide | Descrição | . | Getting Started | Connect your first radio and send a message | . | Messages & Channels | Channel broadcasts, direct messages, reactions, and encryption | . | Nodes | Understanding the mesh network node list | . | Signal Meter | How the LoRa signal quality meter works | . | Units & Locale | How temperatures, distances, and times adapt to your region | . | Desktop App | Linux, macOS, and Windows desktop usage | . | Architecture | App architecture overview for contributors | . | 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. ",
    "url": "/Meshtastic-Android/main/pt-rBR/#quick-links",
    
    "relUrl": "/pt-rBR/#quick-links"
  },"2047": {
    "doc": "Home",
    "title": "Home",
    "content": " ",
    "url": "/Meshtastic-Android/main/pt-rBR/",
    
    "relUrl": "/pt-rBR/"
  },"2048": {
    "doc": "Home",
    "title": "Meshtastic Android App Documentation",
    "content": "User and developer documentation for the Meshtastic Android and Desktop app, built with Kotlin Multiplatform. Use the sidebar navigation to browse the User Guide for app features and the Developer Guide for contributing to the project. ",
    "url": "/Meshtastic-Android/main/en/#meshtastic-android-app-documentation",
    
    "relUrl": "/en/#meshtastic-android-app-documentation"
  },"2049": {
    "doc": "Home",
    "title": "Quick Links",
    "content": "| Guide | Description | . | Getting Started | Connect your first radio and send a message | . | Messages & Channels | Channel broadcasts, direct messages, reactions, and encryption | . | Nodes | Understanding the mesh network node list | . | Signal Meter | How the LoRa signal quality meter works | . | Units & Locale | How temperatures, distances, and times adapt to your region | . | Desktop App | Linux, macOS, and Windows desktop usage | . | Architecture | App architecture overview for contributors | . | 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. ",
    "url": "/Meshtastic-Android/main/en/#quick-links",
    
    "relUrl": "/en/#quick-links"
  },"2050": {
    "doc": "Home",
    "title": "Home",
    "content": " ",
    "url": "/Meshtastic-Android/main/en/",
    
    "relUrl": "/en/"
  },"2051": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": "The Map screen shows the geographic positions of nodes on your mesh, along with shared waypoints. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/map-and-waypoints.html#map--waypoints",
    
    "relUrl": "/sk-rSK/user/map-and-waypoints.html#map--waypoints"
  },"2052": {
    "doc": "Map & Waypoints",
    "title": "Map View",
    "content": "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 . Each node that reports a position is shown as a node chip marker displaying the node’s short name. The chip is colored by the node’s own identity color (a stable color derived from its node number) — the same chip used in the node list, so a node looks the same everywhere. Marker color does not encode online/offline status. When a node’s position updates live, its marker briefly pulses. Nearby markers are clustered as you zoom out. Map Controls . | Zoom — pinch or use +/- buttons | Pan — drag to explore | Center — tap the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/map-and-waypoints.html#map-view",
    
    "relUrl": "/sk-rSK/user/map-and-waypoints.html#map-view"
  },"2053": {
    "doc": "Map & Waypoints",
    "title": "Waypoints",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. Creating a Waypoint . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | Enter a name and optional description. | Choose an icon/emoji for the waypoint. | Tap Send to share with the mesh. | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. Waypoint Properties . | Property | Popis | . | Názov | Short identifier (max 29 characters) | . | Popis | Optional longer description | . | Icon | Visual marker emoji on the map | . | Zamknuté | If locked, only the creator can edit or delete | . | Expiration | Optional auto-remove date and time | . | Geofence | Optional enter/exit alert area — see Waypoint Geofences | . Waypoint Expiration . Waypoints can be set to expire automatically: . | Never (default) — waypoint remains until manually deleted | Timed — pick a specific date and time; the waypoint is automatically removed once that time passes. 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 is based on the absolute time you picked, not a duration from when the waypoint was created or received. Waypoint Geofences . Any waypoint can also define a geofence — an alert area — so you or others get notified when a node enters or leaves it: . | Set a geofence radius from the preset chips (or Off to disable), or tap Set area on map to draw a custom rectangular area instead. | Once a region is set, toggle Notify on enter and/or Notify on exit. | Optionally enable Favorites only to limit alerts to your favorited nodes. | . Since waypoints (and their geofences) are broadcast to the whole mesh, only the creator is alerted by default. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. Managing Waypoints . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/map-and-waypoints.html#waypoints",
    
    "relUrl": "/sk-rSK/user/map-and-waypoints.html#waypoints"
  },"2054": {
    "doc": "Map & Waypoints",
    "title": "Map Layers",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Imported layers are listed with a toggle to show/hide each one and an option to remove it. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. Site Planner . Site Planner estimates RF coverage for a transmitter and draws it on the map as a color-coded overlay. Open it from a map control, or from a node’s detail page via Estimate coverage (shown only for nodes with a known position). Configure the transmitter (location, frequency, TX power, antenna gain and height), the receiver (sensitivity, height), and simulation options (max range, high-resolution terrain, color palette), then run the estimate. Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/map-and-waypoints.html#map-layers",
    
    "relUrl": "/sk-rSK/user/map-and-waypoints.html#map-layers"
  },"2055": {
    "doc": "Map & Waypoints",
    "title": "Position Sharing",
    "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. 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. To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/map-and-waypoints.html#position-sharing",
    
    "relUrl": "/sk-rSK/user/map-and-waypoints.html#position-sharing"
  },"2056": {
    "doc": "Map & Waypoints",
    "title": "Map Sources",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | Notes | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | Tmavá | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/map-and-waypoints.html#map-sources",
    
    "relUrl": "/sk-rSK/user/map-and-waypoints.html#map-sources"
  },"2057": {
    "doc": "Map & Waypoints",
    "title": "Related Topics",
    "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | Units & Locale — distance and coordinate display formats | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/map-and-waypoints.html#related-topics",
    
    "relUrl": "/sk-rSK/user/map-and-waypoints.html#related-topics"
  },"2058": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": " ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/map-and-waypoints.html",
    
    "relUrl": "/sk-rSK/user/map-and-waypoints.html"
  },"2059": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": "The Map screen shows the geographic positions of nodes on your mesh, along with shared waypoints. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/map-and-waypoints.html#map--waypoints",
    
    "relUrl": "/be-rBY/user/map-and-waypoints.html#map--waypoints"
  },"2060": {
    "doc": "Map & Waypoints",
    "title": "Map View",
    "content": "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 . Each node that reports a position is shown as a node chip marker displaying the node’s short name. The chip is colored by the node’s own identity color (a stable color derived from its node number) — the same chip used in the node list, so a node looks the same everywhere. Marker color does not encode online/offline status. When a node’s position updates live, its marker briefly pulses. Nearby markers are clustered as you zoom out. Map Controls . | Zoom — pinch or use +/- buttons | Pan — drag to explore | Center — tap the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/map-and-waypoints.html#map-view",
    
    "relUrl": "/be-rBY/user/map-and-waypoints.html#map-view"
  },"2061": {
    "doc": "Map & Waypoints",
    "title": "Waypoints",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. Creating a Waypoint . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | Enter a name and optional description. | Choose an icon/emoji for the waypoint. | Tap Send to share with the mesh. | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. Waypoint Properties . | Property | Апісанне | . | Назва | Short identifier (max 29 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 date and time | . | Geofence | Optional enter/exit alert area — see Waypoint Geofences | . Waypoint Expiration . Waypoints can be set to expire automatically: . | Never (default) — waypoint remains until manually deleted | Timed — pick a specific date and time; the waypoint is automatically removed once that time passes. 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 is based on the absolute time you picked, not a duration from when the waypoint was created or received. Waypoint Geofences . Any waypoint can also define a geofence — an alert area — so you or others get notified when a node enters or leaves it: . | Set a geofence radius from the preset chips (or Off to disable), or tap Set area on map to draw a custom rectangular area instead. | Once a region is set, toggle Notify on enter and/or Notify on exit. | Optionally enable Favorites only to limit alerts to your favorited nodes. | . Since waypoints (and their geofences) are broadcast to the whole mesh, only the creator is alerted by default. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. Managing Waypoints . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/map-and-waypoints.html#waypoints",
    
    "relUrl": "/be-rBY/user/map-and-waypoints.html#waypoints"
  },"2062": {
    "doc": "Map & Waypoints",
    "title": "Map Layers",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Imported layers are listed with a toggle to show/hide each one and an option to remove it. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. Site Planner . Site Planner estimates RF coverage for a transmitter and draws it on the map as a color-coded overlay. Open it from a map control, or from a node’s detail page via Estimate coverage (shown only for nodes with a known position). Configure the transmitter (location, frequency, TX power, antenna gain and height), the receiver (sensitivity, height), and simulation options (max range, high-resolution terrain, color palette), then run the estimate. Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/map-and-waypoints.html#map-layers",
    
    "relUrl": "/be-rBY/user/map-and-waypoints.html#map-layers"
  },"2063": {
    "doc": "Map & Waypoints",
    "title": "Position Sharing",
    "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. 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. To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/map-and-waypoints.html#position-sharing",
    
    "relUrl": "/be-rBY/user/map-and-waypoints.html#position-sharing"
  },"2064": {
    "doc": "Map & Waypoints",
    "title": "Map Sources",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | Notes | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | Dark | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/map-and-waypoints.html#map-sources",
    
    "relUrl": "/be-rBY/user/map-and-waypoints.html#map-sources"
  },"2065": {
    "doc": "Map & Waypoints",
    "title": "Related Topics",
    "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | Units & Locale — distance and coordinate display formats | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/map-and-waypoints.html#related-topics",
    
    "relUrl": "/be-rBY/user/map-and-waypoints.html#related-topics"
  },"2066": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": " ",
    "url": "/Meshtastic-Android/main/be-rBY/user/map-and-waypoints.html",
    
    "relUrl": "/be-rBY/user/map-and-waypoints.html"
  },"2067": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": "The Map screen shows the geographic positions of nodes on your mesh, along with shared waypoints. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/map-and-waypoints.html#map--waypoints",
    
    "relUrl": "/it-rIT/user/map-and-waypoints.html#map--waypoints"
  },"2068": {
    "doc": "Map & Waypoints",
    "title": "Map View",
    "content": "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 . Each node that reports a position is shown as a node chip marker displaying the node’s short name. The chip is colored by the node’s own identity color (a stable color derived from its node number) — the same chip used in the node list, so a node looks the same everywhere. Marker color does not encode online/offline status. When a node’s position updates live, its marker briefly pulses. Nearby markers are clustered as you zoom out. Map Controls . | Zoom — pinch or use +/- buttons | Pan — drag to explore | Center — tap the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/map-and-waypoints.html#map-view",
    
    "relUrl": "/it-rIT/user/map-and-waypoints.html#map-view"
  },"2069": {
    "doc": "Map & Waypoints",
    "title": "Waypoints",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. Creating a Waypoint . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | Enter a name and optional description. | Choose an icon/emoji for the waypoint. | Tap Send to share with the mesh. | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. Waypoint Properties . | Property | Descrizione | . | Nome | Short identifier (max 29 characters) | . | Descrizione | Optional longer description | . | Icon | Visual marker emoji on the map | . | Bloccato | If locked, only the creator can edit or delete | . | Expiration | Optional auto-remove date and time | . | Geofence | Optional enter/exit alert area — see Waypoint Geofences | . Waypoint Expiration . Waypoints can be set to expire automatically: . | Never (default) — waypoint remains until manually deleted | Timed — pick a specific date and time; the waypoint is automatically removed once that time passes. 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 is based on the absolute time you picked, not a duration from when the waypoint was created or received. Waypoint Geofences . Any waypoint can also define a geofence — an alert area — so you or others get notified when a node enters or leaves it: . | Set a geofence radius from the preset chips (or Off to disable), or tap Set area on map to draw a custom rectangular area instead. | Once a region is set, toggle Notify on enter and/or Notify on exit. | Optionally enable Favorites only to limit alerts to your favorited nodes. | . Since waypoints (and their geofences) are broadcast to the whole mesh, only the creator is alerted by default. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. Managing Waypoints . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/map-and-waypoints.html#waypoints",
    
    "relUrl": "/it-rIT/user/map-and-waypoints.html#waypoints"
  },"2070": {
    "doc": "Map & Waypoints",
    "title": "Livelli della mappa",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Imported layers are listed with a toggle to show/hide each one and an option to remove it. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. Site Planner . Site Planner estimates RF coverage for a transmitter and draws it on the map as a color-coded overlay. Open it from a map control, or from a node’s detail page via Estimate coverage (shown only for nodes with a known position). Configure the transmitter (location, frequency, TX power, antenna gain and height), the receiver (sensitivity, height), and simulation options (max range, high-resolution terrain, color palette), then run the estimate. Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/map-and-waypoints.html#livelli-della-mappa",
    
    "relUrl": "/it-rIT/user/map-and-waypoints.html#livelli-della-mappa"
  },"2071": {
    "doc": "Map & Waypoints",
    "title": "Position Sharing",
    "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. 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. To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/map-and-waypoints.html#position-sharing",
    
    "relUrl": "/it-rIT/user/map-and-waypoints.html#position-sharing"
  },"2072": {
    "doc": "Map & Waypoints",
    "title": "Map Sources",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | Note | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | Scuro | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/map-and-waypoints.html#map-sources",
    
    "relUrl": "/it-rIT/user/map-and-waypoints.html#map-sources"
  },"2073": {
    "doc": "Map & Waypoints",
    "title": "Related Topics",
    "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | Units & Locale — distance and coordinate display formats | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/map-and-waypoints.html#related-topics",
    
    "relUrl": "/it-rIT/user/map-and-waypoints.html#related-topics"
  },"2074": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": " ",
    "url": "/Meshtastic-Android/main/it-rIT/user/map-and-waypoints.html",
    
    "relUrl": "/it-rIT/user/map-and-waypoints.html"
  },"2075": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": "The Map screen shows the geographic positions of nodes on your mesh, along with shared waypoints. ",
    "url": "/Meshtastic-Android/main/es-rES/user/map-and-waypoints.html#map--waypoints",
    
    "relUrl": "/es-rES/user/map-and-waypoints.html#map--waypoints"
  },"2076": {
    "doc": "Map & Waypoints",
    "title": "Map View",
    "content": "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 . Each node that reports a position is shown as a node chip marker displaying the node’s short name. The chip is colored by the node’s own identity color (a stable color derived from its node number) — the same chip used in the node list, so a node looks the same everywhere. Marker color does not encode online/offline status. When a node’s position updates live, its marker briefly pulses. Nearby markers are clustered as you zoom out. Map Controls . | Zoom — pinch or use +/- buttons | Pan — drag to explore | Center — tap the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/es-rES/user/map-and-waypoints.html#map-view",
    
    "relUrl": "/es-rES/user/map-and-waypoints.html#map-view"
  },"2077": {
    "doc": "Map & Waypoints",
    "title": "Waypoints",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. Creating a Waypoint . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | Enter a name and optional description. | Choose an icon/emoji for the waypoint. | Tap Send to share with the mesh. | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. Waypoint Properties . | Property | Descripción | . | Nombre | Short identifier (max 29 characters) | . | Descripción | Optional longer description | . | Icon | Visual marker emoji on the map | . | Bloqueado | If locked, only the creator can edit or delete | . | Expiration | Optional auto-remove date and time | . | Geofence | Optional enter/exit alert area — see Waypoint Geofences | . Waypoint Expiration . Waypoints can be set to expire automatically: . | Never (default) — waypoint remains until manually deleted | Timed — pick a specific date and time; the waypoint is automatically removed once that time passes. 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 is based on the absolute time you picked, not a duration from when the waypoint was created or received. Waypoint Geofences . Any waypoint can also define a geofence — an alert area — so you or others get notified when a node enters or leaves it: . | Set a geofence radius from the preset chips (or Off to disable), or tap Set area on map to draw a custom rectangular area instead. | Once a region is set, toggle Notify on enter and/or Notify on exit. | Optionally enable Favorites only to limit alerts to your favorited nodes. | . Since waypoints (and their geofences) are broadcast to the whole mesh, only the creator is alerted by default. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. Managing Waypoints . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/map-and-waypoints.html#waypoints",
    
    "relUrl": "/es-rES/user/map-and-waypoints.html#waypoints"
  },"2078": {
    "doc": "Map & Waypoints",
    "title": "Capas del mapa",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Imported layers are listed with a toggle to show/hide each one and an option to remove it. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. Site Planner . Site Planner estimates RF coverage for a transmitter and draws it on the map as a color-coded overlay. Open it from a map control, or from a node’s detail page via Estimate coverage (shown only for nodes with a known position). Configure the transmitter (location, frequency, TX power, antenna gain and height), the receiver (sensitivity, height), and simulation options (max range, high-resolution terrain, color palette), then run the estimate. Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/es-rES/user/map-and-waypoints.html#capas-del-mapa",
    
    "relUrl": "/es-rES/user/map-and-waypoints.html#capas-del-mapa"
  },"2079": {
    "doc": "Map & Waypoints",
    "title": "Position Sharing",
    "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. 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. To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/es-rES/user/map-and-waypoints.html#position-sharing",
    
    "relUrl": "/es-rES/user/map-and-waypoints.html#position-sharing"
  },"2080": {
    "doc": "Map & Waypoints",
    "title": "Map Sources",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | Notas | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | Oscuro | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/es-rES/user/map-and-waypoints.html#map-sources",
    
    "relUrl": "/es-rES/user/map-and-waypoints.html#map-sources"
  },"2081": {
    "doc": "Map & Waypoints",
    "title": "Related Topics",
    "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | Units & Locale — distance and coordinate display formats | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/map-and-waypoints.html#related-topics",
    
    "relUrl": "/es-rES/user/map-and-waypoints.html#related-topics"
  },"2082": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": " ",
    "url": "/Meshtastic-Android/main/es-rES/user/map-and-waypoints.html",
    
    "relUrl": "/es-rES/user/map-and-waypoints.html"
  },"2083": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": "The Map screen shows the geographic positions of nodes on your mesh, along with shared waypoints. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/map-and-waypoints.html#map--waypoints",
    
    "relUrl": "/sl-rSI/user/map-and-waypoints.html#map--waypoints"
  },"2084": {
    "doc": "Map & Waypoints",
    "title": "Map View",
    "content": "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 . Each node that reports a position is shown as a node chip marker displaying the node’s short name. The chip is colored by the node’s own identity color (a stable color derived from its node number) — the same chip used in the node list, so a node looks the same everywhere. Marker color does not encode online/offline status. When a node’s position updates live, its marker briefly pulses. Nearby markers are clustered as you zoom out. Map Controls . | Zoom — pinch or use +/- buttons | Pan — drag to explore | Center — tap the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/map-and-waypoints.html#map-view",
    
    "relUrl": "/sl-rSI/user/map-and-waypoints.html#map-view"
  },"2085": {
    "doc": "Map & Waypoints",
    "title": "Waypoints",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. Creating a Waypoint . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | Enter a name and optional description. | Choose an icon/emoji for the waypoint. | Tap Send to share with the mesh. | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. Waypoint Properties . | Property | Opis | . | Ime | Short identifier (max 29 characters) | . | Opis | Optional longer description | . | Icon | Visual marker emoji on the map | . | Zaklenjeno | If locked, only the creator can edit or delete | . | Expiration | Optional auto-remove date and time | . | Geofence | Optional enter/exit alert area — see Waypoint Geofences | . Waypoint Expiration . Waypoints can be set to expire automatically: . | Never (default) — waypoint remains until manually deleted | Timed — pick a specific date and time; the waypoint is automatically removed once that time passes. 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 is based on the absolute time you picked, not a duration from when the waypoint was created or received. Waypoint Geofences . Any waypoint can also define a geofence — an alert area — so you or others get notified when a node enters or leaves it: . | Set a geofence radius from the preset chips (or Off to disable), or tap Set area on map to draw a custom rectangular area instead. | Once a region is set, toggle Notify on enter and/or Notify on exit. | Optionally enable Favorites only to limit alerts to your favorited nodes. | . Since waypoints (and their geofences) are broadcast to the whole mesh, only the creator is alerted by default. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. Managing Waypoints . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/map-and-waypoints.html#waypoints",
    
    "relUrl": "/sl-rSI/user/map-and-waypoints.html#waypoints"
  },"2086": {
    "doc": "Map & Waypoints",
    "title": "Map Layers",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Imported layers are listed with a toggle to show/hide each one and an option to remove it. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. Site Planner . Site Planner estimates RF coverage for a transmitter and draws it on the map as a color-coded overlay. Open it from a map control, or from a node’s detail page via Estimate coverage (shown only for nodes with a known position). Configure the transmitter (location, frequency, TX power, antenna gain and height), the receiver (sensitivity, height), and simulation options (max range, high-resolution terrain, color palette), then run the estimate. Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/map-and-waypoints.html#map-layers",
    
    "relUrl": "/sl-rSI/user/map-and-waypoints.html#map-layers"
  },"2087": {
    "doc": "Map & Waypoints",
    "title": "Position Sharing",
    "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. 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. To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/map-and-waypoints.html#position-sharing",
    
    "relUrl": "/sl-rSI/user/map-and-waypoints.html#position-sharing"
  },"2088": {
    "doc": "Map & Waypoints",
    "title": "Map Sources",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | Notes | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | Temna tema | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/map-and-waypoints.html#map-sources",
    
    "relUrl": "/sl-rSI/user/map-and-waypoints.html#map-sources"
  },"2089": {
    "doc": "Map & Waypoints",
    "title": "Related Topics",
    "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | Units & Locale — distance and coordinate display formats | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/map-and-waypoints.html#related-topics",
    
    "relUrl": "/sl-rSI/user/map-and-waypoints.html#related-topics"
  },"2090": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": " ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/map-and-waypoints.html",
    
    "relUrl": "/sl-rSI/user/map-and-waypoints.html"
  },"2091": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": "The Map screen shows the geographic positions of nodes on your mesh, along with shared waypoints. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/map-and-waypoints.html#map--waypoints",
    
    "relUrl": "/no-rNO/user/map-and-waypoints.html#map--waypoints"
  },"2092": {
    "doc": "Map & Waypoints",
    "title": "Map View",
    "content": "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 . Each node that reports a position is shown as a node chip marker displaying the node’s short name. The chip is colored by the node’s own identity color (a stable color derived from its node number) — the same chip used in the node list, so a node looks the same everywhere. Marker color does not encode online/offline status. When a node’s position updates live, its marker briefly pulses. Nearby markers are clustered as you zoom out. Map Controls . | Zoom — pinch or use +/- buttons | Pan — drag to explore | Center — tap the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/map-and-waypoints.html#map-view",
    
    "relUrl": "/no-rNO/user/map-and-waypoints.html#map-view"
  },"2093": {
    "doc": "Map & Waypoints",
    "title": "Waypoints",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. Creating a Waypoint . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | Enter a name and optional description. | Choose an icon/emoji for the waypoint. | Tap Send to share with the mesh. | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. Waypoint Properties . | Property | Beskrivelse | . | Navn | Short identifier (max 29 characters) | . | Beskrivelse | Optional longer description | . | Icon | Visual marker emoji on the map | . | Låst | If locked, only the creator can edit or delete | . | Expiration | Optional auto-remove date and time | . | Geofence | Optional enter/exit alert area — see Waypoint Geofences | . Waypoint Expiration . Waypoints can be set to expire automatically: . | Never (default) — waypoint remains until manually deleted | Timed — pick a specific date and time; the waypoint is automatically removed once that time passes. 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 is based on the absolute time you picked, not a duration from when the waypoint was created or received. Waypoint Geofences . Any waypoint can also define a geofence — an alert area — so you or others get notified when a node enters or leaves it: . | Set a geofence radius from the preset chips (or Off to disable), or tap Set area on map to draw a custom rectangular area instead. | Once a region is set, toggle Notify on enter and/or Notify on exit. | Optionally enable Favorites only to limit alerts to your favorited nodes. | . Since waypoints (and their geofences) are broadcast to the whole mesh, only the creator is alerted by default. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. Managing Waypoints . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/map-and-waypoints.html#waypoints",
    
    "relUrl": "/no-rNO/user/map-and-waypoints.html#waypoints"
  },"2094": {
    "doc": "Map & Waypoints",
    "title": "Map Layers",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Imported layers are listed with a toggle to show/hide each one and an option to remove it. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. Site Planner . Site Planner estimates RF coverage for a transmitter and draws it on the map as a color-coded overlay. Open it from a map control, or from a node’s detail page via Estimate coverage (shown only for nodes with a known position). Configure the transmitter (location, frequency, TX power, antenna gain and height), the receiver (sensitivity, height), and simulation options (max range, high-resolution terrain, color palette), then run the estimate. Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/map-and-waypoints.html#map-layers",
    
    "relUrl": "/no-rNO/user/map-and-waypoints.html#map-layers"
  },"2095": {
    "doc": "Map & Waypoints",
    "title": "Position Sharing",
    "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. 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. To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/map-and-waypoints.html#position-sharing",
    
    "relUrl": "/no-rNO/user/map-and-waypoints.html#position-sharing"
  },"2096": {
    "doc": "Map & Waypoints",
    "title": "Map Sources",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | Notes | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | Mørk | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/map-and-waypoints.html#map-sources",
    
    "relUrl": "/no-rNO/user/map-and-waypoints.html#map-sources"
  },"2097": {
    "doc": "Map & Waypoints",
    "title": "Related Topics",
    "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | Units & Locale — distance and coordinate display formats | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/map-and-waypoints.html#related-topics",
    
    "relUrl": "/no-rNO/user/map-and-waypoints.html#related-topics"
  },"2098": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": " ",
    "url": "/Meshtastic-Android/main/no-rNO/user/map-and-waypoints.html",
    
    "relUrl": "/no-rNO/user/map-and-waypoints.html"
  },"2099": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": "The Map screen shows the geographic positions of nodes on your mesh, along with shared waypoints. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/map-and-waypoints.html#map--waypoints",
    
    "relUrl": "/hu-rHU/user/map-and-waypoints.html#map--waypoints"
  },"2100": {
    "doc": "Map & Waypoints",
    "title": "Map View",
    "content": "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 . Each node that reports a position is shown as a node chip marker displaying the node’s short name. The chip is colored by the node’s own identity color (a stable color derived from its node number) — the same chip used in the node list, so a node looks the same everywhere. Marker color does not encode online/offline status. When a node’s position updates live, its marker briefly pulses. Nearby markers are clustered as you zoom out. Map Controls . | Zoom — pinch or use +/- buttons | Pan — drag to explore | Center — tap the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/map-and-waypoints.html#map-view",
    
    "relUrl": "/hu-rHU/user/map-and-waypoints.html#map-view"
  },"2101": {
    "doc": "Map & Waypoints",
    "title": "Waypoints",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. Creating a Waypoint . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | Enter a name and optional description. | Choose an icon/emoji for the waypoint. | Tap Send to share with the mesh. | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. Waypoint Properties . | Property | Leírás | . | Név | Short identifier (max 29 characters) | . | Leírás | Optional longer description | . | Icon | Visual marker emoji on the map | . | Zárolt | If locked, only the creator can edit or delete | . | Expiration | Optional auto-remove date and time | . | Geofence | Optional enter/exit alert area — see Waypoint Geofences | . Waypoint Expiration . Waypoints can be set to expire automatically: . | Never (default) — waypoint remains until manually deleted | Timed — pick a specific date and time; the waypoint is automatically removed once that time passes. 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 is based on the absolute time you picked, not a duration from when the waypoint was created or received. Waypoint Geofences . Any waypoint can also define a geofence — an alert area — so you or others get notified when a node enters or leaves it: . | Set a geofence radius from the preset chips (or Off to disable), or tap Set area on map to draw a custom rectangular area instead. | Once a region is set, toggle Notify on enter and/or Notify on exit. | Optionally enable Favorites only to limit alerts to your favorited nodes. | . Since waypoints (and their geofences) are broadcast to the whole mesh, only the creator is alerted by default. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. Managing Waypoints . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/map-and-waypoints.html#waypoints",
    
    "relUrl": "/hu-rHU/user/map-and-waypoints.html#waypoints"
  },"2102": {
    "doc": "Map & Waypoints",
    "title": "Térképrétegek",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Imported layers are listed with a toggle to show/hide each one and an option to remove it. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. Site Planner . Site Planner estimates RF coverage for a transmitter and draws it on the map as a color-coded overlay. Open it from a map control, or from a node’s detail page via Estimate coverage (shown only for nodes with a known position). Configure the transmitter (location, frequency, TX power, antenna gain and height), the receiver (sensitivity, height), and simulation options (max range, high-resolution terrain, color palette), then run the estimate. Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/map-and-waypoints.html#t%C3%A9rk%C3%A9pr%C3%A9tegek",
    
    "relUrl": "/hu-rHU/user/map-and-waypoints.html#térképrétegek"
  },"2103": {
    "doc": "Map & Waypoints",
    "title": "Position Sharing",
    "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. 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. To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/map-and-waypoints.html#position-sharing",
    
    "relUrl": "/hu-rHU/user/map-and-waypoints.html#position-sharing"
  },"2104": {
    "doc": "Map & Waypoints",
    "title": "Map Sources",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | Jegyzetek | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | Sötét | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/map-and-waypoints.html#map-sources",
    
    "relUrl": "/hu-rHU/user/map-and-waypoints.html#map-sources"
  },"2105": {
    "doc": "Map & Waypoints",
    "title": "Related Topics",
    "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | Units & Locale — distance and coordinate display formats | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/map-and-waypoints.html#related-topics",
    
    "relUrl": "/hu-rHU/user/map-and-waypoints.html#related-topics"
  },"2106": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": " ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/map-and-waypoints.html",
    
    "relUrl": "/hu-rHU/user/map-and-waypoints.html"
  },"2107": {
    "doc": "Карта и путевые точки",
    "title": "Карта и путевые точки",
    "content": "Экран карты показывает географическое положение нод твоей mesh-сети, а также общие путевые точки. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/map-and-waypoints.html",
    
    "relUrl": "/ru-rRU/user/map-and-waypoints.html"
  },"2108": {
    "doc": "Карта и путевые точки",
    "title": "Вид карты",
    "content": "На карте отображаются: . | Расположение нод — цветные маркеры для каждой ноды, передающей свои координаты | Путевые точки — общие точки интереса | Твоё местоположение — твоё текущее местоположение по GPS | . Маркеры нод . Каждая нода, передающая своё местоположение, отображается в виде маркера-бирки с коротким именем ноды. Цвет бирки определяется собственным цветом идентификации ноды (постоянным цветом, получаемым из её номера) — тем же самым, что используется в списке нод, поэтому нода везде выглядит одинаково. Цвет маркера не отображает статус в сети/не в сети. Когда местоположение ноды обновляется в реальном времени, её маркер ненадолго подсвечивается пульсацией. Близко расположенные маркеры группируются в кластеры при уменьшении масштаба. Управление картой . | Масштаб — используйте щипок или кнопки +/- | Перемещение — перетаскивайте карту для исследования | Center — tap the location button to center on your position | Нажатие на ноду — коснитесь маркера ноды для просмотра подробностей | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. Нажмите на компас, чтобы сориентировать карту на север, или нажмите кнопку местоположения, чтобы отцентрироваться на твоей текущей позиции. On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/map-and-waypoints.html#%D0%B2%D0%B8%D0%B4-%D0%BA%D0%B0%D1%80%D1%82%D1%8B",
    
    "relUrl": "/ru-rRU/user/map-and-waypoints.html#вид-карты"
  },"2109": {
    "doc": "Карта и путевые точки",
    "title": "Путевые точки",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. Создание путевой точки . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | Введите имя и, при желании, описанье. | Выберите значок/эмодзи для путевой точки. | Нажмите “Отправить”, чтобы поделиться с mesh-сетью. | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. Свойства путевой точки . | Свойство | Описание | . | Имя | Короткий идентификатор (не более 29 символов) | . | Описание | Необязательное более длинное описание | . | Значок | Визуальный эмодзи маркер на карте | . | Заблокировано | Если заблокировано, только создатель может изменить или удалить | . | Истечение срока | Необязательная дата и время автоматического удаления | . | Геозона | Optional enter/exit alert area — see Waypoint Geofences | . Истечение срока путевой точки . Для путевых точек можно настроить автоматическое истечение срока: . | Никогда (по умолчанию) — путевая точка остаётся, пока не будет удалена вручную | По времени — выберите конкретные дату и время; путевая точка будет автоматически удалена, как только это время наступит. Полезно для временных меток, таких как точки сбора, опасности или места встреч. | . Истёкшие путевые точки автоматически скрываются с карты, чтобы не загромождать отображение. Обратный отсчёт до истечения срока основан на заданном тобою абсолютном времени, а не на промежутке с момента создания или получения путевой точки. Геозоны путевых точек . Любая путевая точка может также задавать геозону — область оповещения, — чтобы ты или другие участники получали уведомления, когда нода входит в неё или покидает её: . | Задайте радиус геозоны с помощью готовых вариантов (или “Выкл”, чтобы отключить), либо нажмите “Задать область на карте”, чтобы нарисовать собственную прямоугольную область. | После задания области включите переключатели “Оповещать при входе” и/или “Оповещать при выходе”. | При необходимости включите “Только избранные”, чтобы ограничить оповещения только избранными нодами. | . Поскольку путевые точки (и их геозоны) передаются всей mesh-сети, по умолчанию оповещается только создатель. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. Управление путевыми точками . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/map-and-waypoints.html#%D0%BF%D1%83%D1%82%D0%B5%D0%B2%D1%8B%D0%B5-%D1%82%D0%BE%D1%87%D0%BA%D0%B8",
    
    "relUrl": "/ru-rRU/user/map-and-waypoints.html#путевые-точки"
  },"2110": {
    "doc": "Карта и путевые точки",
    "title": "Слои карты",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Импортированные слои отображаются в списке с переключателем для показа/скрытия каждого и возможностью удалить слой. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. Планировщик участков . Планировщик участков оценивает радиочастотное покрытие для передатчика и отображает его на карте в виде цветового наложения. Откройте его с панели управления картой или со страницы сведений о ноде через “Оценку покрытия” (отображается только для нод с известным местоположением). Настройте передатчик (местоположение, частота, мощность передачи, усиление и высота антенны), приёмник (чувствительность, высота) и параметры симуляции (максимальная дальность, рельеф высокого разрешения, цветовая палитра), затем запустите расчёт. Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/map-and-waypoints.html#%D1%81%D0%BB%D0%BE%D0%B8-%D0%BA%D0%B0%D1%80%D1%82%D1%8B",
    
    "relUrl": "/ru-rRU/user/map-and-waypoints.html#слои-карты"
  },"2111": {
    "doc": "Карта и путевые точки",
    "title": "Передача геоданных",
    "content": "Включение передачи геоданных . Твоя нода передаёт свои GPS-координаты на основе: . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. Вопросы приватности . 🔒 Приватность: Данные о местоположении передаются всем нодам на твоём канале. Если ты не хочешь раскрывать своё местоположение, отключите GPS в настройках или используйте фиксированное/фиктивное местоположение. To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/map-and-waypoints.html#%D0%BF%D0%B5%D1%80%D0%B5%D0%B4%D0%B0%D1%87%D0%B0-%D0%B3%D0%B5%D0%BE%D0%B4%D0%B0%D0%BD%D0%BD%D1%8B%D1%85",
    
    "relUrl": "/ru-rRU/user/map-and-waypoints.html#передача-геоданных"
  },"2112": {
    "doc": "Карта и путевые точки",
    "title": "Источники карт",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | Заметки | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | Темная | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/map-and-waypoints.html#%D0%B8%D1%81%D1%82%D0%BE%D1%87%D0%BD%D0%B8%D0%BA%D0%B8-%D0%BA%D0%B0%D1%80%D1%82",
    
    "relUrl": "/ru-rRU/user/map-and-waypoints.html#источники-карт"
  },"2113": {
    "doc": "Карта и путевые точки",
    "title": "Связанные темы",
    "content": ". | Ноды — просмотр и фильтрация списка нод | Метрики нод — качество сигнала и история местоположения для отдельных нод | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | Единицы измерения и регион — форматы отображения расстояний и координат | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/map-and-waypoints.html#%D1%81%D0%B2%D1%8F%D0%B7%D0%B0%D0%BD%D0%BD%D1%8B%D0%B5-%D1%82%D0%B5%D0%BC%D1%8B",
    
    "relUrl": "/ru-rRU/user/map-and-waypoints.html#связанные-темы"
  },"2114": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": "The Map screen shows the geographic positions of nodes on your mesh, along with shared waypoints. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/map-and-waypoints.html#map--waypoints",
    
    "relUrl": "/cs-rCZ/user/map-and-waypoints.html#map--waypoints"
  },"2115": {
    "doc": "Map & Waypoints",
    "title": "Map View",
    "content": "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 . Each node that reports a position is shown as a node chip marker displaying the node’s short name. The chip is colored by the node’s own identity color (a stable color derived from its node number) — the same chip used in the node list, so a node looks the same everywhere. Marker color does not encode online/offline status. When a node’s position updates live, its marker briefly pulses. Nearby markers are clustered as you zoom out. Map Controls . | Zoom — pinch or use +/- buttons | Pan — drag to explore | Center — tap the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/map-and-waypoints.html#map-view",
    
    "relUrl": "/cs-rCZ/user/map-and-waypoints.html#map-view"
  },"2116": {
    "doc": "Map & Waypoints",
    "title": "Waypoints",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. Creating a Waypoint . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | Enter a name and optional description. | Choose an icon/emoji for the waypoint. | Tap Send to share with the mesh. | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. Waypoint Properties . | Property | Popis | . | Jméno | Short identifier (max 29 characters) | . | Popis | Optional longer description | . | Icon | Visual marker emoji on the map | . | Uzamknout | If locked, only the creator can edit or delete | . | Expiration | Optional auto-remove date and time | . | Geofence | Optional enter/exit alert area — see Waypoint Geofences | . Waypoint Expiration . Waypoints can be set to expire automatically: . | Never (default) — waypoint remains until manually deleted | Timed — pick a specific date and time; the waypoint is automatically removed once that time passes. 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 is based on the absolute time you picked, not a duration from when the waypoint was created or received. Waypoint Geofences . Any waypoint can also define a geofence — an alert area — so you or others get notified when a node enters or leaves it: . | Set a geofence radius from the preset chips (or Off to disable), or tap Set area on map to draw a custom rectangular area instead. | Once a region is set, toggle Notify on enter and/or Notify on exit. | Optionally enable Favorites only to limit alerts to your favorited nodes. | . Since waypoints (and their geofences) are broadcast to the whole mesh, only the creator is alerted by default. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. Managing Waypoints . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/map-and-waypoints.html#waypoints",
    
    "relUrl": "/cs-rCZ/user/map-and-waypoints.html#waypoints"
  },"2117": {
    "doc": "Map & Waypoints",
    "title": "Mapové vrstvy",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Imported layers are listed with a toggle to show/hide each one and an option to remove it. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. Site Planner . Site Planner estimates RF coverage for a transmitter and draws it on the map as a color-coded overlay. Open it from a map control, or from a node’s detail page via Estimate coverage (shown only for nodes with a known position). Configure the transmitter (location, frequency, TX power, antenna gain and height), the receiver (sensitivity, height), and simulation options (max range, high-resolution terrain, color palette), then run the estimate. Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/map-and-waypoints.html#mapov%C3%A9-vrstvy",
    
    "relUrl": "/cs-rCZ/user/map-and-waypoints.html#mapové-vrstvy"
  },"2118": {
    "doc": "Map & Waypoints",
    "title": "Position Sharing",
    "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. 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. To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/map-and-waypoints.html#position-sharing",
    
    "relUrl": "/cs-rCZ/user/map-and-waypoints.html#position-sharing"
  },"2119": {
    "doc": "Map & Waypoints",
    "title": "Map Sources",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | Poznámka | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | Tmavý | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/map-and-waypoints.html#map-sources",
    
    "relUrl": "/cs-rCZ/user/map-and-waypoints.html#map-sources"
  },"2120": {
    "doc": "Map & Waypoints",
    "title": "Related Topics",
    "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | Units & Locale — distance and coordinate display formats | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/map-and-waypoints.html#related-topics",
    
    "relUrl": "/cs-rCZ/user/map-and-waypoints.html#related-topics"
  },"2121": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": " ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/map-and-waypoints.html",
    
    "relUrl": "/cs-rCZ/user/map-and-waypoints.html"
  },"2122": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": "The Map screen shows the geographic positions of nodes on your mesh, along with shared waypoints. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/map-and-waypoints.html#map--waypoints",
    
    "relUrl": "/bg-rBG/user/map-and-waypoints.html#map--waypoints"
  },"2123": {
    "doc": "Map & Waypoints",
    "title": "Map View",
    "content": "The map displays: . | Node positions — colored markers for each node reporting location | Waypoints — shared points of interest | Вашата позиция — вашето текущо GPS местоположение | . Node Markers . Each node that reports a position is shown as a node chip marker displaying the node’s short name. The chip is colored by the node’s own identity color (a stable color derived from its node number) — the same chip used in the node list, so a node looks the same everywhere. Marker color does not encode online/offline status. When a node’s position updates live, its marker briefly pulses. Nearby markers are clustered as you zoom out. Map Controls . | Zoom — pinch or use +/- buttons | Pan — drag to explore | Center — tap the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/map-and-waypoints.html#map-view",
    
    "relUrl": "/bg-rBG/user/map-and-waypoints.html#map-view"
  },"2124": {
    "doc": "Map & Waypoints",
    "title": "Waypoints",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. Creating a Waypoint . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | Enter a name and optional description. | Choose an icon/emoji for the waypoint. | Tap Send to share with the mesh. | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. Waypoint Properties . | Property | Описание | . | Име | Short identifier (max 29 characters) | . | Описание | Optional longer description | . | Икона | Visual marker emoji on the map | . | Заключен | If locked, only the creator can edit or delete | . | Expiration | Optional auto-remove date and time | . | Geofence | Optional enter/exit alert area — see Waypoint Geofences | . Waypoint Expiration . Waypoints can be set to expire automatically: . | Never (default) — waypoint remains until manually deleted | Timed — pick a specific date and time; the waypoint is automatically removed once that time passes. 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 is based on the absolute time you picked, not a duration from when the waypoint was created or received. Waypoint Geofences . Any waypoint can also define a geofence — an alert area — so you or others get notified when a node enters or leaves it: . | Set a geofence radius from the preset chips (or Off to disable), or tap Set area on map to draw a custom rectangular area instead. | Once a region is set, toggle Notify on enter and/or Notify on exit. | Optionally enable Favorites only to limit alerts to your favorited nodes. | . Since waypoints (and their geofences) are broadcast to the whole mesh, only the creator is alerted by default. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. Managing Waypoints . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/map-and-waypoints.html#waypoints",
    
    "relUrl": "/bg-rBG/user/map-and-waypoints.html#waypoints"
  },"2125": {
    "doc": "Map & Waypoints",
    "title": "Слоеве на картата",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Imported layers are listed with a toggle to show/hide each one and an option to remove it. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. Site Planner . Site Planner estimates RF coverage for a transmitter and draws it on the map as a color-coded overlay. Open it from a map control, or from a node’s detail page via Estimate coverage (shown only for nodes with a known position). Configure the transmitter (location, frequency, TX power, antenna gain and height), the receiver (sensitivity, height), and simulation options (max range, high-resolution terrain, color palette), then run the estimate. Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/map-and-waypoints.html#%D1%81%D0%BB%D0%BE%D0%B5%D0%B2%D0%B5-%D0%BD%D0%B0-%D0%BA%D0%B0%D1%80%D1%82%D0%B0%D1%82%D0%B0",
    
    "relUrl": "/bg-rBG/user/map-and-waypoints.html#слоеве-на-картата"
  },"2126": {
    "doc": "Map & Waypoints",
    "title": "Position Sharing",
    "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. 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. To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/map-and-waypoints.html#position-sharing",
    
    "relUrl": "/bg-rBG/user/map-and-waypoints.html#position-sharing"
  },"2127": {
    "doc": "Map & Waypoints",
    "title": "Map Sources",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | Бележки | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | Тъмна | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/map-and-waypoints.html#map-sources",
    
    "relUrl": "/bg-rBG/user/map-and-waypoints.html#map-sources"
  },"2128": {
    "doc": "Map & Waypoints",
    "title": "Свързани теми",
    "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | Units & Locale — distance and coordinate display formats | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/map-and-waypoints.html#%D1%81%D0%B2%D1%8A%D1%80%D0%B7%D0%B0%D0%BD%D0%B8-%D1%82%D0%B5%D0%BC%D0%B8",
    
    "relUrl": "/bg-rBG/user/map-and-waypoints.html#свързани-теми"
  },"2129": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": " ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/map-and-waypoints.html",
    
    "relUrl": "/bg-rBG/user/map-and-waypoints.html"
  },"2130": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": "The Map screen shows the geographic positions of nodes on your mesh, along with shared waypoints. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/map-and-waypoints.html#map--waypoints",
    
    "relUrl": "/ga-rIE/user/map-and-waypoints.html#map--waypoints"
  },"2131": {
    "doc": "Map & Waypoints",
    "title": "Map View",
    "content": "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 . Each node that reports a position is shown as a node chip marker displaying the node’s short name. The chip is colored by the node’s own identity color (a stable color derived from its node number) — the same chip used in the node list, so a node looks the same everywhere. Marker color does not encode online/offline status. When a node’s position updates live, its marker briefly pulses. Nearby markers are clustered as you zoom out. Map Controls . | Zoom — pinch or use +/- buttons | Pan — drag to explore | Center — tap the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/map-and-waypoints.html#map-view",
    
    "relUrl": "/ga-rIE/user/map-and-waypoints.html#map-view"
  },"2132": {
    "doc": "Map & Waypoints",
    "title": "Waypoints",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. Creating a Waypoint . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | Enter a name and optional description. | Choose an icon/emoji for the waypoint. | Tap Send to share with the mesh. | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. Waypoint Properties . | Property | Cur síos | . | Ainm | Short identifier (max 29 characters) | . | Cur síos | Optional longer description | . | Icon | Visual marker emoji on the map | . | Ceangailte | If locked, only the creator can edit or delete | . | Expiration | Optional auto-remove date and time | . | Geofence | Optional enter/exit alert area — see Waypoint Geofences | . Waypoint Expiration . Waypoints can be set to expire automatically: . | Never (default) — waypoint remains until manually deleted | Timed — pick a specific date and time; the waypoint is automatically removed once that time passes. 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 is based on the absolute time you picked, not a duration from when the waypoint was created or received. Waypoint Geofences . Any waypoint can also define a geofence — an alert area — so you or others get notified when a node enters or leaves it: . | Set a geofence radius from the preset chips (or Off to disable), or tap Set area on map to draw a custom rectangular area instead. | Once a region is set, toggle Notify on enter and/or Notify on exit. | Optionally enable Favorites only to limit alerts to your favorited nodes. | . Since waypoints (and their geofences) are broadcast to the whole mesh, only the creator is alerted by default. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. Managing Waypoints . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/map-and-waypoints.html#waypoints",
    
    "relUrl": "/ga-rIE/user/map-and-waypoints.html#waypoints"
  },"2133": {
    "doc": "Map & Waypoints",
    "title": "Map Layers",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Imported layers are listed with a toggle to show/hide each one and an option to remove it. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. Site Planner . Site Planner estimates RF coverage for a transmitter and draws it on the map as a color-coded overlay. Open it from a map control, or from a node’s detail page via Estimate coverage (shown only for nodes with a known position). Configure the transmitter (location, frequency, TX power, antenna gain and height), the receiver (sensitivity, height), and simulation options (max range, high-resolution terrain, color palette), then run the estimate. Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/map-and-waypoints.html#map-layers",
    
    "relUrl": "/ga-rIE/user/map-and-waypoints.html#map-layers"
  },"2134": {
    "doc": "Map & Waypoints",
    "title": "Position Sharing",
    "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. 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. To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/map-and-waypoints.html#position-sharing",
    
    "relUrl": "/ga-rIE/user/map-and-waypoints.html#position-sharing"
  },"2135": {
    "doc": "Map & Waypoints",
    "title": "Map Sources",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | Notes | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | Dorcha | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/map-and-waypoints.html#map-sources",
    
    "relUrl": "/ga-rIE/user/map-and-waypoints.html#map-sources"
  },"2136": {
    "doc": "Map & Waypoints",
    "title": "Related Topics",
    "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | Units & Locale — distance and coordinate display formats | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/map-and-waypoints.html#related-topics",
    
    "relUrl": "/ga-rIE/user/map-and-waypoints.html#related-topics"
  },"2137": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": " ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/map-and-waypoints.html",
    
    "relUrl": "/ga-rIE/user/map-and-waypoints.html"
  },"2138": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": "The Map screen shows the geographic positions of nodes on your mesh, along with shared waypoints. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/map-and-waypoints.html#map--waypoints",
    
    "relUrl": "/fr-rCA/user/map-and-waypoints.html#map--waypoints"
  },"2139": {
    "doc": "Map & Waypoints",
    "title": "Map View",
    "content": "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 . Each node that reports a position is shown as a node chip marker displaying the node’s short name. The chip is colored by the node’s own identity color (a stable color derived from its node number) — the same chip used in the node list, so a node looks the same everywhere. Marker color does not encode online/offline status. When a node’s position updates live, its marker briefly pulses. Nearby markers are clustered as you zoom out. Map Controls . | Zoom — pinch or use +/- buttons | Pan — drag to explore | Center — tap the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/map-and-waypoints.html#map-view",
    
    "relUrl": "/fr-rCA/user/map-and-waypoints.html#map-view"
  },"2140": {
    "doc": "Map & Waypoints",
    "title": "Waypoints",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. Creating a Waypoint . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | Enter a name and optional description. | Choose an icon/emoji for the waypoint. | Tap Send to share with the mesh. | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. Waypoint Properties . | Property | Description | . | Nom | Short identifier (max 29 characters) | . | Description | Optional longer description | . | Icon | Visual marker emoji on the map | . | Verrouillé | If locked, only the creator can edit or delete | . | Expiration | Optional auto-remove date and time | . | Geofence | Optional enter/exit alert area — see Waypoint Geofences | . Waypoint Expiration . Waypoints can be set to expire automatically: . | Never (default) — waypoint remains until manually deleted | Timed — pick a specific date and time; the waypoint is automatically removed once that time passes. 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 is based on the absolute time you picked, not a duration from when the waypoint was created or received. Waypoint Geofences . Any waypoint can also define a geofence — an alert area — so you or others get notified when a node enters or leaves it: . | Set a geofence radius from the preset chips (or Off to disable), or tap Set area on map to draw a custom rectangular area instead. | Once a region is set, toggle Notify on enter and/or Notify on exit. | Optionally enable Favorites only to limit alerts to your favorited nodes. | . Since waypoints (and their geofences) are broadcast to the whole mesh, only the creator is alerted by default. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. Managing Waypoints . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/map-and-waypoints.html#waypoints",
    
    "relUrl": "/fr-rCA/user/map-and-waypoints.html#waypoints"
  },"2141": {
    "doc": "Map & Waypoints",
    "title": "Couches cartographiques",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Imported layers are listed with a toggle to show/hide each one and an option to remove it. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. Site Planner . Site Planner estimates RF coverage for a transmitter and draws it on the map as a color-coded overlay. Open it from a map control, or from a node’s detail page via Estimate coverage (shown only for nodes with a known position). Configure the transmitter (location, frequency, TX power, antenna gain and height), the receiver (sensitivity, height), and simulation options (max range, high-resolution terrain, color palette), then run the estimate. Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/map-and-waypoints.html#couches-cartographiques",
    
    "relUrl": "/fr-rCA/user/map-and-waypoints.html#couches-cartographiques"
  },"2142": {
    "doc": "Map & Waypoints",
    "title": "Position Sharing",
    "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. 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. To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/map-and-waypoints.html#position-sharing",
    
    "relUrl": "/fr-rCA/user/map-and-waypoints.html#position-sharing"
  },"2143": {
    "doc": "Map & Waypoints",
    "title": "Map Sources",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | Notes | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | Sombre | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/map-and-waypoints.html#map-sources",
    
    "relUrl": "/fr-rCA/user/map-and-waypoints.html#map-sources"
  },"2144": {
    "doc": "Map & Waypoints",
    "title": "Related Topics",
    "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | Units & Locale — distance and coordinate display formats | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/map-and-waypoints.html#related-topics",
    
    "relUrl": "/fr-rCA/user/map-and-waypoints.html#related-topics"
  },"2145": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": " ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/map-and-waypoints.html",
    
    "relUrl": "/fr-rCA/user/map-and-waypoints.html"
  },"2146": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": "The Map screen shows the geographic positions of nodes on your mesh, along with shared waypoints. ",
    "url": "/Meshtastic-Android/main/srp/user/map-and-waypoints.html#map--waypoints",
    
    "relUrl": "/srp/user/map-and-waypoints.html#map--waypoints"
  },"2147": {
    "doc": "Map & Waypoints",
    "title": "Map View",
    "content": "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 . Each node that reports a position is shown as a node chip marker displaying the node’s short name. The chip is colored by the node’s own identity color (a stable color derived from its node number) — the same chip used in the node list, so a node looks the same everywhere. Marker color does not encode online/offline status. When a node’s position updates live, its marker briefly pulses. Nearby markers are clustered as you zoom out. Map Controls . | Zoom — pinch or use +/- buttons | Pan — drag to explore | Center — tap the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/srp/user/map-and-waypoints.html#map-view",
    
    "relUrl": "/srp/user/map-and-waypoints.html#map-view"
  },"2148": {
    "doc": "Map & Waypoints",
    "title": "Waypoints",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. Creating a Waypoint . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | Enter a name and optional description. | Choose an icon/emoji for the waypoint. | Tap Send to share with the mesh. | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. Waypoint Properties . | Property | Опис | . | Име | Short identifier (max 29 characters) | . | Опис | Optional longer description | . | Иконица | Visual marker emoji on the map | . | Закључан | If locked, only the creator can edit or delete | . | Expiration | Optional auto-remove date and time | . | Geofence | Optional enter/exit alert area — see Waypoint Geofences | . Waypoint Expiration . Waypoints can be set to expire automatically: . | Never (default) — waypoint remains until manually deleted | Timed — pick a specific date and time; the waypoint is automatically removed once that time passes. 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 is based on the absolute time you picked, not a duration from when the waypoint was created or received. Waypoint Geofences . Any waypoint can also define a geofence — an alert area — so you or others get notified when a node enters or leaves it: . | Set a geofence radius from the preset chips (or Off to disable), or tap Set area on map to draw a custom rectangular area instead. | Once a region is set, toggle Notify on enter and/or Notify on exit. | Optionally enable Favorites only to limit alerts to your favorited nodes. | . Since waypoints (and their geofences) are broadcast to the whole mesh, only the creator is alerted by default. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. Managing Waypoints . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/srp/user/map-and-waypoints.html#waypoints",
    
    "relUrl": "/srp/user/map-and-waypoints.html#waypoints"
  },"2149": {
    "doc": "Map & Waypoints",
    "title": "Map Layers",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Imported layers are listed with a toggle to show/hide each one and an option to remove it. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. Site Planner . Site Planner estimates RF coverage for a transmitter and draws it on the map as a color-coded overlay. Open it from a map control, or from a node’s detail page via Estimate coverage (shown only for nodes with a known position). Configure the transmitter (location, frequency, TX power, antenna gain and height), the receiver (sensitivity, height), and simulation options (max range, high-resolution terrain, color palette), then run the estimate. Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/srp/user/map-and-waypoints.html#map-layers",
    
    "relUrl": "/srp/user/map-and-waypoints.html#map-layers"
  },"2150": {
    "doc": "Map & Waypoints",
    "title": "Position Sharing",
    "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. 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. To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/srp/user/map-and-waypoints.html#position-sharing",
    
    "relUrl": "/srp/user/map-and-waypoints.html#position-sharing"
  },"2151": {
    "doc": "Map & Waypoints",
    "title": "Map Sources",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | Белешке | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | Тамна | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/srp/user/map-and-waypoints.html#map-sources",
    
    "relUrl": "/srp/user/map-and-waypoints.html#map-sources"
  },"2152": {
    "doc": "Map & Waypoints",
    "title": "Related Topics",
    "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | Units & Locale — distance and coordinate display formats | . ",
    "url": "/Meshtastic-Android/main/srp/user/map-and-waypoints.html#related-topics",
    
    "relUrl": "/srp/user/map-and-waypoints.html#related-topics"
  },"2153": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": " ",
    "url": "/Meshtastic-Android/main/srp/user/map-and-waypoints.html",
    
    "relUrl": "/srp/user/map-and-waypoints.html"
  },"2154": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": "The Map screen shows the geographic positions of nodes on your mesh, along with shared waypoints. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/map-and-waypoints.html#map--waypoints",
    
    "relUrl": "/ca-rES/user/map-and-waypoints.html#map--waypoints"
  },"2155": {
    "doc": "Map & Waypoints",
    "title": "Map View",
    "content": "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 . Each node that reports a position is shown as a node chip marker displaying the node’s short name. The chip is colored by the node’s own identity color (a stable color derived from its node number) — the same chip used in the node list, so a node looks the same everywhere. Marker color does not encode online/offline status. When a node’s position updates live, its marker briefly pulses. Nearby markers are clustered as you zoom out. Map Controls . | Zoom — pinch or use +/- buttons | Pan — drag to explore | Center — tap the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/map-and-waypoints.html#map-view",
    
    "relUrl": "/ca-rES/user/map-and-waypoints.html#map-view"
  },"2156": {
    "doc": "Map & Waypoints",
    "title": "Waypoints",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. Creating a Waypoint . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | Enter a name and optional description. | Choose an icon/emoji for the waypoint. | Tap Send to share with the mesh. | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. Waypoint Properties . | Property | Descripció | . | Nom | Short identifier (max 29 characters) | . | Descripció | Optional longer description | . | Icon | Visual marker emoji on the map | . | Bloquejat | If locked, only the creator can edit or delete | . | Expiration | Optional auto-remove date and time | . | Geofence | Optional enter/exit alert area — see Waypoint Geofences | . Waypoint Expiration . Waypoints can be set to expire automatically: . | Never (default) — waypoint remains until manually deleted | Timed — pick a specific date and time; the waypoint is automatically removed once that time passes. 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 is based on the absolute time you picked, not a duration from when the waypoint was created or received. Waypoint Geofences . Any waypoint can also define a geofence — an alert area — so you or others get notified when a node enters or leaves it: . | Set a geofence radius from the preset chips (or Off to disable), or tap Set area on map to draw a custom rectangular area instead. | Once a region is set, toggle Notify on enter and/or Notify on exit. | Optionally enable Favorites only to limit alerts to your favorited nodes. | . Since waypoints (and their geofences) are broadcast to the whole mesh, only the creator is alerted by default. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. Managing Waypoints . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/map-and-waypoints.html#waypoints",
    
    "relUrl": "/ca-rES/user/map-and-waypoints.html#waypoints"
  },"2157": {
    "doc": "Map & Waypoints",
    "title": "Map Layers",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Imported layers are listed with a toggle to show/hide each one and an option to remove it. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. Site Planner . Site Planner estimates RF coverage for a transmitter and draws it on the map as a color-coded overlay. Open it from a map control, or from a node’s detail page via Estimate coverage (shown only for nodes with a known position). Configure the transmitter (location, frequency, TX power, antenna gain and height), the receiver (sensitivity, height), and simulation options (max range, high-resolution terrain, color palette), then run the estimate. Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/map-and-waypoints.html#map-layers",
    
    "relUrl": "/ca-rES/user/map-and-waypoints.html#map-layers"
  },"2158": {
    "doc": "Map & Waypoints",
    "title": "Position Sharing",
    "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. 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. To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/map-and-waypoints.html#position-sharing",
    
    "relUrl": "/ca-rES/user/map-and-waypoints.html#position-sharing"
  },"2159": {
    "doc": "Map & Waypoints",
    "title": "Map Sources",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | Notes | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | Fosc | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/map-and-waypoints.html#map-sources",
    
    "relUrl": "/ca-rES/user/map-and-waypoints.html#map-sources"
  },"2160": {
    "doc": "Map & Waypoints",
    "title": "Related Topics",
    "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | Units & Locale — distance and coordinate display formats | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/map-and-waypoints.html#related-topics",
    
    "relUrl": "/ca-rES/user/map-and-waypoints.html#related-topics"
  },"2161": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": " ",
    "url": "/Meshtastic-Android/main/ca-rES/user/map-and-waypoints.html",
    
    "relUrl": "/ca-rES/user/map-and-waypoints.html"
  },"2162": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": "The Map screen shows the geographic positions of nodes on your mesh, along with shared waypoints. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/map-and-waypoints.html#map--waypoints",
    
    "relUrl": "/ko-rKR/user/map-and-waypoints.html#map--waypoints"
  },"2163": {
    "doc": "Map & Waypoints",
    "title": "Map View",
    "content": "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 . Each node that reports a position is shown as a node chip marker displaying the node’s short name. The chip is colored by the node’s own identity color (a stable color derived from its node number) — the same chip used in the node list, so a node looks the same everywhere. Marker color does not encode online/offline status. When a node’s position updates live, its marker briefly pulses. Nearby markers are clustered as you zoom out. Map Controls . | Zoom — pinch or use +/- buttons | Pan — drag to explore | Center — tap the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/map-and-waypoints.html#map-view",
    
    "relUrl": "/ko-rKR/user/map-and-waypoints.html#map-view"
  },"2164": {
    "doc": "Map & Waypoints",
    "title": "Waypoints",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. Creating a Waypoint . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | Enter a name and optional description. | Choose an icon/emoji for the waypoint. | Tap Send to share with the mesh. | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. Waypoint Properties . | Property | 설명 | . | 이름 | Short identifier (max 29 characters) | . | 설명 | Optional longer description | . | Icon | Visual marker emoji on the map | . | 잠김 | If locked, only the creator can edit or delete | . | Expiration | Optional auto-remove date and time | . | Geofence | Optional enter/exit alert area — see Waypoint Geofences | . Waypoint Expiration . Waypoints can be set to expire automatically: . | Never (default) — waypoint remains until manually deleted | Timed — pick a specific date and time; the waypoint is automatically removed once that time passes. 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 is based on the absolute time you picked, not a duration from when the waypoint was created or received. Waypoint Geofences . Any waypoint can also define a geofence — an alert area — so you or others get notified when a node enters or leaves it: . | Set a geofence radius from the preset chips (or Off to disable), or tap Set area on map to draw a custom rectangular area instead. | Once a region is set, toggle Notify on enter and/or Notify on exit. | Optionally enable Favorites only to limit alerts to your favorited nodes. | . Since waypoints (and their geofences) are broadcast to the whole mesh, only the creator is alerted by default. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. Managing Waypoints . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/map-and-waypoints.html#waypoints",
    
    "relUrl": "/ko-rKR/user/map-and-waypoints.html#waypoints"
  },"2165": {
    "doc": "Map & Waypoints",
    "title": "Map Layers",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Imported layers are listed with a toggle to show/hide each one and an option to remove it. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. Site Planner . Site Planner estimates RF coverage for a transmitter and draws it on the map as a color-coded overlay. Open it from a map control, or from a node’s detail page via Estimate coverage (shown only for nodes with a known position). Configure the transmitter (location, frequency, TX power, antenna gain and height), the receiver (sensitivity, height), and simulation options (max range, high-resolution terrain, color palette), then run the estimate. Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/map-and-waypoints.html#map-layers",
    
    "relUrl": "/ko-rKR/user/map-and-waypoints.html#map-layers"
  },"2166": {
    "doc": "Map & Waypoints",
    "title": "Position Sharing",
    "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. 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. To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/map-and-waypoints.html#position-sharing",
    
    "relUrl": "/ko-rKR/user/map-and-waypoints.html#position-sharing"
  },"2167": {
    "doc": "Map & Waypoints",
    "title": "Map Sources",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | Notes | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | 다크 | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/map-and-waypoints.html#map-sources",
    
    "relUrl": "/ko-rKR/user/map-and-waypoints.html#map-sources"
  },"2168": {
    "doc": "Map & Waypoints",
    "title": "Related Topics",
    "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | Units & Locale — distance and coordinate display formats | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/map-and-waypoints.html#related-topics",
    
    "relUrl": "/ko-rKR/user/map-and-waypoints.html#related-topics"
  },"2169": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": " ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/map-and-waypoints.html",
    
    "relUrl": "/ko-rKR/user/map-and-waypoints.html"
  },"2170": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": "The Map screen shows the geographic positions of nodes on your mesh, along with shared waypoints. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/map-and-waypoints.html#map--waypoints",
    
    "relUrl": "/sv-rSE/user/map-and-waypoints.html#map--waypoints"
  },"2171": {
    "doc": "Map & Waypoints",
    "title": "Map View",
    "content": "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 . Each node that reports a position is shown as a node chip marker displaying the node’s short name. The chip is colored by the node’s own identity color (a stable color derived from its node number) — the same chip used in the node list, so a node looks the same everywhere. Marker color does not encode online/offline status. When a node’s position updates live, its marker briefly pulses. Nearby markers are clustered as you zoom out. Map Controls . | Zoom — pinch or use +/- buttons | Pan — drag to explore | Center — tap the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/map-and-waypoints.html#map-view",
    
    "relUrl": "/sv-rSE/user/map-and-waypoints.html#map-view"
  },"2172": {
    "doc": "Map & Waypoints",
    "title": "Waypoints",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. Creating a Waypoint . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | Enter a name and optional description. | Choose an icon/emoji for the waypoint. | Tap Send to share with the mesh. | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. Waypoint Properties . | Property | Beskrivning | . | Namn | Short identifier (max 29 characters) | . | Beskrivning | Optional longer description | . | Icon | Visual marker emoji on the map | . | Låst | If locked, only the creator can edit or delete | . | Expiration | Optional auto-remove date and time | . | Geofence | Optional enter/exit alert area — see Waypoint Geofences | . Waypoint Expiration . Waypoints can be set to expire automatically: . | Never (default) — waypoint remains until manually deleted | Timed — pick a specific date and time; the waypoint is automatically removed once that time passes. 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 is based on the absolute time you picked, not a duration from when the waypoint was created or received. Waypoint Geofences . Any waypoint can also define a geofence — an alert area — so you or others get notified when a node enters or leaves it: . | Set a geofence radius from the preset chips (or Off to disable), or tap Set area on map to draw a custom rectangular area instead. | Once a region is set, toggle Notify on enter and/or Notify on exit. | Optionally enable Favorites only to limit alerts to your favorited nodes. | . Since waypoints (and their geofences) are broadcast to the whole mesh, only the creator is alerted by default. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. Managing Waypoints . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/map-and-waypoints.html#waypoints",
    
    "relUrl": "/sv-rSE/user/map-and-waypoints.html#waypoints"
  },"2173": {
    "doc": "Map & Waypoints",
    "title": "Kartlager",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Imported layers are listed with a toggle to show/hide each one and an option to remove it. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. Site Planner . Site Planner estimates RF coverage for a transmitter and draws it on the map as a color-coded overlay. Open it from a map control, or from a node’s detail page via Estimate coverage (shown only for nodes with a known position). Configure the transmitter (location, frequency, TX power, antenna gain and height), the receiver (sensitivity, height), and simulation options (max range, high-resolution terrain, color palette), then run the estimate. Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/map-and-waypoints.html#kartlager",
    
    "relUrl": "/sv-rSE/user/map-and-waypoints.html#kartlager"
  },"2174": {
    "doc": "Map & Waypoints",
    "title": "Position Sharing",
    "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. 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. To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/map-and-waypoints.html#position-sharing",
    
    "relUrl": "/sv-rSE/user/map-and-waypoints.html#position-sharing"
  },"2175": {
    "doc": "Map & Waypoints",
    "title": "Map Sources",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | Anteckningar | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | Mörkt | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/map-and-waypoints.html#map-sources",
    
    "relUrl": "/sv-rSE/user/map-and-waypoints.html#map-sources"
  },"2176": {
    "doc": "Map & Waypoints",
    "title": "Related Topics",
    "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | Units & Locale — distance and coordinate display formats | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/map-and-waypoints.html#related-topics",
    
    "relUrl": "/sv-rSE/user/map-and-waypoints.html#related-topics"
  },"2177": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": " ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/map-and-waypoints.html",
    
    "relUrl": "/sv-rSE/user/map-and-waypoints.html"
  },"2178": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": "The Map screen shows the geographic positions of nodes on your mesh, along with shared waypoints. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/map-and-waypoints.html#map--waypoints",
    
    "relUrl": "/ht-rHT/user/map-and-waypoints.html#map--waypoints"
  },"2179": {
    "doc": "Map & Waypoints",
    "title": "Map View",
    "content": "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 . Each node that reports a position is shown as a node chip marker displaying the node’s short name. The chip is colored by the node’s own identity color (a stable color derived from its node number) — the same chip used in the node list, so a node looks the same everywhere. Marker color does not encode online/offline status. When a node’s position updates live, its marker briefly pulses. Nearby markers are clustered as you zoom out. Map Controls . | Zoom — pinch or use +/- buttons | Pan — drag to explore | Center — tap the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/map-and-waypoints.html#map-view",
    
    "relUrl": "/ht-rHT/user/map-and-waypoints.html#map-view"
  },"2180": {
    "doc": "Map & Waypoints",
    "title": "Waypoints",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. Creating a Waypoint . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | Enter a name and optional description. | Choose an icon/emoji for the waypoint. | Tap Send to share with the mesh. | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. Waypoint Properties . | Property | Deskripsyon | . | Non | Short identifier (max 29 characters) | . | Deskripsyon | Optional longer description | . | Icon | Visual marker emoji on the map | . | Loken | If locked, only the creator can edit or delete | . | Expiration | Optional auto-remove date and time | . | Geofence | Optional enter/exit alert area — see Waypoint Geofences | . Waypoint Expiration . Waypoints can be set to expire automatically: . | Never (default) — waypoint remains until manually deleted | Timed — pick a specific date and time; the waypoint is automatically removed once that time passes. 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 is based on the absolute time you picked, not a duration from when the waypoint was created or received. Waypoint Geofences . Any waypoint can also define a geofence — an alert area — so you or others get notified when a node enters or leaves it: . | Set a geofence radius from the preset chips (or Off to disable), or tap Set area on map to draw a custom rectangular area instead. | Once a region is set, toggle Notify on enter and/or Notify on exit. | Optionally enable Favorites only to limit alerts to your favorited nodes. | . Since waypoints (and their geofences) are broadcast to the whole mesh, only the creator is alerted by default. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. Managing Waypoints . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/map-and-waypoints.html#waypoints",
    
    "relUrl": "/ht-rHT/user/map-and-waypoints.html#waypoints"
  },"2181": {
    "doc": "Map & Waypoints",
    "title": "Map Layers",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Imported layers are listed with a toggle to show/hide each one and an option to remove it. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. Site Planner . Site Planner estimates RF coverage for a transmitter and draws it on the map as a color-coded overlay. Open it from a map control, or from a node’s detail page via Estimate coverage (shown only for nodes with a known position). Configure the transmitter (location, frequency, TX power, antenna gain and height), the receiver (sensitivity, height), and simulation options (max range, high-resolution terrain, color palette), then run the estimate. Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/map-and-waypoints.html#map-layers",
    
    "relUrl": "/ht-rHT/user/map-and-waypoints.html#map-layers"
  },"2182": {
    "doc": "Map & Waypoints",
    "title": "Position Sharing",
    "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. 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. To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/map-and-waypoints.html#position-sharing",
    
    "relUrl": "/ht-rHT/user/map-and-waypoints.html#position-sharing"
  },"2183": {
    "doc": "Map & Waypoints",
    "title": "Map Sources",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | Notes | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | Fènwa | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/map-and-waypoints.html#map-sources",
    
    "relUrl": "/ht-rHT/user/map-and-waypoints.html#map-sources"
  },"2184": {
    "doc": "Map & Waypoints",
    "title": "Related Topics",
    "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | Units & Locale — distance and coordinate display formats | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/map-and-waypoints.html#related-topics",
    
    "relUrl": "/ht-rHT/user/map-and-waypoints.html#related-topics"
  },"2185": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": " ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/map-and-waypoints.html",
    
    "relUrl": "/ht-rHT/user/map-and-waypoints.html"
  },"2186": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": "The Map screen shows the geographic positions of nodes on your mesh, along with shared waypoints. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/map-and-waypoints.html#map--waypoints",
    
    "relUrl": "/sr-rLatn/user/map-and-waypoints.html#map--waypoints"
  },"2187": {
    "doc": "Map & Waypoints",
    "title": "Map View",
    "content": "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 . Each node that reports a position is shown as a node chip marker displaying the node’s short name. The chip is colored by the node’s own identity color (a stable color derived from its node number) — the same chip used in the node list, so a node looks the same everywhere. Marker color does not encode online/offline status. When a node’s position updates live, its marker briefly pulses. Nearby markers are clustered as you zoom out. Map Controls . | Zoom — pinch or use +/- buttons | Pan — drag to explore | Center — tap the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/map-and-waypoints.html#map-view",
    
    "relUrl": "/sr-rLatn/user/map-and-waypoints.html#map-view"
  },"2188": {
    "doc": "Map & Waypoints",
    "title": "Waypoints",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. Creating a Waypoint . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | Enter a name and optional description. | Choose an icon/emoji for the waypoint. | Tap Send to share with the mesh. | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. Waypoint Properties . | Property | Опис | . | Назив | Short identifier (max 29 characters) | . | Опис | Optional longer description | . | Иконица | Visual marker emoji on the map | . | Закључано | If locked, only the creator can edit or delete | . | Expiration | Optional auto-remove date and time | . | Geofence | Optional enter/exit alert area — see Waypoint Geofences | . Waypoint Expiration . Waypoints can be set to expire automatically: . | Never (default) — waypoint remains until manually deleted | Timed — pick a specific date and time; the waypoint is automatically removed once that time passes. 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 is based on the absolute time you picked, not a duration from when the waypoint was created or received. Waypoint Geofences . Any waypoint can also define a geofence — an alert area — so you or others get notified when a node enters or leaves it: . | Set a geofence radius from the preset chips (or Off to disable), or tap Set area on map to draw a custom rectangular area instead. | Once a region is set, toggle Notify on enter and/or Notify on exit. | Optionally enable Favorites only to limit alerts to your favorited nodes. | . Since waypoints (and their geofences) are broadcast to the whole mesh, only the creator is alerted by default. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. Managing Waypoints . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/map-and-waypoints.html#waypoints",
    
    "relUrl": "/sr-rLatn/user/map-and-waypoints.html#waypoints"
  },"2189": {
    "doc": "Map & Waypoints",
    "title": "Map Layers",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Imported layers are listed with a toggle to show/hide each one and an option to remove it. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. Site Planner . Site Planner estimates RF coverage for a transmitter and draws it on the map as a color-coded overlay. Open it from a map control, or from a node’s detail page via Estimate coverage (shown only for nodes with a known position). Configure the transmitter (location, frequency, TX power, antenna gain and height), the receiver (sensitivity, height), and simulation options (max range, high-resolution terrain, color palette), then run the estimate. Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/map-and-waypoints.html#map-layers",
    
    "relUrl": "/sr-rLatn/user/map-and-waypoints.html#map-layers"
  },"2190": {
    "doc": "Map & Waypoints",
    "title": "Position Sharing",
    "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. 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. To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/map-and-waypoints.html#position-sharing",
    
    "relUrl": "/sr-rLatn/user/map-and-waypoints.html#position-sharing"
  },"2191": {
    "doc": "Map & Waypoints",
    "title": "Map Sources",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | Белешке | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | Тамна | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/map-and-waypoints.html#map-sources",
    
    "relUrl": "/sr-rLatn/user/map-and-waypoints.html#map-sources"
  },"2192": {
    "doc": "Map & Waypoints",
    "title": "Related Topics",
    "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | Units & Locale — distance and coordinate display formats | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/map-and-waypoints.html#related-topics",
    
    "relUrl": "/sr-rLatn/user/map-and-waypoints.html#related-topics"
  },"2193": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": " ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/map-and-waypoints.html",
    
    "relUrl": "/sr-rLatn/user/map-and-waypoints.html"
  },"2194": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": "The Map screen shows the geographic positions of nodes on your mesh, along with shared waypoints. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/map-and-waypoints.html#map--waypoints",
    
    "relUrl": "/nl-rNL/user/map-and-waypoints.html#map--waypoints"
  },"2195": {
    "doc": "Map & Waypoints",
    "title": "Map View",
    "content": "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 . Each node that reports a position is shown as a node chip marker displaying the node’s short name. The chip is colored by the node’s own identity color (a stable color derived from its node number) — the same chip used in the node list, so a node looks the same everywhere. Marker color does not encode online/offline status. When a node’s position updates live, its marker briefly pulses. Nearby markers are clustered as you zoom out. Map Controls . | Zoom — pinch or use +/- buttons | Pan — drag to explore | Center — tap the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/map-and-waypoints.html#map-view",
    
    "relUrl": "/nl-rNL/user/map-and-waypoints.html#map-view"
  },"2196": {
    "doc": "Map & Waypoints",
    "title": "Waypoints",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. Creating a Waypoint . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | Enter a name and optional description. | Choose an icon/emoji for the waypoint. | Tap Send to share with the mesh. | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. Waypoint Properties . | Property | Beschrijving | . | Naam | Short identifier (max 29 characters) | . | Beschrijving | Optional longer description | . | Icon | Visual marker emoji on the map | . | Vergrendeld | If locked, only the creator can edit or delete | . | Expiration | Optional auto-remove date and time | . | Geofence | Optional enter/exit alert area — see Waypoint Geofences | . Waypoint Expiration . Waypoints can be set to expire automatically: . | Never (default) — waypoint remains until manually deleted | Timed — pick a specific date and time; the waypoint is automatically removed once that time passes. 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 is based on the absolute time you picked, not a duration from when the waypoint was created or received. Waypoint Geofences . Any waypoint can also define a geofence — an alert area — so you or others get notified when a node enters or leaves it: . | Set a geofence radius from the preset chips (or Off to disable), or tap Set area on map to draw a custom rectangular area instead. | Once a region is set, toggle Notify on enter and/or Notify on exit. | Optionally enable Favorites only to limit alerts to your favorited nodes. | . Since waypoints (and their geofences) are broadcast to the whole mesh, only the creator is alerted by default. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. Managing Waypoints . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/map-and-waypoints.html#waypoints",
    
    "relUrl": "/nl-rNL/user/map-and-waypoints.html#waypoints"
  },"2197": {
    "doc": "Map & Waypoints",
    "title": "Map Layers",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Imported layers are listed with a toggle to show/hide each one and an option to remove it. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. Site Planner . Site Planner estimates RF coverage for a transmitter and draws it on the map as a color-coded overlay. Open it from a map control, or from a node’s detail page via Estimate coverage (shown only for nodes with a known position). Configure the transmitter (location, frequency, TX power, antenna gain and height), the receiver (sensitivity, height), and simulation options (max range, high-resolution terrain, color palette), then run the estimate. Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/map-and-waypoints.html#map-layers",
    
    "relUrl": "/nl-rNL/user/map-and-waypoints.html#map-layers"
  },"2198": {
    "doc": "Map & Waypoints",
    "title": "Position Sharing",
    "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. 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. To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/map-and-waypoints.html#position-sharing",
    
    "relUrl": "/nl-rNL/user/map-and-waypoints.html#position-sharing"
  },"2199": {
    "doc": "Map & Waypoints",
    "title": "Map Sources",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | Notes | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | Donker | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/map-and-waypoints.html#map-sources",
    
    "relUrl": "/nl-rNL/user/map-and-waypoints.html#map-sources"
  },"2200": {
    "doc": "Map & Waypoints",
    "title": "Related Topics",
    "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | Units & Locale — distance and coordinate display formats | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/map-and-waypoints.html#related-topics",
    
    "relUrl": "/nl-rNL/user/map-and-waypoints.html#related-topics"
  },"2201": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": " ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/map-and-waypoints.html",
    
    "relUrl": "/nl-rNL/user/map-and-waypoints.html"
  },"2202": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": "The Map screen shows the geographic positions of nodes on your mesh, along with shared waypoints. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/map-and-waypoints.html#map--waypoints",
    
    "relUrl": "/uk-rUA/user/map-and-waypoints.html#map--waypoints"
  },"2203": {
    "doc": "Map & Waypoints",
    "title": "Map View",
    "content": "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 . Each node that reports a position is shown as a node chip marker displaying the node’s short name. The chip is colored by the node’s own identity color (a stable color derived from its node number) — the same chip used in the node list, so a node looks the same everywhere. Marker color does not encode online/offline status. When a node’s position updates live, its marker briefly pulses. Nearby markers are clustered as you zoom out. Map Controls . | Zoom — pinch or use +/- buttons | Pan — drag to explore | Center — tap the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/map-and-waypoints.html#map-view",
    
    "relUrl": "/uk-rUA/user/map-and-waypoints.html#map-view"
  },"2204": {
    "doc": "Map & Waypoints",
    "title": "Waypoints",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. Creating a Waypoint . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | Enter a name and optional description. | Choose an icon/emoji for the waypoint. | Tap Send to share with the mesh. | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. Waypoint Properties . | Property | Опис | . | Ім’я | Short identifier (max 29 characters) | . | Опис | Optional longer description | . | Icon | Visual marker emoji on the map | . | Блоковано | If locked, only the creator can edit or delete | . | Expiration | Optional auto-remove date and time | . | Geofence | Optional enter/exit alert area — see Waypoint Geofences | . Waypoint Expiration . Waypoints can be set to expire automatically: . | Never (default) — waypoint remains until manually deleted | Timed — pick a specific date and time; the waypoint is automatically removed once that time passes. 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 is based on the absolute time you picked, not a duration from when the waypoint was created or received. Waypoint Geofences . Any waypoint can also define a geofence — an alert area — so you or others get notified when a node enters or leaves it: . | Set a geofence radius from the preset chips (or Off to disable), or tap Set area on map to draw a custom rectangular area instead. | Once a region is set, toggle Notify on enter and/or Notify on exit. | Optionally enable Favorites only to limit alerts to your favorited nodes. | . Since waypoints (and their geofences) are broadcast to the whole mesh, only the creator is alerted by default. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. Managing Waypoints . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/map-and-waypoints.html#waypoints",
    
    "relUrl": "/uk-rUA/user/map-and-waypoints.html#waypoints"
  },"2205": {
    "doc": "Map & Waypoints",
    "title": "Шари мапи",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Imported layers are listed with a toggle to show/hide each one and an option to remove it. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. Site Planner . Site Planner estimates RF coverage for a transmitter and draws it on the map as a color-coded overlay. Open it from a map control, or from a node’s detail page via Estimate coverage (shown only for nodes with a known position). Configure the transmitter (location, frequency, TX power, antenna gain and height), the receiver (sensitivity, height), and simulation options (max range, high-resolution terrain, color palette), then run the estimate. Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/map-and-waypoints.html#%D1%88%D0%B0%D1%80%D0%B8-%D0%BC%D0%B0%D0%BF%D0%B8",
    
    "relUrl": "/uk-rUA/user/map-and-waypoints.html#шари-мапи"
  },"2206": {
    "doc": "Map & Waypoints",
    "title": "Position Sharing",
    "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. 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. To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/map-and-waypoints.html#position-sharing",
    
    "relUrl": "/uk-rUA/user/map-and-waypoints.html#position-sharing"
  },"2207": {
    "doc": "Map & Waypoints",
    "title": "Map Sources",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | Нотатки | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | Темна | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/map-and-waypoints.html#map-sources",
    
    "relUrl": "/uk-rUA/user/map-and-waypoints.html#map-sources"
  },"2208": {
    "doc": "Map & Waypoints",
    "title": "Related Topics",
    "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | Units & Locale — distance and coordinate display formats | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/map-and-waypoints.html#related-topics",
    
    "relUrl": "/uk-rUA/user/map-and-waypoints.html#related-topics"
  },"2209": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": " ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/map-and-waypoints.html",
    
    "relUrl": "/uk-rUA/user/map-and-waypoints.html"
  },"2210": {
    "doc": "Kartta ja reittipisteet",
    "title": "Kartta ja reittipisteet",
    "content": "Karttanäkymä näyttää mesh-verkkosi radioiden maantieteelliset sijainnit sekä jaetut reittipisteet. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/map-and-waypoints.html",
    
    "relUrl": "/fi-rFI/user/map-and-waypoints.html"
  },"2211": {
    "doc": "Kartta ja reittipisteet",
    "title": "Karttanäkymä",
    "content": "Kartta näyttää: . | Radion sijainnit — kunkin sijaintia lähettävän radion värilliset merkit | Reittipisteet — jaetut kiinnostavat kohteet | Oma sijaintisi — nykyinen GPS-sijaintisi | . Radioiden merkinnät . Jokainen sijaintinsa raportoiva radio näytetään radiotunnisteena, jossa näkyy radion lyhyt nimi. Tunniste väritetään radion oman tunnistevärin mukaan (pysyvä väri, joka muodostetaan radion numerosta) — sama radiotunniste näkyy myös radioluettelossa, joten radio näyttää kaikkialla samalta. Merkin väri ei ilmaise, onko radio verkossa vai poissa verkosta. Kun radion sijainti päivittyy reaaliajassa, sen merkki sykkii hetken. Lähekkäiset merkit ryhmitellään, kun loitonnat karttaa. Kartan hallinta . | Zoomaus — nipistä tai käytä +/- -painikkeita | Panorointi — vedä karttaa | Keskitä — napauta sijaintipainiketta keskittääksesi kartan omaan sijaintiisi | Radion napautus — avaa radion tiedot napauttamalla merkkiä | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. Napauta kompassia suunnan palauttamiseksi pohjoiseen tai sijaintipainiketta keskittääksesi oman sijaintisi. On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/map-and-waypoints.html#karttan%C3%A4kym%C3%A4",
    
    "relUrl": "/fi-rFI/user/map-and-waypoints.html#karttanäkymä"
  },"2212": {
    "doc": "Kartta ja reittipisteet",
    "title": "Reittipisteet",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. Reittipisteen luominen . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Kosketa karttaa halutusta kohdasta ja pidä sormi paikallaan. | Anna nimi ja valinnainen kuvaus. | Valitse reittipisteelle kuvake tai emoji. | Napauta Lähetä jakaaksesi sen verkkoon. | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. Reittipisteen ominaisuudet . | Ominaisuus | Kuvaus | . | Nimi | Lyhyt tunniste (enintään 29 merkkiä) | . | Kuvaus | Valinnainen pidempi kuvaus | . | Kuvake | Visuaalinen merkkiemoji kartalla | . | Lukittu | Jos lukittu, vain merkin luonut voi muokata tai poistaa sen | . | Voimassaoloaika | Valinnainen automaattinen poistopäivä ja -aika | . | Aluerajaus | Valinnainen saapumis-/poistumishälytysalue — katso Reittipisteiden geoaidat | . Reittipisteen vanheneminen . Reittipisteet voidaan asettaa vanhenemaan automaattisesti: . | Ei koskaan (oletus) — reittipiste pysyy voimassa kunnes se poistetaan manuaalisesti | Ajastettu — valitse tietty päivämäärä ja kellonaika. Reittipiste poistetaan automaattisesti, kun kyseinen ajankohta on ohitettu. Hyödyllinen tilapäisille merkinnöille kuten kokoontumispaikat, vaarat tai tapaamispaikat. | . Vanhentuneet reittipisteet piilotetaan automaattisesti kartalta, jotta näkymä pysyy selkeänä. Poistumisen ajastus perustuu valitsemaasi päivämäärään ja kellonaikaan, ei siihen, kuinka kauan reittipiste on ollut olemassa tai vastaanotettuna. Reittipisteiden aluerajaukset . Mikä tahansa reittipiste voidaan määrittää myös aluerajaukseksi eli ilmoitusalueeksi, jolloin sinä tai muut käyttäjät saatte ilmoituksen, kun radio saapuu alueelle tai poistuu sieltä: . | Määritä aluerajauksen säde valmiista vaihtoehdoista (tai valitse Pois poistaaksesi toiminnon käytöstä), tai napauta Määritä alue kartalla piirtääksesi mukautetun suorakulmaisen alueen. | Kun alue on määritetty, ota käyttöön Ilmoita saapuessa ja/tai Ilmoita poistuttaessa. | Voit halutessasi ottaa käyttöön Vain suosikit -asetuksen, jolloin ilmoituksia näytetään vain suosikkiradioistasi. | . Koska reittipisteet (ja niiden aluerajaukset) lähetetään koko mesh-verkkoon, oletusarvoisesti ilmoitukset saa vain niiden luoja. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. Reittipisteiden hallinta . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/map-and-waypoints.html#reittipisteet",
    
    "relUrl": "/fi-rFI/user/map-and-waypoints.html#reittipisteet"
  },"2213": {
    "doc": "Kartta ja reittipisteet",
    "title": "Karttatasot",
    "content": "Napauta kartan tasokuvaketta avataksesi Hallitse karttatasoja. Tuo omia peitekuvia .kml-, .kmz- tai GeoJSON-muodossa, mukaan lukien KMZ-maanpeitekuvat (georeferoidut kuvat, kuten viedyt topografiset tai ilmakuvat), jotka sijoitetaan kartalle niiden määritettyjen rajojen mukaisesti. Lisää sellainen valitsemalla tiedosto Lisää taso -toiminnolla, avaamalla tiedosto Meshtasticissa tai jakamalla se sovellukseen toisesta sovelluksesta. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Tuodut karttatasot näkyvät luettelossa, jossa voit näyttää tai piilottaa ne sekä poistaa ne. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. Tämä toimii Google Play -versiossa, F-Droid-versiossa ja Desktopissa, joissa käytetään samaa karttatasojen tallennusta ja tiedostonvalitsinta. Site Planner . Site Planner arvioi lähettimen kuuluvuusalueen ja piirtää sen kartalle värikoodattuna peittoalueena. Avaa se kartan ohjaimista tai radion tiedoista Arvioi peittoalue -toiminnolla (näkyy vain radioille, joilla on tunnettu sijainti). Määritä lähettimen asetukset (sijainti, taajuus, lähetysteho, antennin vahvistus ja korkeus), vastaanottimen asetukset (herkkyys ja korkeus) sekä simuloinnin asetukset (enimmäisetäisyys, korkean tarkkuuden maastomalli ja väripaletti), ja käynnistä sitten arviointi. Kuten karttatasotkin, Site Planner toimii sekä Google Play- että F-Droid-versioissa, joissa valmis arvio piirretään kartalle peitekuvana. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/map-and-waypoints.html#karttatasot",
    
    "relUrl": "/fi-rFI/user/map-and-waypoints.html#karttatasot"
  },"2214": {
    "doc": "Kartta ja reittipisteet",
    "title": "Sijainnin jakaminen",
    "content": "Sijainnin jakamisen käyttöönotto . Radiosi jakaa GPS-sijaintinsa seuraavilla tavoilla: . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. Tietosuoja . 🔒 Yksityisyys: sijaintitiedot lähetetään kaikille saman kanavan radioille. Jos et halua sijaintiasi jaettavan, poista GPS käytöstä asetuksista tai käytä kiinteää tai valesijaintia. To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/map-and-waypoints.html#sijainnin-jakaminen",
    
    "relUrl": "/fi-rFI/user/map-and-waypoints.html#sijainnin-jakaminen"
  },"2215": {
    "doc": "Kartta ja reittipisteet",
    "title": "Karttalähteet",
    "content": "Jokaisessa versiossa kartan työkalurivillä on karttapohjan valitsin. Google Play -versioissa käytetään Googlen omia karttatyyppejä. F-Droid- ja Työpöytä-versioissa käytetään MapLibren vektorityylejä. Alempana karttapohjan valitsimessa kaikki tarjoavat samat rasterikarttapohjat: . | Karttapohja | Viestit | . | Normaali / Satelliitti / Maasto / Hybridi | Vain Google Play – Googlen omat karttatyypit | . | Liberty | Oletus F-Droid- ja Desktop-versioissa. Vektorinen tiekartta | . | Positron | F-Droid and Desktop only. Vähäkontrastinen vektorikartta, jonka päällä radiomerkit erottuvat hyvin | . | Tumma | F-Droid and Desktop only. Tummiin teemoihin sopiva vektorikartta | . | OpenStreetMap | Perinteiset rasterimuotoiset tiekarttaruudut | . | OpenTopoMap | Rasterimuotoinen topografinen kartta | . | USGS Topo / USGS Imagery | Vain Yhdysvaltojen kattavuus | . | Esri Topo / Esri Imagery | Topografinen kartta ja satelliittikuvat | . Peitekuvat voidaan ottaa käyttöön minkä tahansa karttapohjan päällä karttatasovalikosta: . | Säätutka — NOAA NEXRAD -heijastavuus (Yhdysvaltojen kattavuus) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Oman karttatiilipalvelun lisääminen . Mikä tahansa XYZ-karttatiilipalvelu voidaan lisätä karttapohjaksi kaikkiin versioihin, myös työpöytiin. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. Esimerkiksi kansallinen karttapalvelu: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Karttatiilet tallennetaan välimuistiin levylle, joten kartan siirtäminen ei lataa juuri katsottua aluetta uudelleen. Androidissa tällä samalla näkymällä voidaan tuoda myös paikallinen .mbtiles-arkisto täysin offline-käyttöä varten. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/map-and-waypoints.html#karttal%C3%A4hteet",
    
    "relUrl": "/fi-rFI/user/map-and-waypoints.html#karttalähteet"
  },"2216": {
    "doc": "Kartta ja reittipisteet",
    "title": "Aiheeseen liittyvät aiheet",
    "content": ". | Radiot — tarkastele ja suodata radiolistaa | Radion mittarit — signaalin laatu ja sijaintihistoria yksittäisille radioille | Paikallinen mesh-verkon etsintä — reitiselvitys ja naapuritiedot mesh-verkon rakenteen hahmottamiseen | Yksiköt ja kieliasetukset — etäisyys- ja koordinaattien näyttömuodot | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/map-and-waypoints.html#aiheeseen-liittyv%C3%A4t-aiheet",
    
    "relUrl": "/fi-rFI/user/map-and-waypoints.html#aiheeseen-liittyvät-aiheet"
  },"2217": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": "The Map screen shows the geographic positions of nodes on your mesh, along with shared waypoints. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/map-and-waypoints.html#map--waypoints",
    
    "relUrl": "/is-rIS/user/map-and-waypoints.html#map--waypoints"
  },"2218": {
    "doc": "Map & Waypoints",
    "title": "Map View",
    "content": "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 . Each node that reports a position is shown as a node chip marker displaying the node’s short name. The chip is colored by the node’s own identity color (a stable color derived from its node number) — the same chip used in the node list, so a node looks the same everywhere. Marker color does not encode online/offline status. When a node’s position updates live, its marker briefly pulses. Nearby markers are clustered as you zoom out. Map Controls . | Zoom — pinch or use +/- buttons | Pan — drag to explore | Center — tap the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/map-and-waypoints.html#map-view",
    
    "relUrl": "/is-rIS/user/map-and-waypoints.html#map-view"
  },"2219": {
    "doc": "Map & Waypoints",
    "title": "Waypoints",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. Creating a Waypoint . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | Enter a name and optional description. | Choose an icon/emoji for the waypoint. | Tap Send to share with the mesh. | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. Waypoint Properties . | Property | Lýsing | . | Heiti | Short identifier (max 29 characters) | . | Lýsing | Optional longer description | . | Icon | Visual marker emoji on the map | . | Læst | If locked, only the creator can edit or delete | . | Expiration | Optional auto-remove date and time | . | Geofence | Optional enter/exit alert area — see Waypoint Geofences | . Waypoint Expiration . Waypoints can be set to expire automatically: . | Never (default) — waypoint remains until manually deleted | Timed — pick a specific date and time; the waypoint is automatically removed once that time passes. 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 is based on the absolute time you picked, not a duration from when the waypoint was created or received. Waypoint Geofences . Any waypoint can also define a geofence — an alert area — so you or others get notified when a node enters or leaves it: . | Set a geofence radius from the preset chips (or Off to disable), or tap Set area on map to draw a custom rectangular area instead. | Once a region is set, toggle Notify on enter and/or Notify on exit. | Optionally enable Favorites only to limit alerts to your favorited nodes. | . Since waypoints (and their geofences) are broadcast to the whole mesh, only the creator is alerted by default. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. Managing Waypoints . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/map-and-waypoints.html#waypoints",
    
    "relUrl": "/is-rIS/user/map-and-waypoints.html#waypoints"
  },"2220": {
    "doc": "Map & Waypoints",
    "title": "Map Layers",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Imported layers are listed with a toggle to show/hide each one and an option to remove it. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. Site Planner . Site Planner estimates RF coverage for a transmitter and draws it on the map as a color-coded overlay. Open it from a map control, or from a node’s detail page via Estimate coverage (shown only for nodes with a known position). Configure the transmitter (location, frequency, TX power, antenna gain and height), the receiver (sensitivity, height), and simulation options (max range, high-resolution terrain, color palette), then run the estimate. Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/map-and-waypoints.html#map-layers",
    
    "relUrl": "/is-rIS/user/map-and-waypoints.html#map-layers"
  },"2221": {
    "doc": "Map & Waypoints",
    "title": "Position Sharing",
    "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. 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. To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/map-and-waypoints.html#position-sharing",
    
    "relUrl": "/is-rIS/user/map-and-waypoints.html#position-sharing"
  },"2222": {
    "doc": "Map & Waypoints",
    "title": "Map Sources",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | Notes | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | Dökkt | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/map-and-waypoints.html#map-sources",
    
    "relUrl": "/is-rIS/user/map-and-waypoints.html#map-sources"
  },"2223": {
    "doc": "Map & Waypoints",
    "title": "Related Topics",
    "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | Units & Locale — distance and coordinate display formats | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/map-and-waypoints.html#related-topics",
    
    "relUrl": "/is-rIS/user/map-and-waypoints.html#related-topics"
  },"2224": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": " ",
    "url": "/Meshtastic-Android/main/is-rIS/user/map-and-waypoints.html",
    
    "relUrl": "/is-rIS/user/map-and-waypoints.html"
  },"2225": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": "The Map screen shows the geographic positions of nodes on your mesh, along with shared waypoints. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/map-and-waypoints.html#map--waypoints",
    
    "relUrl": "/lt-rLT/user/map-and-waypoints.html#map--waypoints"
  },"2226": {
    "doc": "Map & Waypoints",
    "title": "Map View",
    "content": "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 . Each node that reports a position is shown as a node chip marker displaying the node’s short name. The chip is colored by the node’s own identity color (a stable color derived from its node number) — the same chip used in the node list, so a node looks the same everywhere. Marker color does not encode online/offline status. When a node’s position updates live, its marker briefly pulses. Nearby markers are clustered as you zoom out. Map Controls . | Zoom — pinch or use +/- buttons | Pan — drag to explore | Center — tap the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/map-and-waypoints.html#map-view",
    
    "relUrl": "/lt-rLT/user/map-and-waypoints.html#map-view"
  },"2227": {
    "doc": "Map & Waypoints",
    "title": "Waypoints",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. Creating a Waypoint . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | Enter a name and optional description. | Choose an icon/emoji for the waypoint. | Tap Send to share with the mesh. | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. Waypoint Properties . | Property | Aprašymas | . | Pavadinimas | Short identifier (max 29 characters) | . | Aprašymas | Optional longer description | . | Icon | Visual marker emoji on the map | . | Užrakintas | If locked, only the creator can edit or delete | . | Expiration | Optional auto-remove date and time | . | Geofence | Optional enter/exit alert area — see Waypoint Geofences | . Waypoint Expiration . Waypoints can be set to expire automatically: . | Never (default) — waypoint remains until manually deleted | Timed — pick a specific date and time; the waypoint is automatically removed once that time passes. 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 is based on the absolute time you picked, not a duration from when the waypoint was created or received. Waypoint Geofences . Any waypoint can also define a geofence — an alert area — so you or others get notified when a node enters or leaves it: . | Set a geofence radius from the preset chips (or Off to disable), or tap Set area on map to draw a custom rectangular area instead. | Once a region is set, toggle Notify on enter and/or Notify on exit. | Optionally enable Favorites only to limit alerts to your favorited nodes. | . Since waypoints (and their geofences) are broadcast to the whole mesh, only the creator is alerted by default. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. Managing Waypoints . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/map-and-waypoints.html#waypoints",
    
    "relUrl": "/lt-rLT/user/map-and-waypoints.html#waypoints"
  },"2228": {
    "doc": "Map & Waypoints",
    "title": "Map Layers",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Imported layers are listed with a toggle to show/hide each one and an option to remove it. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. Site Planner . Site Planner estimates RF coverage for a transmitter and draws it on the map as a color-coded overlay. Open it from a map control, or from a node’s detail page via Estimate coverage (shown only for nodes with a known position). Configure the transmitter (location, frequency, TX power, antenna gain and height), the receiver (sensitivity, height), and simulation options (max range, high-resolution terrain, color palette), then run the estimate. Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/map-and-waypoints.html#map-layers",
    
    "relUrl": "/lt-rLT/user/map-and-waypoints.html#map-layers"
  },"2229": {
    "doc": "Map & Waypoints",
    "title": "Position Sharing",
    "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. 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. To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/map-and-waypoints.html#position-sharing",
    
    "relUrl": "/lt-rLT/user/map-and-waypoints.html#position-sharing"
  },"2230": {
    "doc": "Map & Waypoints",
    "title": "Map Sources",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | Notes | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | Tamsi | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/map-and-waypoints.html#map-sources",
    
    "relUrl": "/lt-rLT/user/map-and-waypoints.html#map-sources"
  },"2231": {
    "doc": "Map & Waypoints",
    "title": "Related Topics",
    "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | Units & Locale — distance and coordinate display formats | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/map-and-waypoints.html#related-topics",
    
    "relUrl": "/lt-rLT/user/map-and-waypoints.html#related-topics"
  },"2232": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": " ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/map-and-waypoints.html",
    
    "relUrl": "/lt-rLT/user/map-and-waypoints.html"
  },"2233": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": "The Map screen shows the geographic positions of nodes on your mesh, along with shared waypoints. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/map-and-waypoints.html#map--waypoints",
    
    "relUrl": "/gl-rES/user/map-and-waypoints.html#map--waypoints"
  },"2234": {
    "doc": "Map & Waypoints",
    "title": "Map View",
    "content": "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 . Each node that reports a position is shown as a node chip marker displaying the node’s short name. The chip is colored by the node’s own identity color (a stable color derived from its node number) — the same chip used in the node list, so a node looks the same everywhere. Marker color does not encode online/offline status. When a node’s position updates live, its marker briefly pulses. Nearby markers are clustered as you zoom out. Map Controls . | Zoom — pinch or use +/- buttons | Pan — drag to explore | Center — tap the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/map-and-waypoints.html#map-view",
    
    "relUrl": "/gl-rES/user/map-and-waypoints.html#map-view"
  },"2235": {
    "doc": "Map & Waypoints",
    "title": "Waypoints",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. Creating a Waypoint . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | Enter a name and optional description. | Choose an icon/emoji for the waypoint. | Tap Send to share with the mesh. | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. Waypoint Properties . | Property | Descrición | . | Nome | Short identifier (max 29 characters) | . | Descrición | Optional longer description | . | Icon | Visual marker emoji on the map | . | Bloqueado | If locked, only the creator can edit or delete | . | Expiration | Optional auto-remove date and time | . | Geofence | Optional enter/exit alert area — see Waypoint Geofences | . Waypoint Expiration . Waypoints can be set to expire automatically: . | Never (default) — waypoint remains until manually deleted | Timed — pick a specific date and time; the waypoint is automatically removed once that time passes. 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 is based on the absolute time you picked, not a duration from when the waypoint was created or received. Waypoint Geofences . Any waypoint can also define a geofence — an alert area — so you or others get notified when a node enters or leaves it: . | Set a geofence radius from the preset chips (or Off to disable), or tap Set area on map to draw a custom rectangular area instead. | Once a region is set, toggle Notify on enter and/or Notify on exit. | Optionally enable Favorites only to limit alerts to your favorited nodes. | . Since waypoints (and their geofences) are broadcast to the whole mesh, only the creator is alerted by default. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. Managing Waypoints . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/map-and-waypoints.html#waypoints",
    
    "relUrl": "/gl-rES/user/map-and-waypoints.html#waypoints"
  },"2236": {
    "doc": "Map & Waypoints",
    "title": "Map Layers",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Imported layers are listed with a toggle to show/hide each one and an option to remove it. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. Site Planner . Site Planner estimates RF coverage for a transmitter and draws it on the map as a color-coded overlay. Open it from a map control, or from a node’s detail page via Estimate coverage (shown only for nodes with a known position). Configure the transmitter (location, frequency, TX power, antenna gain and height), the receiver (sensitivity, height), and simulation options (max range, high-resolution terrain, color palette), then run the estimate. Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/map-and-waypoints.html#map-layers",
    
    "relUrl": "/gl-rES/user/map-and-waypoints.html#map-layers"
  },"2237": {
    "doc": "Map & Waypoints",
    "title": "Position Sharing",
    "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. 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. To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/map-and-waypoints.html#position-sharing",
    
    "relUrl": "/gl-rES/user/map-and-waypoints.html#position-sharing"
  },"2238": {
    "doc": "Map & Waypoints",
    "title": "Map Sources",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | Notes | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | Escuro | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/map-and-waypoints.html#map-sources",
    
    "relUrl": "/gl-rES/user/map-and-waypoints.html#map-sources"
  },"2239": {
    "doc": "Map & Waypoints",
    "title": "Related Topics",
    "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | Units & Locale — distance and coordinate display formats | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/map-and-waypoints.html#related-topics",
    
    "relUrl": "/gl-rES/user/map-and-waypoints.html#related-topics"
  },"2240": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": " ",
    "url": "/Meshtastic-Android/main/gl-rES/user/map-and-waypoints.html",
    
    "relUrl": "/gl-rES/user/map-and-waypoints.html"
  },"2241": {
    "doc": "マップとウェイポイント",
    "title": "マップとウェイポイント",
    "content": "マップ画面には、メッシュ上のノードの地理的な位置が、共有されたウェイポイントとともに表示されます。 . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/map-and-waypoints.html",
    
    "relUrl": "/ja-rJP/user/map-and-waypoints.html"
  },"2242": {
    "doc": "マップとウェイポイント",
    "title": "マップビュー",
    "content": "マップには次のものが表示されます： . | ノードの位置： 位置を報告している各ノードの色付きマーカー | ウェイポイント： 共有された注目地点 | 自分の位置： 現在の GPS 位置 | . ノードのマーカー . 位置を報告している各ノードは、そのノードの短縮名を表示するノードチップマーカーとして表示されます。チップは、そのノード固有のアイデンティティカラー（ノード番号から導かれる一定の色）で色付けされます。ノードリストで使われるのと同じチップなので、どこでも同じ見た目になります。マーカーの色は、オンライン／オフラインの状態を表しません。ノードの位置がライブで更新されると、そのマーカーが短く脈打つように点滅します。縮小すると、近くのマーカーはまとめて表示（クラスタリング）されます。 . マップの操作 . | ズーム： ピンチ操作、または +/− ボタンを使います | 移動： ドラッグして見て回ります | Center — tap the location button to center on your position | ノードのタップ： ノードのマーカーをタップすると詳細を表示します | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. コンパスをタップすると北を上に向け直し、位置ボタンをタップすると現在の位置を中央に表示します。 On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/map-and-waypoints.html#%E3%83%9E%E3%83%83%E3%83%97%E3%83%93%E3%83%A5%E3%83%BC",
    
    "relUrl": "/ja-rJP/user/map-and-waypoints.html#マップビュー"
  },"2243": {
    "doc": "マップとウェイポイント",
    "title": "ウェイポイント",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. ウェイポイントを作成する . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | 名前と、任意で説明を入力します。 | ウェイポイントのアイコン／絵文字を選びます。 | 「送信」をタップしてメッシュに共有します。 | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. ウェイポイントのプロパティ . | プロパティ | 説明 | . | 名前 | 短い識別子（最大 29 文字） | . | 説明 | 任意の、より詳しい説明 | . | アイコン | マップ上の視覚的なマーカー絵文字 | . | ロック済み | ロックすると、作成者だけが編集・削除できます | . | 有効期限 | 任意の、自動削除する日時 | . | ジオフェンス | Optional enter/exit alert area — see Waypoint Geofences | . ウェイポイントの有効期限 . ウェイポイントは、自動的に期限切れになるよう設定できます： . | なし（デフォルト）：手動で削除するまでウェイポイントは残ります | 期限付き：特定の日時を指定します。その時刻を過ぎると、ウェイポイントは自動的に削除されます。集合地点、危険箇所、待ち合わせ場所などの一時的なマーカーに便利です。 | . 期限切れのウェイポイントは、表示が煩雑にならないよう、自動的にマップから隠されます。有効期限のカウントダウンは、指定した絶対時刻を基準とし、ウェイポイントが作成または受信されてからの経過時間ではありません。 . ウェイポイントのジオフェンス . どのウェイポイントにもジオフェンス（通知エリア）を設定できます。これにより、ノードがそのエリアに進入または退出したときに、あなたや他のメンバーに通知が届きます： . | プリセットのチップからジオフェンスの半径を設定する（無効にするにはオフ）か、「マップ上でエリアを設定」をタップして、任意の四角形のエリアを描画します。 | エリアを設定したら、「進入時に通知」や「退出時に通知」を切り替えます。 | 任意で「お気に入りのみ」を有効にすると、通知をお気に入りのノードに限定できます。 | . ウェイポイント（およびそのジオフェンス）はメッシュ全体にブロードキャストされるため、デフォルトでは作成者だけに通知されます。 If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. ウェイポイントを管理する . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/map-and-waypoints.html#%E3%82%A6%E3%82%A7%E3%82%A4%E3%83%9D%E3%82%A4%E3%83%B3%E3%83%88",
    
    "relUrl": "/ja-rJP/user/map-and-waypoints.html#ウェイポイント"
  },"2244": {
    "doc": "マップとウェイポイント",
    "title": "マップレイヤー",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. インポートしたレイヤーは、それぞれ表示／非表示を切り替えるトグルと、削除するオプションとともに一覧表示されます。 Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. サイトプランナー . サイトプランナーは、送信機の RF カバレッジを推定し、色分けされたオーバーレイとしてマップに描画します。マップの操作から開くか、ノードの詳細ページから「カバレッジを推定」で開きます（位置が判明しているノードでのみ表示されます）。送信機（位置、周波数、送信出力、アンテナ利得と高さ）、受信機（感度、高さ）、シミュレーションのオプション（最大範囲、高解像度の地形、カラーパレット）を設定してから、推定を実行します。 Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/map-and-waypoints.html#%E3%83%9E%E3%83%83%E3%83%97%E3%83%AC%E3%82%A4%E3%83%A4%E3%83%BC",
    
    "relUrl": "/ja-rJP/user/map-and-waypoints.html#マップレイヤー"
  },"2245": {
    "doc": "マップとウェイポイント",
    "title": "位置の共有",
    "content": "位置の共有を有効にする . ノードは、次のいずれかに基づいて GPS 位置を共有します： . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. プライバシーに関する注意 . 🔒 プライバシー： 位置データは、チャンネル上のすべてのノードにブロードキャストされます。位置を共有したくない場合は、設定で GPS 位置を無効にするか、固定／ダミーの位置を使用してください。 To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/map-and-waypoints.html#%E4%BD%8D%E7%BD%AE%E3%81%AE%E5%85%B1%E6%9C%89",
    
    "relUrl": "/ja-rJP/user/map-and-waypoints.html#位置の共有"
  },"2246": {
    "doc": "マップとウェイポイント",
    "title": "マップソース",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | 備考 | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | ダーク | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/map-and-waypoints.html#%E3%83%9E%E3%83%83%E3%83%97%E3%82%BD%E3%83%BC%E3%82%B9",
    
    "relUrl": "/ja-rJP/user/map-and-waypoints.html#マップソース"
  },"2247": {
    "doc": "マップとウェイポイント",
    "title": "関連トピック",
    "content": ". | ノード：ノードリストの表示と絞り込み | ノードメトリクス：各ノードの信号品質と位置履歴 | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | 単位とロケール：距離と座標の表示形式 | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/map-and-waypoints.html#%E9%96%A2%E9%80%A3%E3%83%88%E3%83%94%E3%83%83%E3%82%AF",
    
    "relUrl": "/ja-rJP/user/map-and-waypoints.html#関連トピック"
  },"2248": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": "The Map screen shows the geographic positions of nodes on your mesh, along with shared waypoints. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/map-and-waypoints.html#map--waypoints",
    
    "relUrl": "/de-rDE/user/map-and-waypoints.html#map--waypoints"
  },"2249": {
    "doc": "Map & Waypoints",
    "title": "Map View",
    "content": "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 . Each node that reports a position is shown as a node chip marker displaying the node’s short name. Der Chip ist in der individuellen Identitätsfarbe des Knotens gehalten (einer festen Farbe, die sich aus der Knotennummer ableitet) – es handelt sich um denselben Chip wie in der Knotenliste, sodass ein Knoten überall gleich aussieht. Marker color does not encode online/offline status. When a node’s position updates live, its marker briefly pulses. Nearby markers are clustered as you zoom out. Kartensteuerung . | Zoom — pinch or use +/- buttons | Pan — drag to explore | Center — tap the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/map-and-waypoints.html#map-view",
    
    "relUrl": "/de-rDE/user/map-and-waypoints.html#map-view"
  },"2250": {
    "doc": "Map & Waypoints",
    "title": "Waypoints",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. Creating a Waypoint . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | Enter a name and optional description. | Choose an icon/emoji for the waypoint. | Tap Send to share with the mesh. | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. Waypoint Properties . | Property | Beschreibung | . | Name | Short identifier (max 29 characters) | . | Beschreibung | Optional longer description | . | Symbol | Visual marker emoji on the map | . | Gesperrt | If locked, only the creator can edit or delete | . | Expiration | Optional auto-remove date and time | . | Geofence | Optional enter/exit alert area — see Waypoint Geofences | . Waypoint Expiration . Waypoints can be set to expire automatically: . | Never (default) — waypoint remains until manually deleted | Timed — pick a specific date and time; the waypoint is automatically removed once that time passes. 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 is based on the absolute time you picked, not a duration from when the waypoint was created or received. Waypoint Geofences . Any waypoint can also define a geofence — an alert area — so you or others get notified when a node enters or leaves it: . | Set a geofence radius from the preset chips (or Off to disable), or tap Set area on map to draw a custom rectangular area instead. | Once a region is set, toggle Notify on enter and/or Notify on exit. | Optionally enable Favorites only to limit alerts to your favorited nodes. | . Since waypoints (and their geofences) are broadcast to the whole mesh, only the creator is alerted by default. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. Managing Waypoints . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/map-and-waypoints.html#waypoints",
    
    "relUrl": "/de-rDE/user/map-and-waypoints.html#waypoints"
  },"2251": {
    "doc": "Map & Waypoints",
    "title": "Kartenebenen",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Imported layers are listed with a toggle to show/hide each one and an option to remove it. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. Site Planner . Site Planner estimates RF coverage for a transmitter and draws it on the map as a color-coded overlay. Open it from a map control, or from a node’s detail page via Estimate coverage (shown only for nodes with a known position). Configure the transmitter (location, frequency, TX power, antenna gain and height), the receiver (sensitivity, height), and simulation options (max range, high-resolution terrain, color palette), then run the estimate. Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/map-and-waypoints.html#kartenebenen",
    
    "relUrl": "/de-rDE/user/map-and-waypoints.html#kartenebenen"
  },"2252": {
    "doc": "Map & Waypoints",
    "title": "Position Sharing",
    "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. 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. To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/map-and-waypoints.html#position-sharing",
    
    "relUrl": "/de-rDE/user/map-and-waypoints.html#position-sharing"
  },"2253": {
    "doc": "Map & Waypoints",
    "title": "Map Sources",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | Knoten | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | Dunkel | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/map-and-waypoints.html#map-sources",
    
    "relUrl": "/de-rDE/user/map-and-waypoints.html#map-sources"
  },"2254": {
    "doc": "Map & Waypoints",
    "title": "Related Topics",
    "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | Units & Locale — distance and coordinate display formats | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/map-and-waypoints.html#related-topics",
    
    "relUrl": "/de-rDE/user/map-and-waypoints.html#related-topics"
  },"2255": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": " ",
    "url": "/Meshtastic-Android/main/de-rDE/user/map-and-waypoints.html",
    
    "relUrl": "/de-rDE/user/map-and-waypoints.html"
  },"2256": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": "The Map screen shows the geographic positions of nodes on your mesh, along with shared waypoints. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/map-and-waypoints.html#map--waypoints",
    
    "relUrl": "/ar-rSA/user/map-and-waypoints.html#map--waypoints"
  },"2257": {
    "doc": "Map & Waypoints",
    "title": "Map View",
    "content": "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 . Each node that reports a position is shown as a node chip marker displaying the node’s short name. The chip is colored by the node’s own identity color (a stable color derived from its node number) — the same chip used in the node list, so a node looks the same everywhere. Marker color does not encode online/offline status. When a node’s position updates live, its marker briefly pulses. Nearby markers are clustered as you zoom out. Map Controls . | Zoom — pinch or use +/- buttons | Pan — drag to explore | Center — tap the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/map-and-waypoints.html#map-view",
    
    "relUrl": "/ar-rSA/user/map-and-waypoints.html#map-view"
  },"2258": {
    "doc": "Map & Waypoints",
    "title": "Waypoints",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. Creating a Waypoint . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | Enter a name and optional description. | Choose an icon/emoji for the waypoint. | Tap Send to share with the mesh. | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. Waypoint Properties . | Property | الوصف | . | الاسم | Short identifier (max 29 characters) | . | الوصف | Optional longer description | . | Icon | Visual marker emoji on the map | . | مقفل | If locked, only the creator can edit or delete | . | Expiration | Optional auto-remove date and time | . | Geofence | Optional enter/exit alert area — see Waypoint Geofences | . Waypoint Expiration . Waypoints can be set to expire automatically: . | Never (default) — waypoint remains until manually deleted | Timed — pick a specific date and time; the waypoint is automatically removed once that time passes. 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 is based on the absolute time you picked, not a duration from when the waypoint was created or received. Waypoint Geofences . Any waypoint can also define a geofence — an alert area — so you or others get notified when a node enters or leaves it: . | Set a geofence radius from the preset chips (or Off to disable), or tap Set area on map to draw a custom rectangular area instead. | Once a region is set, toggle Notify on enter and/or Notify on exit. | Optionally enable Favorites only to limit alerts to your favorited nodes. | . Since waypoints (and their geofences) are broadcast to the whole mesh, only the creator is alerted by default. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. Managing Waypoints . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/map-and-waypoints.html#waypoints",
    
    "relUrl": "/ar-rSA/user/map-and-waypoints.html#waypoints"
  },"2259": {
    "doc": "Map & Waypoints",
    "title": "Map Layers",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Imported layers are listed with a toggle to show/hide each one and an option to remove it. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. Site Planner . Site Planner estimates RF coverage for a transmitter and draws it on the map as a color-coded overlay. Open it from a map control, or from a node’s detail page via Estimate coverage (shown only for nodes with a known position). Configure the transmitter (location, frequency, TX power, antenna gain and height), the receiver (sensitivity, height), and simulation options (max range, high-resolution terrain, color palette), then run the estimate. Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/map-and-waypoints.html#map-layers",
    
    "relUrl": "/ar-rSA/user/map-and-waypoints.html#map-layers"
  },"2260": {
    "doc": "Map & Waypoints",
    "title": "Position Sharing",
    "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. 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. To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/map-and-waypoints.html#position-sharing",
    
    "relUrl": "/ar-rSA/user/map-and-waypoints.html#position-sharing"
  },"2261": {
    "doc": "Map & Waypoints",
    "title": "Map Sources",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | Notes | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | Dark | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/map-and-waypoints.html#map-sources",
    
    "relUrl": "/ar-rSA/user/map-and-waypoints.html#map-sources"
  },"2262": {
    "doc": "Map & Waypoints",
    "title": "Related Topics",
    "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | Units & Locale — distance and coordinate display formats | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/map-and-waypoints.html#related-topics",
    
    "relUrl": "/ar-rSA/user/map-and-waypoints.html#related-topics"
  },"2263": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": " ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/map-and-waypoints.html",
    
    "relUrl": "/ar-rSA/user/map-and-waypoints.html"
  },"2264": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": "The Map screen shows the geographic positions of nodes on your mesh, along with shared waypoints. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/map-and-waypoints.html#map--waypoints",
    
    "relUrl": "/hr-rHR/user/map-and-waypoints.html#map--waypoints"
  },"2265": {
    "doc": "Map & Waypoints",
    "title": "Map View",
    "content": "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 . Each node that reports a position is shown as a node chip marker displaying the node’s short name. The chip is colored by the node’s own identity color (a stable color derived from its node number) — the same chip used in the node list, so a node looks the same everywhere. Marker color does not encode online/offline status. When a node’s position updates live, its marker briefly pulses. Nearby markers are clustered as you zoom out. Map Controls . | Zoom — pinch or use +/- buttons | Pan — drag to explore | Center — tap the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/map-and-waypoints.html#map-view",
    
    "relUrl": "/hr-rHR/user/map-and-waypoints.html#map-view"
  },"2266": {
    "doc": "Map & Waypoints",
    "title": "Waypoints",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. Creating a Waypoint . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | Enter a name and optional description. | Choose an icon/emoji for the waypoint. | Tap Send to share with the mesh. | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. Waypoint Properties . | Property | Opis | . | Ime | Short identifier (max 29 characters) | . | Opis | Optional longer description | . | Icon | Visual marker emoji on the map | . | Zaključano | If locked, only the creator can edit or delete | . | Expiration | Optional auto-remove date and time | . | Geofence | Optional enter/exit alert area — see Waypoint Geofences | . Waypoint Expiration . Waypoints can be set to expire automatically: . | Never (default) — waypoint remains until manually deleted | Timed — pick a specific date and time; the waypoint is automatically removed once that time passes. 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 is based on the absolute time you picked, not a duration from when the waypoint was created or received. Waypoint Geofences . Any waypoint can also define a geofence — an alert area — so you or others get notified when a node enters or leaves it: . | Set a geofence radius from the preset chips (or Off to disable), or tap Set area on map to draw a custom rectangular area instead. | Once a region is set, toggle Notify on enter and/or Notify on exit. | Optionally enable Favorites only to limit alerts to your favorited nodes. | . Since waypoints (and their geofences) are broadcast to the whole mesh, only the creator is alerted by default. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. Managing Waypoints . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/map-and-waypoints.html#waypoints",
    
    "relUrl": "/hr-rHR/user/map-and-waypoints.html#waypoints"
  },"2267": {
    "doc": "Map & Waypoints",
    "title": "Map Layers",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Imported layers are listed with a toggle to show/hide each one and an option to remove it. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. Site Planner . Site Planner estimates RF coverage for a transmitter and draws it on the map as a color-coded overlay. Open it from a map control, or from a node’s detail page via Estimate coverage (shown only for nodes with a known position). Configure the transmitter (location, frequency, TX power, antenna gain and height), the receiver (sensitivity, height), and simulation options (max range, high-resolution terrain, color palette), then run the estimate. Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/map-and-waypoints.html#map-layers",
    
    "relUrl": "/hr-rHR/user/map-and-waypoints.html#map-layers"
  },"2268": {
    "doc": "Map & Waypoints",
    "title": "Position Sharing",
    "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. 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. To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/map-and-waypoints.html#position-sharing",
    
    "relUrl": "/hr-rHR/user/map-and-waypoints.html#position-sharing"
  },"2269": {
    "doc": "Map & Waypoints",
    "title": "Map Sources",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | Notes | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | Tamna | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/map-and-waypoints.html#map-sources",
    
    "relUrl": "/hr-rHR/user/map-and-waypoints.html#map-sources"
  },"2270": {
    "doc": "Map & Waypoints",
    "title": "Related Topics",
    "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | Units & Locale — distance and coordinate display formats | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/map-and-waypoints.html#related-topics",
    
    "relUrl": "/hr-rHR/user/map-and-waypoints.html#related-topics"
  },"2271": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": " ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/map-and-waypoints.html",
    
    "relUrl": "/hr-rHR/user/map-and-waypoints.html"
  },"2272": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": "The Map screen shows the geographic positions of nodes on your mesh, along with shared waypoints. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/map-and-waypoints.html#map--waypoints",
    
    "relUrl": "/pt-rPT/user/map-and-waypoints.html#map--waypoints"
  },"2273": {
    "doc": "Map & Waypoints",
    "title": "Map View",
    "content": "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 . Each node that reports a position is shown as a node chip marker displaying the node’s short name. The chip is colored by the node’s own identity color (a stable color derived from its node number) — the same chip used in the node list, so a node looks the same everywhere. Marker color does not encode online/offline status. When a node’s position updates live, its marker briefly pulses. Nearby markers are clustered as you zoom out. Map Controls . | Zoom — pinch or use +/- buttons | Pan — drag to explore | Center — tap the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/map-and-waypoints.html#map-view",
    
    "relUrl": "/pt-rPT/user/map-and-waypoints.html#map-view"
  },"2274": {
    "doc": "Map & Waypoints",
    "title": "Waypoints",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. Creating a Waypoint . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | Enter a name and optional description. | Choose an icon/emoji for the waypoint. | Tap Send to share with the mesh. | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. Waypoint Properties . | Property | Descrição | . | Nome | Short identifier (max 29 characters) | . | Descrição | Optional longer description | . | Icon | Visual marker emoji on the map | . | Bloqueado | If locked, only the creator can edit or delete | . | Expiration | Optional auto-remove date and time | . | Geofence | Optional enter/exit alert area — see Waypoint Geofences | . Waypoint Expiration . Waypoints can be set to expire automatically: . | Never (default) — waypoint remains until manually deleted | Timed — pick a specific date and time; the waypoint is automatically removed once that time passes. 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 is based on the absolute time you picked, not a duration from when the waypoint was created or received. Waypoint Geofences . Any waypoint can also define a geofence — an alert area — so you or others get notified when a node enters or leaves it: . | Set a geofence radius from the preset chips (or Off to disable), or tap Set area on map to draw a custom rectangular area instead. | Once a region is set, toggle Notify on enter and/or Notify on exit. | Optionally enable Favorites only to limit alerts to your favorited nodes. | . Since waypoints (and their geofences) are broadcast to the whole mesh, only the creator is alerted by default. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. Managing Waypoints . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/map-and-waypoints.html#waypoints",
    
    "relUrl": "/pt-rPT/user/map-and-waypoints.html#waypoints"
  },"2275": {
    "doc": "Map & Waypoints",
    "title": "Map Layers",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Imported layers are listed with a toggle to show/hide each one and an option to remove it. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. Site Planner . Site Planner estimates RF coverage for a transmitter and draws it on the map as a color-coded overlay. Open it from a map control, or from a node’s detail page via Estimate coverage (shown only for nodes with a known position). Configure the transmitter (location, frequency, TX power, antenna gain and height), the receiver (sensitivity, height), and simulation options (max range, high-resolution terrain, color palette), then run the estimate. Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/map-and-waypoints.html#map-layers",
    
    "relUrl": "/pt-rPT/user/map-and-waypoints.html#map-layers"
  },"2276": {
    "doc": "Map & Waypoints",
    "title": "Position Sharing",
    "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. 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. To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/map-and-waypoints.html#position-sharing",
    
    "relUrl": "/pt-rPT/user/map-and-waypoints.html#position-sharing"
  },"2277": {
    "doc": "Map & Waypoints",
    "title": "Map Sources",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | Notes | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | Escuro | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/map-and-waypoints.html#map-sources",
    
    "relUrl": "/pt-rPT/user/map-and-waypoints.html#map-sources"
  },"2278": {
    "doc": "Map & Waypoints",
    "title": "Related Topics",
    "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | Units & Locale — distance and coordinate display formats | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/map-and-waypoints.html#related-topics",
    
    "relUrl": "/pt-rPT/user/map-and-waypoints.html#related-topics"
  },"2279": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": " ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/map-and-waypoints.html",
    
    "relUrl": "/pt-rPT/user/map-and-waypoints.html"
  },"2280": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": "The Map screen shows the geographic positions of nodes on your mesh, along with shared waypoints. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/map-and-waypoints.html#map--waypoints",
    
    "relUrl": "/pl-rPL/user/map-and-waypoints.html#map--waypoints"
  },"2281": {
    "doc": "Map & Waypoints",
    "title": "Map View",
    "content": "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 . Each node that reports a position is shown as a node chip marker displaying the node’s short name. The chip is colored by the node’s own identity color (a stable color derived from its node number) — the same chip used in the node list, so a node looks the same everywhere. Marker color does not encode online/offline status. When a node’s position updates live, its marker briefly pulses. Nearby markers are clustered as you zoom out. Map Controls . | Zoom — pinch or use +/- buttons | Pan — drag to explore | Center — tap the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/map-and-waypoints.html#map-view",
    
    "relUrl": "/pl-rPL/user/map-and-waypoints.html#map-view"
  },"2282": {
    "doc": "Map & Waypoints",
    "title": "Waypoints",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. Creating a Waypoint . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | Enter a name and optional description. | Choose an icon/emoji for the waypoint. | Tap Send to share with the mesh. | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. Waypoint Properties . | Property | Opis | . | Nazwa | Short identifier (max 29 characters) | . | Opis | Optional longer description | . | Icon | Visual marker emoji on the map | . | Zablokowany | If locked, only the creator can edit or delete | . | Expiration | Optional auto-remove date and time | . | Geofence | Optional enter/exit alert area — see Waypoint Geofences | . Waypoint Expiration . Waypoints can be set to expire automatically: . | Never (default) — waypoint remains until manually deleted | Timed — pick a specific date and time; the waypoint is automatically removed once that time passes. 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 is based on the absolute time you picked, not a duration from when the waypoint was created or received. Waypoint Geofences . Any waypoint can also define a geofence — an alert area — so you or others get notified when a node enters or leaves it: . | Set a geofence radius from the preset chips (or Off to disable), or tap Set area on map to draw a custom rectangular area instead. | Once a region is set, toggle Notify on enter and/or Notify on exit. | Optionally enable Favorites only to limit alerts to your favorited nodes. | . Since waypoints (and their geofences) are broadcast to the whole mesh, only the creator is alerted by default. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. Managing Waypoints . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/map-and-waypoints.html#waypoints",
    
    "relUrl": "/pl-rPL/user/map-and-waypoints.html#waypoints"
  },"2283": {
    "doc": "Map & Waypoints",
    "title": "Warstwy map",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Imported layers are listed with a toggle to show/hide each one and an option to remove it. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. Site Planner . Site Planner estimates RF coverage for a transmitter and draws it on the map as a color-coded overlay. Open it from a map control, or from a node’s detail page via Estimate coverage (shown only for nodes with a known position). Configure the transmitter (location, frequency, TX power, antenna gain and height), the receiver (sensitivity, height), and simulation options (max range, high-resolution terrain, color palette), then run the estimate. Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/map-and-waypoints.html#warstwy-map",
    
    "relUrl": "/pl-rPL/user/map-and-waypoints.html#warstwy-map"
  },"2284": {
    "doc": "Map & Waypoints",
    "title": "Position Sharing",
    "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. 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. To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/map-and-waypoints.html#position-sharing",
    
    "relUrl": "/pl-rPL/user/map-and-waypoints.html#position-sharing"
  },"2285": {
    "doc": "Map & Waypoints",
    "title": "Map Sources",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | Notatki | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | Ciemny | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/map-and-waypoints.html#map-sources",
    
    "relUrl": "/pl-rPL/user/map-and-waypoints.html#map-sources"
  },"2286": {
    "doc": "Map & Waypoints",
    "title": "Related Topics",
    "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | Units & Locale — distance and coordinate display formats | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/map-and-waypoints.html#related-topics",
    
    "relUrl": "/pl-rPL/user/map-and-waypoints.html#related-topics"
  },"2287": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": " ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/map-and-waypoints.html",
    
    "relUrl": "/pl-rPL/user/map-and-waypoints.html"
  },"2288": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": "The Map screen shows the geographic positions of nodes on your mesh, along with shared waypoints. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/map-and-waypoints.html#map--waypoints",
    
    "relUrl": "/zh-rCN/user/map-and-waypoints.html#map--waypoints"
  },"2289": {
    "doc": "Map & Waypoints",
    "title": "Map View",
    "content": "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 . Each node that reports a position is shown as a node chip marker displaying the node’s short name. The chip is colored by the node’s own identity color (a stable color derived from its node number) — the same chip used in the node list, so a node looks the same everywhere. Marker color does not encode online/offline status. When a node’s position updates live, its marker briefly pulses. Nearby markers are clustered as you zoom out. Map Controls . | Zoom — pinch or use +/- buttons | Pan — drag to explore | Center — tap the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/map-and-waypoints.html#map-view",
    
    "relUrl": "/zh-rCN/user/map-and-waypoints.html#map-view"
  },"2290": {
    "doc": "Map & Waypoints",
    "title": "Waypoints",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. Creating a Waypoint . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | Enter a name and optional description. | Choose an icon/emoji for the waypoint. | Tap Send to share with the mesh. | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. Waypoint Properties . | Property | 说明 | . | 名称 | Short identifier (max 29 characters) | . | 说明 | Optional longer description | . | 图标 | Visual marker emoji on the map | . | 锁定 | If locked, only the creator can edit or delete | . | Expiration | Optional auto-remove date and time | . | 地图围栏 | Optional enter/exit alert area — see Waypoint Geofences | . Waypoint Expiration . Waypoints can be set to expire automatically: . | Never (default) — waypoint remains until manually deleted | Timed — pick a specific date and time; the waypoint is automatically removed once that time passes. 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 is based on the absolute time you picked, not a duration from when the waypoint was created or received. Waypoint Geofences . Any waypoint can also define a geofence — an alert area — so you or others get notified when a node enters or leaves it: . | Set a geofence radius from the preset chips (or Off to disable), or tap Set area on map to draw a custom rectangular area instead. | Once a region is set, toggle Notify on enter and/or Notify on exit. | Optionally enable Favorites only to limit alerts to your favorited nodes. | . Since waypoints (and their geofences) are broadcast to the whole mesh, only the creator is alerted by default. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. Managing Waypoints . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/map-and-waypoints.html#waypoints",
    
    "relUrl": "/zh-rCN/user/map-and-waypoints.html#waypoints"
  },"2291": {
    "doc": "Map & Waypoints",
    "title": "地图图层",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Imported layers are listed with a toggle to show/hide each one and an option to remove it. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. Site Planner . Site Planner estimates RF coverage for a transmitter and draws it on the map as a color-coded overlay. Open it from a map control, or from a node’s detail page via Estimate coverage (shown only for nodes with a known position). Configure the transmitter (location, frequency, TX power, antenna gain and height), the receiver (sensitivity, height), and simulation options (max range, high-resolution terrain, color palette), then run the estimate. Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/map-and-waypoints.html#%E5%9C%B0%E5%9B%BE%E5%9B%BE%E5%B1%82",
    
    "relUrl": "/zh-rCN/user/map-and-waypoints.html#地图图层"
  },"2292": {
    "doc": "Map & Waypoints",
    "title": "Position Sharing",
    "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. 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. To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/map-and-waypoints.html#position-sharing",
    
    "relUrl": "/zh-rCN/user/map-and-waypoints.html#position-sharing"
  },"2293": {
    "doc": "Map & Waypoints",
    "title": "Map Sources",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | 注 | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | 深色 | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/map-and-waypoints.html#map-sources",
    
    "relUrl": "/zh-rCN/user/map-and-waypoints.html#map-sources"
  },"2294": {
    "doc": "Map & Waypoints",
    "title": "Related Topics",
    "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | Units & Locale — distance and coordinate display formats | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/map-and-waypoints.html#related-topics",
    
    "relUrl": "/zh-rCN/user/map-and-waypoints.html#related-topics"
  },"2295": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": " ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/map-and-waypoints.html",
    
    "relUrl": "/zh-rCN/user/map-and-waypoints.html"
  },"2296": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": "The Map screen shows the geographic positions of nodes on your mesh, along with shared waypoints. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/map-and-waypoints.html#map--waypoints",
    
    "relUrl": "/sq-rAL/user/map-and-waypoints.html#map--waypoints"
  },"2297": {
    "doc": "Map & Waypoints",
    "title": "Map View",
    "content": "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 . Each node that reports a position is shown as a node chip marker displaying the node’s short name. The chip is colored by the node’s own identity color (a stable color derived from its node number) — the same chip used in the node list, so a node looks the same everywhere. Marker color does not encode online/offline status. When a node’s position updates live, its marker briefly pulses. Nearby markers are clustered as you zoom out. Map Controls . | Zoom — pinch or use +/- buttons | Pan — drag to explore | Center — tap the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/map-and-waypoints.html#map-view",
    
    "relUrl": "/sq-rAL/user/map-and-waypoints.html#map-view"
  },"2298": {
    "doc": "Map & Waypoints",
    "title": "Waypoints",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. Creating a Waypoint . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | Enter a name and optional description. | Choose an icon/emoji for the waypoint. | Tap Send to share with the mesh. | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. Waypoint Properties . | Property | Përshkrimi | . | Emri | Short identifier (max 29 characters) | . | Përshkrimi | Optional longer description | . | Icon | Visual marker emoji on the map | . | I bllokuar | If locked, only the creator can edit or delete | . | Expiration | Optional auto-remove date and time | . | Geofence | Optional enter/exit alert area — see Waypoint Geofences | . Waypoint Expiration . Waypoints can be set to expire automatically: . | Never (default) — waypoint remains until manually deleted | Timed — pick a specific date and time; the waypoint is automatically removed once that time passes. 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 is based on the absolute time you picked, not a duration from when the waypoint was created or received. Waypoint Geofences . Any waypoint can also define a geofence — an alert area — so you or others get notified when a node enters or leaves it: . | Set a geofence radius from the preset chips (or Off to disable), or tap Set area on map to draw a custom rectangular area instead. | Once a region is set, toggle Notify on enter and/or Notify on exit. | Optionally enable Favorites only to limit alerts to your favorited nodes. | . Since waypoints (and their geofences) are broadcast to the whole mesh, only the creator is alerted by default. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. Managing Waypoints . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/map-and-waypoints.html#waypoints",
    
    "relUrl": "/sq-rAL/user/map-and-waypoints.html#waypoints"
  },"2299": {
    "doc": "Map & Waypoints",
    "title": "Map Layers",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Imported layers are listed with a toggle to show/hide each one and an option to remove it. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. Site Planner . Site Planner estimates RF coverage for a transmitter and draws it on the map as a color-coded overlay. Open it from a map control, or from a node’s detail page via Estimate coverage (shown only for nodes with a known position). Configure the transmitter (location, frequency, TX power, antenna gain and height), the receiver (sensitivity, height), and simulation options (max range, high-resolution terrain, color palette), then run the estimate. Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/map-and-waypoints.html#map-layers",
    
    "relUrl": "/sq-rAL/user/map-and-waypoints.html#map-layers"
  },"2300": {
    "doc": "Map & Waypoints",
    "title": "Position Sharing",
    "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. 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. To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/map-and-waypoints.html#position-sharing",
    
    "relUrl": "/sq-rAL/user/map-and-waypoints.html#position-sharing"
  },"2301": {
    "doc": "Map & Waypoints",
    "title": "Map Sources",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | Notes | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | Errësirë | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/map-and-waypoints.html#map-sources",
    
    "relUrl": "/sq-rAL/user/map-and-waypoints.html#map-sources"
  },"2302": {
    "doc": "Map & Waypoints",
    "title": "Related Topics",
    "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | Units & Locale — distance and coordinate display formats | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/map-and-waypoints.html#related-topics",
    
    "relUrl": "/sq-rAL/user/map-and-waypoints.html#related-topics"
  },"2303": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": " ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/map-and-waypoints.html",
    
    "relUrl": "/sq-rAL/user/map-and-waypoints.html"
  },"2304": {
    "doc": "地圖與航點",
    "title": "地圖與航點",
    "content": "地圖畫面顯示 mesh 網路上各節點的地理位置，以及已分享的航點。 . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/map-and-waypoints.html",
    
    "relUrl": "/zh-rTW/user/map-and-waypoints.html"
  },"2305": {
    "doc": "地圖與航點",
    "title": "地圖檢視",
    "content": "地圖顯示以下內容： . | 節點位置 — 每個回報位置的節點以彩色標記顯示 | 航點 — 已分享的興趣點 | 您的位置 — 您目前的 GPS 定位 | . 節點標記 . Each node that reports a position is shown as a node chip marker displaying the node’s short name. The chip is colored by the node’s own identity color (a stable color derived from its node number) — the same chip used in the node list, so a node looks the same everywhere. Marker color does not encode online/offline status. When a node’s position updates live, its marker briefly pulses. Nearby markers are clustered as you zoom out. 地圖控制項 . | 縮放 — 雙指縮放或使用 +/- 按鈕 | 平移 — 拖曳以瀏覽地圖 | Center — tap the location button to center on your position | 點選節點 — 點選節點標記以檢視詳細資訊 | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. 點選羅盤可重新對齊正北方向，或點選位置按鈕使地圖以您目前位置為中心。 On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/map-and-waypoints.html#%E5%9C%B0%E5%9C%96%E6%AA%A2%E8%A6%96",
    
    "relUrl": "/zh-rTW/user/map-and-waypoints.html#地圖檢視"
  },"2306": {
    "doc": "地圖與航點",
    "title": "航點",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. 建立航點 . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | 輸入名稱及選填的說明。 | 為航點選擇圖示或表情符號。 | 點選「傳送」以分享至 mesh 網路。 | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. 航點屬性 . | 屬性 | 描述說明 | . | 名稱 | Short identifier (max 29 characters) | . | 描述說明 | 選填的較長說明 | . | 圖示 | 地圖上的視覺標記表情符號 | . | 鎖定 | 若已鎖定，僅建立者可編輯或刪除 | . | 到期時間 | Optional auto-remove date and time | . | Geofence | Optional enter/exit alert area — see Waypoint Geofences | . 航點到期設定 . 航點可設定為自動到期： . | 永不到期（預設）— 航點將保留至手動刪除為止 | Timed — pick a specific date and time; the waypoint is automatically removed once that time passes. 適用於臨時標記，例如集合點、危險區域或會面地點。 | . 已到期的航點將自動從地圖上隱藏，以避免畫面雜亂。 The expiration countdown is based on the absolute time you picked, not a duration from when the waypoint was created or received. Waypoint Geofences . Any waypoint can also define a geofence — an alert area — so you or others get notified when a node enters or leaves it: . | Set a geofence radius from the preset chips (or Off to disable), or tap Set area on map to draw a custom rectangular area instead. | Once a region is set, toggle Notify on enter and/or Notify on exit. | Optionally enable Favorites only to limit alerts to your favorited nodes. | . Since waypoints (and their geofences) are broadcast to the whole mesh, only the creator is alerted by default. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. 管理航點 . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/map-and-waypoints.html#%E8%88%AA%E9%BB%9E",
    
    "relUrl": "/zh-rTW/user/map-and-waypoints.html#航點"
  },"2307": {
    "doc": "地圖與航點",
    "title": "地圖圖層",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Imported layers are listed with a toggle to show/hide each one and an option to remove it. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. Site Planner . Site Planner estimates RF coverage for a transmitter and draws it on the map as a color-coded overlay. Open it from a map control, or from a node’s detail page via Estimate coverage (shown only for nodes with a known position). Configure the transmitter (location, frequency, TX power, antenna gain and height), the receiver (sensitivity, height), and simulation options (max range, high-resolution terrain, color palette), then run the estimate. Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/map-and-waypoints.html#%E5%9C%B0%E5%9C%96%E5%9C%96%E5%B1%A4",
    
    "relUrl": "/zh-rTW/user/map-and-waypoints.html#地圖圖層"
  },"2308": {
    "doc": "地圖與航點",
    "title": "位置分享",
    "content": "啟用位置分享 . 您的節點依據以下方式分享 GPS 位置： . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. 隱私注意事項 . 🔒 隱私：位置資料將廣播至您頻道上的所有節點。若不想分享您的位置，請在設定中停用 GPS 定位，或使用固定／假位置。 To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/map-and-waypoints.html#%E4%BD%8D%E7%BD%AE%E5%88%86%E4%BA%AB",
    
    "relUrl": "/zh-rTW/user/map-and-waypoints.html#位置分享"
  },"2309": {
    "doc": "地圖與航點",
    "title": "地圖來源",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | 備註 | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | 深色 | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/map-and-waypoints.html#%E5%9C%B0%E5%9C%96%E4%BE%86%E6%BA%90",
    
    "relUrl": "/zh-rTW/user/map-and-waypoints.html#地圖來源"
  },"2310": {
    "doc": "地圖與航點",
    "title": "相關主題",
    "content": ". | 〔節點〕(nodes) — 檢視與篩選您的節點清單 | 〔節點數據〕(node-metrics) — 各節點的訊號品質與位置歷史記錄 | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | 〔單位與地區設定〕(units-and-locale) — 距離與座標的顯示格式 | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/map-and-waypoints.html#%E7%9B%B8%E9%97%9C%E4%B8%BB%E9%A1%8C",
    
    "relUrl": "/zh-rTW/user/map-and-waypoints.html#相關主題"
  },"2311": {
    "doc": "Kaart ja teekonnapunktid",
    "title": "Kaart ja teekonnapunktid",
    "content": "Kaardiekraan näitab kärgvõrgu sõlmede geograafilisi asukohti koos jagatud teekonnapunktidega. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/map-and-waypoints.html",
    
    "relUrl": "/et-rEE/user/map-and-waypoints.html"
  },"2312": {
    "doc": "Kaart ja teekonnapunktid",
    "title": "Kaardi vaade",
    "content": "Kaardil kuvatakse: . | Sõlmede asukohad — värvilised markerid iga sõlme asukoha kohta | Waypoints — shared points of interest | Teie asukoht — teie praegune GPS asukoht | . Node Markers . Iga asukohta teavitav sõlm kuvatakse sõlme kiibi markerina, mis kuvab sõlme lühinime. Kiip on värvitud sõlme enda identiteedivärviga (stabiilne värv, mis on tuletatud sõlme numbrist) – sama kiip, mida kasutatakse sõlmede loendis, seega näeb sõlm kõikjal ühesugune välja. Markeri värv ei kodeeri võrguühenduseta/võrguühenduseta olekut. Kui sõlme asukoht reaalajas uueneb, pulseerib selle marker lühidalt. Nearby markers are clustered as you zoom out. Kaardi juhtnupud . | Suumi – näpista või +/- nuppude kasutamine | Pan — drag to explore | Center — tap the location button to center on your position | Sõlme puudutamine – üksikasjade kuvamiseks puuduta sõlmel | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. Põhjasuuna muutmiseks puuduta kompassi või praeguse asukoha keskpunkti seadmiseks asukohanuppu. On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/map-and-waypoints.html#kaardi-vaade",
    
    "relUrl": "/et-rEE/user/map-and-waypoints.html#kaardi-vaade"
  },"2313": {
    "doc": "Kaart ja teekonnapunktid",
    "title": "Teekonnapunkt",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. Loo teekonnapunkt . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | Sisestage nimi ja valikuline kirjeldus. | Vali teekonnapunktile ikoon/emoji. | Puuduta Saada jagamiseks kärgvõrku. | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. Waypoint Properties . | Property | Kirjeldus | . | Nimi | Lühike identifikaator (max 29 tähemärki) | . | Kirjeldus | Optional longer description | . | Ikoon | Visuaalse markeri emotikon kaardil | . | Lukustatud | If locked, only the creator can edit or delete | . | Expiration | Optional auto-remove date and time | . | Geopiire | Optional enter/exit alert area — see Waypoint Geofences | . Waypoint Expiration . Waypoints can be set to expire automatically: . | Never (default) — waypoint remains until manually deleted | Timed — pick a specific date and time; the waypoint is automatically removed once that time passes. Kasulik ajutiste märkide, näiteks kogunemispunktide, ohtude või kohtumispaikade jaoks. | . Aegunud teekonnapunktid peidetakse kaardilt automaatselt, et need ekraani ei risustaks. The expiration countdown is based on the absolute time you picked, not a duration from when the waypoint was created or received. Teekonnapunktide geopiirded . Iga teekonnapunkt saab määratleda ka geopiirde – hoiatusala –, et teid või teisi teavitataks, kui sõlm sinna siseneb või sealt lahkub: . | Määra geopiirde raadius eelmääratletud kiipide hulgast (või keelamiseks Väljas) või puuduta kohandatud ristkülikukujulise ala joonistamiseks Määra kaardile ala. | Kui piirkond on määratud, lülita sisse Teavita sisenemisel ja/või Teavita väljumisel. | Soovi korral luba Ainult lemmikud, et piirata märguandeid oma lemmiksõlmedega. | . Kuna teekonnapunktid (ja nende geopiirded) edastatakse kogu kärgvõrgule, teavitatakse vaikimisi ainult loojat. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. Managing Waypoints . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/map-and-waypoints.html#teekonnapunkt",
    
    "relUrl": "/et-rEE/user/map-and-waypoints.html#teekonnapunkt"
  },"2314": {
    "doc": "Kaart ja teekonnapunktid",
    "title": "Kaardikihid",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Imporditud kihid on loetletud koos lülitiga iga kihi kuvamiseks/peitmiseks ja valikuga selle eemaldamiseks. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. Saidi planeerija . Asukoha planeerija hindab saatja raadiosageduslikku leviala ja joonistab selle kaardile värvikoodiga kihina. Ava see kaardihalduselemendist või sõlme detaillehelt valiku Hinnatud katvus kaudu (kuvatakse ainult teadaoleva asukohaga sõlmede puhul). Konfi saatja (asukoht, sagedus, saatja võimsus, antenni võimendus ja kõrgus), vastuvõtja (tundlikkus, kõrgus) ja simulatsioonivalikud (maksimaalne ulatus, kõrge eraldusvõimega maastik, värvipalett) ning seejärel käivita hinnang. Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/map-and-waypoints.html#kaardikihid",
    
    "relUrl": "/et-rEE/user/map-and-waypoints.html#kaardikihid"
  },"2315": {
    "doc": "Kaart ja teekonnapunktid",
    "title": "Position Sharing",
    "content": "Enabling Position Sharing . Sõlm jagab oma GPS asukohta järgmise alusel: . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. Privacy Considerations . 🔒 Privaatsus: asukoha andmed levitatakse kõigile sinu kanali sõlmedele. Kui sa ei soovi, et sinu asukohta jagataks, keela GPS asukohta seadetes või kasuta fikseeritud/võltsasukohta. To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/map-and-waypoints.html#position-sharing",
    
    "relUrl": "/et-rEE/user/map-and-waypoints.html#position-sharing"
  },"2316": {
    "doc": "Kaart ja teekonnapunktid",
    "title": "Kaardi allikad",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | Sõnumid | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | Tume | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/map-and-waypoints.html#kaardi-allikad",
    
    "relUrl": "/et-rEE/user/map-and-waypoints.html#kaardi-allikad"
  },"2317": {
    "doc": "Kaart ja teekonnapunktid",
    "title": "Seotud teemad",
    "content": ". | Sõlmed — vaata ja filtreeri oma sõlmede loendit | Node Metrics — signal quality and position history for individual nodes | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | Ühikud ja lokaat — kauguse ja koordinaatide kuvamise ühikud | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/map-and-waypoints.html#seotud-teemad",
    
    "relUrl": "/et-rEE/user/map-and-waypoints.html#seotud-teemad"
  },"2318": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": "The Map screen shows the geographic positions of nodes on your mesh, along with shared waypoints. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/map-and-waypoints.html#map--waypoints",
    
    "relUrl": "/fr-rFR/user/map-and-waypoints.html#map--waypoints"
  },"2319": {
    "doc": "Map & Waypoints",
    "title": "Map View",
    "content": "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 . Each node that reports a position is shown as a node chip marker displaying the node’s short name. The chip is colored by the node’s own identity color (a stable color derived from its node number) — the same chip used in the node list, so a node looks the same everywhere. Marker color does not encode online/offline status. When a node’s position updates live, its marker briefly pulses. Nearby markers are clustered as you zoom out. Map Controls . | Zoom — pinch or use +/- buttons | Pan — drag to explore | Center — tap the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/map-and-waypoints.html#map-view",
    
    "relUrl": "/fr-rFR/user/map-and-waypoints.html#map-view"
  },"2320": {
    "doc": "Map & Waypoints",
    "title": "Waypoints",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. Creating a Waypoint . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | Enter a name and optional description. | Choose an icon/emoji for the waypoint. | Tap Send to share with the mesh. | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. Waypoint Properties . | Property | Description | . | Nom | Short identifier (max 29 characters) | . | Description | Optional longer description | . | Icon | Visual marker emoji on the map | . | Verrouillé | If locked, only the creator can edit or delete | . | Expiration | Optional auto-remove date and time | . | Geofence | Optional enter/exit alert area — see Waypoint Geofences | . Waypoint Expiration . Waypoints can be set to expire automatically: . | Never (default) — waypoint remains until manually deleted | Timed — pick a specific date and time; the waypoint is automatically removed once that time passes. 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 is based on the absolute time you picked, not a duration from when the waypoint was created or received. Waypoint Geofences . Any waypoint can also define a geofence — an alert area — so you or others get notified when a node enters or leaves it: . | Set a geofence radius from the preset chips (or Off to disable), or tap Set area on map to draw a custom rectangular area instead. | Once a region is set, toggle Notify on enter and/or Notify on exit. | Optionally enable Favorites only to limit alerts to your favorited nodes. | . Since waypoints (and their geofences) are broadcast to the whole mesh, only the creator is alerted by default. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. Managing Waypoints . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/map-and-waypoints.html#waypoints",
    
    "relUrl": "/fr-rFR/user/map-and-waypoints.html#waypoints"
  },"2321": {
    "doc": "Map & Waypoints",
    "title": "Couches cartographiques",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Imported layers are listed with a toggle to show/hide each one and an option to remove it. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. Site Planner . Site Planner estimates RF coverage for a transmitter and draws it on the map as a color-coded overlay. Open it from a map control, or from a node’s detail page via Estimate coverage (shown only for nodes with a known position). Configure the transmitter (location, frequency, TX power, antenna gain and height), the receiver (sensitivity, height), and simulation options (max range, high-resolution terrain, color palette), then run the estimate. Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/map-and-waypoints.html#couches-cartographiques",
    
    "relUrl": "/fr-rFR/user/map-and-waypoints.html#couches-cartographiques"
  },"2322": {
    "doc": "Map & Waypoints",
    "title": "Position Sharing",
    "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. 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. To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/map-and-waypoints.html#position-sharing",
    
    "relUrl": "/fr-rFR/user/map-and-waypoints.html#position-sharing"
  },"2323": {
    "doc": "Map & Waypoints",
    "title": "Map Sources",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | Notes | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | Sombre | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/map-and-waypoints.html#map-sources",
    
    "relUrl": "/fr-rFR/user/map-and-waypoints.html#map-sources"
  },"2324": {
    "doc": "Map & Waypoints",
    "title": "Related Topics",
    "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | Units & Locale — distance and coordinate display formats | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/map-and-waypoints.html#related-topics",
    
    "relUrl": "/fr-rFR/user/map-and-waypoints.html#related-topics"
  },"2325": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": " ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/map-and-waypoints.html",
    
    "relUrl": "/fr-rFR/user/map-and-waypoints.html"
  },"2326": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": "The Map screen shows the geographic positions of nodes on your mesh, along with shared waypoints. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/map-and-waypoints.html#map--waypoints",
    
    "relUrl": "/tr-rTR/user/map-and-waypoints.html#map--waypoints"
  },"2327": {
    "doc": "Map & Waypoints",
    "title": "Map View",
    "content": "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 . Each node that reports a position is shown as a node chip marker displaying the node’s short name. The chip is colored by the node’s own identity color (a stable color derived from its node number) — the same chip used in the node list, so a node looks the same everywhere. Marker color does not encode online/offline status. When a node’s position updates live, its marker briefly pulses. Nearby markers are clustered as you zoom out. Map Controls . | Zoom — pinch or use +/- buttons | Pan — drag to explore | Center — tap the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/map-and-waypoints.html#map-view",
    
    "relUrl": "/tr-rTR/user/map-and-waypoints.html#map-view"
  },"2328": {
    "doc": "Map & Waypoints",
    "title": "Waypoints",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. Creating a Waypoint . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | Enter a name and optional description. | Choose an icon/emoji for the waypoint. | Tap Send to share with the mesh. | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. Waypoint Properties . | Property | Açıklaması | . | İsmi | Short identifier (max 29 characters) | . | Açıklaması | Optional longer description | . | Icon | Visual marker emoji on the map | . | Kilitli | If locked, only the creator can edit or delete | . | Expiration | Optional auto-remove date and time | . | Geofence | Optional enter/exit alert area — see Waypoint Geofences | . Waypoint Expiration . Waypoints can be set to expire automatically: . | Never (default) — waypoint remains until manually deleted | Timed — pick a specific date and time; the waypoint is automatically removed once that time passes. 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 is based on the absolute time you picked, not a duration from when the waypoint was created or received. Waypoint Geofences . Any waypoint can also define a geofence — an alert area — so you or others get notified when a node enters or leaves it: . | Set a geofence radius from the preset chips (or Off to disable), or tap Set area on map to draw a custom rectangular area instead. | Once a region is set, toggle Notify on enter and/or Notify on exit. | Optionally enable Favorites only to limit alerts to your favorited nodes. | . Since waypoints (and their geofences) are broadcast to the whole mesh, only the creator is alerted by default. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. Managing Waypoints . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/map-and-waypoints.html#waypoints",
    
    "relUrl": "/tr-rTR/user/map-and-waypoints.html#waypoints"
  },"2329": {
    "doc": "Map & Waypoints",
    "title": "Map Layers",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Imported layers are listed with a toggle to show/hide each one and an option to remove it. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. Site Planner . Site Planner estimates RF coverage for a transmitter and draws it on the map as a color-coded overlay. Open it from a map control, or from a node’s detail page via Estimate coverage (shown only for nodes with a known position). Configure the transmitter (location, frequency, TX power, antenna gain and height), the receiver (sensitivity, height), and simulation options (max range, high-resolution terrain, color palette), then run the estimate. Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/map-and-waypoints.html#map-layers",
    
    "relUrl": "/tr-rTR/user/map-and-waypoints.html#map-layers"
  },"2330": {
    "doc": "Map & Waypoints",
    "title": "Position Sharing",
    "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. 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. To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/map-and-waypoints.html#position-sharing",
    
    "relUrl": "/tr-rTR/user/map-and-waypoints.html#position-sharing"
  },"2331": {
    "doc": "Map & Waypoints",
    "title": "Map Sources",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | Notes | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | Koyu | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/map-and-waypoints.html#map-sources",
    
    "relUrl": "/tr-rTR/user/map-and-waypoints.html#map-sources"
  },"2332": {
    "doc": "Map & Waypoints",
    "title": "Related Topics",
    "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | Units & Locale — distance and coordinate display formats | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/map-and-waypoints.html#related-topics",
    
    "relUrl": "/tr-rTR/user/map-and-waypoints.html#related-topics"
  },"2333": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": " ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/map-and-waypoints.html",
    
    "relUrl": "/tr-rTR/user/map-and-waypoints.html"
  },"2334": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": "The Map screen shows the geographic positions of nodes on your mesh, along with shared waypoints. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/map-and-waypoints.html#map--waypoints",
    
    "relUrl": "/el-rGR/user/map-and-waypoints.html#map--waypoints"
  },"2335": {
    "doc": "Map & Waypoints",
    "title": "Map View",
    "content": "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 . Each node that reports a position is shown as a node chip marker displaying the node’s short name. The chip is colored by the node’s own identity color (a stable color derived from its node number) — the same chip used in the node list, so a node looks the same everywhere. Marker color does not encode online/offline status. When a node’s position updates live, its marker briefly pulses. Nearby markers are clustered as you zoom out. Map Controls . | Zoom — pinch or use +/- buttons | Pan — drag to explore | Center — tap the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/map-and-waypoints.html#map-view",
    
    "relUrl": "/el-rGR/user/map-and-waypoints.html#map-view"
  },"2336": {
    "doc": "Map & Waypoints",
    "title": "Waypoints",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. Creating a Waypoint . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | Enter a name and optional description. | Choose an icon/emoji for the waypoint. | Tap Send to share with the mesh. | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. Waypoint Properties . | Property | Περιγραφή | . | Ονομα | Short identifier (max 29 characters) | . | Περιγραφή | Optional longer description | . | Icon | Visual marker emoji on the map | . | Κλειδωμένο | If locked, only the creator can edit or delete | . | Expiration | Optional auto-remove date and time | . | Geofence | Optional enter/exit alert area — see Waypoint Geofences | . Waypoint Expiration . Waypoints can be set to expire automatically: . | Never (default) — waypoint remains until manually deleted | Timed — pick a specific date and time; the waypoint is automatically removed once that time passes. 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 is based on the absolute time you picked, not a duration from when the waypoint was created or received. Waypoint Geofences . Any waypoint can also define a geofence — an alert area — so you or others get notified when a node enters or leaves it: . | Set a geofence radius from the preset chips (or Off to disable), or tap Set area on map to draw a custom rectangular area instead. | Once a region is set, toggle Notify on enter and/or Notify on exit. | Optionally enable Favorites only to limit alerts to your favorited nodes. | . Since waypoints (and their geofences) are broadcast to the whole mesh, only the creator is alerted by default. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. Managing Waypoints . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/map-and-waypoints.html#waypoints",
    
    "relUrl": "/el-rGR/user/map-and-waypoints.html#waypoints"
  },"2337": {
    "doc": "Map & Waypoints",
    "title": "Map Layers",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Imported layers are listed with a toggle to show/hide each one and an option to remove it. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. Site Planner . Site Planner estimates RF coverage for a transmitter and draws it on the map as a color-coded overlay. Open it from a map control, or from a node’s detail page via Estimate coverage (shown only for nodes with a known position). Configure the transmitter (location, frequency, TX power, antenna gain and height), the receiver (sensitivity, height), and simulation options (max range, high-resolution terrain, color palette), then run the estimate. Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/map-and-waypoints.html#map-layers",
    
    "relUrl": "/el-rGR/user/map-and-waypoints.html#map-layers"
  },"2338": {
    "doc": "Map & Waypoints",
    "title": "Position Sharing",
    "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. 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. To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/map-and-waypoints.html#position-sharing",
    
    "relUrl": "/el-rGR/user/map-and-waypoints.html#position-sharing"
  },"2339": {
    "doc": "Map & Waypoints",
    "title": "Map Sources",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | Notes | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | Σκούρο | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/map-and-waypoints.html#map-sources",
    
    "relUrl": "/el-rGR/user/map-and-waypoints.html#map-sources"
  },"2340": {
    "doc": "Map & Waypoints",
    "title": "Related Topics",
    "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | Units & Locale — distance and coordinate display formats | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/map-and-waypoints.html#related-topics",
    
    "relUrl": "/el-rGR/user/map-and-waypoints.html#related-topics"
  },"2341": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": " ",
    "url": "/Meshtastic-Android/main/el-rGR/user/map-and-waypoints.html",
    
    "relUrl": "/el-rGR/user/map-and-waypoints.html"
  },"2342": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": "The Map screen shows the geographic positions of nodes on your mesh, along with shared waypoints. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/map-and-waypoints.html#map--waypoints",
    
    "relUrl": "/ro-rRO/user/map-and-waypoints.html#map--waypoints"
  },"2343": {
    "doc": "Map & Waypoints",
    "title": "Map View",
    "content": "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 . Each node that reports a position is shown as a node chip marker displaying the node’s short name. The chip is colored by the node’s own identity color (a stable color derived from its node number) — the same chip used in the node list, so a node looks the same everywhere. Marker color does not encode online/offline status. When a node’s position updates live, its marker briefly pulses. Nearby markers are clustered as you zoom out. Map Controls . | Zoom — pinch or use +/- buttons | Pan — drag to explore | Center — tap the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/map-and-waypoints.html#map-view",
    
    "relUrl": "/ro-rRO/user/map-and-waypoints.html#map-view"
  },"2344": {
    "doc": "Map & Waypoints",
    "title": "Waypoints",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. Creating a Waypoint . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | Enter a name and optional description. | Choose an icon/emoji for the waypoint. | Tap Send to share with the mesh. | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. Waypoint Properties . | Property | Descriere | . | Nume | Short identifier (max 29 characters) | . | Descriere | Optional longer description | . | Icon | Visual marker emoji on the map | . | Blocat | If locked, only the creator can edit or delete | . | Expiration | Optional auto-remove date and time | . | Geofence | Optional enter/exit alert area — see Waypoint Geofences | . Waypoint Expiration . Waypoints can be set to expire automatically: . | Never (default) — waypoint remains until manually deleted | Timed — pick a specific date and time; the waypoint is automatically removed once that time passes. 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 is based on the absolute time you picked, not a duration from when the waypoint was created or received. Waypoint Geofences . Any waypoint can also define a geofence — an alert area — so you or others get notified when a node enters or leaves it: . | Set a geofence radius from the preset chips (or Off to disable), or tap Set area on map to draw a custom rectangular area instead. | Once a region is set, toggle Notify on enter and/or Notify on exit. | Optionally enable Favorites only to limit alerts to your favorited nodes. | . Since waypoints (and their geofences) are broadcast to the whole mesh, only the creator is alerted by default. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. Managing Waypoints . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/map-and-waypoints.html#waypoints",
    
    "relUrl": "/ro-rRO/user/map-and-waypoints.html#waypoints"
  },"2345": {
    "doc": "Map & Waypoints",
    "title": "Map Layers",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Imported layers are listed with a toggle to show/hide each one and an option to remove it. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. Site Planner . Site Planner estimates RF coverage for a transmitter and draws it on the map as a color-coded overlay. Open it from a map control, or from a node’s detail page via Estimate coverage (shown only for nodes with a known position). Configure the transmitter (location, frequency, TX power, antenna gain and height), the receiver (sensitivity, height), and simulation options (max range, high-resolution terrain, color palette), then run the estimate. Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/map-and-waypoints.html#map-layers",
    
    "relUrl": "/ro-rRO/user/map-and-waypoints.html#map-layers"
  },"2346": {
    "doc": "Map & Waypoints",
    "title": "Position Sharing",
    "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. 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. To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/map-and-waypoints.html#position-sharing",
    
    "relUrl": "/ro-rRO/user/map-and-waypoints.html#position-sharing"
  },"2347": {
    "doc": "Map & Waypoints",
    "title": "Map Sources",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | Notițe | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | Întunecat | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/map-and-waypoints.html#map-sources",
    
    "relUrl": "/ro-rRO/user/map-and-waypoints.html#map-sources"
  },"2348": {
    "doc": "Map & Waypoints",
    "title": "Related Topics",
    "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | Units & Locale — distance and coordinate display formats | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/map-and-waypoints.html#related-topics",
    
    "relUrl": "/ro-rRO/user/map-and-waypoints.html#related-topics"
  },"2349": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": " ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/map-and-waypoints.html",
    
    "relUrl": "/ro-rRO/user/map-and-waypoints.html"
  },"2350": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": "The Map screen shows the geographic positions of nodes on your mesh, along with shared waypoints. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/map-and-waypoints.html#map--waypoints",
    
    "relUrl": "/iw-rIL/user/map-and-waypoints.html#map--waypoints"
  },"2351": {
    "doc": "Map & Waypoints",
    "title": "Map View",
    "content": "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 . Each node that reports a position is shown as a node chip marker displaying the node’s short name. The chip is colored by the node’s own identity color (a stable color derived from its node number) — the same chip used in the node list, so a node looks the same everywhere. Marker color does not encode online/offline status. When a node’s position updates live, its marker briefly pulses. Nearby markers are clustered as you zoom out. Map Controls . | Zoom — pinch or use +/- buttons | Pan — drag to explore | Center — tap the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/map-and-waypoints.html#map-view",
    
    "relUrl": "/iw-rIL/user/map-and-waypoints.html#map-view"
  },"2352": {
    "doc": "Map & Waypoints",
    "title": "Waypoints",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. Creating a Waypoint . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | Enter a name and optional description. | Choose an icon/emoji for the waypoint. | Tap Send to share with the mesh. | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. Waypoint Properties . | Property | תיאור | . | שם | Short identifier (max 29 characters) | . | תיאור | Optional longer description | . | Icon | Visual marker emoji on the map | . | נעול | If locked, only the creator can edit or delete | . | Expiration | Optional auto-remove date and time | . | Geofence | Optional enter/exit alert area — see Waypoint Geofences | . Waypoint Expiration . Waypoints can be set to expire automatically: . | Never (default) — waypoint remains until manually deleted | Timed — pick a specific date and time; the waypoint is automatically removed once that time passes. 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 is based on the absolute time you picked, not a duration from when the waypoint was created or received. Waypoint Geofences . Any waypoint can also define a geofence — an alert area — so you or others get notified when a node enters or leaves it: . | Set a geofence radius from the preset chips (or Off to disable), or tap Set area on map to draw a custom rectangular area instead. | Once a region is set, toggle Notify on enter and/or Notify on exit. | Optionally enable Favorites only to limit alerts to your favorited nodes. | . Since waypoints (and their geofences) are broadcast to the whole mesh, only the creator is alerted by default. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. Managing Waypoints . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/map-and-waypoints.html#waypoints",
    
    "relUrl": "/iw-rIL/user/map-and-waypoints.html#waypoints"
  },"2353": {
    "doc": "Map & Waypoints",
    "title": "Map Layers",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Imported layers are listed with a toggle to show/hide each one and an option to remove it. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. Site Planner . Site Planner estimates RF coverage for a transmitter and draws it on the map as a color-coded overlay. Open it from a map control, or from a node’s detail page via Estimate coverage (shown only for nodes with a known position). Configure the transmitter (location, frequency, TX power, antenna gain and height), the receiver (sensitivity, height), and simulation options (max range, high-resolution terrain, color palette), then run the estimate. Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/map-and-waypoints.html#map-layers",
    
    "relUrl": "/iw-rIL/user/map-and-waypoints.html#map-layers"
  },"2354": {
    "doc": "Map & Waypoints",
    "title": "Position Sharing",
    "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. 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. To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/map-and-waypoints.html#position-sharing",
    
    "relUrl": "/iw-rIL/user/map-and-waypoints.html#position-sharing"
  },"2355": {
    "doc": "Map & Waypoints",
    "title": "Map Sources",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | Notes | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | כהה | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/map-and-waypoints.html#map-sources",
    
    "relUrl": "/iw-rIL/user/map-and-waypoints.html#map-sources"
  },"2356": {
    "doc": "Map & Waypoints",
    "title": "Related Topics",
    "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | Units & Locale — distance and coordinate display formats | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/map-and-waypoints.html#related-topics",
    
    "relUrl": "/iw-rIL/user/map-and-waypoints.html#related-topics"
  },"2357": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": " ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/map-and-waypoints.html",
    
    "relUrl": "/iw-rIL/user/map-and-waypoints.html"
  },"2358": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": "The Map screen shows the geographic positions of nodes on your mesh, along with shared waypoints. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/map-and-waypoints.html#map--waypoints",
    
    "relUrl": "/pt-rBR/user/map-and-waypoints.html#map--waypoints"
  },"2359": {
    "doc": "Map & Waypoints",
    "title": "Map View",
    "content": "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 . Each node that reports a position is shown as a node chip marker displaying the node’s short name. The chip is colored by the node’s own identity color (a stable color derived from its node number) — the same chip used in the node list, so a node looks the same everywhere. Marker color does not encode online/offline status. When a node’s position updates live, its marker briefly pulses. Nearby markers are clustered as you zoom out. Map Controls . | Zoom — pinch or use +/- buttons | Pan — drag to explore | Center — tap the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/map-and-waypoints.html#map-view",
    
    "relUrl": "/pt-rBR/user/map-and-waypoints.html#map-view"
  },"2360": {
    "doc": "Map & Waypoints",
    "title": "Waypoints",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. Creating a Waypoint . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | Enter a name and optional description. | Choose an icon/emoji for the waypoint. | Tap Send to share with the mesh. | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. Waypoint Properties . | Property | Descrição | . | Nome | Short identifier (max 29 characters) | . | Descrição | Optional longer description | . | Icon | Visual marker emoji on the map | . | Bloqueado | If locked, only the creator can edit or delete | . | Expiration | Optional auto-remove date and time | . | Geofence | Optional enter/exit alert area — see Waypoint Geofences | . Waypoint Expiration . Waypoints can be set to expire automatically: . | Never (default) — waypoint remains until manually deleted | Timed — pick a specific date and time; the waypoint is automatically removed once that time passes. 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 is based on the absolute time you picked, not a duration from when the waypoint was created or received. Waypoint Geofences . Any waypoint can also define a geofence — an alert area — so you or others get notified when a node enters or leaves it: . | Set a geofence radius from the preset chips (or Off to disable), or tap Set area on map to draw a custom rectangular area instead. | Once a region is set, toggle Notify on enter and/or Notify on exit. | Optionally enable Favorites only to limit alerts to your favorited nodes. | . Since waypoints (and their geofences) are broadcast to the whole mesh, only the creator is alerted by default. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. Managing Waypoints . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/map-and-waypoints.html#waypoints",
    
    "relUrl": "/pt-rBR/user/map-and-waypoints.html#waypoints"
  },"2361": {
    "doc": "Map & Waypoints",
    "title": "Camadas do Mapa",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Imported layers are listed with a toggle to show/hide each one and an option to remove it. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. Site Planner . Site Planner estimates RF coverage for a transmitter and draws it on the map as a color-coded overlay. Open it from a map control, or from a node’s detail page via Estimate coverage (shown only for nodes with a known position). Configure the transmitter (location, frequency, TX power, antenna gain and height), the receiver (sensitivity, height), and simulation options (max range, high-resolution terrain, color palette), then run the estimate. Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/map-and-waypoints.html#camadas-do-mapa",
    
    "relUrl": "/pt-rBR/user/map-and-waypoints.html#camadas-do-mapa"
  },"2362": {
    "doc": "Map & Waypoints",
    "title": "Position Sharing",
    "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. 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. To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/map-and-waypoints.html#position-sharing",
    
    "relUrl": "/pt-rBR/user/map-and-waypoints.html#position-sharing"
  },"2363": {
    "doc": "Map & Waypoints",
    "title": "Map Sources",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | Notes | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | Escuro | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/map-and-waypoints.html#map-sources",
    
    "relUrl": "/pt-rBR/user/map-and-waypoints.html#map-sources"
  },"2364": {
    "doc": "Map & Waypoints",
    "title": "Related Topics",
    "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | Units & Locale — distance and coordinate display formats | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/map-and-waypoints.html#related-topics",
    
    "relUrl": "/pt-rBR/user/map-and-waypoints.html#related-topics"
  },"2365": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": " ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/map-and-waypoints.html",
    
    "relUrl": "/pt-rBR/user/map-and-waypoints.html"
  },"2366": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": "The Map screen shows the geographic positions of nodes on your mesh, along with shared waypoints. ",
    "url": "/Meshtastic-Android/main/en/user/map-and-waypoints.html#map--waypoints",
    
    "relUrl": "/en/user/map-and-waypoints.html#map--waypoints"
  },"2367": {
    "doc": "Map & Waypoints",
    "title": "Map View",
    "content": "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 . Each node that reports a position is shown as a node chip marker displaying the node’s short name. The chip is colored by the node’s own identity color (a stable color derived from its node number) — the same chip used in the node list, so a node looks the same everywhere. Marker color does not encode online/offline status. When a node’s position updates live, its marker briefly pulses. Nearby markers are clustered as you zoom out. Map Controls . | Zoom — pinch or use +/- buttons | Pan — drag to explore | Center — tap the location button to center on your position | Node tap — tap a node marker to view details | . The floating toolbar provides quick access to the compass, the map type and layers pickers, node filters, Site Planner, and location tracking. Tap the compass to reorient north-up, or tap the location button to center on your current position. On Google Play builds a refresh button joins them while a network layer is showing; on F-Droid and Desktop, refresh a network layer from its own row in the layers sheet instead. Filtering the Map . Tap the filter button in the floating toolbar to open Filter map. Display controls what is drawn: Only Favorites, Show Waypoints, Show Precision Circles, and a slider that hides nodes not heard from recently. Node roles is a chip per device role, plus All to show every role; a selected chip means that role is shown. Nodes narrows the set further with Hide offline nodes, Only show direct nodes, Signed only, Encrypted only, Exclude MQTT, Show ignored nodes, and Include unknown — the same rules as the node list’s filter toggles. A dot on the filter button means at least one filter is hiding something — check it before concluding the mesh is quiet. Turning Show Waypoints off hides every waypoint, including your own. Show ignored nodes adds them to the map rather than showing only them — unlike the node list’s Only show ignored Nodes. ",
    "url": "/Meshtastic-Android/main/en/user/map-and-waypoints.html#map-view",
    
    "relUrl": "/en/user/map-and-waypoints.html#map-view"
  },"2368": {
    "doc": "Map & Waypoints",
    "title": "Waypoints",
    "content": "Waypoints are shared points of interest, visible to everyone on your mesh. Creating a Waypoint . Your radio must be connected — the map ignores a touch & hold while it is not, because saving a waypoint means broadcasting it. | Touch & hold the map at the desired location. | Enter a name and optional description. | Choose an icon/emoji for the waypoint. | Tap Send to share with the mesh. | . Waypoints always broadcast to the whole mesh on the primary channel. Unlike a message, a waypoint cannot be addressed to one channel or sent as a direct message. Waypoint Properties . | Property | Description | . | Name | Short identifier (max 29 characters) | . | Description | Optional longer description | . | Icon | Visual marker emoji on the map | . | Locked | If locked, only the creator can edit or delete | . | Expiration | Optional auto-remove date and time | . | Geofence | Optional enter/exit alert area — see Waypoint Geofences | . Waypoint Expiration . Waypoints can be set to expire automatically: . | Never (default) — waypoint remains until manually deleted | Timed — pick a specific date and time; the waypoint is automatically removed once that time passes. 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 is based on the absolute time you picked, not a duration from when the waypoint was created or received. Waypoint Geofences . Any waypoint can also define a geofence — an alert area — so you or others get notified when a node enters or leaves it: . | Set a geofence radius from the preset chips (or Off to disable), or tap Set area on map to draw a custom rectangular area instead. | Once a region is set, toggle Notify on enter and/or Notify on exit. | Optionally enable Favorites only to limit alerts to your favorited nodes. | . Since waypoints (and their geofences) are broadcast to the whole mesh, only the creator is alerted by default. If someone else shares a geofenced waypoint with you, its detail view offers a Notify me of crossings opt-in so you can also receive enter/exit alerts for it. Managing Waypoints . | Tap a waypoint to see its name, description, and geofence radius. On Google Play builds the first tap opens the marker’s info bubble — tap the bubble to open the waypoint itself | Locked waypoints can only be changed on the mesh by the node that locked them | Unlocked waypoints can be edited by any mesh member while connected to a radio — saving re-broadcasts the waypoint | Confirming a delete removes your own copy. To remove it from everyone else’s map too, select Delete for everyone in the delete dialog; that box appears only for a waypoint you may change (unlocked, or locked by you) and only while you are connected | . ",
    "url": "/Meshtastic-Android/main/en/user/map-and-waypoints.html#waypoints",
    
    "relUrl": "/en/user/map-and-waypoints.html#waypoints"
  },"2369": {
    "doc": "Map & Waypoints",
    "title": "Map Layers",
    "content": "Tap the layers icon on the map to open Manage Map Layers. It imports your own overlays in .kml, .kmz, or GeoJSON format — including KMZ ground overlays (georeferenced images, such as exported topo or aerial tiles), which drape at their stated bounds. Add one by picking a file with Add Layer, opening a file with Meshtastic, or sharing it into the app from another app. Add Network Layer instead takes a name and an http:// or https:// URL pointing at a KML or GeoJSON file; that layer then carries its own refresh button in the sheet. On Google Play builds the toolbar’s refresh button re-fetches every visible network layer at once. Imported layers are listed with a toggle to show/hide each one and an option to remove it. Each layer — imported or built-in overlay — carries its own opacity slider while it is switched on, so an overlay can be faded back rather than only switched off. This works on the Google Play build, the F-Droid build, and Desktop, which shares the same layer store and file picker. Site Planner . Site Planner estimates RF coverage for a transmitter and draws it on the map as a color-coded overlay. Open it from a map control, or from a node’s detail page via Estimate coverage (shown only for nodes with a known position). Configure the transmitter (location, frequency, TX power, antenna gain and height), the receiver (sensitivity, height), and simulation options (max range, high-resolution terrain, color palette), then run the estimate. Like map layers, Site Planner works on both the Google Play and F-Droid builds, where the finished estimate is drawn on the map as a coverage overlay. On Desktop the same form is shown but the planner opens in your browser; to bring the estimate onto the map, click the transmitter pin in the browser, choose the planner’s GeoJSON export, then add the downloaded file under Manage Map Layers with Add Layer. Use the GeoJSON export, not the KML one — the KML is a ground-overlay image this map cannot draw. ",
    "url": "/Meshtastic-Android/main/en/user/map-and-waypoints.html#map-layers",
    
    "relUrl": "/en/user/map-and-waypoints.html#map-layers"
  },"2370": {
    "doc": "Map & Waypoints",
    "title": "Position Sharing",
    "content": "Enabling Position Sharing . Your node shares its GPS position based on: . | Broadcast Interval — share the position on a fixed timer | Smart Position — share only once you have moved far enough; Smart Interval sets the shortest gap between broadcasts and Smart Distance how far you must move | Fixed Position — publish a latitude, longitude, and altitude you enter by hand instead of the GPS reading | GPS Mode (Physical Hardware) — GPS enabled, disabled, or not present on this hardware; offered only while Fixed Position is off | . Configure position behavior in Settings → Device configuration → Position. The screen is only reachable while your radio is connected, and saving it reboots the radio. For the full field list, see Settings — Radio & User. 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. To keep sharing a position without pinpointing yourself, edit the channel in Settings → Channels, turn Precise location off, and set the slider beneath it — the channel then publishes an approximate area, shown as ± a distance, instead of an exact point. ",
    "url": "/Meshtastic-Android/main/en/user/map-and-waypoints.html#position-sharing",
    
    "relUrl": "/en/user/map-and-waypoints.html#position-sharing"
  },"2371": {
    "doc": "Map & Waypoints",
    "title": "Map Sources",
    "content": "Every build offers a base map picker from the map toolbar. Google Play builds open on Google’s own map types; F-Droid and Desktop builds open on MapLibre’s vector styles. Further down the base map picker, all three offer the same raster base maps: . | Base map | Notes | . | Normal / Satellite / Terrain / Hybrid | Google Play only — Google’s own map types | . | Liberty | Default on F-Droid and Desktop. Vector street map | . | Positron | F-Droid and Desktop only. Low-contrast vector map; keeps node markers legible over it | . | Dark | F-Droid and Desktop only. Vector map suited to dark themes | . | OpenStreetMap | Classic raster street tiles | . | OpenTopoMap | Raster topographic | . | USGS Topo / USGS Imagery | US coverage only | . | Esri Topo / Esri Imagery | Topographic and satellite imagery | . Overlays can be toggled on top of any base map, from the layers sheet: . | Weather radar — NOAA NEXRAD reflectivity (US coverage) | Hillshade — terrain relief from an online tile source, on F-Droid and Desktop only; Google Play draws hillshade from downloaded offline terrain instead. Useful for understanding why a link fails, since LoRa range is limited by terrain | . Adding your own tile source . Any XYZ tile endpoint can be added as a base map, on every flavor and on desktop. Open Manage Custom Tile Sources at the foot of the base map picker and paste a URL template using {z}, {x} and {y} — plus {s} if the provider uses rotating subdomains. A national mapping service, for example: . https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/{z}/{x}/{y}.jpeg . Tiles are cached on disk, so panning does not re-download what you were just looking at. On Android, the same screen also imports a local .mbtiles archive for fully offline use. On F-Droid, select a vector base map first — Liberty, Positron, or Dark — since a download is defined against a vector style and Start Download stays disabled over a raster one. Frame the area you want on screen, then tap Start Download in the layers sheet: that creates a paused pack covering the current zoom plus two levels deeper. Press play on the pack’s row to actually download it. On Google Play, the layers sheet’s Offline Manager section downloads its own offline regions instead — water, roads and administrative boundaries extracted from the public Protomaps basemap dataset, drawn directly as map shapes rather than raster tiles. Frame the area you want, tap Start Download, and once it finishes flip Show on map to draw it (it’s off by default so it never surprises you by covering up the live map). You can still import a pre-made .mbtiles archive here too, as before. Desktop has neither, though the offline terrain described next does work there. Offline terrain . Hillshade and elevation contours can be downloaded for offline use as well, so a downloaded area still shows why a link fails when there is no network. The terrain data comes from Mapterhorn and is credited on the map. On Google Play, each downloaded region in the Offline Manager list has a Download Terrain button and Hillshade and Contours switches; terrain attaches to that region and shares its storage limit, and an area too large for terrain asks you to zoom in or pick a smaller region. On F-Droid and Desktop, the layers sheet has an Offline Terrain section of its own: frame the area, tap Start Download, and the hillshade and contours draw from the downloaded tiles from then on. Going offline . An Offline pill appears over the map whenever the device has no network connection. On Google Play builds, if you’ve imported a local .mbtiles archive, the map switches to it automatically the moment the network drops — no toggle to remember — and switches back once you’re reconnected, as long as you haven’t picked a different base map yourself in between. On F-Droid, a downloaded offline area keeps rendering on its own; the pill is purely informational there. Desktop downloads offline terrain but no base-map packs, so the pill is informational there too. ",
    "url": "/Meshtastic-Android/main/en/user/map-and-waypoints.html#map-sources",
    
    "relUrl": "/en/user/map-and-waypoints.html#map-sources"
  },"2372": {
    "doc": "Map & Waypoints",
    "title": "Related Topics",
    "content": ". | Nodes — view and filter your node list | Node Metrics — signal quality and position history for individual nodes | Local Mesh Discovery — traceroute and neighbor info for understanding mesh topology | Units & Locale — distance and coordinate display formats | . ",
    "url": "/Meshtastic-Android/main/en/user/map-and-waypoints.html#related-topics",
    
    "relUrl": "/en/user/map-and-waypoints.html#related-topics"
  },"2373": {
    "doc": "Map & Waypoints",
    "title": "Map & Waypoints",
    "content": " ",
    "url": "/Meshtastic-Android/main/en/user/map-and-waypoints.html",
    
    "relUrl": "/en/user/map-and-waypoints.html"
  },"2374": {
    "doc": "Measurement & Formatting",
    "title": "Measurement & Formatting",
    "content": "How the Meshtastic Android/KMP app formats numbers, units, and locale-sensitive values. ",
    "url": "/Meshtastic-Android/main/en/developer/measurement.html#measurement--formatting",
    
    "relUrl": "/en/developer/measurement.html#measurement--formatting"
  },"2375": {
    "doc": "Measurement & Formatting",
    "title": "Overview",
    "content": "All measurement data transmitted by Meshtastic nodes uses metric units (meters, °C, hPa, m/s, etc.). The app converts and formats these values for display using two core utilities: . | Utility | Location | Purpose | . | MetricFormatter | core/common/.../util/MetricFormatter.kt | Converts and formats physical measurements (temperature, pressure, speed, etc.) | . | NumberFormatter | core/common/.../util/NumberFormatter.kt | Decimal formatting: format follows the OS locale, formatInvariant keeps a fixed dot separator | . | MeasureFormatting | core/common/.../util/MeasureFormatting.kt | Pairs a fixed English unit symbol with a locale-formatted number, for the units that convert | . Both live in org.meshtastic.core.common.util and are available to all KMP targets (Android, Desktop, iOS). ",
    "url": "/Meshtastic-Android/main/en/developer/measurement.html#overview",
    
    "relUrl": "/en/developer/measurement.html#overview"
  },"2376": {
    "doc": "Measurement & Formatting",
    "title": "MetricFormatter API",
    "content": "MetricFormatter is a Kotlin object with pure functions for each measurement type: . object MetricFormatter { fun temperature(celsius: Float, isFahrenheit: Boolean): String fun voltage(volts: Float, decimalPlaces: Int = 2): String fun current(milliAmps: Float, decimalPlaces: Int = 1): String fun percent(value: Float, decimalPlaces: Int = 1): String fun humidity(value: Float): String fun pressure(hPa: Float, decimalPlaces: Int = 1): String fun snr(value: Float?, decimalPlaces: Int = 1): String fun rssi(value: Int?): String fun degreeSymbol(isFahrenheit: Boolean): String fun percent(value: Int): String fun windSpeed(metersPerSecond: Float, isImperial: Boolean, decimalPlaces: Int = 1): String fun rainfall(millimeters: Float, isImperial: Boolean, decimalPlaces: Int = 1): String fun weight(kilograms: Float, isImperial: Boolean, decimalPlaces: Int = 2): String } `snr` and `rssi` take a nullable reading and render the `—` placeholder when it is absent. Usage . // Temperature — Fahrenheit conversion is handled automatically MetricFormatter.temperature(22.5f, isFahrenheit = true) // \"72.5°F\" MetricFormatter.temperature(22.5f, isFahrenheit = false) // \"22.5°C\" // Signal metrics MetricFormatter.snr(-5.2f) // \"-5.2 dB\" MetricFormatter.rssi(-97) // \"-97 dBm\" // Environment MetricFormatter.pressure(1013.25f) // \"1013.3 hPa\" MetricFormatter.humidity(65.0f) // \"65%\" MetricFormatter.windSpeed(3.7f, isImperial = false) // \"13.3 km/h\" MetricFormatter.windSpeed(3.7f, isImperial = true) // \"8.3 mph\" MetricFormatter.rainfall(12.3f, isImperial = false) // \"12.3 mm\" MetricFormatter.rainfall(12.3f, isImperial = true) // \"0.5 in\" // Power MetricFormatter.voltage(3.95f) // \"3.95 V\" MetricFormatter.current(125.0f) // \"125.0 mA\" . ",
    "url": "/Meshtastic-Android/main/en/developer/measurement.html#metricformatter-api",
    
    "relUrl": "/en/developer/measurement.html#metricformatter-api"
  },"2377": {
    "doc": "Measurement & Formatting",
    "title": "NumberFormatter",
    "content": "NumberFormatter has two halves, and picking the wrong one is the mistake to avoid: . object NumberFormatter { fun format(value: Double, decimalPlaces: Int): String // follows the OS locale fun format(value: Float, decimalPlaces: Int): String // follows the OS locale fun formatInvariant(value: Double, decimalPlaces: Int): String // fixed dot separator } . Use \u00000\u0000 for anything a person reads. It delegates to the platform’s own number formatter through an expect/actual (java.text.NumberFormat on JVM and Android), so a number reads the way that user writes numbers. NaN and infinity render as —. Use \u00000\u0000 for anything a machine parses — a CoT payload another client reads, or a value written out and read back. Localizing those turns 1.5 into 1,5 and breaks the reader. It rounds half away from zero to match the locale path, which matters because firmware reports SNR in quarter-dB steps and ties are routine. ",
    "url": "/Meshtastic-Android/main/en/developer/measurement.html#numberformatter",
    
    "relUrl": "/en/developer/measurement.html#numberformatter"
  },"2378": {
    "doc": "Measurement & Formatting",
    "title": "Unit conversion",
    "content": "Four measurements convert away from metric for display, each gated by a boolean flag sourced from the device locale or preferences: . | Measurement | Flag | Source | Conversion | . | temperature | isFahrenheit | getSystemTemperatureUnit() | °F = °C × 1.8 + 32 | . | windSpeed | isImperial | getSystemMeasurementSystem() | m/s × 3.6 → km/h, or × 2.23694 → mph | . | rainfall | isImperial | getSystemMeasurementSystem() | mm ÷ 25.4 → in | . | weight | isImperial | getSystemMeasurementSystem() | kg × 2.20462 → lb | . The two source functions (in core/common/.../util/MeasurementSystem.kt) are deliberately separate: some locales mix systems (the UK uses miles for distance but Celsius for temperature), so temperature must never be derived from the distance unit. On Android, getSystemTemperatureUnit() delegates to androidx.core.text.util.LocalePreferences, which resolves CLDR locale data and honors the Android 14+ Regional preferences temperature override. The in-app Units choice (UnitsOverride, stored in UiPrefs) is folded in by LocaleUnitsProvider, which is the only place display code takes units from. A Konsist rule (MeasurementSystemSourceTest) keeps direct reads of the OS resolution out of the rest of the codebase, because a direct read follows the locale but ignores the setting. A forced system carries its temperature with it (metric → °C, imperial → °F), overriding even an explicit OS regional temperature preference. getSystemMeasurementSystem() resolves the locale in this order (temperature is separate: as described above, getSystemTemperatureUnit() reads the regional temperature preference via LocalePreferences, shares only the region backfill, and falls back to Celsius): . | The ms Unicode extension (the Android 16+ Measurement system preference) wins outright. | A locale with no region — the in-app language picker offers bare tags like en — takes its region from the system configuration rather than letting ICU guess one from the language. | Anything still unclassified falls back to metric, never imperial. | . The Android and Desktop implementations share the region table and the override reader in commonMain, so the two clients can’t disagree about the same locale. Everything else (voltage, current, pressure, SNR, RSSI, humidity, percent) displays in its native metric units. The user-facing Units & Locale page explains what end users see. ",
    "url": "/Meshtastic-Android/main/en/developer/measurement.html#unit-conversion",
    
    "relUrl": "/en/developer/measurement.html#unit-conversion"
  },"2379": {
    "doc": "Measurement & Formatting",
    "title": "Adding a new measurement type",
    "content": "To add a new measurement formatter: . | Add a function to \u00000\u0000 in core/common/src/commonMain/kotlin/org/meshtastic/core/common/util/MetricFormatter.kt: . fun radiation(microSieverts: Float, decimalPlaces: Int = 2): String = \"${NumberFormatter.format(microSieverts, decimalPlaces)} μSv/h\" . | Add tests in core/common/src/commonTest/: . @Test fun radiationFormatting() { assertEquals(\"0.15 μSv/h\", MetricFormatter.radiation(0.15f)) assertEquals(\"1.23 μSv/h\", MetricFormatter.radiation(1.234f)) } . | Use in UI — call from any commonMain composable or ViewModel: . Text(text = MetricFormatter.radiation(node.radiationLevel)) . | Run verification: ./gradlew :core:common:allTests . | . ",
    "url": "/Meshtastic-Android/main/en/developer/measurement.html#adding-a-new-measurement-type",
    
    "relUrl": "/en/developer/measurement.html#adding-a-new-measurement-type"
  },"2380": {
    "doc": "Measurement & Formatting",
    "title": "DateFormatter",
    "content": "Date and time formatting uses the DateFormatter expect object with platform-specific actual implementations: . | Function | Output Example | . | formatRelativeTime() | “5 min ago” | . | formatDateTime() | “May 13, 2026 2:30 PM” | . | formatShortDate() | “May 13” | . | formatTime() | “2:30 PM” | . | formatTimeWithSeconds() | “2:30:45 PM” | . | formatDate() | “2026-05-13” | . | formatDateTimeShort() | “5/13/26 2:30 PM” | . Unlike MetricFormatter, DateFormatter is declared with expect/actual (an expect object in commonMain, an actual object per platform) because date formatting inherently depends on platform locale APIs. ",
    "url": "/Meshtastic-Android/main/en/developer/measurement.html#dateformatter",
    
    "relUrl": "/en/developer/measurement.html#dateformatter"
  },"2381": {
    "doc": "Measurement & Formatting",
    "title": "Design decisions",
    "content": "| Decision | Rationale | . | Display formatting follows the OS locale | A number shown to a user should read the way that user writes numbers | . | formatInvariant keeps a fixed . for machine-read values | Interop payloads and re-parsed values break if localized | . | Only temperature, wind speed, rainfall and weight convert | The remaining metric units are universally understood in their native form | . | object singleton pattern | Stateless utility — no instance management needed | . ",
    "url": "/Meshtastic-Android/main/en/developer/measurement.html#design-decisions",
    
    "relUrl": "/en/developer/measurement.html#design-decisions"
  },"2382": {
    "doc": "Measurement & Formatting",
    "title": "Related",
    "content": ". | User-facing docs: Units & Locale explains what end users see | Source code: core/common/src/commonMain/kotlin/org/meshtastic/core/common/util/MetricFormatter.kt | Tests: core/common/src/commonTest/kotlin/org/meshtastic/core/common/util/MetricFormatterTest.kt | . ",
    "url": "/Meshtastic-Android/main/en/developer/measurement.html#related",
    
    "relUrl": "/en/developer/measurement.html#related"
  },"2383": {
    "doc": "Measurement & Formatting",
    "title": "Measurement & Formatting",
    "content": " ",
    "url": "/Meshtastic-Android/main/en/developer/measurement.html",
    
    "relUrl": "/en/developer/measurement.html"
  },"2384": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": "Meshtastic supports two communication modes: channel broadcasts and direct messages. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/messages-and-channels.html#messages--channels",
    
    "relUrl": "/sk-rSK/user/messages-and-channels.html#messages--channels"
  },"2385": {
    "doc": "Messages & Channels",
    "title": "Kanále",
    "content": "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 radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. Channel Security . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | Icon | What it means | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: 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 . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/messages-and-channels.html#kan%C3%A1le",
    
    "relUrl": "/sk-rSK/user/messages-and-channels.html#kanále"
  },"2386": {
    "doc": "Messages & Channels",
    "title": "Direct Messages",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. Sending a Direct Message . | Open the Messages tab. | Select a conversation, or tap a node in the node list. | Type your message and tap Send. | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. Message States . A status label appears under your own outgoing messages only (incoming messages from others show no status label): . | State | Meaning | . | Sending… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | Delivered to recipient | The strongest confirmation for a direct message — an acknowledgment came back | . | Delivered to mesh | For a channel broadcast, the message reached the mesh (broadcasts have no per-recipient ack) | . | Relayed, not confirmed by recipient | For a direct message, shown in a warning color — the message was relayed but no acknowledgment has come back yet | . | Routing via SF++ chain… | Being routed/buffered by the Store & Forward Plus Plus chain | . | Confirmed on SF++ chain | Confirmed delivered via the SF++ chain | . | Chyba | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Chyba | Meaning | What to Do | . | Žiadna trasa | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Rate limited | The mesh is throttling you for sending too fast | Wait before sending again. | . | Not authorized | The destination refused the request | Check you have the right channel and keys for that node. | . | Recipient needs your key | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | Recipient key unavailable | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | Could not send encrypted message | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Admin session expired | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Admin key not authorized | The target node does not accept your admin key | Verify the admin key matches on both nodes. | . | Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. | . | Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. | . | No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. | . | Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. | . | Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/messages-and-channels.html#direct-messages",
    
    "relUrl": "/sk-rSK/user/messages-and-channels.html#direct-messages"
  },"2387": {
    "doc": "Messages & Channels",
    "title": "Message Features",
    "content": "Quick Chat . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Searching Messages . You can search the full history of any conversation directly from the chat screen: . | Open a conversation (a channel or a direct message). | Tap the search icon in the top bar. | Type into the Search messages… field. The search runs as you type, across all stored messages in that conversation. | Use the N / M result counter and the previous / next arrows to jump between matches, which are highlighted in the conversation. | . 💡 Tip: Search is full-text and stays within the conversation you opened it from — it doesn’t search across other channels or contacts. It matches against the messages already stored on your device, so it works fully offline. 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. Text Formatting . Messages support lightweight inline Markdown. Received messages render the styling with the syntax characters removed: . | Typ | Syntax | Renders as | . | Bold | **bold** | bold | . | Italic | *italic* | italic | . | Strikethrough | ~~strike~~ | strike | . | Inline code | `code` | monospace code | . | Link | [label](https://example.com) | a tappable label | . When composing, focus the message field and type at least three characters to reveal a formatting toolbar below the input. Select text and tap a style to wrap it (tap again to remove it); with no selection, a style inserts an empty pair with the cursor between the markers. The link button opens a dialog to enter a URL. As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 Tip: Formatting is carried as literal characters on the mesh — the same bytes iOS sends. Clients that don’t support Markdown (older apps, plain firmware clients) will show the raw **/~~ characters. URLs, email addresses, and phone numbers are still auto-linked whether or not you use Markdown. Mentions . Type @ while composing to mention a node — a picker suggests matching contacts as you type. In a received message, a mention appears as a highlighted chip showing the node’s name; tap it to jump straight to that node’s detail page. Reactions . React to messages with emoji: . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. Message Actions . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | Reply — quote the message in your response | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . Message Priority . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . Message Limits . | Maximum length: 200 bytes (approximately 200 characters for ASCII text) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | Rate limiting: The mesh enforces airtime fairness; heavy message volume may be throttled | Delivery: Messages are retried automatically if no acknowledgment is received | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/messages-and-channels.html#message-features",
    
    "relUrl": "/sk-rSK/user/messages-and-channels.html#message-features"
  },"2388": {
    "doc": "Messages & Channels",
    "title": "Best Practices",
    "content": ". | 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 | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/messages-and-channels.html#best-practices",
    
    "relUrl": "/sk-rSK/user/messages-and-channels.html#best-practices"
  },"2389": {
    "doc": "Messages & Channels",
    "title": "Related Topics",
    "content": ". | Nodes — tap a node to start a direct message | Settings — Radio & User — configure channel encryption and presets | MQTT — bridge channel messages to the internet | Channel configuration — detailed channel settings on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/messages-and-channels.html#related-topics",
    
    "relUrl": "/sk-rSK/user/messages-and-channels.html#related-topics"
  },"2390": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": " ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/messages-and-channels.html",
    
    "relUrl": "/sk-rSK/user/messages-and-channels.html"
  },"2391": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": "Meshtastic supports two communication modes: channel broadcasts and direct messages. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/messages-and-channels.html#messages--channels",
    
    "relUrl": "/be-rBY/user/messages-and-channels.html#messages--channels"
  },"2392": {
    "doc": "Messages & Channels",
    "title": "Каналы",
    "content": "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 radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. Channel Security . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | Icon | What it means | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: 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 . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/messages-and-channels.html#%D0%BA%D0%B0%D0%BD%D0%B0%D0%BB%D1%8B",
    
    "relUrl": "/be-rBY/user/messages-and-channels.html#каналы"
  },"2393": {
    "doc": "Messages & Channels",
    "title": "Direct Messages",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. Sending a Direct Message . | Open the Messages tab. | Select a conversation, or tap a node in the node list. | Type your message and tap Send. | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. Message States . A status label appears under your own outgoing messages only (incoming messages from others show no status label): . | State | Meaning | . | Sending… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | Delivered to recipient | The strongest confirmation for a direct message — an acknowledgment came back | . | Delivered to mesh | For a channel broadcast, the message reached the mesh (broadcasts have no per-recipient ack) | . | Relayed, not confirmed by recipient | For a direct message, shown in a warning color — the message was relayed but no acknowledgment has come back yet | . | Routing via SF++ chain… | Being routed/buffered by the Store & Forward Plus Plus chain | . | Confirmed on SF++ chain | Confirmed delivered via the SF++ chain | . | Памылка | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Памылка | Meaning | What to Do | . | Няма маршруту | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Rate limited | The mesh is throttling you for sending too fast | Wait before sending again. | . | Not authorized | The destination refused the request | Check you have the right channel and keys for that node. | . | Recipient needs your key | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | Recipient key unavailable | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | Could not send encrypted message | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Admin session expired | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Admin key not authorized | The target node does not accept your admin key | Verify the admin key matches on both nodes. | . | Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. | . | Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. | . | No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. | . | Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. | . | Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/messages-and-channels.html#direct-messages",
    
    "relUrl": "/be-rBY/user/messages-and-channels.html#direct-messages"
  },"2394": {
    "doc": "Messages & Channels",
    "title": "Message Features",
    "content": "Quick Chat . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Searching Messages . You can search the full history of any conversation directly from the chat screen: . | Open a conversation (a channel or a direct message). | Tap the search icon in the top bar. | Type into the Search messages… field. The search runs as you type, across all stored messages in that conversation. | Use the N / M result counter and the previous / next arrows to jump between matches, which are highlighted in the conversation. | . 💡 Tip: Search is full-text and stays within the conversation you opened it from — it doesn’t search across other channels or contacts. It matches against the messages already stored on your device, so it works fully offline. 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. Text Formatting . Messages support lightweight inline Markdown. Received messages render the styling with the syntax characters removed: . | Тып | Syntax | Renders as | . | Bold | **bold** | bold | . | Italic | *italic* | italic | . | Strikethrough | ~~strike~~ | strike | . | Inline code | `code` | monospace code | . | Link | [label](https://example.com) | a tappable label | . When composing, focus the message field and type at least three characters to reveal a formatting toolbar below the input. Select text and tap a style to wrap it (tap again to remove it); with no selection, a style inserts an empty pair with the cursor between the markers. The link button opens a dialog to enter a URL. As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 Tip: Formatting is carried as literal characters on the mesh — the same bytes iOS sends. Clients that don’t support Markdown (older apps, plain firmware clients) will show the raw **/~~ characters. URLs, email addresses, and phone numbers are still auto-linked whether or not you use Markdown. Mentions . Type @ while composing to mention a node — a picker suggests matching contacts as you type. In a received message, a mention appears as a highlighted chip showing the node’s name; tap it to jump straight to that node’s detail page. Reactions . React to messages with emoji: . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. Message Actions . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | Reply — quote the message in your response | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . Message Priority . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . Message Limits . | Maximum length: 200 bytes (approximately 200 characters for ASCII text) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | Rate limiting: The mesh enforces airtime fairness; heavy message volume may be throttled | Delivery: Messages are retried automatically if no acknowledgment is received | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/messages-and-channels.html#message-features",
    
    "relUrl": "/be-rBY/user/messages-and-channels.html#message-features"
  },"2395": {
    "doc": "Messages & Channels",
    "title": "Best Practices",
    "content": ". | 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 | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/messages-and-channels.html#best-practices",
    
    "relUrl": "/be-rBY/user/messages-and-channels.html#best-practices"
  },"2396": {
    "doc": "Messages & Channels",
    "title": "Related Topics",
    "content": ". | Nodes — tap a node to start a direct message | Settings — Radio & User — configure channel encryption and presets | MQTT — bridge channel messages to the internet | Channel configuration — detailed channel settings on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/messages-and-channels.html#related-topics",
    
    "relUrl": "/be-rBY/user/messages-and-channels.html#related-topics"
  },"2397": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": " ",
    "url": "/Meshtastic-Android/main/be-rBY/user/messages-and-channels.html",
    
    "relUrl": "/be-rBY/user/messages-and-channels.html"
  },"2398": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": "Meshtastic supports two communication modes: channel broadcasts and direct messages. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/messages-and-channels.html#messages--channels",
    
    "relUrl": "/it-rIT/user/messages-and-channels.html#messages--channels"
  },"2399": {
    "doc": "Messages & Channels",
    "title": "Canali",
    "content": "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 radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. Sicurezza del canale . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | Icon | What it means | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: 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 . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/messages-and-channels.html#canali",
    
    "relUrl": "/it-rIT/user/messages-and-channels.html#canali"
  },"2400": {
    "doc": "Messages & Channels",
    "title": "Messaggi Diretti",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. Sending a Direct Message . | Open the Messages tab. | Select a conversation, or tap a node in the node list. | Type your message and tap Send. | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. Message States . A status label appears under your own outgoing messages only (incoming messages from others show no status label): . | State | Meaning | . | Sending… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | Delivered to recipient | The strongest confirmation for a direct message — an acknowledgment came back | . | Delivered to mesh | For a channel broadcast, the message reached the mesh (broadcasts have no per-recipient ack) | . | Relayed, not confirmed by recipient | For a direct message, shown in a warning color — the message was relayed but no acknowledgment has come back yet | . | Percorso tramite catena SF++… | Being routed/buffered by the Store & Forward Plus Plus chain | . | Confermato sulla catena SF++ | Confirmed delivered via the SF++ chain | . | Errori | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Errori | Meaning | What to Do | . | Nessun percorso | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Consegna alla mesh non riuscita | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Rate limited | The mesh is throttling you for sending too fast | Wait before sending again. | . | Not authorized | The destination refused the request | Check you have the right channel and keys for that node. | . | Il destinatario ha bisogno della tua chiave | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | Chiave del destinatario non disponibile | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | Impossibile inviare il messaggio cifrato | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Admin session expired | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Admin key not authorized | The target node does not accept your admin key | Verify the admin key matches on both nodes. | . | Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. | . | Il messaggio è troppo grande per essere inviato | Message exceeds maximum payload size | Shorten the message and try again. | . | No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. | . | Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. | . | Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/messages-and-channels.html#messaggi-diretti",
    
    "relUrl": "/it-rIT/user/messages-and-channels.html#messaggi-diretti"
  },"2401": {
    "doc": "Messages & Channels",
    "title": "Message Features",
    "content": "Quick Chat . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Searching Messages . You can search the full history of any conversation directly from the chat screen: . | Open a conversation (a channel or a direct message). | Tap the search icon in the top bar. | Type into the Search messages… field. The search runs as you type, across all stored messages in that conversation. | Use the N / M result counter and the previous / next arrows to jump between matches, which are highlighted in the conversation. | . 💡 Tip: Search is full-text and stays within the conversation you opened it from — it doesn’t search across other channels or contacts. It matches against the messages already stored on your device, so it works fully offline. 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. Text Formatting . Messages support lightweight inline Markdown. Received messages render the styling with the syntax characters removed: . | Tipo | Syntax | Renders as | . | Bold | **bold** | bold | . | Italic | *italic* | italic | . | Strikethrough | ~~strike~~ | strike | . | Inline code | `code` | monospace code | . | Link | [label](https://example.com) | a tappable label | . When composing, focus the message field and type at least three characters to reveal a formatting toolbar below the input. Select text and tap a style to wrap it (tap again to remove it); with no selection, a style inserts an empty pair with the cursor between the markers. The link button opens a dialog to enter a URL. As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 Tip: Formatting is carried as literal characters on the mesh — the same bytes iOS sends. Clients that don’t support Markdown (older apps, plain firmware clients) will show the raw **/~~ characters. URLs, email addresses, and phone numbers are still auto-linked whether or not you use Markdown. Mentions . Type @ while composing to mention a node — a picker suggests matching contacts as you type. In a received message, a mention appears as a highlighted chip showing the node’s name; tap it to jump straight to that node’s detail page. Reactions . React to messages with emoji: . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. Message Actions . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | Reply — quote the message in your response | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . Message Priority . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . Message Limits . | Maximum length: 200 bytes (approximately 200 characters for ASCII text) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | Rate limiting: The mesh enforces airtime fairness; heavy message volume may be throttled | Delivery: Messages are retried automatically if no acknowledgment is received | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/messages-and-channels.html#message-features",
    
    "relUrl": "/it-rIT/user/messages-and-channels.html#message-features"
  },"2402": {
    "doc": "Messages & Channels",
    "title": "Buone pratiche",
    "content": ". | 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 | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/messages-and-channels.html#buone-pratiche",
    
    "relUrl": "/it-rIT/user/messages-and-channels.html#buone-pratiche"
  },"2403": {
    "doc": "Messages & Channels",
    "title": "Related Topics",
    "content": ". | Nodes — tap a node to start a direct message | Settings — Radio & User — configure channel encryption and presets | MQTT — bridge channel messages to the internet | Channel configuration — detailed channel settings on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/messages-and-channels.html#related-topics",
    
    "relUrl": "/it-rIT/user/messages-and-channels.html#related-topics"
  },"2404": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": " ",
    "url": "/Meshtastic-Android/main/it-rIT/user/messages-and-channels.html",
    
    "relUrl": "/it-rIT/user/messages-and-channels.html"
  },"2405": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": "Meshtastic supports two communication modes: channel broadcasts and direct messages. ",
    "url": "/Meshtastic-Android/main/es-rES/user/messages-and-channels.html#messages--channels",
    
    "relUrl": "/es-rES/user/messages-and-channels.html#messages--channels"
  },"2406": {
    "doc": "Messages & Channels",
    "title": "Canales",
    "content": "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 radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. Seguridad del canal . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | Icon | What it means | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: 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 . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/es-rES/user/messages-and-channels.html#canales",
    
    "relUrl": "/es-rES/user/messages-and-channels.html#canales"
  },"2407": {
    "doc": "Messages & Channels",
    "title": "Direct Messages",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. Sending a Direct Message . | Open the Messages tab. | Select a conversation, or tap a node in the node list. | Type your message and tap Send. | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. Message States . A status label appears under your own outgoing messages only (incoming messages from others show no status label): . | State | Meaning | . | Sending… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | Delivered to recipient | The strongest confirmation for a direct message — an acknowledgment came back | . | Delivered to mesh | For a channel broadcast, the message reached the mesh (broadcasts have no per-recipient ack) | . | Relayed, not confirmed by recipient | For a direct message, shown in a warning color — the message was relayed but no acknowledgment has come back yet | . | Routing via SF++ chain… | Being routed/buffered by the Store & Forward Plus Plus chain | . | Confirmed on SF++ chain | Confirmed delivered via the SF++ chain | . | Error | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Error | Meaning | What to Do | . | Sin ruta | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Rate limited | The mesh is throttling you for sending too fast | Wait before sending again. | . | Not authorized | The destination refused the request | Check you have the right channel and keys for that node. | . | Recipient needs your key | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | Recipient key unavailable | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | Could not send encrypted message | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Admin session expired | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Admin key not authorized | The target node does not accept your admin key | Verify the admin key matches on both nodes. | . | Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. | . | Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. | . | No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. | . | Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. | . | Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/es-rES/user/messages-and-channels.html#direct-messages",
    
    "relUrl": "/es-rES/user/messages-and-channels.html#direct-messages"
  },"2408": {
    "doc": "Messages & Channels",
    "title": "Message Features",
    "content": "Quick Chat . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Searching Messages . You can search the full history of any conversation directly from the chat screen: . | Open a conversation (a channel or a direct message). | Tap the search icon in the top bar. | Type into the Search messages… field. The search runs as you type, across all stored messages in that conversation. | Use the N / M result counter and the previous / next arrows to jump between matches, which are highlighted in the conversation. | . 💡 Tip: Search is full-text and stays within the conversation you opened it from — it doesn’t search across other channels or contacts. It matches against the messages already stored on your device, so it works fully offline. 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. Text Formatting . Messages support lightweight inline Markdown. Received messages render the styling with the syntax characters removed: . | Tipo | Syntax | Renders as | . | Bold | **bold** | bold | . | Italic | *italic* | italic | . | Strikethrough | ~~strike~~ | strike | . | Inline code | `code` | monospace code | . | Link | [label](https://example.com) | a tappable label | . When composing, focus the message field and type at least three characters to reveal a formatting toolbar below the input. Select text and tap a style to wrap it (tap again to remove it); with no selection, a style inserts an empty pair with the cursor between the markers. The link button opens a dialog to enter a URL. As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 Tip: Formatting is carried as literal characters on the mesh — the same bytes iOS sends. Clients that don’t support Markdown (older apps, plain firmware clients) will show the raw **/~~ characters. URLs, email addresses, and phone numbers are still auto-linked whether or not you use Markdown. Mentions . Type @ while composing to mention a node — a picker suggests matching contacts as you type. In a received message, a mention appears as a highlighted chip showing the node’s name; tap it to jump straight to that node’s detail page. Reactions . React to messages with emoji: . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. Message Actions . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | Reply — quote the message in your response | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . Message Priority . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . Message Limits . | Maximum length: 200 bytes (approximately 200 characters for ASCII text) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | Rate limiting: The mesh enforces airtime fairness; heavy message volume may be throttled | Delivery: Messages are retried automatically if no acknowledgment is received | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/messages-and-channels.html#message-features",
    
    "relUrl": "/es-rES/user/messages-and-channels.html#message-features"
  },"2409": {
    "doc": "Messages & Channels",
    "title": "Best Practices",
    "content": ". | 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 | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/messages-and-channels.html#best-practices",
    
    "relUrl": "/es-rES/user/messages-and-channels.html#best-practices"
  },"2410": {
    "doc": "Messages & Channels",
    "title": "Related Topics",
    "content": ". | Nodes — tap a node to start a direct message | Settings — Radio & User — configure channel encryption and presets | MQTT — bridge channel messages to the internet | Channel configuration — detailed channel settings on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/messages-and-channels.html#related-topics",
    
    "relUrl": "/es-rES/user/messages-and-channels.html#related-topics"
  },"2411": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": " ",
    "url": "/Meshtastic-Android/main/es-rES/user/messages-and-channels.html",
    
    "relUrl": "/es-rES/user/messages-and-channels.html"
  },"2412": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": "Meshtastic supports two communication modes: channel broadcasts and direct messages. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/messages-and-channels.html#messages--channels",
    
    "relUrl": "/sl-rSI/user/messages-and-channels.html#messages--channels"
  },"2413": {
    "doc": "Messages & Channels",
    "title": "Channels",
    "content": "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 radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. Channel Security . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | Icon | What it means | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: 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 . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/messages-and-channels.html#channels",
    
    "relUrl": "/sl-rSI/user/messages-and-channels.html#channels"
  },"2414": {
    "doc": "Messages & Channels",
    "title": "Direct Messages",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. Sending a Direct Message . | Open the Messages tab. | Select a conversation, or tap a node in the node list. | Type your message and tap Send. | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. Message States . A status label appears under your own outgoing messages only (incoming messages from others show no status label): . | State | Meaning | . | Sending… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | Delivered to recipient | The strongest confirmation for a direct message — an acknowledgment came back | . | Delivered to mesh | For a channel broadcast, the message reached the mesh (broadcasts have no per-recipient ack) | . | Relayed, not confirmed by recipient | For a direct message, shown in a warning color — the message was relayed but no acknowledgment has come back yet | . | Routing via SF++ chain… | Being routed/buffered by the Store & Forward Plus Plus chain | . | Confirmed on SF++ chain | Confirmed delivered via the SF++ chain | . | Napaka | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Napaka | Meaning | What to Do | . | Brez poti | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Rate limited | The mesh is throttling you for sending too fast | Wait before sending again. | . | Not authorized | The destination refused the request | Check you have the right channel and keys for that node. | . | Recipient needs your key | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | Recipient key unavailable | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | Could not send encrypted message | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Admin session expired | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Admin key not authorized | The target node does not accept your admin key | Verify the admin key matches on both nodes. | . | Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. | . | Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. | . | No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. | . | Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. | . | Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/messages-and-channels.html#direct-messages",
    
    "relUrl": "/sl-rSI/user/messages-and-channels.html#direct-messages"
  },"2415": {
    "doc": "Messages & Channels",
    "title": "Message Features",
    "content": "Quick Chat . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Searching Messages . You can search the full history of any conversation directly from the chat screen: . | Open a conversation (a channel or a direct message). | Tap the search icon in the top bar. | Type into the Search messages… field. The search runs as you type, across all stored messages in that conversation. | Use the N / M result counter and the previous / next arrows to jump between matches, which are highlighted in the conversation. | . 💡 Tip: Search is full-text and stays within the conversation you opened it from — it doesn’t search across other channels or contacts. It matches against the messages already stored on your device, so it works fully offline. 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. Text Formatting . Messages support lightweight inline Markdown. Received messages render the styling with the syntax characters removed: . | Type | Syntax | Renders as | . | Bold | **bold** | bold | . | Italic | *italic* | italic | . | Strikethrough | ~~strike~~ | strike | . | Inline code | `code` | monospace code | . | Link | [label](https://example.com) | a tappable label | . When composing, focus the message field and type at least three characters to reveal a formatting toolbar below the input. Select text and tap a style to wrap it (tap again to remove it); with no selection, a style inserts an empty pair with the cursor between the markers. The link button opens a dialog to enter a URL. As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 Tip: Formatting is carried as literal characters on the mesh — the same bytes iOS sends. Clients that don’t support Markdown (older apps, plain firmware clients) will show the raw **/~~ characters. URLs, email addresses, and phone numbers are still auto-linked whether or not you use Markdown. Mentions . Type @ while composing to mention a node — a picker suggests matching contacts as you type. In a received message, a mention appears as a highlighted chip showing the node’s name; tap it to jump straight to that node’s detail page. Reactions . React to messages with emoji: . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. Message Actions . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | Reply — quote the message in your response | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . Message Priority . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . Message Limits . | Maximum length: 200 bytes (approximately 200 characters for ASCII text) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | Rate limiting: The mesh enforces airtime fairness; heavy message volume may be throttled | Delivery: Messages are retried automatically if no acknowledgment is received | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/messages-and-channels.html#message-features",
    
    "relUrl": "/sl-rSI/user/messages-and-channels.html#message-features"
  },"2416": {
    "doc": "Messages & Channels",
    "title": "Best Practices",
    "content": ". | 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 | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/messages-and-channels.html#best-practices",
    
    "relUrl": "/sl-rSI/user/messages-and-channels.html#best-practices"
  },"2417": {
    "doc": "Messages & Channels",
    "title": "Related Topics",
    "content": ". | Nodes — tap a node to start a direct message | Settings — Radio & User — configure channel encryption and presets | MQTT — bridge channel messages to the internet | Channel configuration — detailed channel settings on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/messages-and-channels.html#related-topics",
    
    "relUrl": "/sl-rSI/user/messages-and-channels.html#related-topics"
  },"2418": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": " ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/messages-and-channels.html",
    
    "relUrl": "/sl-rSI/user/messages-and-channels.html"
  },"2419": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": "Meshtastic supports two communication modes: channel broadcasts and direct messages. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/messages-and-channels.html#messages--channels",
    
    "relUrl": "/no-rNO/user/messages-and-channels.html#messages--channels"
  },"2420": {
    "doc": "Messages & Channels",
    "title": "Channels",
    "content": "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 radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. Channel Security . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | Icon | What it means | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: 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 . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/messages-and-channels.html#channels",
    
    "relUrl": "/no-rNO/user/messages-and-channels.html#channels"
  },"2421": {
    "doc": "Messages & Channels",
    "title": "Direct Messages",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. Sending a Direct Message . | Open the Messages tab. | Select a conversation, or tap a node in the node list. | Type your message and tap Send. | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. Message States . A status label appears under your own outgoing messages only (incoming messages from others show no status label): . | State | Meaning | . | Sending… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | Delivered to recipient | The strongest confirmation for a direct message — an acknowledgment came back | . | Delivered to mesh | For a channel broadcast, the message reached the mesh (broadcasts have no per-recipient ack) | . | Relayed, not confirmed by recipient | For a direct message, shown in a warning color — the message was relayed but no acknowledgment has come back yet | . | Routing via SF++ chain… | Being routed/buffered by the Store & Forward Plus Plus chain | . | Confirmed on SF++ chain | Confirmed delivered via the SF++ chain | . | Feil | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Feil | Meaning | What to Do | . | Ingen rute | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Rate limited | The mesh is throttling you for sending too fast | Wait before sending again. | . | Not authorized | The destination refused the request | Check you have the right channel and keys for that node. | . | Recipient needs your key | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | Recipient key unavailable | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | Could not send encrypted message | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Admin session expired | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Admin key not authorized | The target node does not accept your admin key | Verify the admin key matches on both nodes. | . | Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. | . | Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. | . | No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. | . | Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. | . | Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/messages-and-channels.html#direct-messages",
    
    "relUrl": "/no-rNO/user/messages-and-channels.html#direct-messages"
  },"2422": {
    "doc": "Messages & Channels",
    "title": "Message Features",
    "content": "Quick Chat . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Searching Messages . You can search the full history of any conversation directly from the chat screen: . | Open a conversation (a channel or a direct message). | Tap the search icon in the top bar. | Type into the Search messages… field. The search runs as you type, across all stored messages in that conversation. | Use the N / M result counter and the previous / next arrows to jump between matches, which are highlighted in the conversation. | . 💡 Tip: Search is full-text and stays within the conversation you opened it from — it doesn’t search across other channels or contacts. It matches against the messages already stored on your device, so it works fully offline. 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. Text Formatting . Messages support lightweight inline Markdown. Received messages render the styling with the syntax characters removed: . | Type | Syntax | Renders as | . | Bold | **bold** | bold | . | Italic | *italic* | italic | . | Strikethrough | ~~strike~~ | strike | . | Inline code | `code` | monospace code | . | Link | [label](https://example.com) | a tappable label | . When composing, focus the message field and type at least three characters to reveal a formatting toolbar below the input. Select text and tap a style to wrap it (tap again to remove it); with no selection, a style inserts an empty pair with the cursor between the markers. The link button opens a dialog to enter a URL. As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 Tip: Formatting is carried as literal characters on the mesh — the same bytes iOS sends. Clients that don’t support Markdown (older apps, plain firmware clients) will show the raw **/~~ characters. URLs, email addresses, and phone numbers are still auto-linked whether or not you use Markdown. Mentions . Type @ while composing to mention a node — a picker suggests matching contacts as you type. In a received message, a mention appears as a highlighted chip showing the node’s name; tap it to jump straight to that node’s detail page. Reactions . React to messages with emoji: . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. Message Actions . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | Reply — quote the message in your response | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . Message Priority . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . Message Limits . | Maximum length: 200 bytes (approximately 200 characters for ASCII text) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | Rate limiting: The mesh enforces airtime fairness; heavy message volume may be throttled | Delivery: Messages are retried automatically if no acknowledgment is received | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/messages-and-channels.html#message-features",
    
    "relUrl": "/no-rNO/user/messages-and-channels.html#message-features"
  },"2423": {
    "doc": "Messages & Channels",
    "title": "Best Practices",
    "content": ". | 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 | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/messages-and-channels.html#best-practices",
    
    "relUrl": "/no-rNO/user/messages-and-channels.html#best-practices"
  },"2424": {
    "doc": "Messages & Channels",
    "title": "Related Topics",
    "content": ". | Nodes — tap a node to start a direct message | Settings — Radio & User — configure channel encryption and presets | MQTT — bridge channel messages to the internet | Channel configuration — detailed channel settings on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/messages-and-channels.html#related-topics",
    
    "relUrl": "/no-rNO/user/messages-and-channels.html#related-topics"
  },"2425": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": " ",
    "url": "/Meshtastic-Android/main/no-rNO/user/messages-and-channels.html",
    
    "relUrl": "/no-rNO/user/messages-and-channels.html"
  },"2426": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": "Meshtastic supports two communication modes: channel broadcasts and direct messages. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/messages-and-channels.html#messages--channels",
    
    "relUrl": "/hu-rHU/user/messages-and-channels.html#messages--channels"
  },"2427": {
    "doc": "Messages & Channels",
    "title": "Csatornák",
    "content": "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 radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. Csatorna biztonság . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | Icon | What it means | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: 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 . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/messages-and-channels.html#csatorn%C3%A1k",
    
    "relUrl": "/hu-rHU/user/messages-and-channels.html#csatornák"
  },"2428": {
    "doc": "Messages & Channels",
    "title": "Direct Messages",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. Sending a Direct Message . | Open the Messages tab. | Select a conversation, or tap a node in the node list. | Type your message and tap Send. | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. Message States . A status label appears under your own outgoing messages only (incoming messages from others show no status label): . | State | Meaning | . | Sending… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | Delivered to recipient | The strongest confirmation for a direct message — an acknowledgment came back | . | Delivered to mesh | For a channel broadcast, the message reached the mesh (broadcasts have no per-recipient ack) | . | Relayed, not confirmed by recipient | For a direct message, shown in a warning color — the message was relayed but no acknowledgment has come back yet | . | Routing via SF++ chain… | Being routed/buffered by the Store & Forward Plus Plus chain | . | Confirmed on SF++ chain | Confirmed delivered via the SF++ chain | . | Hiba | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Hiba | Meaning | What to Do | . | Nincs út | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Rate limited | The mesh is throttling you for sending too fast | Wait before sending again. | . | Not authorized | The destination refused the request | Check you have the right channel and keys for that node. | . | Recipient needs your key | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | Recipient key unavailable | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | Could not send encrypted message | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Admin session expired | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Admin key not authorized | The target node does not accept your admin key | Verify the admin key matches on both nodes. | . | Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. | . | Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. | . | No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. | . | Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. | . | Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/messages-and-channels.html#direct-messages",
    
    "relUrl": "/hu-rHU/user/messages-and-channels.html#direct-messages"
  },"2429": {
    "doc": "Messages & Channels",
    "title": "Message Features",
    "content": "Quick Chat . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Searching Messages . You can search the full history of any conversation directly from the chat screen: . | Open a conversation (a channel or a direct message). | Tap the search icon in the top bar. | Type into the Search messages… field. The search runs as you type, across all stored messages in that conversation. | Use the N / M result counter and the previous / next arrows to jump between matches, which are highlighted in the conversation. | . 💡 Tip: Search is full-text and stays within the conversation you opened it from — it doesn’t search across other channels or contacts. It matches against the messages already stored on your device, so it works fully offline. 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. Text Formatting . Messages support lightweight inline Markdown. Received messages render the styling with the syntax characters removed: . | Típus | Syntax | Renders as | . | Bold | **bold** | bold | . | Italic | *italic* | italic | . | Strikethrough | ~~strike~~ | strike | . | Inline code | `code` | monospace code | . | Link | [label](https://example.com) | a tappable label | . When composing, focus the message field and type at least three characters to reveal a formatting toolbar below the input. Select text and tap a style to wrap it (tap again to remove it); with no selection, a style inserts an empty pair with the cursor between the markers. The link button opens a dialog to enter a URL. As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 Tip: Formatting is carried as literal characters on the mesh — the same bytes iOS sends. Clients that don’t support Markdown (older apps, plain firmware clients) will show the raw **/~~ characters. URLs, email addresses, and phone numbers are still auto-linked whether or not you use Markdown. Mentions . Type @ while composing to mention a node — a picker suggests matching contacts as you type. In a received message, a mention appears as a highlighted chip showing the node’s name; tap it to jump straight to that node’s detail page. Reactions . React to messages with emoji: . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. Message Actions . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | Reply — quote the message in your response | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . Message Priority . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . Message Limits . | Maximum length: 200 bytes (approximately 200 characters for ASCII text) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | Rate limiting: The mesh enforces airtime fairness; heavy message volume may be throttled | Delivery: Messages are retried automatically if no acknowledgment is received | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/messages-and-channels.html#message-features",
    
    "relUrl": "/hu-rHU/user/messages-and-channels.html#message-features"
  },"2430": {
    "doc": "Messages & Channels",
    "title": "Best Practices",
    "content": ". | 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 | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/messages-and-channels.html#best-practices",
    
    "relUrl": "/hu-rHU/user/messages-and-channels.html#best-practices"
  },"2431": {
    "doc": "Messages & Channels",
    "title": "Related Topics",
    "content": ". | Nodes — tap a node to start a direct message | Settings — Radio & User — configure channel encryption and presets | MQTT — bridge channel messages to the internet | Channel configuration — detailed channel settings on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/messages-and-channels.html#related-topics",
    
    "relUrl": "/hu-rHU/user/messages-and-channels.html#related-topics"
  },"2432": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": " ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/messages-and-channels.html",
    
    "relUrl": "/hu-rHU/user/messages-and-channels.html"
  },"2433": {
    "doc": "Сообщения и каналы",
    "title": "Сообщения и каналы",
    "content": "Meshtastic поддерживает два режима связи: вещание по каналам и личные сообщения. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/messages-and-channels.html",
    
    "relUrl": "/ru-rRU/user/messages-and-channels.html"
  },"2434": {
    "doc": "Сообщения и каналы",
    "title": "Каналы",
    "content": "Каналы - это общие группы для связи. Все узлы, настроенные с одинаковым ключом канала, могут читать и отправлять сообщения в этом канале. Канал по умолчанию . Every Meshtastic radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. Безопасность канала . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | Иконка | Что это значит | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: Always configure a unique PSK for private communications. Канал по умолчанию намеренно открыт, чтобы новые пользователи могли обнаружить mesh-сеть — но вам следует создать отдельный зашифрованный канал для любой конфиденциальной информации. Добавление канала . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/messages-and-channels.html#%D0%BA%D0%B0%D0%BD%D0%B0%D0%BB%D1%8B",
    
    "relUrl": "/ru-rRU/user/messages-and-channels.html#каналы"
  },"2435": {
    "doc": "Сообщения и каналы",
    "title": "Личные сообщения",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. Отправка личного сообщения . | Откройте вкладку Сообщения. | Select a conversation, or tap a node in the node list. | Введите сообщение и нажмите “Отправить”. | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. Состояние сообщения . Метка статуса отображается только под твоими исходящими сообщениями (входящие сообщения от других не имеют метки статуса): . | Состояние | Значение | . | Отправка… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | Доставлено получателю | Самое надёжное подтверждение для личного сообщения — получено подтверждение о доставке | . | Отправлено в сеть | Для широковещательного сообщения в канале — сообщение достигло mesh-сети (у широковещательных сообщений нет подтверждений для каждого получателя) | . | Передано, не подтверждено получателем | Для личного сообщения, отображается предупреждающим цветом — сообщение было ретранслировано, но подтверждение ещё не получено | . | Маршрутизация по SF++ цепочке… | Находится в процессе маршрутизации/буферизации в цепочке Store & Forward Plus Plus | . | Подтверждено в цепочке SF++ | Подтверждена доставка через цепочку SF++ | . | Ошибки | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . Ошибки доставки . Когда сообщение не удаётся доставить, индикатор ошибки показывает, что пошло не так: . | Ошибки | Значение | Что делать | . | Нет маршрута | Путь к целевой ноде отсутствует | Получатель может быть не в сети или вне зоны действия mesh-сети. Повторите попытку позже или подойдите ближе. | . | Нет радиоинтерфейса | Нет доступного радиоинтерфейса для отправки | Проверь, подключено ли твоё радио и доступно ли оно. | . | Не удалось доставить в сеть | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Ограничение скорости | The mesh is throttling you for sending too fast | Wait before sending again. | . | Не авторизовано | The destination refused the request | Check you have the right channel and keys for that node. | . | Получателю нужен ваш ключ | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | Ключ получателя недоступен | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | Не удалось отправить зашифрованное сообщение | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Сеанс администратора истёк | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Ключ администратора не авторизован | The target node does not accept your admin key | Проверьте соответствие ключа администратора на обоих узлах. | . | Несовпадение канала/ключа | Канал/ключ назначения не совпадает | Убедитесь, что обе ноды используют один и тот же канал и PSK. | . | Слишком большое сообщение для отправки | Сообщение превышает максимальный размер полезной нагрузки | Сократи сообщение и повтори попытку. | . | Нет ответа приложения | Приложение или плагин не ответили на запрос | Повтори попытку или проверь состояние приложения или модуля назначения. | . | Ограничение рабочего цикла (Dity cycle) | Достигнут региональный лимит эфирного времени | Дождись сброса окна рабочего цикла. | . | Неверный запрос | Повреждённый или неверный запрос | Если проблема сохраняется, повтори попытку после обновления или перезапуска приложения. | . 💡 Совет: Большинство ошибок доставки разрешаются сами собой. Если нода доступна с перебоями, mesh-сеть будет повторять попытки. For persistent No route errors, check that intermediate Router nodes are online. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/messages-and-channels.html#%D0%BB%D0%B8%D1%87%D0%BD%D1%8B%D0%B5-%D1%81%D0%BE%D0%BE%D0%B1%D1%89%D0%B5%D0%BD%D0%B8%D1%8F",
    
    "relUrl": "/ru-rRU/user/messages-and-channels.html#личные-сообщения"
  },"2436": {
    "doc": "Сообщения и каналы",
    "title": "Функции сообщений",
    "content": "Быстрый чат . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Поиск сообщений . Ты можешь искать по всей истории любой переписки прямо на экране чата: . | Откройте переписку (канал или личное сообщение). | Нажмите значок поиска в верхней панели. | Введите текст в поле “Поиск сообщений…”. Поиск выполняется по мере твоего ввода по всем сохранённым сообщениям в этой переписке. | Используйте счётчик результатов N / M и стрелки вперёд / назад для перехода между совпадениями, которые подсвечиваются в переписке. | . 💡 Совет: Поиск полнотекстовый и ограничивается перепиской, из которого ты его открыл — он не ищет по другим каналам или контактам. Он сопоставляет текст с сообщениями, уже сохранёнными на твоём устройстве, поэтому работает полностью офлайн. Пузырьки сообщения . Сообщения отображаются в виде пузырьков чата — отправленные справа, полученные слева. В каждом пузырьке отображаются отправитель, время и статус доставки. Сообщения с ответами содержат цитируемый предпросмотр исходного сообщения над ответом. Форматирование текста . Сообщения поддерживают облегчённую встроенную разметку Markdown. Полученные сообщения отображают оформление со скрытыми символами синтаксиса: . | Тип | Синтаксис | Отображается как | . | Жирный | **жирный** | жирный | . | Курсив | *курсив* | курсив | . | Зачёркнутый | ~~зачёркнутый~~ | зачёркнутый | . | Встроенный код | `код` | моноширинный код | . | Ссылка | [текст](https://example.com) | нажимаемая ссылка | . При создании сообщения установите фокус на поле ввода и введите не менее трёх символов — под полем появится панель форматирования. Выделите текст и нажмите на стиль, чтобы применить его (повторное нажатие убирает форматирование); если текст не выделен, будет вставлена пустая пара символов разметки, а курсор окажется между ними. Кнопка вставки ссылки открывает диалог для ввода URL-адреса. As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 Совет: Форматирование передаётся по mesh-сети как есть — теми же байтами, что и iOS. Клиенты, не поддерживающие Markdown (старые приложения, простые клиенты на прошивке), отобразят сырые символы **/~~. URL-адреса, адреса электронной почты и номера телефонов всё равно автоматически становятся ссылками независимо от того, используете ли вы Markdown. Упоминания . Введите @ при написании сообщения, чтобы упомянуть ноду — по мере твоего ввода будет появляться список подходящих контактов. В полученном сообщении упоминание отображается как выделенный элемент с именем ноды; нажмите на него, чтобы сразу перейти на страницу сведений о ноде. Реакции . Реагируйте на сообщения с помощью эмодзи: . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | Реакции появляются под пузырьком сообщения | Несколько пользователей могут отреагировать на одно и то же сообщение | Реагируйте на свои сообщения или сообщения других | . 💡 Совет: Реакции очень лёгкие — они потребляют гораздо меньше трафика mesh-сети по сравнению с полными текстовыми сообщениями. Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. Действия с сообщениями . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | Ответить — процитировать сообщение в твоём ответе | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . Приоритет сообщений . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . Ограничения сообщений . | Максимальная длина: 200 байт (примерно 200 символов для текста в ASCII) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | Ограничение скорости: Mesh-сеть обеспечивает справедливое распределение эфирного времени; большой объем сообщений может быть ограничен | Доставка: Сообщения автоматически повторяются при отсутствии подтверждения | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/messages-and-channels.html#%D1%84%D1%83%D0%BD%D0%BA%D1%86%D0%B8%D0%B8-%D1%81%D0%BE%D0%BE%D0%B1%D1%89%D0%B5%D0%BD%D0%B8%D0%B9",
    
    "relUrl": "/ru-rRU/user/messages-and-channels.html#функции-сообщений"
  },"2437": {
    "doc": "Сообщения и каналы",
    "title": "Рекомендации",
    "content": ". | Используйте каналы для координации в группах | Используйте личные сообщения для приватного общения один на один | Пишите короткие сообщения — пропускная способность mesh-сети ограничена | Настройте шифрование для конфиденциальной связи | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/messages-and-channels.html#%D1%80%D0%B5%D0%BA%D0%BE%D0%BC%D0%B5%D0%BD%D0%B4%D0%B0%D1%86%D0%B8%D0%B8",
    
    "relUrl": "/ru-rRU/user/messages-and-channels.html#рекомендации"
  },"2438": {
    "doc": "Сообщения и каналы",
    "title": "Связанные темы",
    "content": ". | Ноды — нажмите на ноду, чтобы начать личный чат | Настройки — Радио и пользователь — настройка шифрования каналов и пресетов | MQTT — мост для передачи сообщений канала в интернет | Конфигурация каналов — подробные параметры каналов на meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/messages-and-channels.html#%D1%81%D0%B2%D1%8F%D0%B7%D0%B0%D0%BD%D0%BD%D1%8B%D0%B5-%D1%82%D0%B5%D0%BC%D1%8B",
    
    "relUrl": "/ru-rRU/user/messages-and-channels.html#связанные-темы"
  },"2439": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": "Meshtastic supports two communication modes: channel broadcasts and direct messages. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/messages-and-channels.html#messages--channels",
    
    "relUrl": "/cs-rCZ/user/messages-and-channels.html#messages--channels"
  },"2440": {
    "doc": "Messages & Channels",
    "title": "Kanály",
    "content": "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 radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. Zabezpečení kanálu . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | Icon | What it means | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: 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 . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/messages-and-channels.html#kan%C3%A1ly",
    
    "relUrl": "/cs-rCZ/user/messages-and-channels.html#kanály"
  },"2441": {
    "doc": "Messages & Channels",
    "title": "Direct Messages",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. Sending a Direct Message . | Open the Messages tab. | Select a conversation, or tap a node in the node list. | Type your message and tap Send. | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. Message States . A status label appears under your own outgoing messages only (incoming messages from others show no status label): . | State | Meaning | . | Sending… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | Delivered to recipient | The strongest confirmation for a direct message — an acknowledgment came back | . | Doručeno do mesh sítě | For a channel broadcast, the message reached the mesh (broadcasts have no per-recipient ack) | . | Relayed, not confirmed by recipient | For a direct message, shown in a warning color — the message was relayed but no acknowledgment has come back yet | . | Routing via SF++ chain… | Being routed/buffered by the Store & Forward Plus Plus chain | . | Confirmed on SF++ chain | Confirmed delivered via the SF++ chain | . | Chyba | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Chyba | Meaning | What to Do | . | Žádná trasa | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Nepodařilo se doručit do mesh sítě | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Rate limited | The mesh is throttling you for sending too fast | Wait before sending again. | . | Neautorizováno | The destination refused the request | Check you have the right channel and keys for that node. | . | Recipient needs your key | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | Recipient key unavailable | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | Nepodařilo se odeslat šifrovanou zprávu | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Admin session expired | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Admin key not authorized | The target node does not accept your admin key | Verify the admin key matches on both nodes. | . | Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. | . | Zpráva je příliš dlouhá pro odeslání | Message exceeds maximum payload size | Shorten the message and try again. | . | No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. | . | Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. | . | Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/messages-and-channels.html#direct-messages",
    
    "relUrl": "/cs-rCZ/user/messages-and-channels.html#direct-messages"
  },"2442": {
    "doc": "Messages & Channels",
    "title": "Message Features",
    "content": "Quick Chat . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Searching Messages . You can search the full history of any conversation directly from the chat screen: . | Open a conversation (a channel or a direct message). | Tap the search icon in the top bar. | Type into the Search messages… field. The search runs as you type, across all stored messages in that conversation. | Use the N / M result counter and the previous / next arrows to jump between matches, which are highlighted in the conversation. | . 💡 Tip: Search is full-text and stays within the conversation you opened it from — it doesn’t search across other channels or contacts. It matches against the messages already stored on your device, so it works fully offline. 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. Text Formatting . Messages support lightweight inline Markdown. Received messages render the styling with the syntax characters removed: . | Typ | Syntax | Renders as | . | Bold | **bold** | bold | . | Italic | *italic* | italic | . | Strikethrough | ~~strike~~ | strike | . | Inline code | `code` | monospace code | . | Link | [label](https://example.com) | a tappable label | . When composing, focus the message field and type at least three characters to reveal a formatting toolbar below the input. Select text and tap a style to wrap it (tap again to remove it); with no selection, a style inserts an empty pair with the cursor between the markers. The link button opens a dialog to enter a URL. As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 Tip: Formatting is carried as literal characters on the mesh — the same bytes iOS sends. Clients that don’t support Markdown (older apps, plain firmware clients) will show the raw **/~~ characters. URLs, email addresses, and phone numbers are still auto-linked whether or not you use Markdown. Mentions . Type @ while composing to mention a node — a picker suggests matching contacts as you type. In a received message, a mention appears as a highlighted chip showing the node’s name; tap it to jump straight to that node’s detail page. Reactions . React to messages with emoji: . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. Message Actions . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | Reply — quote the message in your response | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . Message Priority . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . Message Limits . | Maximum length: 200 bytes (approximately 200 characters for ASCII text) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | Rate limiting: The mesh enforces airtime fairness; heavy message volume may be throttled | Delivery: Messages are retried automatically if no acknowledgment is received | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/messages-and-channels.html#message-features",
    
    "relUrl": "/cs-rCZ/user/messages-and-channels.html#message-features"
  },"2443": {
    "doc": "Messages & Channels",
    "title": "Best Practices",
    "content": ". | 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 | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/messages-and-channels.html#best-practices",
    
    "relUrl": "/cs-rCZ/user/messages-and-channels.html#best-practices"
  },"2444": {
    "doc": "Messages & Channels",
    "title": "Related Topics",
    "content": ". | Nodes — tap a node to start a direct message | Settings — Radio & User — configure channel encryption and presets | MQTT — bridge channel messages to the internet | Channel configuration — detailed channel settings on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/messages-and-channels.html#related-topics",
    
    "relUrl": "/cs-rCZ/user/messages-and-channels.html#related-topics"
  },"2445": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": " ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/messages-and-channels.html",
    
    "relUrl": "/cs-rCZ/user/messages-and-channels.html"
  },"2446": {
    "doc": "Съобщения & Канали",
    "title": "Съобщения & Канали",
    "content": "Meshtastic supports two communication modes: channel broadcasts and direct messages. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/messages-and-channels.html#%D1%81%D1%8A%D0%BE%D0%B1%D1%89%D0%B5%D0%BD%D0%B8%D1%8F--%D0%BA%D0%B0%D0%BD%D0%B0%D0%BB%D0%B8",
    
    "relUrl": "/bg-rBG/user/messages-and-channels.html#съобщения--канали"
  },"2447": {
    "doc": "Съобщения & Канали",
    "title": "Канали",
    "content": "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 radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. Сигурност на канала . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | Икона | What it means | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: 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 . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/messages-and-channels.html#%D0%BA%D0%B0%D0%BD%D0%B0%D0%BB%D0%B8",
    
    "relUrl": "/bg-rBG/user/messages-and-channels.html#канали"
  },"2448": {
    "doc": "Съобщения & Канали",
    "title": "Директни съобщения",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. Sending a Direct Message . | Open the Messages tab. | Select a conversation, or tap a node in the node list. | Type your message and tap Send. | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. Message States . A status label appears under your own outgoing messages only (incoming messages from others show no status label): . | Състояние | Значение | . | Sending… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | Delivered to recipient | The strongest confirmation for a direct message — an acknowledgment came back | . | Доставено до mesh | For a channel broadcast, the message reached the mesh (broadcasts have no per-recipient ack) | . | Relayed, not confirmed by recipient | For a direct message, shown in a warning color — the message was relayed but no acknowledgment has come back yet | . |   | Being routed/buffered by the Store & Forward Plus Plus chain | . | Confirmed on SF++ chain | Confirmed delivered via the SF++ chain | . | Грешка | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Грешка | Meaning | What to Do | . | Няма маршрут | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Rate limited | The mesh is throttling you for sending too fast | Wait before sending again. | . | Not authorized | The destination refused the request | Check you have the right channel and keys for that node. | . | Получателят се нуждае от вашия ключ | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | Ключът на получателя не е наличен | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | Не можа да се изпрати криптирано съобщение | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Admin session expired | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Admin key not authorized | The target node does not accept your admin key | Verify the admin key matches on both nodes. | . | Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. | . | Съобщението е твърде голямо за изпращане | Message exceeds maximum payload size | Shorten the message and try again. | . | No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. | . | Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. | . | Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/messages-and-channels.html#%D0%B4%D0%B8%D1%80%D0%B5%D0%BA%D1%82%D0%BD%D0%B8-%D1%81%D1%8A%D0%BE%D0%B1%D1%89%D0%B5%D0%BD%D0%B8%D1%8F",
    
    "relUrl": "/bg-rBG/user/messages-and-channels.html#директни-съобщения"
  },"2449": {
    "doc": "Съобщения & Канали",
    "title": "Message Features",
    "content": "Quick Chat . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Searching Messages . You can search the full history of any conversation directly from the chat screen: . | Open a conversation (a channel or a direct message). | Tap the search icon in the top bar. | Type into the Search messages… field. The search runs as you type, across all stored messages in that conversation. | Use the N / M result counter and the previous / next arrows to jump between matches, which are highlighted in the conversation. | . 💡 Tip: Search is full-text and stays within the conversation you opened it from — it doesn’t search across other channels or contacts. It matches against the messages already stored on your device, so it works fully offline. 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. Text Formatting . Messages support lightweight inline Markdown. Received messages render the styling with the syntax characters removed: . | Тип | Syntax | Renders as | . | Bold | **bold** | bold | . | Italic | *italic* | italic | . | Strikethrough | ~~strike~~ | strike | . | Inline code | `code` | monospace code | . | Link | [label](https://example.com) | a tappable label | . When composing, focus the message field and type at least three characters to reveal a formatting toolbar below the input. Select text and tap a style to wrap it (tap again to remove it); with no selection, a style inserts an empty pair with the cursor between the markers. The link button opens a dialog to enter a URL. As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 Tip: Formatting is carried as literal characters on the mesh — the same bytes iOS sends. Clients that don’t support Markdown (older apps, plain firmware clients) will show the raw **/~~ characters. URLs, email addresses, and phone numbers are still auto-linked whether or not you use Markdown. Mentions . Type @ while composing to mention a node — a picker suggests matching contacts as you type. In a received message, a mention appears as a highlighted chip showing the node’s name; tap it to jump straight to that node’s detail page. Reactions . React to messages with emoji: . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. Message Actions . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | Reply — quote the message in your response | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . Message Priority . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . Message Limits . | Maximum length: 200 bytes (approximately 200 characters for ASCII text) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | Rate limiting: The mesh enforces airtime fairness; heavy message volume may be throttled | Delivery: Messages are retried automatically if no acknowledgment is received | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/messages-and-channels.html#message-features",
    
    "relUrl": "/bg-rBG/user/messages-and-channels.html#message-features"
  },"2450": {
    "doc": "Съобщения & Канали",
    "title": "Най-добри практики",
    "content": ". | 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 | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/messages-and-channels.html#%D0%BD%D0%B0%D0%B9-%D0%B4%D0%BE%D0%B1%D1%80%D0%B8-%D0%BF%D1%80%D0%B0%D0%BA%D1%82%D0%B8%D0%BA%D0%B8",
    
    "relUrl": "/bg-rBG/user/messages-and-channels.html#най-добри-практики"
  },"2451": {
    "doc": "Съобщения & Канали",
    "title": "Related Topics",
    "content": ". | Nodes — tap a node to start a direct message | Settings — Radio & User — configure channel encryption and presets | MQTT — bridge channel messages to the internet | Channel configuration — detailed channel settings on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/messages-and-channels.html#related-topics",
    
    "relUrl": "/bg-rBG/user/messages-and-channels.html#related-topics"
  },"2452": {
    "doc": "Съобщения & Канали",
    "title": "Съобщения & Канали",
    "content": " ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/messages-and-channels.html",
    
    "relUrl": "/bg-rBG/user/messages-and-channels.html"
  },"2453": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": "Meshtastic supports two communication modes: channel broadcasts and direct messages. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/messages-and-channels.html#messages--channels",
    
    "relUrl": "/ga-rIE/user/messages-and-channels.html#messages--channels"
  },"2454": {
    "doc": "Messages & Channels",
    "title": "Channels",
    "content": "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 radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. Channel Security . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | Icon | What it means | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: 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 . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/messages-and-channels.html#channels",
    
    "relUrl": "/ga-rIE/user/messages-and-channels.html#channels"
  },"2455": {
    "doc": "Messages & Channels",
    "title": "Direct Messages",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. Sending a Direct Message . | Open the Messages tab. | Select a conversation, or tap a node in the node list. | Type your message and tap Send. | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. Message States . A status label appears under your own outgoing messages only (incoming messages from others show no status label): . | State | Meaning | . | Sending… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | Delivered to recipient | The strongest confirmation for a direct message — an acknowledgment came back | . | Delivered to mesh | For a channel broadcast, the message reached the mesh (broadcasts have no per-recipient ack) | . | Relayed, not confirmed by recipient | For a direct message, shown in a warning color — the message was relayed but no acknowledgment has come back yet | . | Routing via SF++ chain… | Being routed/buffered by the Store & Forward Plus Plus chain | . | Confirmed on SF++ chain | Confirmed delivered via the SF++ chain | . | Earráid | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Earráid | Meaning | What to Do | . | Gan route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Rate limited | The mesh is throttling you for sending too fast | Wait before sending again. | . | Not authorized | The destination refused the request | Check you have the right channel and keys for that node. | . | Recipient needs your key | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | Recipient key unavailable | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | Could not send encrypted message | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Admin session expired | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Admin key not authorized | The target node does not accept your admin key | Verify the admin key matches on both nodes. | . | Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. | . | Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. | . | No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. | . | Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. | . | Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/messages-and-channels.html#direct-messages",
    
    "relUrl": "/ga-rIE/user/messages-and-channels.html#direct-messages"
  },"2456": {
    "doc": "Messages & Channels",
    "title": "Message Features",
    "content": "Quick Chat . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Searching Messages . You can search the full history of any conversation directly from the chat screen: . | Open a conversation (a channel or a direct message). | Tap the search icon in the top bar. | Type into the Search messages… field. The search runs as you type, across all stored messages in that conversation. | Use the N / M result counter and the previous / next arrows to jump between matches, which are highlighted in the conversation. | . 💡 Tip: Search is full-text and stays within the conversation you opened it from — it doesn’t search across other channels or contacts. It matches against the messages already stored on your device, so it works fully offline. 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. Text Formatting . Messages support lightweight inline Markdown. Received messages render the styling with the syntax characters removed: . | Type | Syntax | Renders as | . | Bold | **bold** | bold | . | Italic | *italic* | italic | . | Strikethrough | ~~strike~~ | strike | . | Inline code | `code` | monospace code | . | Link | [label](https://example.com) | a tappable label | . When composing, focus the message field and type at least three characters to reveal a formatting toolbar below the input. Select text and tap a style to wrap it (tap again to remove it); with no selection, a style inserts an empty pair with the cursor between the markers. The link button opens a dialog to enter a URL. As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 Tip: Formatting is carried as literal characters on the mesh — the same bytes iOS sends. Clients that don’t support Markdown (older apps, plain firmware clients) will show the raw **/~~ characters. URLs, email addresses, and phone numbers are still auto-linked whether or not you use Markdown. Mentions . Type @ while composing to mention a node — a picker suggests matching contacts as you type. In a received message, a mention appears as a highlighted chip showing the node’s name; tap it to jump straight to that node’s detail page. Reactions . React to messages with emoji: . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. Message Actions . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | Reply — quote the message in your response | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . Message Priority . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . Message Limits . | Maximum length: 200 bytes (approximately 200 characters for ASCII text) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | Rate limiting: The mesh enforces airtime fairness; heavy message volume may be throttled | Delivery: Messages are retried automatically if no acknowledgment is received | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/messages-and-channels.html#message-features",
    
    "relUrl": "/ga-rIE/user/messages-and-channels.html#message-features"
  },"2457": {
    "doc": "Messages & Channels",
    "title": "Best Practices",
    "content": ". | 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 | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/messages-and-channels.html#best-practices",
    
    "relUrl": "/ga-rIE/user/messages-and-channels.html#best-practices"
  },"2458": {
    "doc": "Messages & Channels",
    "title": "Related Topics",
    "content": ". | Nodes — tap a node to start a direct message | Settings — Radio & User — configure channel encryption and presets | MQTT — bridge channel messages to the internet | Channel configuration — detailed channel settings on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/messages-and-channels.html#related-topics",
    
    "relUrl": "/ga-rIE/user/messages-and-channels.html#related-topics"
  },"2459": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": " ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/messages-and-channels.html",
    
    "relUrl": "/ga-rIE/user/messages-and-channels.html"
  },"2460": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": "Meshtastic supports two communication modes: channel broadcasts and direct messages. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/messages-and-channels.html#messages--channels",
    
    "relUrl": "/fr-rCA/user/messages-and-channels.html#messages--channels"
  },"2461": {
    "doc": "Messages & Channels",
    "title": "Canaux",
    "content": "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 radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. Sécurité du canal . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | Icon | What it means | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: 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 . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/messages-and-channels.html#canaux",
    
    "relUrl": "/fr-rCA/user/messages-and-channels.html#canaux"
  },"2462": {
    "doc": "Messages & Channels",
    "title": "Messages directs",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. Sending a Direct Message . | Open the Messages tab. | Select a conversation, or tap a node in the node list. | Type your message and tap Send. | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. Message States . A status label appears under your own outgoing messages only (incoming messages from others show no status label): . | State | Meaning | . | Sending… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | Delivered to recipient | The strongest confirmation for a direct message — an acknowledgment came back | . | Délivré au nœud | For a channel broadcast, the message reached the mesh (broadcasts have no per-recipient ack) | . | Relayed, not confirmed by recipient | For a direct message, shown in a warning color — the message was relayed but no acknowledgment has come back yet | . | Routage via chaîne SF++… | Being routed/buffered by the Store & Forward Plus Plus chain | . | Confirmé via chaîne SF++ | Confirmed delivered via the SF++ chain | . | Erreur | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Erreur | Meaning | What to Do | . | Pas de routage | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Rate limited | The mesh is throttling you for sending too fast | Wait before sending again. | . | Not authorized | The destination refused the request | Check you have the right channel and keys for that node. | . | Recipient needs your key | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | Recipient key unavailable | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | Could not send encrypted message | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Admin session expired | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Admin key not authorized | The target node does not accept your admin key | Verify the admin key matches on both nodes. | . | Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. | . | Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. | . | No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. | . | Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. | . | Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/messages-and-channels.html#messages-directs",
    
    "relUrl": "/fr-rCA/user/messages-and-channels.html#messages-directs"
  },"2463": {
    "doc": "Messages & Channels",
    "title": "Message Features",
    "content": "Quick Chat . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Searching Messages . You can search the full history of any conversation directly from the chat screen: . | Open a conversation (a channel or a direct message). | Tap the search icon in the top bar. | Type into the Search messages… field. The search runs as you type, across all stored messages in that conversation. | Use the N / M result counter and the previous / next arrows to jump between matches, which are highlighted in the conversation. | . 💡 Tip: Search is full-text and stays within the conversation you opened it from — it doesn’t search across other channels or contacts. It matches against the messages already stored on your device, so it works fully offline. 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. Text Formatting . Messages support lightweight inline Markdown. Received messages render the styling with the syntax characters removed: . | Type | Syntax | Renders as | . | Bold | **bold** | bold | . | Italic | *italic* | italic | . | Strikethrough | ~~strike~~ | strike | . | Inline code | `code` | monospace code | . | Link | [label](https://example.com) | a tappable label | . When composing, focus the message field and type at least three characters to reveal a formatting toolbar below the input. Select text and tap a style to wrap it (tap again to remove it); with no selection, a style inserts an empty pair with the cursor between the markers. The link button opens a dialog to enter a URL. As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 Tip: Formatting is carried as literal characters on the mesh — the same bytes iOS sends. Clients that don’t support Markdown (older apps, plain firmware clients) will show the raw **/~~ characters. URLs, email addresses, and phone numbers are still auto-linked whether or not you use Markdown. Mentions . Type @ while composing to mention a node — a picker suggests matching contacts as you type. In a received message, a mention appears as a highlighted chip showing the node’s name; tap it to jump straight to that node’s detail page. Reactions . React to messages with emoji: . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. Message Actions . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | Reply — quote the message in your response | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . Message Priority . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . Message Limits . | Maximum length: 200 bytes (approximately 200 characters for ASCII text) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | Rate limiting: The mesh enforces airtime fairness; heavy message volume may be throttled | Delivery: Messages are retried automatically if no acknowledgment is received | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/messages-and-channels.html#message-features",
    
    "relUrl": "/fr-rCA/user/messages-and-channels.html#message-features"
  },"2464": {
    "doc": "Messages & Channels",
    "title": "Best Practices",
    "content": ". | 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 | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/messages-and-channels.html#best-practices",
    
    "relUrl": "/fr-rCA/user/messages-and-channels.html#best-practices"
  },"2465": {
    "doc": "Messages & Channels",
    "title": "Related Topics",
    "content": ". | Nodes — tap a node to start a direct message | Settings — Radio & User — configure channel encryption and presets | MQTT — bridge channel messages to the internet | Channel configuration — detailed channel settings on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/messages-and-channels.html#related-topics",
    
    "relUrl": "/fr-rCA/user/messages-and-channels.html#related-topics"
  },"2466": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": " ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/messages-and-channels.html",
    
    "relUrl": "/fr-rCA/user/messages-and-channels.html"
  },"2467": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": "Meshtastic supports two communication modes: channel broadcasts and direct messages. ",
    "url": "/Meshtastic-Android/main/srp/user/messages-and-channels.html#messages--channels",
    
    "relUrl": "/srp/user/messages-and-channels.html#messages--channels"
  },"2468": {
    "doc": "Messages & Channels",
    "title": "Канали",
    "content": "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 radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. Channel Security . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | Иконица | What it means | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: 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 . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/srp/user/messages-and-channels.html#%D0%BA%D0%B0%D0%BD%D0%B0%D0%BB%D0%B8",
    
    "relUrl": "/srp/user/messages-and-channels.html#канали"
  },"2469": {
    "doc": "Messages & Channels",
    "title": "Директне поруке",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. Sending a Direct Message . | Open the Messages tab. | Select a conversation, or tap a node in the node list. | Type your message and tap Send. | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. Message States . A status label appears under your own outgoing messages only (incoming messages from others show no status label): . | State | Meaning | . | Sending… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | Delivered to recipient | The strongest confirmation for a direct message — an acknowledgment came back | . | Delivered to mesh | For a channel broadcast, the message reached the mesh (broadcasts have no per-recipient ack) | . | Relayed, not confirmed by recipient | For a direct message, shown in a warning color — the message was relayed but no acknowledgment has come back yet | . | Routing via SF++ chain… | Being routed/buffered by the Store & Forward Plus Plus chain | . | Confirmed on SF++ chain | Confirmed delivered via the SF++ chain | . | Грешка | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Грешка | Meaning | What to Do | . | Нема руте | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Rate limited | The mesh is throttling you for sending too fast | Wait before sending again. | . | Not authorized | The destination refused the request | Check you have the right channel and keys for that node. | . | Recipient needs your key | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | Recipient key unavailable | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | Could not send encrypted message | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Admin session expired | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Admin key not authorized | The target node does not accept your admin key | Verify the admin key matches on both nodes. | . | Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. | . | Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. | . | No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. | . | Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. | . | Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/srp/user/messages-and-channels.html#%D0%B4%D0%B8%D1%80%D0%B5%D0%BA%D1%82%D0%BD%D0%B5-%D0%BF%D0%BE%D1%80%D1%83%D0%BA%D0%B5",
    
    "relUrl": "/srp/user/messages-and-channels.html#директне-поруке"
  },"2470": {
    "doc": "Messages & Channels",
    "title": "Message Features",
    "content": "Quick Chat . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Searching Messages . You can search the full history of any conversation directly from the chat screen: . | Open a conversation (a channel or a direct message). | Tap the search icon in the top bar. | Type into the Search messages… field. The search runs as you type, across all stored messages in that conversation. | Use the N / M result counter and the previous / next arrows to jump between matches, which are highlighted in the conversation. | . 💡 Tip: Search is full-text and stays within the conversation you opened it from — it doesn’t search across other channels or contacts. It matches against the messages already stored on your device, so it works fully offline. 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. Text Formatting . Messages support lightweight inline Markdown. Received messages render the styling with the syntax characters removed: . | Type | Syntax | Renders as | . | Bold | **bold** | bold | . | Italic | *italic* | italic | . | Strikethrough | ~~strike~~ | strike | . | Inline code | `code` | monospace code | . | Link | [label](https://example.com) | a tappable label | . When composing, focus the message field and type at least three characters to reveal a formatting toolbar below the input. Select text and tap a style to wrap it (tap again to remove it); with no selection, a style inserts an empty pair with the cursor between the markers. The link button opens a dialog to enter a URL. As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 Tip: Formatting is carried as literal characters on the mesh — the same bytes iOS sends. Clients that don’t support Markdown (older apps, plain firmware clients) will show the raw **/~~ characters. URLs, email addresses, and phone numbers are still auto-linked whether or not you use Markdown. Mentions . Type @ while composing to mention a node — a picker suggests matching contacts as you type. In a received message, a mention appears as a highlighted chip showing the node’s name; tap it to jump straight to that node’s detail page. Reactions . React to messages with emoji: . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. Message Actions . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | Reply — quote the message in your response | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . Message Priority . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . Message Limits . | Maximum length: 200 bytes (approximately 200 characters for ASCII text) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | Rate limiting: The mesh enforces airtime fairness; heavy message volume may be throttled | Delivery: Messages are retried automatically if no acknowledgment is received | . ",
    "url": "/Meshtastic-Android/main/srp/user/messages-and-channels.html#message-features",
    
    "relUrl": "/srp/user/messages-and-channels.html#message-features"
  },"2471": {
    "doc": "Messages & Channels",
    "title": "Best Practices",
    "content": ". | 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 | . ",
    "url": "/Meshtastic-Android/main/srp/user/messages-and-channels.html#best-practices",
    
    "relUrl": "/srp/user/messages-and-channels.html#best-practices"
  },"2472": {
    "doc": "Messages & Channels",
    "title": "Related Topics",
    "content": ". | Nodes — tap a node to start a direct message | Settings — Radio & User — configure channel encryption and presets | MQTT — bridge channel messages to the internet | Channel configuration — detailed channel settings on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/srp/user/messages-and-channels.html#related-topics",
    
    "relUrl": "/srp/user/messages-and-channels.html#related-topics"
  },"2473": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": " ",
    "url": "/Meshtastic-Android/main/srp/user/messages-and-channels.html",
    
    "relUrl": "/srp/user/messages-and-channels.html"
  },"2474": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": "Meshtastic supports two communication modes: channel broadcasts and direct messages. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/messages-and-channels.html#messages--channels",
    
    "relUrl": "/ca-rES/user/messages-and-channels.html#messages--channels"
  },"2475": {
    "doc": "Messages & Channels",
    "title": "Channels",
    "content": "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 radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. Channel Security . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | Icon | What it means | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: 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 . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/messages-and-channels.html#channels",
    
    "relUrl": "/ca-rES/user/messages-and-channels.html#channels"
  },"2476": {
    "doc": "Messages & Channels",
    "title": "Direct Messages",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. Sending a Direct Message . | Open the Messages tab. | Select a conversation, or tap a node in the node list. | Type your message and tap Send. | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. Message States . A status label appears under your own outgoing messages only (incoming messages from others show no status label): . | State | Meaning | . | Sending… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | Delivered to recipient | The strongest confirmation for a direct message — an acknowledgment came back | . | Delivered to mesh | For a channel broadcast, the message reached the mesh (broadcasts have no per-recipient ack) | . | Relayed, not confirmed by recipient | For a direct message, shown in a warning color — the message was relayed but no acknowledgment has come back yet | . | Routing via SF++ chain… | Being routed/buffered by the Store & Forward Plus Plus chain | . | Confirmed on SF++ chain | Confirmed delivered via the SF++ chain | . | Error | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Error | Meaning | What to Do | . | Sense ruta | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Rate limited | The mesh is throttling you for sending too fast | Wait before sending again. | . | Not authorized | The destination refused the request | Check you have the right channel and keys for that node. | . | Recipient needs your key | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | Recipient key unavailable | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | Could not send encrypted message | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Admin session expired | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Admin key not authorized | The target node does not accept your admin key | Verify the admin key matches on both nodes. | . | Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. | . | Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. | . | No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. | . | Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. | . | Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/messages-and-channels.html#direct-messages",
    
    "relUrl": "/ca-rES/user/messages-and-channels.html#direct-messages"
  },"2477": {
    "doc": "Messages & Channels",
    "title": "Message Features",
    "content": "Quick Chat . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Searching Messages . You can search the full history of any conversation directly from the chat screen: . | Open a conversation (a channel or a direct message). | Tap the search icon in the top bar. | Type into the Search messages… field. The search runs as you type, across all stored messages in that conversation. | Use the N / M result counter and the previous / next arrows to jump between matches, which are highlighted in the conversation. | . 💡 Tip: Search is full-text and stays within the conversation you opened it from — it doesn’t search across other channels or contacts. It matches against the messages already stored on your device, so it works fully offline. 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. Text Formatting . Messages support lightweight inline Markdown. Received messages render the styling with the syntax characters removed: . | Type | Syntax | Renders as | . | Bold | **bold** | bold | . | Italic | *italic* | italic | . | Strikethrough | ~~strike~~ | strike | . | Inline code | `code` | monospace code | . | Link | [label](https://example.com) | a tappable label | . When composing, focus the message field and type at least three characters to reveal a formatting toolbar below the input. Select text and tap a style to wrap it (tap again to remove it); with no selection, a style inserts an empty pair with the cursor between the markers. The link button opens a dialog to enter a URL. As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 Tip: Formatting is carried as literal characters on the mesh — the same bytes iOS sends. Clients that don’t support Markdown (older apps, plain firmware clients) will show the raw **/~~ characters. URLs, email addresses, and phone numbers are still auto-linked whether or not you use Markdown. Mentions . Type @ while composing to mention a node — a picker suggests matching contacts as you type. In a received message, a mention appears as a highlighted chip showing the node’s name; tap it to jump straight to that node’s detail page. Reactions . React to messages with emoji: . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. Message Actions . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | Reply — quote the message in your response | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . Message Priority . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . Message Limits . | Maximum length: 200 bytes (approximately 200 characters for ASCII text) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | Rate limiting: The mesh enforces airtime fairness; heavy message volume may be throttled | Delivery: Messages are retried automatically if no acknowledgment is received | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/messages-and-channels.html#message-features",
    
    "relUrl": "/ca-rES/user/messages-and-channels.html#message-features"
  },"2478": {
    "doc": "Messages & Channels",
    "title": "Best Practices",
    "content": ". | 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 | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/messages-and-channels.html#best-practices",
    
    "relUrl": "/ca-rES/user/messages-and-channels.html#best-practices"
  },"2479": {
    "doc": "Messages & Channels",
    "title": "Related Topics",
    "content": ". | Nodes — tap a node to start a direct message | Settings — Radio & User — configure channel encryption and presets | MQTT — bridge channel messages to the internet | Channel configuration — detailed channel settings on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/messages-and-channels.html#related-topics",
    
    "relUrl": "/ca-rES/user/messages-and-channels.html#related-topics"
  },"2480": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": " ",
    "url": "/Meshtastic-Android/main/ca-rES/user/messages-and-channels.html",
    
    "relUrl": "/ca-rES/user/messages-and-channels.html"
  },"2481": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": "Meshtastic supports two communication modes: channel broadcasts and direct messages. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/messages-and-channels.html#messages--channels",
    
    "relUrl": "/ko-rKR/user/messages-and-channels.html#messages--channels"
  },"2482": {
    "doc": "Messages & Channels",
    "title": "채널",
    "content": "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 radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. Channel Security . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | Icon | What it means | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: 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 . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/messages-and-channels.html#%EC%B1%84%EB%84%90",
    
    "relUrl": "/ko-rKR/user/messages-and-channels.html#채널"
  },"2483": {
    "doc": "Messages & Channels",
    "title": "Direct Messages",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. Sending a Direct Message . | Open the Messages tab. | Select a conversation, or tap a node in the node list. | Type your message and tap Send. | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. Message States . A status label appears under your own outgoing messages only (incoming messages from others show no status label): . | State | Meaning | . | Sending… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | Delivered to recipient | The strongest confirmation for a direct message — an acknowledgment came back | . | Delivered to mesh | For a channel broadcast, the message reached the mesh (broadcasts have no per-recipient ack) | . | Relayed, not confirmed by recipient | For a direct message, shown in a warning color — the message was relayed but no acknowledgment has come back yet | . | Routing via SF++ chain… | Being routed/buffered by the Store & Forward Plus Plus chain | . | Confirmed on SF++ chain | Confirmed delivered via the SF++ chain | . | Error | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Error | Meaning | What to Do | . | 루트 없음 | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Rate limited | The mesh is throttling you for sending too fast | Wait before sending again. | . | Not authorized | The destination refused the request | Check you have the right channel and keys for that node. | . | Recipient needs your key | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | Recipient key unavailable | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | Could not send encrypted message | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Admin session expired | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Admin key not authorized | The target node does not accept your admin key | Verify the admin key matches on both nodes. | . | Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. | . | Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. | . | No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. | . | Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. | . | Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/messages-and-channels.html#direct-messages",
    
    "relUrl": "/ko-rKR/user/messages-and-channels.html#direct-messages"
  },"2484": {
    "doc": "Messages & Channels",
    "title": "Message Features",
    "content": "Quick Chat . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Searching Messages . You can search the full history of any conversation directly from the chat screen: . | Open a conversation (a channel or a direct message). | Tap the search icon in the top bar. | Type into the Search messages… field. The search runs as you type, across all stored messages in that conversation. | Use the N / M result counter and the previous / next arrows to jump between matches, which are highlighted in the conversation. | . 💡 Tip: Search is full-text and stays within the conversation you opened it from — it doesn’t search across other channels or contacts. It matches against the messages already stored on your device, so it works fully offline. 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. Text Formatting . Messages support lightweight inline Markdown. Received messages render the styling with the syntax characters removed: . | 타입 | Syntax | Renders as | . | Bold | **bold** | bold | . | Italic | *italic* | italic | . | Strikethrough | ~~strike~~ | strike | . | Inline code | `code` | monospace code | . | Link | [label](https://example.com) | a tappable label | . When composing, focus the message field and type at least three characters to reveal a formatting toolbar below the input. Select text and tap a style to wrap it (tap again to remove it); with no selection, a style inserts an empty pair with the cursor between the markers. The link button opens a dialog to enter a URL. As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 Tip: Formatting is carried as literal characters on the mesh — the same bytes iOS sends. Clients that don’t support Markdown (older apps, plain firmware clients) will show the raw **/~~ characters. URLs, email addresses, and phone numbers are still auto-linked whether or not you use Markdown. Mentions . Type @ while composing to mention a node — a picker suggests matching contacts as you type. In a received message, a mention appears as a highlighted chip showing the node’s name; tap it to jump straight to that node’s detail page. Reactions . React to messages with emoji: . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. Message Actions . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | Reply — quote the message in your response | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . Message Priority . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . Message Limits . | Maximum length: 200 bytes (approximately 200 characters for ASCII text) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | Rate limiting: The mesh enforces airtime fairness; heavy message volume may be throttled | Delivery: Messages are retried automatically if no acknowledgment is received | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/messages-and-channels.html#message-features",
    
    "relUrl": "/ko-rKR/user/messages-and-channels.html#message-features"
  },"2485": {
    "doc": "Messages & Channels",
    "title": "Best Practices",
    "content": ". | 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 | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/messages-and-channels.html#best-practices",
    
    "relUrl": "/ko-rKR/user/messages-and-channels.html#best-practices"
  },"2486": {
    "doc": "Messages & Channels",
    "title": "Related Topics",
    "content": ". | Nodes — tap a node to start a direct message | Settings — Radio & User — configure channel encryption and presets | MQTT — bridge channel messages to the internet | Channel configuration — detailed channel settings on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/messages-and-channels.html#related-topics",
    
    "relUrl": "/ko-rKR/user/messages-and-channels.html#related-topics"
  },"2487": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": " ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/messages-and-channels.html",
    
    "relUrl": "/ko-rKR/user/messages-and-channels.html"
  },"2488": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": "Meshtastic supports two communication modes: channel broadcasts and direct messages. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/messages-and-channels.html#messages--channels",
    
    "relUrl": "/sv-rSE/user/messages-and-channels.html#messages--channels"
  },"2489": {
    "doc": "Messages & Channels",
    "title": "Kanaler",
    "content": "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 radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. Kanalsäkerhet . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | Icon | What it means | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: 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 . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/messages-and-channels.html#kanaler",
    
    "relUrl": "/sv-rSE/user/messages-and-channels.html#kanaler"
  },"2490": {
    "doc": "Messages & Channels",
    "title": "Direct Messages",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. Sending a Direct Message . | Open the Messages tab. | Select a conversation, or tap a node in the node list. | Type your message and tap Send. | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. Message States . A status label appears under your own outgoing messages only (incoming messages from others show no status label): . | State | Meaning | . | Sending… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | Delivered to recipient | The strongest confirmation for a direct message — an acknowledgment came back | . | Levererad till nät | For a channel broadcast, the message reached the mesh (broadcasts have no per-recipient ack) | . | Relayed, not confirmed by recipient | For a direct message, shown in a warning color — the message was relayed but no acknowledgment has come back yet | . | Routing via SF++ chain… | Being routed/buffered by the Store & Forward Plus Plus chain | . | Confirmed on SF++ chain | Confirmed delivered via the SF++ chain | . | Fel | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Fel | Meaning | What to Do | . | Ingen rutt | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Rate limited | The mesh is throttling you for sending too fast | Wait before sending again. | . | Not authorized | The destination refused the request | Check you have the right channel and keys for that node. | . | Recipient needs your key | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | Recipient key unavailable | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | Could not send encrypted message | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Admin session expired | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Admin key not authorized | The target node does not accept your admin key | Verify the admin key matches on both nodes. | . | Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. | . | Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. | . | No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. | . | Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. | . | Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/messages-and-channels.html#direct-messages",
    
    "relUrl": "/sv-rSE/user/messages-and-channels.html#direct-messages"
  },"2491": {
    "doc": "Messages & Channels",
    "title": "Message Features",
    "content": "Quick Chat . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Searching Messages . You can search the full history of any conversation directly from the chat screen: . | Open a conversation (a channel or a direct message). | Tap the search icon in the top bar. | Type into the Search messages… field. The search runs as you type, across all stored messages in that conversation. | Use the N / M result counter and the previous / next arrows to jump between matches, which are highlighted in the conversation. | . 💡 Tip: Search is full-text and stays within the conversation you opened it from — it doesn’t search across other channels or contacts. It matches against the messages already stored on your device, so it works fully offline. 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. Text Formatting . Messages support lightweight inline Markdown. Received messages render the styling with the syntax characters removed: . | Typ | Syntax | Renders as | . | Bold | **bold** | bold | . | Italic | *italic* | italic | . | Strikethrough | ~~strike~~ | strike | . | Inline code | `code` | monospace code | . | Link | [label](https://example.com) | a tappable label | . When composing, focus the message field and type at least three characters to reveal a formatting toolbar below the input. Select text and tap a style to wrap it (tap again to remove it); with no selection, a style inserts an empty pair with the cursor between the markers. The link button opens a dialog to enter a URL. As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 Tip: Formatting is carried as literal characters on the mesh — the same bytes iOS sends. Clients that don’t support Markdown (older apps, plain firmware clients) will show the raw **/~~ characters. URLs, email addresses, and phone numbers are still auto-linked whether or not you use Markdown. Mentions . Type @ while composing to mention a node — a picker suggests matching contacts as you type. In a received message, a mention appears as a highlighted chip showing the node’s name; tap it to jump straight to that node’s detail page. Reactions . React to messages with emoji: . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. Message Actions . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | Reply — quote the message in your response | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . Message Priority . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . Message Limits . | Maximum length: 200 bytes (approximately 200 characters for ASCII text) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | Rate limiting: The mesh enforces airtime fairness; heavy message volume may be throttled | Delivery: Messages are retried automatically if no acknowledgment is received | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/messages-and-channels.html#message-features",
    
    "relUrl": "/sv-rSE/user/messages-and-channels.html#message-features"
  },"2492": {
    "doc": "Messages & Channels",
    "title": "Best Practices",
    "content": ". | 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 | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/messages-and-channels.html#best-practices",
    
    "relUrl": "/sv-rSE/user/messages-and-channels.html#best-practices"
  },"2493": {
    "doc": "Messages & Channels",
    "title": "Related Topics",
    "content": ". | Nodes — tap a node to start a direct message | Settings — Radio & User — configure channel encryption and presets | MQTT — bridge channel messages to the internet | Channel configuration — detailed channel settings on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/messages-and-channels.html#related-topics",
    
    "relUrl": "/sv-rSE/user/messages-and-channels.html#related-topics"
  },"2494": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": " ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/messages-and-channels.html",
    
    "relUrl": "/sv-rSE/user/messages-and-channels.html"
  },"2495": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": "Meshtastic supports two communication modes: channel broadcasts and direct messages. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/messages-and-channels.html#messages--channels",
    
    "relUrl": "/ht-rHT/user/messages-and-channels.html#messages--channels"
  },"2496": {
    "doc": "Messages & Channels",
    "title": "Channels",
    "content": "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 radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. Channel Security . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | Icon | What it means | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: 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 . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/messages-and-channels.html#channels",
    
    "relUrl": "/ht-rHT/user/messages-and-channels.html#channels"
  },"2497": {
    "doc": "Messages & Channels",
    "title": "Direct Messages",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. Sending a Direct Message . | Open the Messages tab. | Select a conversation, or tap a node in the node list. | Type your message and tap Send. | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. Message States . A status label appears under your own outgoing messages only (incoming messages from others show no status label): . | State | Meaning | . | Sending… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | Delivered to recipient | The strongest confirmation for a direct message — an acknowledgment came back | . | Delivered to mesh | For a channel broadcast, the message reached the mesh (broadcasts have no per-recipient ack) | . | Relayed, not confirmed by recipient | For a direct message, shown in a warning color — the message was relayed but no acknowledgment has come back yet | . | Routing via SF++ chain… | Being routed/buffered by the Store & Forward Plus Plus chain | . | Confirmed on SF++ chain | Confirmed delivered via the SF++ chain | . | Erè | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Erè | Meaning | What to Do | . | Pa gen wout | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Rate limited | The mesh is throttling you for sending too fast | Wait before sending again. | . | Not authorized | The destination refused the request | Check you have the right channel and keys for that node. | . | Recipient needs your key | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | Recipient key unavailable | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | Could not send encrypted message | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Admin session expired | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Admin key not authorized | The target node does not accept your admin key | Verify the admin key matches on both nodes. | . | Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. | . | Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. | . | No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. | . | Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. | . | Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/messages-and-channels.html#direct-messages",
    
    "relUrl": "/ht-rHT/user/messages-and-channels.html#direct-messages"
  },"2498": {
    "doc": "Messages & Channels",
    "title": "Message Features",
    "content": "Quick Chat . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Searching Messages . You can search the full history of any conversation directly from the chat screen: . | Open a conversation (a channel or a direct message). | Tap the search icon in the top bar. | Type into the Search messages… field. The search runs as you type, across all stored messages in that conversation. | Use the N / M result counter and the previous / next arrows to jump between matches, which are highlighted in the conversation. | . 💡 Tip: Search is full-text and stays within the conversation you opened it from — it doesn’t search across other channels or contacts. It matches against the messages already stored on your device, so it works fully offline. 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. Text Formatting . Messages support lightweight inline Markdown. Received messages render the styling with the syntax characters removed: . | Type | Syntax | Renders as | . | Bold | **bold** | bold | . | Italic | *italic* | italic | . | Strikethrough | ~~strike~~ | strike | . | Inline code | `code` | monospace code | . | Link | [label](https://example.com) | a tappable label | . When composing, focus the message field and type at least three characters to reveal a formatting toolbar below the input. Select text and tap a style to wrap it (tap again to remove it); with no selection, a style inserts an empty pair with the cursor between the markers. The link button opens a dialog to enter a URL. As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 Tip: Formatting is carried as literal characters on the mesh — the same bytes iOS sends. Clients that don’t support Markdown (older apps, plain firmware clients) will show the raw **/~~ characters. URLs, email addresses, and phone numbers are still auto-linked whether or not you use Markdown. Mentions . Type @ while composing to mention a node — a picker suggests matching contacts as you type. In a received message, a mention appears as a highlighted chip showing the node’s name; tap it to jump straight to that node’s detail page. Reactions . React to messages with emoji: . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. Message Actions . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | Reply — quote the message in your response | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . Message Priority . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . Message Limits . | Maximum length: 200 bytes (approximately 200 characters for ASCII text) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | Rate limiting: The mesh enforces airtime fairness; heavy message volume may be throttled | Delivery: Messages are retried automatically if no acknowledgment is received | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/messages-and-channels.html#message-features",
    
    "relUrl": "/ht-rHT/user/messages-and-channels.html#message-features"
  },"2499": {
    "doc": "Messages & Channels",
    "title": "Best Practices",
    "content": ". | 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 | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/messages-and-channels.html#best-practices",
    
    "relUrl": "/ht-rHT/user/messages-and-channels.html#best-practices"
  },"2500": {
    "doc": "Messages & Channels",
    "title": "Related Topics",
    "content": ". | Nodes — tap a node to start a direct message | Settings — Radio & User — configure channel encryption and presets | MQTT — bridge channel messages to the internet | Channel configuration — detailed channel settings on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/messages-and-channels.html#related-topics",
    
    "relUrl": "/ht-rHT/user/messages-and-channels.html#related-topics"
  },"2501": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": " ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/messages-and-channels.html",
    
    "relUrl": "/ht-rHT/user/messages-and-channels.html"
  },"2502": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": "Meshtastic supports two communication modes: channel broadcasts and direct messages. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/messages-and-channels.html#messages--channels",
    
    "relUrl": "/sr-rLatn/user/messages-and-channels.html#messages--channels"
  },"2503": {
    "doc": "Messages & Channels",
    "title": "Канали",
    "content": "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 radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. Channel Security . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | Иконица | What it means | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: 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 . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/messages-and-channels.html#%D0%BA%D0%B0%D0%BD%D0%B0%D0%BB%D0%B8",
    
    "relUrl": "/sr-rLatn/user/messages-and-channels.html#канали"
  },"2504": {
    "doc": "Messages & Channels",
    "title": "Директне поруке",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. Sending a Direct Message . | Open the Messages tab. | Select a conversation, or tap a node in the node list. | Type your message and tap Send. | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. Message States . A status label appears under your own outgoing messages only (incoming messages from others show no status label): . | State | Meaning | . | Sending… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | Delivered to recipient | The strongest confirmation for a direct message — an acknowledgment came back | . | Delivered to mesh | For a channel broadcast, the message reached the mesh (broadcasts have no per-recipient ack) | . | Relayed, not confirmed by recipient | For a direct message, shown in a warning color — the message was relayed but no acknowledgment has come back yet | . | Routing via SF++ chain… | Being routed/buffered by the Store & Forward Plus Plus chain | . | Confirmed on SF++ chain | Confirmed delivered via the SF++ chain | . | Грешка | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Грешка | Meaning | What to Do | . | Nema rute | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Rate limited | The mesh is throttling you for sending too fast | Wait before sending again. | . | Not authorized | The destination refused the request | Check you have the right channel and keys for that node. | . | Recipient needs your key | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | Recipient key unavailable | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | Could not send encrypted message | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Admin session expired | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Admin key not authorized | The target node does not accept your admin key | Verify the admin key matches on both nodes. | . | Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. | . | Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. | . | No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. | . | Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. | . | Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/messages-and-channels.html#%D0%B4%D0%B8%D1%80%D0%B5%D0%BA%D1%82%D0%BD%D0%B5-%D0%BF%D0%BE%D1%80%D1%83%D0%BA%D0%B5",
    
    "relUrl": "/sr-rLatn/user/messages-and-channels.html#директне-поруке"
  },"2505": {
    "doc": "Messages & Channels",
    "title": "Message Features",
    "content": "Quick Chat . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Searching Messages . You can search the full history of any conversation directly from the chat screen: . | Open a conversation (a channel or a direct message). | Tap the search icon in the top bar. | Type into the Search messages… field. The search runs as you type, across all stored messages in that conversation. | Use the N / M result counter and the previous / next arrows to jump between matches, which are highlighted in the conversation. | . 💡 Tip: Search is full-text and stays within the conversation you opened it from — it doesn’t search across other channels or contacts. It matches against the messages already stored on your device, so it works fully offline. 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. Text Formatting . Messages support lightweight inline Markdown. Received messages render the styling with the syntax characters removed: . | Type | Syntax | Renders as | . | Bold | **bold** | bold | . | Italic | *italic* | italic | . | Strikethrough | ~~strike~~ | strike | . | Inline code | `code` | monospace code | . | Link | [label](https://example.com) | a tappable label | . When composing, focus the message field and type at least three characters to reveal a formatting toolbar below the input. Select text and tap a style to wrap it (tap again to remove it); with no selection, a style inserts an empty pair with the cursor between the markers. The link button opens a dialog to enter a URL. As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 Tip: Formatting is carried as literal characters on the mesh — the same bytes iOS sends. Clients that don’t support Markdown (older apps, plain firmware clients) will show the raw **/~~ characters. URLs, email addresses, and phone numbers are still auto-linked whether or not you use Markdown. Mentions . Type @ while composing to mention a node — a picker suggests matching contacts as you type. In a received message, a mention appears as a highlighted chip showing the node’s name; tap it to jump straight to that node’s detail page. Reactions . React to messages with emoji: . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. Message Actions . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | Reply — quote the message in your response | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . Message Priority . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . Message Limits . | Maximum length: 200 bytes (approximately 200 characters for ASCII text) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | Rate limiting: The mesh enforces airtime fairness; heavy message volume may be throttled | Delivery: Messages are retried automatically if no acknowledgment is received | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/messages-and-channels.html#message-features",
    
    "relUrl": "/sr-rLatn/user/messages-and-channels.html#message-features"
  },"2506": {
    "doc": "Messages & Channels",
    "title": "Best Practices",
    "content": ". | 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 | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/messages-and-channels.html#best-practices",
    
    "relUrl": "/sr-rLatn/user/messages-and-channels.html#best-practices"
  },"2507": {
    "doc": "Messages & Channels",
    "title": "Related Topics",
    "content": ". | Nodes — tap a node to start a direct message | Settings — Radio & User — configure channel encryption and presets | MQTT — bridge channel messages to the internet | Channel configuration — detailed channel settings on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/messages-and-channels.html#related-topics",
    
    "relUrl": "/sr-rLatn/user/messages-and-channels.html#related-topics"
  },"2508": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": " ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/messages-and-channels.html",
    
    "relUrl": "/sr-rLatn/user/messages-and-channels.html"
  },"2509": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": "Meshtastic supports two communication modes: channel broadcasts and direct messages. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/messages-and-channels.html#messages--channels",
    
    "relUrl": "/nl-rNL/user/messages-and-channels.html#messages--channels"
  },"2510": {
    "doc": "Messages & Channels",
    "title": "Kanalen",
    "content": "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 radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. Channel Security . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | Icon | What it means | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: 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 . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/messages-and-channels.html#kanalen",
    
    "relUrl": "/nl-rNL/user/messages-and-channels.html#kanalen"
  },"2511": {
    "doc": "Messages & Channels",
    "title": "Direct Messages",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. Sending a Direct Message . | Open the Messages tab. | Select a conversation, or tap a node in the node list. | Type your message and tap Send. | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. Message States . A status label appears under your own outgoing messages only (incoming messages from others show no status label): . | State | Meaning | . | Sending… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | Delivered to recipient | The strongest confirmation for a direct message — an acknowledgment came back | . | Delivered to mesh | For a channel broadcast, the message reached the mesh (broadcasts have no per-recipient ack) | . | Relayed, not confirmed by recipient | For a direct message, shown in a warning color — the message was relayed but no acknowledgment has come back yet | . | Routing via SF++ chain… | Being routed/buffered by the Store & Forward Plus Plus chain | . | Confirmed on SF++ chain | Confirmed delivered via the SF++ chain | . | Foutmelding | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Foutmelding | Meaning | What to Do | . | Geen route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Rate limited | The mesh is throttling you for sending too fast | Wait before sending again. | . | Not authorized | The destination refused the request | Check you have the right channel and keys for that node. | . | Recipient needs your key | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | Recipient key unavailable | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | Could not send encrypted message | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Admin session expired | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Admin key not authorized | The target node does not accept your admin key | Verify the admin key matches on both nodes. | . | Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. | . | Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. | . | No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. | . | Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. | . | Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/messages-and-channels.html#direct-messages",
    
    "relUrl": "/nl-rNL/user/messages-and-channels.html#direct-messages"
  },"2512": {
    "doc": "Messages & Channels",
    "title": "Message Features",
    "content": "Quick Chat . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Searching Messages . You can search the full history of any conversation directly from the chat screen: . | Open a conversation (a channel or a direct message). | Tap the search icon in the top bar. | Type into the Search messages… field. The search runs as you type, across all stored messages in that conversation. | Use the N / M result counter and the previous / next arrows to jump between matches, which are highlighted in the conversation. | . 💡 Tip: Search is full-text and stays within the conversation you opened it from — it doesn’t search across other channels or contacts. It matches against the messages already stored on your device, so it works fully offline. 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. Text Formatting . Messages support lightweight inline Markdown. Received messages render the styling with the syntax characters removed: . | Type | Syntax | Renders as | . | Bold | **bold** | bold | . | Italic | *italic* | italic | . | Strikethrough | ~~strike~~ | strike | . | Inline code | `code` | monospace code | . | Link | [label](https://example.com) | a tappable label | . When composing, focus the message field and type at least three characters to reveal a formatting toolbar below the input. Select text and tap a style to wrap it (tap again to remove it); with no selection, a style inserts an empty pair with the cursor between the markers. The link button opens a dialog to enter a URL. As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 Tip: Formatting is carried as literal characters on the mesh — the same bytes iOS sends. Clients that don’t support Markdown (older apps, plain firmware clients) will show the raw **/~~ characters. URLs, email addresses, and phone numbers are still auto-linked whether or not you use Markdown. Mentions . Type @ while composing to mention a node — a picker suggests matching contacts as you type. In a received message, a mention appears as a highlighted chip showing the node’s name; tap it to jump straight to that node’s detail page. Reactions . React to messages with emoji: . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. Message Actions . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | Reply — quote the message in your response | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . Message Priority . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . Message Limits . | Maximum length: 200 bytes (approximately 200 characters for ASCII text) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | Rate limiting: The mesh enforces airtime fairness; heavy message volume may be throttled | Delivery: Messages are retried automatically if no acknowledgment is received | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/messages-and-channels.html#message-features",
    
    "relUrl": "/nl-rNL/user/messages-and-channels.html#message-features"
  },"2513": {
    "doc": "Messages & Channels",
    "title": "Best Practices",
    "content": ". | 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 | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/messages-and-channels.html#best-practices",
    
    "relUrl": "/nl-rNL/user/messages-and-channels.html#best-practices"
  },"2514": {
    "doc": "Messages & Channels",
    "title": "Related Topics",
    "content": ". | Nodes — tap a node to start a direct message | Settings — Radio & User — configure channel encryption and presets | MQTT — bridge channel messages to the internet | Channel configuration — detailed channel settings on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/messages-and-channels.html#related-topics",
    
    "relUrl": "/nl-rNL/user/messages-and-channels.html#related-topics"
  },"2515": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": " ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/messages-and-channels.html",
    
    "relUrl": "/nl-rNL/user/messages-and-channels.html"
  },"2516": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": "Meshtastic supports two communication modes: channel broadcasts and direct messages. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/messages-and-channels.html#messages--channels",
    
    "relUrl": "/uk-rUA/user/messages-and-channels.html#messages--channels"
  },"2517": {
    "doc": "Messages & Channels",
    "title": "Канали",
    "content": "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 radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. Безпека каналу . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | Icon | What it means | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: 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 . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/messages-and-channels.html#%D0%BA%D0%B0%D0%BD%D0%B0%D0%BB%D0%B8",
    
    "relUrl": "/uk-rUA/user/messages-and-channels.html#канали"
  },"2518": {
    "doc": "Messages & Channels",
    "title": "Direct Messages",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. Sending a Direct Message . | Open the Messages tab. | Select a conversation, or tap a node in the node list. | Type your message and tap Send. | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. Message States . A status label appears under your own outgoing messages only (incoming messages from others show no status label): . | State | Meaning | . | Sending… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | Delivered to recipient | The strongest confirmation for a direct message — an acknowledgment came back | . | Доставлено в мережу | For a channel broadcast, the message reached the mesh (broadcasts have no per-recipient ack) | . | Relayed, not confirmed by recipient | For a direct message, shown in a warning color — the message was relayed but no acknowledgment has come back yet | . | Маршрутизація через SF++ ланцюжок… | Being routed/buffered by the Store & Forward Plus Plus chain | . | Підтверджений на ланцюжку SF++ | Confirmed delivered via the SF++ chain | . | Error | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Error | Meaning | What to Do | . | Маршрут відсутній | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Rate limited | The mesh is throttling you for sending too fast | Wait before sending again. | . | Not authorized | The destination refused the request | Check you have the right channel and keys for that node. | . | Recipient needs your key | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | Recipient key unavailable | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | Could not send encrypted message | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Admin session expired | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Admin key not authorized | The target node does not accept your admin key | Verify the admin key matches on both nodes. | . | Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. | . | Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. | . | No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. | . | Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. | . | Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/messages-and-channels.html#direct-messages",
    
    "relUrl": "/uk-rUA/user/messages-and-channels.html#direct-messages"
  },"2519": {
    "doc": "Messages & Channels",
    "title": "Message Features",
    "content": "Quick Chat . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Searching Messages . You can search the full history of any conversation directly from the chat screen: . | Open a conversation (a channel or a direct message). | Tap the search icon in the top bar. | Type into the Search messages… field. The search runs as you type, across all stored messages in that conversation. | Use the N / M result counter and the previous / next arrows to jump between matches, which are highlighted in the conversation. | . 💡 Tip: Search is full-text and stays within the conversation you opened it from — it doesn’t search across other channels or contacts. It matches against the messages already stored on your device, so it works fully offline. 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. Text Formatting . Messages support lightweight inline Markdown. Received messages render the styling with the syntax characters removed: . | Тип | Syntax | Renders as | . | Bold | **bold** | bold | . | Italic | *italic* | italic | . | Strikethrough | ~~strike~~ | strike | . | Inline code | `code` | monospace code | . | Link | [label](https://example.com) | a tappable label | . When composing, focus the message field and type at least three characters to reveal a formatting toolbar below the input. Select text and tap a style to wrap it (tap again to remove it); with no selection, a style inserts an empty pair with the cursor between the markers. The link button opens a dialog to enter a URL. As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 Tip: Formatting is carried as literal characters on the mesh — the same bytes iOS sends. Clients that don’t support Markdown (older apps, plain firmware clients) will show the raw **/~~ characters. URLs, email addresses, and phone numbers are still auto-linked whether or not you use Markdown. Mentions . Type @ while composing to mention a node — a picker suggests matching contacts as you type. In a received message, a mention appears as a highlighted chip showing the node’s name; tap it to jump straight to that node’s detail page. Reactions . React to messages with emoji: . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. Message Actions . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | Reply — quote the message in your response | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . Message Priority . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . Message Limits . | Maximum length: 200 bytes (approximately 200 characters for ASCII text) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | Rate limiting: The mesh enforces airtime fairness; heavy message volume may be throttled | Delivery: Messages are retried automatically if no acknowledgment is received | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/messages-and-channels.html#message-features",
    
    "relUrl": "/uk-rUA/user/messages-and-channels.html#message-features"
  },"2520": {
    "doc": "Messages & Channels",
    "title": "Best Practices",
    "content": ". | 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 | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/messages-and-channels.html#best-practices",
    
    "relUrl": "/uk-rUA/user/messages-and-channels.html#best-practices"
  },"2521": {
    "doc": "Messages & Channels",
    "title": "Related Topics",
    "content": ". | Nodes — tap a node to start a direct message | Settings — Radio & User — configure channel encryption and presets | MQTT — bridge channel messages to the internet | Channel configuration — detailed channel settings on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/messages-and-channels.html#related-topics",
    
    "relUrl": "/uk-rUA/user/messages-and-channels.html#related-topics"
  },"2522": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": " ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/messages-and-channels.html",
    
    "relUrl": "/uk-rUA/user/messages-and-channels.html"
  },"2523": {
    "doc": "Viestit ja kanavat",
    "title": "Viestit ja kanavat",
    "content": "Meshtastic tukee kahta viestintätilaa: kanavaviestit ja suoraviestit. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/messages-and-channels.html",
    
    "relUrl": "/fi-rFI/user/messages-and-channels.html"
  },"2524": {
    "doc": "Viestit ja kanavat",
    "title": "Kanavat",
    "content": "Kanavat ovat jaettuja viestintäryhmiä. Kaikki radiot, jotka on määritetty samalla kanava-avaimella, voivat lukea ja lähettää viestejä kyseisellä kanavalla. Oletuskanava . Jokaisessa Meshtastic-radiossa on oletuksena LongFast-kanava. Se on salattu tunnetulla oletusavaimella, joten kuka tahansa, joka käyttää Meshtasticia samalla esiasetuksella, voi lukea sen. Kanavan turvallisuus . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | Ikoni | Mitä se tarkoittaa | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Tietoturva: Määritä yksityistä viestintää varten aina yksilöllinen PSK. Oletuskanava on tarkoituksella avoin, jotta uudet käyttäjät löytävät mesh-verkon — luo erillinen salattu kanava arkaluontoiselle viestinnälle. Kanavan lisääminen . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/messages-and-channels.html#kanavat",
    
    "relUrl": "/fi-rFI/user/messages-and-channels.html#kanavat"
  },"2525": {
    "doc": "Viestit ja kanavat",
    "title": "Yksityisviestit",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. Yksityisviestin lähettäminen . | Avaa Viestit-välilehti. | Valitse keskustelu tai napauta radiota Radiot-luettelossa. | Kirjoita viesti ja napauta Lähetä. | . Keskusteluluettelon hallinta . Viestit-välilehdellä näkyvät keskustelusi. Jokainen rivi näyttää tärkeimmät tiedot yhdellä silmäyksellä, ja voit toimia suoraan riviltä: . | Lähettämättömät luonnokset säilyvät. Kirjoita viesti keskusteluun ja poistu lähettämättä sitä, niin teksti on edelleen tallessa, kun palaat. Rivillä näkyy viimeisimmän viestin sijasta Draft: … — lähettämätön luonnos pitää rivin ylimpänä. | Lukematon-merkki: Laskuri näkyy rivillä, kunnes avaat keskustelun. | Pyyhkäise oikealle mykistääksesi (pyyhkäise uudelleen poistaaksesi mykistyksen) ja pyyhkäise vasemmalle poistaaksesi. Poistaminen kysyy ensin vahvistuksen, mykistäminen näyttää Kumoa-toiminnon sisältävän ilmoituspalkin. | Kosketa pitkään valitaksesi yhden tai useamman keskustelun ja käytä sitten toimintopalkkia niiden kiinnittämiseen, merkitsemiseen lukemattomiksi, mykistämiseen tai poistamiseen yhdessä. Kiinnitetyissä keskusteluissa näkyy nuppineulamerkki, ja ne siirtyvät oman osionsa alkuun. | Luettelo on jaettu Kanaviin ja Suoraviesteihin, joilla kummallakin on oma kutistettava otsikkonsa ja jotka lajitellaan erikseen — siksi kiinnitetty suoraviesti nousee oman osionsa alkuun, ei Kanavat-osion yläpuolelle. | . Keskustelukuplat . Android 11:ssä ja uudemmissa versioissa viesti-ilmoituksen voi avata kelluvana kuplana, joka pysyy muiden sovellusten päällä. Napauta ilmoituksen kuplakuvaketta ottaaksesi keskustelun käyttöön kuplana. Android muistaa valinnan keskustelukohtaisesti, ja järjestelmän Kuplat-asetukset määrittävät, tarjotaanko niitä lainkaan. Viestin tilat . Tilateksti näkyy vain omissa lähtevissä viesteissäsi (muiden lähettämissä saapuvissa viesteissä ei näytetä tilaa): . | Tila | Merkitys | . | Lähetetään… | Jonossa tai jo välitetty radiolle, mutta lopullista tilaa ei ole vielä vahvistettu. Molemmissa vaiheissa näkyy sama teksti, mutta kuvake ja väri vaihtuvat etenemisen mukaan — jonossa näkyy keltainen lähetyspilvi, ja kun radio on vastaanottanut sen, sininen nuoli | . | Toimitettu vastaanottajalle | Vahvin mahdollinen vahvistus suoralle viestille — vastaanottokuittaus on saatu | . | Toimitettu mesh-verkkoon | Kanavalähetyksessä viesti on saavuttanut mesh-verkon (kanavalähetyksille ei lähetetä vastaanottajakohtaista kuittausta) | . | Välitetty, mutta vastaanottaja ei ole vahvistanut vastaanottoa | Suorassa viestissä tämä näytetään varoitusvärillä — viesti on välitetty eteenpäin, mutta vastaanottokuittausta ei ole vielä saatu | . | Reititetään SF++ ketjun kautta… | Reititetty tai puskuroitu varastoi & välitä Plus Plus -ketjussa | . | Vahvistettu SF++-ketjussa | Toimitus vahvistettu varastoi & välitä++ -ketjun kautta | . | Virhe | Viestin toimitus epäonnistui — napauta tilaa nähdäksesi tarkan syyn (katso Toimitusvirheet) | . Toimitusvirheet . Kun viestin toimitus epäonnistuu, virheilmaisin näyttää, mikä meni pieleen: . | Virhe | Merkitys | Toimenpiteet | . | Ei reittiä | Kohderadioon ei ole reittiä | Vastaanottaja voi olla offline-tilassa tai verkon kantaman ulkopuolella. Yritä myöhemmin tai siirry lähemmäksi. | . | Ei radioliitäntää | Lähetykseen ei ole käytettävissä radioliitäntää | Varmista, että radiosi on yhdistetty ja käytettävissä. | . | Toimitus mesh-verkkoon epäonnistui | Uudelleenyritykset käytetty loppuun. Sama ilmoitus kattaa kolme eri syytä — välityksen hylkäys (NAK), aikakatkaisu tai uudelleenyritysten loppuminen | Siirry lähemmäs, paranna signaalia tai odota olosuhteiden paranevan. Napauta virhettä nähdäksesi tarkan syyn. | . | Lähetysrajoitus saavutettu | Mesh-verkko rajoittaa lähetysnopeuttasi | Odota hetki ennen seuraavan viestin lähettämistä. | . | Ei valtuuksia | Kohde hylkäsi pyynnön | Tarkista, että käytössä on oikea kanava ja oikeat avaimet kyseiselle radiolle. | . | Vastaanottaja tarvitsee avaimesi | Suoraviestin salausta ei voitu suorittaa loppuun, koska toisella radiolla ei vielä ole julkista avaintasi | Vaihda radiotiedot — julkinen avain välittyy niiden mukana. Yleistä ensimmäisessä suoraviestissä uudelle yhteystiedolle. | . | Vastaanottajan avain ei ole käytettävissä | Vastaanottajan julkinen avain puuttuu | Odota, että radion tiedot saapuvat, tai pyydä vastaanottajaa lähettämään ne. | . | Salattua viestiä ei voitu lähettää | Tämän suoraviestin salaus epäonnistui | Varmista, että molemmat radiot ovat vaihtaneet avaimet ja että niissä on yhteensopiva laiteohjelmisto. | . | Ylläpitoistunto on vanhentunut | Etähallintaistunnon aikakatkaisu | Avaa etäradion asetukset uudelleen aloittaaksesi uuden istunnon. | . | Ylläpitoavainta ei ole valtuutettu | Kohderadio ei hyväksy järjestelmänvalvojan avaintasi | Varmista, että ylläpitoavain on sama molemmissa radioissa. | . | Kanavan tai avaimen ristiriita | Kohteen kanava tai avain ei täsmää | Varmista, että molemmat radiot käyttävät samaa kanavaa ja PSK:ta. | . | Viesti on liian suuri lähetettäväksi | Viesti ylittää sallitun enimmäiskoon | Lyhennä viestiä ja yritä uudelleen. | . | Ei sovellusvastausta | Sovellus tai liitännäinen ei vastannut pyyntöön | Yritä uudelleen tai tarkista kohdesovelluksen tai moduulin tila. | . | Käyttöasteen rajoitus | Alueellinen lähetysajan raja saavutettu | Odota, että käyttöasteikkuna nollautuu. | . | Virheellinen pyyntö | Virheellinen tai puutteellinen pyyntö | Jos ongelma jatkuu, päivitä tai käynnistä sovellus uudelleen ja yritä sitten uudelleen. | . 💡 Vinkki: Useimmat toimitusvirheet korjaantuvat itsestään. Jos radio on ajoittain tavoitettavissa, mesh yrittää uudelleen. For persistent No route errors, check that intermediate Router nodes are online. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/messages-and-channels.html#yksityisviestit",
    
    "relUrl": "/fi-rFI/user/messages-and-channels.html#yksityisviestit"
  },"2526": {
    "doc": "Viestit ja kanavat",
    "title": "Viestiominaisuudet",
    "content": "Pikachatti . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Viestien haku . Voit hakea koko keskusteluhistorian suoraan chat-näkymästä: . | Avaa keskustelu (kanava tai suoraviesti). | Napauta hakukuvaketta yläpalkissa. | Kirjoita Etsi viestejä -kenttään. Haku toimii kirjoittaessa ja käy läpi kaikki tallennetut viestit kyseisessä keskustelussa. | Käytä N / M -laskuria ja edellinen/seuraava -nuolia siirtyäksesi osumien välillä, jotka on korostettu keskustelussa. | . 💡 Vinkki: Haku on täystekstihaku ja toimii vain siinä keskustelussa, josta avasit sen — se ei hae muista kanavista tai kontakteista. Se hakee osumat laitteellesi jo tallennetuista viesteistä, joten se toimii täysin offline-tilassa. Viestikuplat . Viestit näkyvät chat-kuplina — lähetetyt viestit oikealla, vastaanotetut vasemmalla. Jokainen kupla näyttää lähettäjän, aikaleiman ja toimitustilan. Vastaukselliset viestit sisältävät alkuperäisen viestin esikatselun vastauksen yläpuolella. Tekstin muotoilu . Viestit tukevat kevyttä rivinsisäistä Markdown-muotoilua. Vastaanotetut viestit näyttävät muotoilun ilman Markdown-syntaksimerkkejä: . | Kirjoita | Syntaksi | Näkyy muodossa | . | Lihavoitu | lihavoitu | lihavoitu | . | Kursivoitu | *kursivoitu* | kursivoitu | . | Yliviivattu | ~~yliviivattu~~ | yliviivattu | . | Rivinsisäinen koodi | `koodi` | tasalevyinen koodi | . | Linkki | [nimi](https://example.com) | napautettava nimi | . Kun kirjoitat viestiä, napauta viestikenttää ja kirjoita vähintään kolme merkkiä, niin kentän alle avautuu muotoilutyökalurivi. Valitse teksti ja napauta muotoilua lisätäksesi sen ympärille merkinnät (napauta uudelleen poistaaksesi ne). Jos tekstiä ei ole valittuna, muotoilu lisää tyhjän merkkiparin ja sijoittaa kohdistimen niiden väliin. Linkkipainike avaa valintaikkunan URL-osoitteen syöttämistä varten. Kirjoittaessasi kentässä näkyy muotoiltu teksti, mutta lähetettävä viesti sisältää edelleen Markdown-merkit. 💡 Vinkki: Muotoilu välitetään mesh-verkossa kirjaimellisina merkkeinä – samoina tavuina, jotka iOS lähettää. Sovellukset, jotka eivät tue Markdownia (vanhemmat sovellukset ja pelkkää laiteohjelmistoa käyttävät laitteet), näyttävät alkuperäiset **- ja ~~-merkit. URL-osoitteet, sähköpostiosoitteet ja puhelinnumerot muutetaan edelleen automaattisesti linkeiksi riippumatta siitä, käytätkö Markdownia. Maininnat . Kirjoita viestiä laatiessasi @ mainitaksesi radion — valitsin ehdottaa kirjoittaessasi vastaavia yhteystietoja. Vastaanotetussa viestissä maininta näkyy korostettuna tunnisteena, jossa näkyy radion nimi. Napauta sitä siirtyäksesi suoraan kyseisen radion tietosivulle. Reaktiot . Reagoi viesteihin emojeilla: . | Kosketa pitkään viestiä tai kaksoisnapauta sitä, niin viestin yläpuolelle avautuu pikareaktiopalkki. Palkin avaaminen ei lähetä mitään. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. Reaktio on oikea mesh-paketti, joten se lähetetään vasta, kun valitset emojin. | Reaktiot näkyvät viestin alapuolella | Useampi käyttäjä voi reagoida samaan viestiin | Voit reagoida omiin ja muiden viesteihin | . 💡 Vinkki: Reaktiot kuluttavat vain vähän mesh-verkon kaistaa verrattuna täysiin tekstiviesteihin. Vastaaminen . Pyyhkäise viestiä oikealle vastataksesi siihen — viestinkirjoituskenttä avautuu siten, että kyseinen viesti on lainattuna. Kun pyyhkäisy ylittää vastauskynnyksen, toiminto aktivoituu. Jos vapautat ennen sitä, viesti palautuu paikalleen eikä mitään tapahdu. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Päiväerottimet . Viestit ryhmitellään päivän mukaan. Kahden viimeisimmän päivän ensimmäisen viestin yläpuolella olevassa erottimessa lukee Tänään tai Eilen, ja sitä vanhemmissa viesteissä näytetään päivämäärä. Siirry viimeisimpiin . Keskustelua ylöspäin vierittäessä näkyviin tulee painike, jolla voit siirtyä uusimpaan viestiin. Kun uusia viestejä saapuu sinun ollessasi ylempänä keskustelussa, siinä näytetään uusimman lähettäjän nimi sekä muiden lukemattomien viestien määrä. Lukumäärä tarkoittaa viestejä, ei henkilöitä — jos yhdeltä henkilöltä on viisi lukematonta viestiä, siinä näkyy hänen nimensä ja +4. Viestitoiminnot . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | Vastaa — lainaa viesti vastaukseesi | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . Viestien prioriteetti . Sovellus lähettää kaikki kirjoittamasi viestit samalla oletusprioriteetilla — valittavana ei ole hätä- tai hälytysprioriteettia, eikä mikään sovelluksessa nosta suoraviestiä kanavalähetyksen edelle. Mahdollinen priorisointi tehdään laiteohjelmistossa, ei tässä. (Sovellus merkitsee osan omasta sisäisestä liikenteestään, kuten järjestelmänvalvojan paketit ja reitiselvityspaketit, luotettaviksi tai taustaliikenteeksi, mutta sitä ei voi hallita viestinkirjoituskentästä.) . Viestirajoitukset . | Enimmäispituus: 200 tavua (noin 200 merkkiä ASCII-tekstille) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | Rajoitusnopeus: mesh-verkko tasaa lähetysajan oikeudenmukaisesti; suuri viestimäärä voi joutua rajoitetuksi | Toimitus: viestit yritetään lähettää uudelleen automaattisesti, jos kuittausta ei saada | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/messages-and-channels.html#viestiominaisuudet",
    
    "relUrl": "/fi-rFI/user/messages-and-channels.html#viestiominaisuudet"
  },"2527": {
    "doc": "Viestit ja kanavat",
    "title": "Parhaat käytännöt",
    "content": ". | Käytä kanavia ryhmäviestintään | Käytä suoraviestejä kahden käyttäjän väliseen yksityiseen viestintään | Pidä viestit lyhyinä — mesh-verkon kaistanleveys on rajallinen | Määritä salaus arkaluontoiselle viestinnälle | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/messages-and-channels.html#parhaat-k%C3%A4yt%C3%A4nn%C3%B6t",
    
    "relUrl": "/fi-rFI/user/messages-and-channels.html#parhaat-käytännöt"
  },"2528": {
    "doc": "Viestit ja kanavat",
    "title": "Aiheeseen liittyvät aiheet",
    "content": ". | Radiot — napauta radiota aloittaaksesi suoraviestin | Asetukset — Radio ja käyttäjä — määritä kanavan salaus ja esiasetukset | MQTT — välittää kanavaviestit internetiin | Kanavien määritys — tarkemmat kanava-asetukset meshtastic.org-sivustolla | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/messages-and-channels.html#aiheeseen-liittyv%C3%A4t-aiheet",
    
    "relUrl": "/fi-rFI/user/messages-and-channels.html#aiheeseen-liittyvät-aiheet"
  },"2529": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": "Meshtastic supports two communication modes: channel broadcasts and direct messages. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/messages-and-channels.html#messages--channels",
    
    "relUrl": "/is-rIS/user/messages-and-channels.html#messages--channels"
  },"2530": {
    "doc": "Messages & Channels",
    "title": "Channels",
    "content": "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 radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. Channel Security . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | Icon | What it means | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: 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 . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/messages-and-channels.html#channels",
    
    "relUrl": "/is-rIS/user/messages-and-channels.html#channels"
  },"2531": {
    "doc": "Messages & Channels",
    "title": "Direct Messages",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. Sending a Direct Message . | Open the Messages tab. | Select a conversation, or tap a node in the node list. | Type your message and tap Send. | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. Message States . A status label appears under your own outgoing messages only (incoming messages from others show no status label): . | State | Meaning | . | Sending… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | Delivered to recipient | The strongest confirmation for a direct message — an acknowledgment came back | . | Delivered to mesh | For a channel broadcast, the message reached the mesh (broadcasts have no per-recipient ack) | . | Relayed, not confirmed by recipient | For a direct message, shown in a warning color — the message was relayed but no acknowledgment has come back yet | . | Routing via SF++ chain… | Being routed/buffered by the Store & Forward Plus Plus chain | . | Confirmed on SF++ chain | Confirmed delivered via the SF++ chain | . | Error | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Error | 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. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Rate limited | The mesh is throttling you for sending too fast | Wait before sending again. | . | Not authorized | The destination refused the request | Check you have the right channel and keys for that node. | . | Recipient needs your key | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | Recipient key unavailable | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | Could not send encrypted message | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Admin session expired | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Admin key not authorized | The target node does not accept your admin key | Verify the admin key matches on both nodes. | . | Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. | . | Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. | . | No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. | . | Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. | . | Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/messages-and-channels.html#direct-messages",
    
    "relUrl": "/is-rIS/user/messages-and-channels.html#direct-messages"
  },"2532": {
    "doc": "Messages & Channels",
    "title": "Message Features",
    "content": "Quick Chat . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Searching Messages . You can search the full history of any conversation directly from the chat screen: . | Open a conversation (a channel or a direct message). | Tap the search icon in the top bar. | Type into the Search messages… field. The search runs as you type, across all stored messages in that conversation. | Use the N / M result counter and the previous / next arrows to jump between matches, which are highlighted in the conversation. | . 💡 Tip: Search is full-text and stays within the conversation you opened it from — it doesn’t search across other channels or contacts. It matches against the messages already stored on your device, so it works fully offline. 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. Text Formatting . Messages support lightweight inline Markdown. Received messages render the styling with the syntax characters removed: . | Type | Syntax | Renders as | . | Bold | **bold** | bold | . | Italic | *italic* | italic | . | Strikethrough | ~~strike~~ | strike | . | Inline code | `code` | monospace code | . | Link | [label](https://example.com) | a tappable label | . When composing, focus the message field and type at least three characters to reveal a formatting toolbar below the input. Select text and tap a style to wrap it (tap again to remove it); with no selection, a style inserts an empty pair with the cursor between the markers. The link button opens a dialog to enter a URL. As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 Tip: Formatting is carried as literal characters on the mesh — the same bytes iOS sends. Clients that don’t support Markdown (older apps, plain firmware clients) will show the raw **/~~ characters. URLs, email addresses, and phone numbers are still auto-linked whether or not you use Markdown. Mentions . Type @ while composing to mention a node — a picker suggests matching contacts as you type. In a received message, a mention appears as a highlighted chip showing the node’s name; tap it to jump straight to that node’s detail page. Reactions . React to messages with emoji: . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. Message Actions . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | Reply — quote the message in your response | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . Message Priority . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . Message Limits . | Maximum length: 200 bytes (approximately 200 characters for ASCII text) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | Rate limiting: The mesh enforces airtime fairness; heavy message volume may be throttled | Delivery: Messages are retried automatically if no acknowledgment is received | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/messages-and-channels.html#message-features",
    
    "relUrl": "/is-rIS/user/messages-and-channels.html#message-features"
  },"2533": {
    "doc": "Messages & Channels",
    "title": "Best Practices",
    "content": ". | 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 | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/messages-and-channels.html#best-practices",
    
    "relUrl": "/is-rIS/user/messages-and-channels.html#best-practices"
  },"2534": {
    "doc": "Messages & Channels",
    "title": "Related Topics",
    "content": ". | Nodes — tap a node to start a direct message | Settings — Radio & User — configure channel encryption and presets | MQTT — bridge channel messages to the internet | Channel configuration — detailed channel settings on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/messages-and-channels.html#related-topics",
    
    "relUrl": "/is-rIS/user/messages-and-channels.html#related-topics"
  },"2535": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": " ",
    "url": "/Meshtastic-Android/main/is-rIS/user/messages-and-channels.html",
    
    "relUrl": "/is-rIS/user/messages-and-channels.html"
  },"2536": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": "Meshtastic supports two communication modes: channel broadcasts and direct messages. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/messages-and-channels.html#messages--channels",
    
    "relUrl": "/lt-rLT/user/messages-and-channels.html#messages--channels"
  },"2537": {
    "doc": "Messages & Channels",
    "title": "Channels",
    "content": "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 radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. Channel Security . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | Icon | What it means | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: 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 . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/messages-and-channels.html#channels",
    
    "relUrl": "/lt-rLT/user/messages-and-channels.html#channels"
  },"2538": {
    "doc": "Messages & Channels",
    "title": "Direct Messages",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. Sending a Direct Message . | Open the Messages tab. | Select a conversation, or tap a node in the node list. | Type your message and tap Send. | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. Message States . A status label appears under your own outgoing messages only (incoming messages from others show no status label): . | State | Meaning | . | Sending… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | Delivered to recipient | The strongest confirmation for a direct message — an acknowledgment came back | . | Delivered to mesh | For a channel broadcast, the message reached the mesh (broadcasts have no per-recipient ack) | . | Relayed, not confirmed by recipient | For a direct message, shown in a warning color — the message was relayed but no acknowledgment has come back yet | . | Routing via SF++ chain… | Being routed/buffered by the Store & Forward Plus Plus chain | . | Confirmed on SF++ chain | Confirmed delivered via the SF++ chain | . | Klaida | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Klaida | Meaning | What to Do | . | Nėra maršruto | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Rate limited | The mesh is throttling you for sending too fast | Wait before sending again. | . | Not authorized | The destination refused the request | Check you have the right channel and keys for that node. | . | Recipient needs your key | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | Recipient key unavailable | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | Could not send encrypted message | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Admin session expired | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Admin key not authorized | The target node does not accept your admin key | Verify the admin key matches on both nodes. | . | Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. | . | Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. | . | No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. | . | Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. | . | Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/messages-and-channels.html#direct-messages",
    
    "relUrl": "/lt-rLT/user/messages-and-channels.html#direct-messages"
  },"2539": {
    "doc": "Messages & Channels",
    "title": "Message Features",
    "content": "Quick Chat . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Searching Messages . You can search the full history of any conversation directly from the chat screen: . | Open a conversation (a channel or a direct message). | Tap the search icon in the top bar. | Type into the Search messages… field. The search runs as you type, across all stored messages in that conversation. | Use the N / M result counter and the previous / next arrows to jump between matches, which are highlighted in the conversation. | . 💡 Tip: Search is full-text and stays within the conversation you opened it from — it doesn’t search across other channels or contacts. It matches against the messages already stored on your device, so it works fully offline. 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. Text Formatting . Messages support lightweight inline Markdown. Received messages render the styling with the syntax characters removed: . | Type | Syntax | Renders as | . | Bold | **bold** | bold | . | Italic | *italic* | italic | . | Strikethrough | ~~strike~~ | strike | . | Inline code | `code` | monospace code | . | Link | [label](https://example.com) | a tappable label | . When composing, focus the message field and type at least three characters to reveal a formatting toolbar below the input. Select text and tap a style to wrap it (tap again to remove it); with no selection, a style inserts an empty pair with the cursor between the markers. The link button opens a dialog to enter a URL. As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 Tip: Formatting is carried as literal characters on the mesh — the same bytes iOS sends. Clients that don’t support Markdown (older apps, plain firmware clients) will show the raw **/~~ characters. URLs, email addresses, and phone numbers are still auto-linked whether or not you use Markdown. Mentions . Type @ while composing to mention a node — a picker suggests matching contacts as you type. In a received message, a mention appears as a highlighted chip showing the node’s name; tap it to jump straight to that node’s detail page. Reactions . React to messages with emoji: . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. Message Actions . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | Reply — quote the message in your response | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . Message Priority . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . Message Limits . | Maximum length: 200 bytes (approximately 200 characters for ASCII text) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | Rate limiting: The mesh enforces airtime fairness; heavy message volume may be throttled | Delivery: Messages are retried automatically if no acknowledgment is received | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/messages-and-channels.html#message-features",
    
    "relUrl": "/lt-rLT/user/messages-and-channels.html#message-features"
  },"2540": {
    "doc": "Messages & Channels",
    "title": "Best Practices",
    "content": ". | 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 | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/messages-and-channels.html#best-practices",
    
    "relUrl": "/lt-rLT/user/messages-and-channels.html#best-practices"
  },"2541": {
    "doc": "Messages & Channels",
    "title": "Related Topics",
    "content": ". | Nodes — tap a node to start a direct message | Settings — Radio & User — configure channel encryption and presets | MQTT — bridge channel messages to the internet | Channel configuration — detailed channel settings on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/messages-and-channels.html#related-topics",
    
    "relUrl": "/lt-rLT/user/messages-and-channels.html#related-topics"
  },"2542": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": " ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/messages-and-channels.html",
    
    "relUrl": "/lt-rLT/user/messages-and-channels.html"
  },"2543": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": "Meshtastic supports two communication modes: channel broadcasts and direct messages. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/messages-and-channels.html#messages--channels",
    
    "relUrl": "/gl-rES/user/messages-and-channels.html#messages--channels"
  },"2544": {
    "doc": "Messages & Channels",
    "title": "Channels",
    "content": "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 radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. Channel Security . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | Icon | What it means | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: 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 . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/messages-and-channels.html#channels",
    
    "relUrl": "/gl-rES/user/messages-and-channels.html#channels"
  },"2545": {
    "doc": "Messages & Channels",
    "title": "Direct Messages",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. Sending a Direct Message . | Open the Messages tab. | Select a conversation, or tap a node in the node list. | Type your message and tap Send. | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. Message States . A status label appears under your own outgoing messages only (incoming messages from others show no status label): . | State | Meaning | . | Sending… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | Delivered to recipient | The strongest confirmation for a direct message — an acknowledgment came back | . | Delivered to mesh | For a channel broadcast, the message reached the mesh (broadcasts have no per-recipient ack) | . | Relayed, not confirmed by recipient | For a direct message, shown in a warning color — the message was relayed but no acknowledgment has come back yet | . | Routing via SF++ chain… | Being routed/buffered by the Store & Forward Plus Plus chain | . | Confirmed on SF++ chain | Confirmed delivered via the SF++ chain | . | Erro | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Erro | 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. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Rate limited | The mesh is throttling you for sending too fast | Wait before sending again. | . | Not authorized | The destination refused the request | Check you have the right channel and keys for that node. | . | Recipient needs your key | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | Recipient key unavailable | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | Could not send encrypted message | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Admin session expired | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Admin key not authorized | The target node does not accept your admin key | Verify the admin key matches on both nodes. | . | Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. | . | Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. | . | No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. | . | Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. | . | Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/messages-and-channels.html#direct-messages",
    
    "relUrl": "/gl-rES/user/messages-and-channels.html#direct-messages"
  },"2546": {
    "doc": "Messages & Channels",
    "title": "Message Features",
    "content": "Quick Chat . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Searching Messages . You can search the full history of any conversation directly from the chat screen: . | Open a conversation (a channel or a direct message). | Tap the search icon in the top bar. | Type into the Search messages… field. The search runs as you type, across all stored messages in that conversation. | Use the N / M result counter and the previous / next arrows to jump between matches, which are highlighted in the conversation. | . 💡 Tip: Search is full-text and stays within the conversation you opened it from — it doesn’t search across other channels or contacts. It matches against the messages already stored on your device, so it works fully offline. 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. Text Formatting . Messages support lightweight inline Markdown. Received messages render the styling with the syntax characters removed: . | Type | Syntax | Renders as | . | Bold | **bold** | bold | . | Italic | *italic* | italic | . | Strikethrough | ~~strike~~ | strike | . | Inline code | `code` | monospace code | . | Link | [label](https://example.com) | a tappable label | . When composing, focus the message field and type at least three characters to reveal a formatting toolbar below the input. Select text and tap a style to wrap it (tap again to remove it); with no selection, a style inserts an empty pair with the cursor between the markers. The link button opens a dialog to enter a URL. As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 Tip: Formatting is carried as literal characters on the mesh — the same bytes iOS sends. Clients that don’t support Markdown (older apps, plain firmware clients) will show the raw **/~~ characters. URLs, email addresses, and phone numbers are still auto-linked whether or not you use Markdown. Mentions . Type @ while composing to mention a node — a picker suggests matching contacts as you type. In a received message, a mention appears as a highlighted chip showing the node’s name; tap it to jump straight to that node’s detail page. Reactions . React to messages with emoji: . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. Message Actions . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | Reply — quote the message in your response | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . Message Priority . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . Message Limits . | Maximum length: 200 bytes (approximately 200 characters for ASCII text) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | Rate limiting: The mesh enforces airtime fairness; heavy message volume may be throttled | Delivery: Messages are retried automatically if no acknowledgment is received | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/messages-and-channels.html#message-features",
    
    "relUrl": "/gl-rES/user/messages-and-channels.html#message-features"
  },"2547": {
    "doc": "Messages & Channels",
    "title": "Best Practices",
    "content": ". | 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 | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/messages-and-channels.html#best-practices",
    
    "relUrl": "/gl-rES/user/messages-and-channels.html#best-practices"
  },"2548": {
    "doc": "Messages & Channels",
    "title": "Related Topics",
    "content": ". | Nodes — tap a node to start a direct message | Settings — Radio & User — configure channel encryption and presets | MQTT — bridge channel messages to the internet | Channel configuration — detailed channel settings on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/messages-and-channels.html#related-topics",
    
    "relUrl": "/gl-rES/user/messages-and-channels.html#related-topics"
  },"2549": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": " ",
    "url": "/Meshtastic-Android/main/gl-rES/user/messages-and-channels.html",
    
    "relUrl": "/gl-rES/user/messages-and-channels.html"
  },"2550": {
    "doc": "メッセージとチャンネル",
    "title": "メッセージとチャンネル",
    "content": "Meshtastic は、チャンネルブロードキャストとダイレクトメッセージの 2 つの通信モードをサポートしています。 . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/messages-and-channels.html",
    
    "relUrl": "/ja-rJP/user/messages-and-channels.html"
  },"2551": {
    "doc": "メッセージとチャンネル",
    "title": "チャンネル",
    "content": "チャンネルは、共有された通信グループです。同じチャンネル鍵を設定したすべてのノードが、そのチャンネルでメッセージを読み書きできます。 . デフォルトチャンネル . Every Meshtastic radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. チャンネルのセキュリティ . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | アイコン | 意味 | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: Always configure a unique PSK for private communications. デフォルトチャンネルは、新規ユーザーがメッシュを見つけられるよう意図的にオープンになっています。ただし、機密性の高い内容には別途、暗号化されたチャンネルを作成してください。 . チャンネルを追加する . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/messages-and-channels.html#%E3%83%81%E3%83%A3%E3%83%B3%E3%83%8D%E3%83%AB",
    
    "relUrl": "/ja-rJP/user/messages-and-channels.html#チャンネル"
  },"2552": {
    "doc": "メッセージとチャンネル",
    "title": "ダイレクトメッセージ",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. ダイレクトメッセージを送信する . | 「メッセージ」タブを開きます。 | Select a conversation, or tap a node in the node list. | メッセージを入力し、「送信」をタップします。 | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. メッセージの状態 . ステータスラベルは、自分が送信したメッセージの下にのみ表示されます（他のユーザーからの受信メッセージにはステータスラベルは表示されません）： . | 状態 | 意味 | . | 送信中… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | 受信者に配信済み | ダイレクトメッセージで最も確実な確認です。受信確認が返ってきています | . | メッシュに配信済み | チャンネルブロードキャストでは、メッセージがメッシュに届いたことを示します（ブロードキャストには受信者ごとの確認応答はありません） | . | 中継済み、受信者による確認なし | ダイレクトメッセージでは警告色で表示されます。メッセージは中継されましたが、まだ受信確認が返ってきていません | . | SF++ チェーン経由でルーティング中… | Store & Forward Plus Plus チェーンによってルーティング／バッファリングされています | . | SF++ チェーンで確認済み | SF++ チェーン経由で配信が確認されました | . | エラー | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . 配信エラー . メッセージの配信に失敗すると、エラーインジケーターが何が問題だったかを示します： . | エラー | 意味 | 対処方法 | . | ルートがありません | 宛先ノードへの経路が存在しません | 受信者がオフラインか、メッシュの範囲外の可能性があります。時間をおくか、距離を縮めてください。 | . | No radio interface | 送信に使える無線インターフェースがありません | Check that your radio is connected and available. | . | メッシュへの配信に失敗しました | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Rate limited | The mesh is throttling you for sending too fast | Wait before sending again. | . | Not authorized | The destination refused the request | Check you have the right channel and keys for that node. | . | 受信者にあなたの鍵が必要です | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | 受信者の鍵を利用できません | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | 暗号化メッセージを送信できませんでした | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Admin session expired | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Admin key not authorized | The target node does not accept your admin key | 両方のノードで管理者鍵が一致しているか確認してください。 | . | Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. | . | メッセージが大きすぎて送信できません | メッセージが最大ペイロードサイズを超えています | Shorten the message and try again. | . | No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. | . | Duty cycle limit | 地域ごとの電波利用時間の上限に達しました | Wait for the duty cycle window to reset. | . | Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. | . 💡 ヒント： ほとんどの配信エラーは自然に解消します。ノードに断続的に到達できる場合、メッシュは再試行します。 For persistent No route errors, check that intermediate Router nodes are online. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/messages-and-channels.html#%E3%83%80%E3%82%A4%E3%83%AC%E3%82%AF%E3%83%88%E3%83%A1%E3%83%83%E3%82%BB%E3%83%BC%E3%82%B8",
    
    "relUrl": "/ja-rJP/user/messages-and-channels.html#ダイレクトメッセージ"
  },"2553": {
    "doc": "メッセージとチャンネル",
    "title": "メッセージの機能",
    "content": "クイックチャット . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. メッセージを検索する . チャット画面から、どの会話でもその全履歴を直接検索できます： . | 会話（チャンネルまたはダイレクトメッセージ）を開きます。 | 上部バーの検索アイコンをタップします。 | 「メッセージを検索…」欄に入力します。検索は入力に応じて、その会話に保存されているすべてのメッセージを対象に実行されます。 | N／M の結果カウンターと前へ／次への矢印を使って、一致箇所間を移動できます。一致箇所は会話内でハイライト表示されます。 | . 💡 ヒント： 検索は全文検索で、開いた会話の中だけを対象とします。他のチャンネルや連絡先をまたいで検索することはありません。デバイスにすでに保存されているメッセージを対象に照合するため、完全にオフラインで動作します。 . メッセージの吹き出し . メッセージはチャットの吹き出しとして表示され、送信メッセージは右側、受信メッセージは左側に並びます。各吹き出しには、送信者・タイムスタンプ・配信状況が表示されます。返信付きのメッセージでは、応答の上に元メッセージの引用プレビューが表示されます。 . テキストの書式 . メッセージは、軽量なインライン Markdown に対応しています。受信したメッセージは、記法の文字が取り除かれた状態でスタイルが適用されて表示されます： . | 種別 | 記法 | 表示結果 | . | 太字 | **bold** | 太字 | . | 斜体 | *italic* | 斜体 | . | 取り消し線 | ~~strike~~ | 取り消し線 | . | インラインコード | `code` | 等幅の code | . | リンク | [label](https://example.com) | タップできるラベル | . メッセージを作成するときは、入力欄にフォーカスして 3 文字以上入力すると、入力欄の下に書式ツールバーが表示されます。テキストを選択してスタイルをタップすると、そのテキストが囲まれます（もう一度タップすると解除されます）。選択していない場合は、空のペアが挿入され、カーソルがマーカーの間に置かれます。リンクボタンをタップすると、URL を入力するダイアログが開きます。 As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 ヒント： 書式はメッシュ上ではそのままの文字として送られます。iOS が送信するのと同じバイト列です。 Markdown に対応していないクライアント（古いアプリや、素のファームウェアのクライアント）では、** や ~~ の文字がそのまま表示されます。 URL、メールアドレス、電話番号は、Markdown を使うかどうかにかかわらず、引き続き自動的にリンクになります。 . メンション . メッセージ作成中に @ を入力するとノードにメンションできます。入力に応じて、一致する連絡先がピッカーに提案されます。受信メッセージでは、メンションはノード名を表示したハイライト付きのチップとして現れます。タップすると、そのノードの詳細ページに直接移動できます。 . リアクション . 絵文字でメッセージにリアクションできます： . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | リアクションはメッセージの吹き出しの下に表示されます | 複数のユーザーが同じメッセージにリアクションできます | 自分のメッセージにも、他の人のメッセージにもリアクションできます | . 💡 ヒント： リアクションは軽量で、通常のテキストメッセージに比べてメッシュの帯域をほとんど消費しません。 . Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. メッセージの操作 . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | 返信： そのメッセージを引用して返信します | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . メッセージの優先度 . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . メッセージの制限 . | 最大長： 200 バイト（ASCII テキストで約 200 文字） | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | レート制限： メッシュは電波利用時間の公平性を確保するため、大量のメッセージは制限されることがあります | 配信： 受信確認がない場合、メッセージは自動的に再送されます | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/messages-and-channels.html#%E3%83%A1%E3%83%83%E3%82%BB%E3%83%BC%E3%82%B8%E3%81%AE%E6%A9%9F%E8%83%BD",
    
    "relUrl": "/ja-rJP/user/messages-and-channels.html#メッセージの機能"
  },"2554": {
    "doc": "メッセージとチャンネル",
    "title": "ベストプラクティス",
    "content": ". | グループでの連携にはチャンネルを使います | 個人間のプライベートな通信にはダイレクトメッセージを使います | メッセージは短くしてください。メッシュの帯域は限られています | 機密性の高い通信には暗号化を設定します | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/messages-and-channels.html#%E3%83%99%E3%82%B9%E3%83%88%E3%83%97%E3%83%A9%E3%82%AF%E3%83%86%E3%82%A3%E3%82%B9",
    
    "relUrl": "/ja-rJP/user/messages-and-channels.html#ベストプラクティス"
  },"2555": {
    "doc": "メッセージとチャンネル",
    "title": "関連トピック",
    "content": ". | ノード：ノードをタップするとダイレクトメッセージを開始できます | 設定：無線機とユーザー：チャンネルの暗号化とプリセットを設定します | MQTT：チャンネルのメッセージをインターネットに橋渡しします | チャンネル設定：meshtastic.org にある詳細なチャンネル設定 | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/messages-and-channels.html#%E9%96%A2%E9%80%A3%E3%83%88%E3%83%94%E3%83%83%E3%82%AF",
    
    "relUrl": "/ja-rJP/user/messages-and-channels.html#関連トピック"
  },"2556": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": "Meshtastic supports two communication modes: channel broadcasts and direct messages. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/messages-and-channels.html#messages--channels",
    
    "relUrl": "/de-rDE/user/messages-and-channels.html#messages--channels"
  },"2557": {
    "doc": "Messages & Channels",
    "title": "Kanäle",
    "content": "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 radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. Kanalsicherheit . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | Symbol | What it means | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: 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 . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/messages-and-channels.html#kan%C3%A4le",
    
    "relUrl": "/de-rDE/user/messages-and-channels.html#kanäle"
  },"2558": {
    "doc": "Messages & Channels",
    "title": "Direktnachrichten",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. Sending a Direct Message . | Open the Messages tab. | Select a conversation, or tap a node in the node list. | Type your message and tap Send. | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. Message States . A status label appears under your own outgoing messages only (incoming messages from others show no status label): . | Status | Meaning | . | Sending… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | Delivered to recipient | The strongest confirmation for a direct message — an acknowledgment came back | . | Versand ins Netz | For a channel broadcast, the message reached the mesh (broadcasts have no per-recipient ack) | . | Relayed, not confirmed by recipient | For a direct message, shown in a warning color — the message was relayed but no acknowledgment has come back yet | . | Routen über den SF++ Weg. | Being routed/buffered by the Store & Forward Plus Plus chain | . | Bestätigt auf dem SF++ Weg. | Confirmed delivered via the SF++ chain | . | Fehler | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Fehler | Meaning | What to Do | . | Keine Route | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Rate limited | The mesh is throttling you for sending too fast | Wait before sending again. | . | Not authorized | The destination refused the request | Check you have the right channel and keys for that node. | . | Empfänger benötigt deinen Schlüssel | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | Empfängerschlüssel nicht verfügbar | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | Konnte verschlüsselte Nachricht nicht senden | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Admin session expired | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Admin key not authorized | The target node does not accept your admin key | Stelle sicher, dass der Admin-Schlüssel auf beiden Knoten übereinstimmt. | . | Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. | . | Nachricht ist zu groß zum Senden | Message exceeds maximum payload size | Shorten the message and try again. | . | No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. | . | Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. | . | Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/messages-and-channels.html#direktnachrichten",
    
    "relUrl": "/de-rDE/user/messages-and-channels.html#direktnachrichten"
  },"2559": {
    "doc": "Messages & Channels",
    "title": "Message Features",
    "content": "Quick Chat . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Searching Messages . You can search the full history of any conversation directly from the chat screen: . | Open a conversation (a channel or a direct message). | Tap the search icon in the top bar. | Type into the Search messages… field. The search runs as you type, across all stored messages in that conversation. | Use the N / M result counter and the previous / next arrows to jump between matches, which are highlighted in the conversation. | . 💡 Tip: Search is full-text and stays within the conversation you opened it from — it doesn’t search across other channels or contacts. It matches against the messages already stored on your device, so it works fully offline. 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. Text Formatting . Messages support lightweight inline Markdown. Received messages render the styling with the syntax characters removed: . | Typ | Syntax | Renders as | . | Bold | **bold** | bold | . | Italic | *italic* | italic | . | Strikethrough | ~~strike~~ | strike | . | Inline code | `code` | monospace code | . | Link | [label](https://example.com) | a tappable label | . When composing, focus the message field and type at least three characters to reveal a formatting toolbar below the input. Select text and tap a style to wrap it (tap again to remove it); with no selection, a style inserts an empty pair with the cursor between the markers. The link button opens a dialog to enter a URL. As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 Tip: Formatting is carried as literal characters on the mesh — the same bytes iOS sends. Clients that don’t support Markdown (older apps, plain firmware clients) will show the raw **/~~ characters. URLs, email addresses, and phone numbers are still auto-linked whether or not you use Markdown. Mentions . Type @ while composing to mention a node — a picker suggests matching contacts as you type. In a received message, a mention appears as a highlighted chip showing the node’s name; tap it to jump straight to that node’s detail page. Reactions . React to messages with emoji: . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. Message Actions . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | Reply — quote the message in your response | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . Message Priority . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . Message Limits . | Maximum length: 200 bytes (approximately 200 characters for ASCII text) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | Rate limiting: The mesh enforces airtime fairness; heavy message volume may be throttled | Delivery: Messages are retried automatically if no acknowledgment is received | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/messages-and-channels.html#message-features",
    
    "relUrl": "/de-rDE/user/messages-and-channels.html#message-features"
  },"2560": {
    "doc": "Messages & Channels",
    "title": "Bewährte Praktiken",
    "content": ". | 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 | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/messages-and-channels.html#bew%C3%A4hrte-praktiken",
    
    "relUrl": "/de-rDE/user/messages-and-channels.html#bewährte-praktiken"
  },"2561": {
    "doc": "Messages & Channels",
    "title": "Related Topics",
    "content": ". | Nodes — tap a node to start a direct message | Settings — Radio & User — configure channel encryption and presets | MQTT — bridge channel messages to the internet | Channel configuration — detailed channel settings on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/messages-and-channels.html#related-topics",
    
    "relUrl": "/de-rDE/user/messages-and-channels.html#related-topics"
  },"2562": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": " ",
    "url": "/Meshtastic-Android/main/de-rDE/user/messages-and-channels.html",
    
    "relUrl": "/de-rDE/user/messages-and-channels.html"
  },"2563": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": "Meshtastic supports two communication modes: channel broadcasts and direct messages. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/messages-and-channels.html#messages--channels",
    
    "relUrl": "/ar-rSA/user/messages-and-channels.html#messages--channels"
  },"2564": {
    "doc": "Messages & Channels",
    "title": "القنوات",
    "content": "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 radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. Channel Security . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | Icon | What it means | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: 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 . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/messages-and-channels.html#%D8%A7%D9%84%D9%82%D9%86%D9%88%D8%A7%D8%AA",
    
    "relUrl": "/ar-rSA/user/messages-and-channels.html#القنوات"
  },"2565": {
    "doc": "Messages & Channels",
    "title": "Direct Messages",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. Sending a Direct Message . | Open the Messages tab. | Select a conversation, or tap a node in the node list. | Type your message and tap Send. | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. Message States . A status label appears under your own outgoing messages only (incoming messages from others show no status label): . | State | Meaning | . | Sending… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | Delivered to recipient | The strongest confirmation for a direct message — an acknowledgment came back | . | Delivered to mesh | For a channel broadcast, the message reached the mesh (broadcasts have no per-recipient ack) | . | Relayed, not confirmed by recipient | For a direct message, shown in a warning color — the message was relayed but no acknowledgment has come back yet | . | Routing via SF++ chain… | Being routed/buffered by the Store & Forward Plus Plus chain | . | Confirmed on SF++ chain | Confirmed delivered via the SF++ chain | . | غلط | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | غلط | Meaning | What to Do | . | لاطريق | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Rate limited | The mesh is throttling you for sending too fast | Wait before sending again. | . | Not authorized | The destination refused the request | Check you have the right channel and keys for that node. | . | Recipient needs your key | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | Recipient key unavailable | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | Could not send encrypted message | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Admin session expired | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Admin key not authorized | The target node does not accept your admin key | Verify the admin key matches on both nodes. | . | Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. | . | Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. | . | No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. | . | Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. | . | Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/messages-and-channels.html#direct-messages",
    
    "relUrl": "/ar-rSA/user/messages-and-channels.html#direct-messages"
  },"2566": {
    "doc": "Messages & Channels",
    "title": "Message Features",
    "content": "Quick Chat . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Searching Messages . You can search the full history of any conversation directly from the chat screen: . | Open a conversation (a channel or a direct message). | Tap the search icon in the top bar. | Type into the Search messages… field. The search runs as you type, across all stored messages in that conversation. | Use the N / M result counter and the previous / next arrows to jump between matches, which are highlighted in the conversation. | . 💡 Tip: Search is full-text and stays within the conversation you opened it from — it doesn’t search across other channels or contacts. It matches against the messages already stored on your device, so it works fully offline. 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. Text Formatting . Messages support lightweight inline Markdown. Received messages render the styling with the syntax characters removed: . | Type | Syntax | Renders as | . | Bold | **bold** | bold | . | Italic | *italic* | italic | . | Strikethrough | ~~strike~~ | strike | . | Inline code | `code` | monospace code | . | Link | [label](https://example.com) | a tappable label | . When composing, focus the message field and type at least three characters to reveal a formatting toolbar below the input. Select text and tap a style to wrap it (tap again to remove it); with no selection, a style inserts an empty pair with the cursor between the markers. The link button opens a dialog to enter a URL. As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 Tip: Formatting is carried as literal characters on the mesh — the same bytes iOS sends. Clients that don’t support Markdown (older apps, plain firmware clients) will show the raw **/~~ characters. URLs, email addresses, and phone numbers are still auto-linked whether or not you use Markdown. Mentions . Type @ while composing to mention a node — a picker suggests matching contacts as you type. In a received message, a mention appears as a highlighted chip showing the node’s name; tap it to jump straight to that node’s detail page. Reactions . React to messages with emoji: . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. Message Actions . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | Reply — quote the message in your response | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . Message Priority . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . Message Limits . | Maximum length: 200 bytes (approximately 200 characters for ASCII text) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | Rate limiting: The mesh enforces airtime fairness; heavy message volume may be throttled | Delivery: Messages are retried automatically if no acknowledgment is received | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/messages-and-channels.html#message-features",
    
    "relUrl": "/ar-rSA/user/messages-and-channels.html#message-features"
  },"2567": {
    "doc": "Messages & Channels",
    "title": "Best Practices",
    "content": ". | 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 | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/messages-and-channels.html#best-practices",
    
    "relUrl": "/ar-rSA/user/messages-and-channels.html#best-practices"
  },"2568": {
    "doc": "Messages & Channels",
    "title": "Related Topics",
    "content": ". | Nodes — tap a node to start a direct message | Settings — Radio & User — configure channel encryption and presets | MQTT — bridge channel messages to the internet | Channel configuration — detailed channel settings on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/messages-and-channels.html#related-topics",
    
    "relUrl": "/ar-rSA/user/messages-and-channels.html#related-topics"
  },"2569": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": " ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/messages-and-channels.html",
    
    "relUrl": "/ar-rSA/user/messages-and-channels.html"
  },"2570": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": "Meshtastic supports two communication modes: channel broadcasts and direct messages. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/messages-and-channels.html#messages--channels",
    
    "relUrl": "/hr-rHR/user/messages-and-channels.html#messages--channels"
  },"2571": {
    "doc": "Messages & Channels",
    "title": "Channels",
    "content": "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 radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. Channel Security . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | Icon | What it means | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: 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 . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/messages-and-channels.html#channels",
    
    "relUrl": "/hr-rHR/user/messages-and-channels.html#channels"
  },"2572": {
    "doc": "Messages & Channels",
    "title": "Direct Messages",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. Sending a Direct Message . | Open the Messages tab. | Select a conversation, or tap a node in the node list. | Type your message and tap Send. | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. Message States . A status label appears under your own outgoing messages only (incoming messages from others show no status label): . | State | Meaning | . | Sending… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | Delivered to recipient | The strongest confirmation for a direct message — an acknowledgment came back | . | Delivered to mesh | For a channel broadcast, the message reached the mesh (broadcasts have no per-recipient ack) | . | Relayed, not confirmed by recipient | For a direct message, shown in a warning color — the message was relayed but no acknowledgment has come back yet | . | Routing via SF++ chain… | Being routed/buffered by the Store & Forward Plus Plus chain | . | Confirmed on SF++ chain | Confirmed delivered via the SF++ chain | . | Pogreška | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Pogreška | 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. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Rate limited | The mesh is throttling you for sending too fast | Wait before sending again. | . | Not authorized | The destination refused the request | Check you have the right channel and keys for that node. | . | Recipient needs your key | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | Recipient key unavailable | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | Could not send encrypted message | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Admin session expired | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Admin key not authorized | The target node does not accept your admin key | Verify the admin key matches on both nodes. | . | Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. | . | Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. | . | No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. | . | Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. | . | Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/messages-and-channels.html#direct-messages",
    
    "relUrl": "/hr-rHR/user/messages-and-channels.html#direct-messages"
  },"2573": {
    "doc": "Messages & Channels",
    "title": "Message Features",
    "content": "Quick Chat . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Searching Messages . You can search the full history of any conversation directly from the chat screen: . | Open a conversation (a channel or a direct message). | Tap the search icon in the top bar. | Type into the Search messages… field. The search runs as you type, across all stored messages in that conversation. | Use the N / M result counter and the previous / next arrows to jump between matches, which are highlighted in the conversation. | . 💡 Tip: Search is full-text and stays within the conversation you opened it from — it doesn’t search across other channels or contacts. It matches against the messages already stored on your device, so it works fully offline. 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. Text Formatting . Messages support lightweight inline Markdown. Received messages render the styling with the syntax characters removed: . | Type | Syntax | Renders as | . | Bold | **bold** | bold | . | Italic | *italic* | italic | . | Strikethrough | ~~strike~~ | strike | . | Inline code | `code` | monospace code | . | Link | [label](https://example.com) | a tappable label | . When composing, focus the message field and type at least three characters to reveal a formatting toolbar below the input. Select text and tap a style to wrap it (tap again to remove it); with no selection, a style inserts an empty pair with the cursor between the markers. The link button opens a dialog to enter a URL. As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 Tip: Formatting is carried as literal characters on the mesh — the same bytes iOS sends. Clients that don’t support Markdown (older apps, plain firmware clients) will show the raw **/~~ characters. URLs, email addresses, and phone numbers are still auto-linked whether or not you use Markdown. Mentions . Type @ while composing to mention a node — a picker suggests matching contacts as you type. In a received message, a mention appears as a highlighted chip showing the node’s name; tap it to jump straight to that node’s detail page. Reactions . React to messages with emoji: . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. Message Actions . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | Reply — quote the message in your response | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . Message Priority . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . Message Limits . | Maximum length: 200 bytes (approximately 200 characters for ASCII text) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | Rate limiting: The mesh enforces airtime fairness; heavy message volume may be throttled | Delivery: Messages are retried automatically if no acknowledgment is received | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/messages-and-channels.html#message-features",
    
    "relUrl": "/hr-rHR/user/messages-and-channels.html#message-features"
  },"2574": {
    "doc": "Messages & Channels",
    "title": "Best Practices",
    "content": ". | 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 | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/messages-and-channels.html#best-practices",
    
    "relUrl": "/hr-rHR/user/messages-and-channels.html#best-practices"
  },"2575": {
    "doc": "Messages & Channels",
    "title": "Related Topics",
    "content": ". | Nodes — tap a node to start a direct message | Settings — Radio & User — configure channel encryption and presets | MQTT — bridge channel messages to the internet | Channel configuration — detailed channel settings on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/messages-and-channels.html#related-topics",
    
    "relUrl": "/hr-rHR/user/messages-and-channels.html#related-topics"
  },"2576": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": " ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/messages-and-channels.html",
    
    "relUrl": "/hr-rHR/user/messages-and-channels.html"
  },"2577": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": "Meshtastic supports two communication modes: channel broadcasts and direct messages. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/messages-and-channels.html#messages--channels",
    
    "relUrl": "/pt-rPT/user/messages-and-channels.html#messages--channels"
  },"2578": {
    "doc": "Messages & Channels",
    "title": "Canal",
    "content": "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 radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. Channel Security . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | Icon | What it means | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: 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 . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/messages-and-channels.html#canal",
    
    "relUrl": "/pt-rPT/user/messages-and-channels.html#canal"
  },"2579": {
    "doc": "Messages & Channels",
    "title": "Direct Messages",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. Sending a Direct Message . | Open the Messages tab. | Select a conversation, or tap a node in the node list. | Type your message and tap Send. | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. Message States . A status label appears under your own outgoing messages only (incoming messages from others show no status label): . | State | Meaning | . | Sending… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | Delivered to recipient | The strongest confirmation for a direct message — an acknowledgment came back | . | Delivered to mesh | For a channel broadcast, the message reached the mesh (broadcasts have no per-recipient ack) | . | Relayed, not confirmed by recipient | For a direct message, shown in a warning color — the message was relayed but no acknowledgment has come back yet | . | Routing via SF++ chain… | Being routed/buffered by the Store & Forward Plus Plus chain | . | Confirmed on SF++ chain | Confirmed delivered via the SF++ chain | . | Erros | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Erros | Meaning | What to Do | . | Sem rota | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Rate limited | The mesh is throttling you for sending too fast | Wait before sending again. | . | Not authorized | The destination refused the request | Check you have the right channel and keys for that node. | . | Recipient needs your key | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | Recipient key unavailable | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | Could not send encrypted message | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Admin session expired | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Admin key not authorized | The target node does not accept your admin key | Verify the admin key matches on both nodes. | . | Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. | . | Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. | . | No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. | . | Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. | . | Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/messages-and-channels.html#direct-messages",
    
    "relUrl": "/pt-rPT/user/messages-and-channels.html#direct-messages"
  },"2580": {
    "doc": "Messages & Channels",
    "title": "Message Features",
    "content": "Quick Chat . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Searching Messages . You can search the full history of any conversation directly from the chat screen: . | Open a conversation (a channel or a direct message). | Tap the search icon in the top bar. | Type into the Search messages… field. The search runs as you type, across all stored messages in that conversation. | Use the N / M result counter and the previous / next arrows to jump between matches, which are highlighted in the conversation. | . 💡 Tip: Search is full-text and stays within the conversation you opened it from — it doesn’t search across other channels or contacts. It matches against the messages already stored on your device, so it works fully offline. 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. Text Formatting . Messages support lightweight inline Markdown. Received messages render the styling with the syntax characters removed: . | Tipo | Syntax | Renders as | . | Bold | **bold** | bold | . | Italic | *italic* | italic | . | Strikethrough | ~~strike~~ | strike | . | Inline code | `code` | monospace code | . | Link | [label](https://example.com) | a tappable label | . When composing, focus the message field and type at least three characters to reveal a formatting toolbar below the input. Select text and tap a style to wrap it (tap again to remove it); with no selection, a style inserts an empty pair with the cursor between the markers. The link button opens a dialog to enter a URL. As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 Tip: Formatting is carried as literal characters on the mesh — the same bytes iOS sends. Clients that don’t support Markdown (older apps, plain firmware clients) will show the raw **/~~ characters. URLs, email addresses, and phone numbers are still auto-linked whether or not you use Markdown. Mentions . Type @ while composing to mention a node — a picker suggests matching contacts as you type. In a received message, a mention appears as a highlighted chip showing the node’s name; tap it to jump straight to that node’s detail page. Reactions . React to messages with emoji: . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. Message Actions . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | Reply — quote the message in your response | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . Message Priority . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . Message Limits . | Maximum length: 200 bytes (approximately 200 characters for ASCII text) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | Rate limiting: The mesh enforces airtime fairness; heavy message volume may be throttled | Delivery: Messages are retried automatically if no acknowledgment is received | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/messages-and-channels.html#message-features",
    
    "relUrl": "/pt-rPT/user/messages-and-channels.html#message-features"
  },"2581": {
    "doc": "Messages & Channels",
    "title": "Best Practices",
    "content": ". | 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 | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/messages-and-channels.html#best-practices",
    
    "relUrl": "/pt-rPT/user/messages-and-channels.html#best-practices"
  },"2582": {
    "doc": "Messages & Channels",
    "title": "Related Topics",
    "content": ". | Nodes — tap a node to start a direct message | Settings — Radio & User — configure channel encryption and presets | MQTT — bridge channel messages to the internet | Channel configuration — detailed channel settings on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/messages-and-channels.html#related-topics",
    
    "relUrl": "/pt-rPT/user/messages-and-channels.html#related-topics"
  },"2583": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": " ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/messages-and-channels.html",
    
    "relUrl": "/pt-rPT/user/messages-and-channels.html"
  },"2584": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": "Meshtastic supports two communication modes: channel broadcasts and direct messages. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/messages-and-channels.html#messages--channels",
    
    "relUrl": "/pl-rPL/user/messages-and-channels.html#messages--channels"
  },"2585": {
    "doc": "Messages & Channels",
    "title": "Kanały",
    "content": "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 radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. Bezpieczeństwo kanału . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | Icon | What it means | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: 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 . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/messages-and-channels.html#kana%C5%82y",
    
    "relUrl": "/pl-rPL/user/messages-and-channels.html#kanały"
  },"2586": {
    "doc": "Messages & Channels",
    "title": "Bezpośrednie Wiadomości",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. Sending a Direct Message . | Open the Messages tab. | Select a conversation, or tap a node in the node list. | Type your message and tap Send. | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. Message States . A status label appears under your own outgoing messages only (incoming messages from others show no status label): . | State | Meaning | . | Sending… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | Delivered to recipient | The strongest confirmation for a direct message — an acknowledgment came back | . | Delivered to mesh | For a channel broadcast, the message reached the mesh (broadcasts have no per-recipient ack) | . | Relayed, not confirmed by recipient | For a direct message, shown in a warning color — the message was relayed but no acknowledgment has come back yet | . | Routing via SF++ chain… | Being routed/buffered by the Store & Forward Plus Plus chain | . | Confirmed on SF++ chain | Confirmed delivered via the SF++ chain | . | Błąd | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Błąd | Meaning | What to Do | . | Brak trasy | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Rate limited | The mesh is throttling you for sending too fast | Wait before sending again. | . | Not authorized | The destination refused the request | Check you have the right channel and keys for that node. | . | Recipient needs your key | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | Recipient key unavailable | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | Could not send encrypted message | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Admin session expired | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Admin key not authorized | The target node does not accept your admin key | Verify the admin key matches on both nodes. | . | Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. | . | Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. | . | No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. | . | Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. | . | Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/messages-and-channels.html#bezpo%C5%9Brednie-wiadomo%C5%9Bci",
    
    "relUrl": "/pl-rPL/user/messages-and-channels.html#bezpośrednie-wiadomości"
  },"2587": {
    "doc": "Messages & Channels",
    "title": "Message Features",
    "content": "Quick Chat . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Searching Messages . You can search the full history of any conversation directly from the chat screen: . | Open a conversation (a channel or a direct message). | Tap the search icon in the top bar. | Type into the Search messages… field. The search runs as you type, across all stored messages in that conversation. | Use the N / M result counter and the previous / next arrows to jump between matches, which are highlighted in the conversation. | . 💡 Tip: Search is full-text and stays within the conversation you opened it from — it doesn’t search across other channels or contacts. It matches against the messages already stored on your device, so it works fully offline. 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. Text Formatting . Messages support lightweight inline Markdown. Received messages render the styling with the syntax characters removed: . | Typ | Syntax | Renders as | . | Bold | **bold** | bold | . | Italic | *italic* | italic | . | Strikethrough | ~~strike~~ | strike | . | Inline code | `code` | monospace code | . | Link | [label](https://example.com) | a tappable label | . When composing, focus the message field and type at least three characters to reveal a formatting toolbar below the input. Select text and tap a style to wrap it (tap again to remove it); with no selection, a style inserts an empty pair with the cursor between the markers. The link button opens a dialog to enter a URL. As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 Tip: Formatting is carried as literal characters on the mesh — the same bytes iOS sends. Clients that don’t support Markdown (older apps, plain firmware clients) will show the raw **/~~ characters. URLs, email addresses, and phone numbers are still auto-linked whether or not you use Markdown. Mentions . Type @ while composing to mention a node — a picker suggests matching contacts as you type. In a received message, a mention appears as a highlighted chip showing the node’s name; tap it to jump straight to that node’s detail page. Reactions . React to messages with emoji: . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. Message Actions . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | Reply — quote the message in your response | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . Message Priority . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . Message Limits . | Maximum length: 200 bytes (approximately 200 characters for ASCII text) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | Rate limiting: The mesh enforces airtime fairness; heavy message volume may be throttled | Delivery: Messages are retried automatically if no acknowledgment is received | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/messages-and-channels.html#message-features",
    
    "relUrl": "/pl-rPL/user/messages-and-channels.html#message-features"
  },"2588": {
    "doc": "Messages & Channels",
    "title": "Best Practices",
    "content": ". | 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 | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/messages-and-channels.html#best-practices",
    
    "relUrl": "/pl-rPL/user/messages-and-channels.html#best-practices"
  },"2589": {
    "doc": "Messages & Channels",
    "title": "Related Topics",
    "content": ". | Nodes — tap a node to start a direct message | Settings — Radio & User — configure channel encryption and presets | MQTT — bridge channel messages to the internet | Channel configuration — detailed channel settings on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/messages-and-channels.html#related-topics",
    
    "relUrl": "/pl-rPL/user/messages-and-channels.html#related-topics"
  },"2590": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": " ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/messages-and-channels.html",
    
    "relUrl": "/pl-rPL/user/messages-and-channels.html"
  },"2591": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": "Meshtastic supports two communication modes: channel broadcasts and direct messages. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/messages-and-channels.html#messages--channels",
    
    "relUrl": "/zh-rCN/user/messages-and-channels.html#messages--channels"
  },"2592": {
    "doc": "Messages & Channels",
    "title": "频道",
    "content": "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 radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. 频道安全 . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | 图标 | What it means | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: 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 . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/messages-and-channels.html#%E9%A2%91%E9%81%93",
    
    "relUrl": "/zh-rCN/user/messages-and-channels.html#频道"
  },"2593": {
    "doc": "Messages & Channels",
    "title": "私聊",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. Sending a Direct Message . | Open the Messages tab. | Select a conversation, or tap a node in the node list. | Type your message and tap Send. | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. Message States . A status label appears under your own outgoing messages only (incoming messages from others show no status label): . | State | Meaning | . | Sending… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | Delivered to recipient | The strongest confirmation for a direct message — an acknowledgment came back | . | 已发送至网状网络 | For a channel broadcast, the message reached the mesh (broadcasts have no per-recipient ack) | . | Relayed, not confirmed by recipient | For a direct message, shown in a warning color — the message was relayed but no acknowledgment has come back yet | . | 通过 SF++ 链路路由… | Being routed/buffered by the Store & Forward Plus Plus chain | . | 已在 SF++ 链上确认 | Confirmed delivered via the SF++ chain | . | 错误 | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | 错误 | Meaning | What to Do | . | 无路径 | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | 发送至MESH失败 | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Rate limited | The mesh is throttling you for sending too fast | Wait before sending again. | . | Not authorized | The destination refused the request | Check you have the right channel and keys for that node. | . | 接收方需要你的密钥 | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | 接收方密钥不可用 | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | 无法发送加密消息 | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Admin session expired | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Admin key not authorized | The target node does not accept your admin key | Verify the admin key matches on both nodes. | . | Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. | . | 消息太大，无法发送 | Message exceeds maximum payload size | Shorten the message and try again. | . | No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. | . | Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. | . | Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/messages-and-channels.html#%E7%A7%81%E8%81%8A",
    
    "relUrl": "/zh-rCN/user/messages-and-channels.html#私聊"
  },"2594": {
    "doc": "Messages & Channels",
    "title": "Message Features",
    "content": "Quick Chat . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Searching Messages . You can search the full history of any conversation directly from the chat screen: . | Open a conversation (a channel or a direct message). | Tap the search icon in the top bar. | Type into the Search messages… field. The search runs as you type, across all stored messages in that conversation. | Use the N / M result counter and the previous / next arrows to jump between matches, which are highlighted in the conversation. | . 💡 Tip: Search is full-text and stays within the conversation you opened it from — it doesn’t search across other channels or contacts. It matches against the messages already stored on your device, so it works fully offline. 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. Text Formatting . Messages support lightweight inline Markdown. Received messages render the styling with the syntax characters removed: . | 类型 | Syntax | Renders as | . | Bold | **bold** | bold | . | Italic | *italic* | italic | . | Strikethrough | ~~strike~~ | strike | . | Inline code | `code` | monospace code | . | Link | [label](https://example.com) | a tappable label | . When composing, focus the message field and type at least three characters to reveal a formatting toolbar below the input. Select text and tap a style to wrap it (tap again to remove it); with no selection, a style inserts an empty pair with the cursor between the markers. The link button opens a dialog to enter a URL. As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 Tip: Formatting is carried as literal characters on the mesh — the same bytes iOS sends. Clients that don’t support Markdown (older apps, plain firmware clients) will show the raw **/~~ characters. URLs, email addresses, and phone numbers are still auto-linked whether or not you use Markdown. Mentions . Type @ while composing to mention a node — a picker suggests matching contacts as you type. In a received message, a mention appears as a highlighted chip showing the node’s name; tap it to jump straight to that node’s detail page. Reactions . React to messages with emoji: . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. Message Actions . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | Reply — quote the message in your response | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . Message Priority . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . Message Limits . | Maximum length: 200 bytes (approximately 200 characters for ASCII text) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | Rate limiting: The mesh enforces airtime fairness; heavy message volume may be throttled | Delivery: Messages are retried automatically if no acknowledgment is received | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/messages-and-channels.html#message-features",
    
    "relUrl": "/zh-rCN/user/messages-and-channels.html#message-features"
  },"2595": {
    "doc": "Messages & Channels",
    "title": "Best Practices",
    "content": ". | 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 | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/messages-and-channels.html#best-practices",
    
    "relUrl": "/zh-rCN/user/messages-and-channels.html#best-practices"
  },"2596": {
    "doc": "Messages & Channels",
    "title": "Related Topics",
    "content": ". | Nodes — tap a node to start a direct message | Settings — Radio & User — configure channel encryption and presets | MQTT — bridge channel messages to the internet | Channel configuration — detailed channel settings on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/messages-and-channels.html#related-topics",
    
    "relUrl": "/zh-rCN/user/messages-and-channels.html#related-topics"
  },"2597": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": " ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/messages-and-channels.html",
    
    "relUrl": "/zh-rCN/user/messages-and-channels.html"
  },"2598": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": "Meshtastic supports two communication modes: channel broadcasts and direct messages. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/messages-and-channels.html#messages--channels",
    
    "relUrl": "/sq-rAL/user/messages-and-channels.html#messages--channels"
  },"2599": {
    "doc": "Messages & Channels",
    "title": "Channels",
    "content": "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 radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. Channel Security . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | Icon | What it means | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: 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 . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/messages-and-channels.html#channels",
    
    "relUrl": "/sq-rAL/user/messages-and-channels.html#channels"
  },"2600": {
    "doc": "Messages & Channels",
    "title": "Direct Messages",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. Sending a Direct Message . | Open the Messages tab. | Select a conversation, or tap a node in the node list. | Type your message and tap Send. | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. Message States . A status label appears under your own outgoing messages only (incoming messages from others show no status label): . | State | Meaning | . | Sending… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | Delivered to recipient | The strongest confirmation for a direct message — an acknowledgment came back | . | Delivered to mesh | For a channel broadcast, the message reached the mesh (broadcasts have no per-recipient ack) | . | Relayed, not confirmed by recipient | For a direct message, shown in a warning color — the message was relayed but no acknowledgment has come back yet | . | Routing via SF++ chain… | Being routed/buffered by the Store & Forward Plus Plus chain | . | Confirmed on SF++ chain | Confirmed delivered via the SF++ chain | . | Gabim | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Gabim | Meaning | What to Do | . | Nuk ka rrugë | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Rate limited | The mesh is throttling you for sending too fast | Wait before sending again. | . | Not authorized | The destination refused the request | Check you have the right channel and keys for that node. | . | Recipient needs your key | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | Recipient key unavailable | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | Could not send encrypted message | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Admin session expired | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Admin key not authorized | The target node does not accept your admin key | Verify the admin key matches on both nodes. | . | Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. | . | Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. | . | No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. | . | Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. | . | Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/messages-and-channels.html#direct-messages",
    
    "relUrl": "/sq-rAL/user/messages-and-channels.html#direct-messages"
  },"2601": {
    "doc": "Messages & Channels",
    "title": "Message Features",
    "content": "Quick Chat . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Searching Messages . You can search the full history of any conversation directly from the chat screen: . | Open a conversation (a channel or a direct message). | Tap the search icon in the top bar. | Type into the Search messages… field. The search runs as you type, across all stored messages in that conversation. | Use the N / M result counter and the previous / next arrows to jump between matches, which are highlighted in the conversation. | . 💡 Tip: Search is full-text and stays within the conversation you opened it from — it doesn’t search across other channels or contacts. It matches against the messages already stored on your device, so it works fully offline. 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. Text Formatting . Messages support lightweight inline Markdown. Received messages render the styling with the syntax characters removed: . | Type | Syntax | Renders as | . | Bold | **bold** | bold | . | Italic | *italic* | italic | . | Strikethrough | ~~strike~~ | strike | . | Inline code | `code` | monospace code | . | Link | [label](https://example.com) | a tappable label | . When composing, focus the message field and type at least three characters to reveal a formatting toolbar below the input. Select text and tap a style to wrap it (tap again to remove it); with no selection, a style inserts an empty pair with the cursor between the markers. The link button opens a dialog to enter a URL. As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 Tip: Formatting is carried as literal characters on the mesh — the same bytes iOS sends. Clients that don’t support Markdown (older apps, plain firmware clients) will show the raw **/~~ characters. URLs, email addresses, and phone numbers are still auto-linked whether or not you use Markdown. Mentions . Type @ while composing to mention a node — a picker suggests matching contacts as you type. In a received message, a mention appears as a highlighted chip showing the node’s name; tap it to jump straight to that node’s detail page. Reactions . React to messages with emoji: . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. Message Actions . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | Reply — quote the message in your response | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . Message Priority . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . Message Limits . | Maximum length: 200 bytes (approximately 200 characters for ASCII text) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | Rate limiting: The mesh enforces airtime fairness; heavy message volume may be throttled | Delivery: Messages are retried automatically if no acknowledgment is received | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/messages-and-channels.html#message-features",
    
    "relUrl": "/sq-rAL/user/messages-and-channels.html#message-features"
  },"2602": {
    "doc": "Messages & Channels",
    "title": "Best Practices",
    "content": ". | 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 | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/messages-and-channels.html#best-practices",
    
    "relUrl": "/sq-rAL/user/messages-and-channels.html#best-practices"
  },"2603": {
    "doc": "Messages & Channels",
    "title": "Related Topics",
    "content": ". | Nodes — tap a node to start a direct message | Settings — Radio & User — configure channel encryption and presets | MQTT — bridge channel messages to the internet | Channel configuration — detailed channel settings on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/messages-and-channels.html#related-topics",
    
    "relUrl": "/sq-rAL/user/messages-and-channels.html#related-topics"
  },"2604": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": " ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/messages-and-channels.html",
    
    "relUrl": "/sq-rAL/user/messages-and-channels.html"
  },"2605": {
    "doc": "訊息與頻道",
    "title": "訊息與頻道",
    "content": "Meshtastic 支援兩種通訊模式：頻道廣播與私訊。 . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/messages-and-channels.html",
    
    "relUrl": "/zh-rTW/user/messages-and-channels.html"
  },"2606": {
    "doc": "訊息與頻道",
    "title": "頻道",
    "content": "頻道是共享的通訊群組。所有設定相同頻道金鑰的節點均可在該頻道上讀取與傳送訊息。 . 預設頻道 . Every Meshtastic radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. 頻道安全性 . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | 圖示 | 代表意義 | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: Always configure a unique PSK for private communications. 預設頻道刻意設計為開放，以便新使用者能探索 mesh 網路 — 但對於任何敏感內容，請另行建立獨立的加密頻道。 . 新增頻道 . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/messages-and-channels.html#%E9%A0%BB%E9%81%93",
    
    "relUrl": "/zh-rTW/user/messages-and-channels.html#頻道"
  },"2607": {
    "doc": "訊息與頻道",
    "title": "私訊",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. 傳送私訊 . | 開啟「訊息」頁籤。 | Select a conversation, or tap a node in the node list. | 輸入訊息後點選「傳送」。 | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. 訊息狀態 . A status label appears under your own outgoing messages only (incoming messages from others show no status label): . | 狀態 | 含義 | . | Sending… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | Delivered to recipient | The strongest confirmation for a direct message — an acknowledgment came back | . | 已傳送至 Mesh | For a channel broadcast, the message reached the mesh (broadcasts have no per-recipient ack) | . | Relayed, not confirmed by recipient | For a direct message, shown in a warning color — the message was relayed but no acknowledgment has come back yet | . | 透過 SF++ 鏈路由… | Being routed/buffered by the Store & Forward Plus Plus chain | . | 已在 SF++ 鏈上確認 | Confirmed delivered via the SF++ chain | . | 錯誤 | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . 傳遞錯誤 . 當訊息傳遞失敗時，錯誤指示器將顯示問題原因： . | 錯誤 | 含義 | 處理方式 | . | 無路徑 | 無法找到通往目標節點的路徑 | 收件者可能已離線或超出 mesh 網路範圍。請稍後再試，或靠近對方後重新傳送。 | . | No radio interface | 無可用的無線電介面進行傳送 | Check that your radio is connected and available. | . | Failed to deliver to mesh | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Rate limited | The mesh is throttling you for sending too fast | Wait before sending again. | . | Not authorized | The destination refused the request | Check you have the right channel and keys for that node. | . | Recipient needs your key | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | Recipient key unavailable | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | Could not send encrypted message | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Admin session expired | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Admin key not authorized | The target node does not accept your admin key | Verify the admin key matches on both nodes. | . | Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. | . | Message is too large to send | 訊息超過最大承載大小 | Shorten the message and try again. | . | No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. | . | Duty cycle limit | 已達地區無線電佔用時間上限 | Wait for the duty cycle window to reset. | . | Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. | . 💡 提示：大多數傳遞錯誤會自動解決。若節點間歇性可到達，mesh 網路將自動重試。 For persistent No route errors, check that intermediate Router nodes are online. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/messages-and-channels.html#%E7%A7%81%E8%A8%8A",
    
    "relUrl": "/zh-rTW/user/messages-and-channels.html#私訊"
  },"2608": {
    "doc": "訊息與頻道",
    "title": "訊息功能",
    "content": "快速聊天 . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Searching Messages . You can search the full history of any conversation directly from the chat screen: . | Open a conversation (a channel or a direct message). | Tap the search icon in the top bar. | Type into the Search messages… field. The search runs as you type, across all stored messages in that conversation. | Use the N / M result counter and the previous / next arrows to jump between matches, which are highlighted in the conversation. | . 💡 Tip: Search is full-text and stays within the conversation you opened it from — it doesn’t search across other channels or contacts. It matches against the messages already stored on your device, so it works fully offline. 訊息泡泡 . 訊息以對話泡泡的形式顯示 — 已傳送的訊息在右側，收到的訊息在左側。每個泡泡顯示傳送者、時間戳記及傳遞狀態。含有回覆的訊息，會在回覆內容上方顯示原始訊息的引用預覽。 . Text Formatting . Messages support lightweight inline Markdown. Received messages render the styling with the syntax characters removed: . | 類型 | Syntax | Renders as | . | Bold | **bold** | bold | . | Italic | *italic* | italic | . | Strikethrough | ~~strike~~ | strike | . | Inline code | `code` | monospace code | . | Link | [label](https://example.com) | a tappable label | . When composing, focus the message field and type at least three characters to reveal a formatting toolbar below the input. Select text and tap a style to wrap it (tap again to remove it); with no selection, a style inserts an empty pair with the cursor between the markers. The link button opens a dialog to enter a URL. As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 Tip: Formatting is carried as literal characters on the mesh — the same bytes iOS sends. Clients that don’t support Markdown (older apps, plain firmware clients) will show the raw **/~~ characters. URLs, email addresses, and phone numbers are still auto-linked whether or not you use Markdown. Mentions . Type @ while composing to mention a node — a picker suggests matching contacts as you type. In a received message, a mention appears as a highlighted chip showing the node’s name; tap it to jump straight to that node’s detail page. 訊息回應 . 以表情符號對訊息作出回應： . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | 訊息回應顯示於訊息泡泡下方 | 多位使用者可對同一則訊息作出回應 | 可對自己或他人的訊息作出回應 | . 💡 提示：訊息回應非常輕量 — 相較於完整文字訊息，佔用極少的 mesh 網路頻寬。 . Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. 訊息動作 . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | 回覆 — 在回覆中引用該訊息 | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . 訊息優先順序 . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . 訊息限制 . | Maximum length: 200 bytes (approximately 200 characters for ASCII text) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | 速率限制：mesh 網路會執行無線電佔用時間公平性管制；大量訊息可能會被節流 | 傳遞：若未收到確認回應，訊息將自動重試 | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/messages-and-channels.html#%E8%A8%8A%E6%81%AF%E5%8A%9F%E8%83%BD",
    
    "relUrl": "/zh-rTW/user/messages-and-channels.html#訊息功能"
  },"2609": {
    "doc": "訊息與頻道",
    "title": "最佳實踐",
    "content": ". | 群組協調請使用頻道 | 個人私下通訊請使用私訊 | 訊息請盡量簡短 — mesh 網路頻寬有限 | 敏感通訊請設定加密 | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/messages-and-channels.html#%E6%9C%80%E4%BD%B3%E5%AF%A6%E8%B8%90",
    
    "relUrl": "/zh-rTW/user/messages-and-channels.html#最佳實踐"
  },"2610": {
    "doc": "訊息與頻道",
    "title": "相關主題",
    "content": ". | 〔節點〕(nodes) — 點選節點以開始傳送私訊 | 〔設定——無線電與使用者〕(settings-radio-user) — 設定頻道加密與預設值 | 〔MQTT〕(mqtt) — 將頻道訊息橋接至網際網路 | Channel configuration — detailed channel settings on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/messages-and-channels.html#%E7%9B%B8%E9%97%9C%E4%B8%BB%E9%A1%8C",
    
    "relUrl": "/zh-rTW/user/messages-and-channels.html#相關主題"
  },"2611": {
    "doc": "Sõnumid ja kanalid",
    "title": "Sõnumid ja kanalid",
    "content": "Meshtastic toetab kahte suhtlusrežiimi: kanalite levitamine ja otsesõnumid. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/messages-and-channels.html",
    
    "relUrl": "/et-rEE/user/messages-and-channels.html"
  },"2612": {
    "doc": "Sõnumid ja kanalid",
    "title": "Kanal",
    "content": "Kanalid on jagatud suhtlusgrupid. Kõik sama kanalivõtmega seadistatud sõlmed saavad sellel kanalil sõnumeid lugeda ja saata. Vaikekanal . Every Meshtastic radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. Kanali turvalisus . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | Ikoon | What it means | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: Always configure a unique PSK for private communications. Vaikimisi kanal on tahtlikult avatud, et uued kasutajad saaksid kärgvõrku avastada – aga kõige tundliku jaoks peaksite looma eraldi krüptitud kanali. Lisa kanal . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/messages-and-channels.html#kanal",
    
    "relUrl": "/et-rEE/user/messages-and-channels.html#kanal"
  },"2613": {
    "doc": "Sõnumid ja kanalid",
    "title": "Otsesõnumid",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. Sending a Direct Message . | Ava vahekaart Sõnumid. | Select a conversation, or tap a node in the node list. | Tippi oma sõnum ja puuduta nuppu Saada. | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. Sõnumi olek . Olekumärgis kuvatakse ainult sinu enda väljaminevate sõnumite all (teiste sissetulevate sõnumite puhul olekumärgist ei kuvata): . | Olek | Tähendus | . | Saadan… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | Saajale kätte toimetatud | Kõige tugevam kinnitus otsesõnumile – vastus tuli | . | Kärgvõrku kohale jõudnud | Kanali leviedastuse puhul jõuab sõnum kärgvõrku (leviedastustel puudub saajapõhine kinnitus) | . | Vahendatud, saaja pole kinnitanud | Otsesõnumi puhul kuvatakse hoiatusvärviga – sõnum edastati, kuid kinnitust pole veel tulnud | . | Marsruutimine SF++ ahela kaudu… | Being routed/buffered by the Store & Forward Plus Plus chain | . | Kinnitatud SF++ ahel | Kinnitatud kohaletoimetamine SF++ keti kaudu | . | Tõrge | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . Delivery Errors . Kui sõnumit ei õnnestu kohale toimetada, näitab veaindikaator, mis valesti läks: . | Tõrge | Tähendab | Mida teha | . | Marsruuti pole | Sihtkoha sõlmeni pole teed olemas | Saaja võib olla võrguühenduseta või võrguühenduse levialast väljas. Try later or move closer. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Piiratud määr | The mesh is throttling you for sending too fast | Wait before sending again. | . | Pole autoriseeritud | The destination refused the request | Check you have the right channel and keys for that node. | . | Saaja vajab sinu võtit | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | Saaja võti pole saadaval | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | Krüptitud sõnumi saatmine ebaõnnestus | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Admin sessioon aegunud | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Administraatori võti pole autoriseeritud | The target node does not accept your admin key | Veendu, et administraatori võti sobiks mõlemas sõlmele. | . | Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. | . | Sõnum on saatmiseks liiga pikk | Sõnum ületab maksimaalset sõnumi mahtu | Lühenda sõnumit ja proovi uuesti. | . | No app response | App or plugin did not respond to the request | Proovi uuesti või kontrolli sihtrakenduse või -mooduli olekut. | . | Töötsükli piirang | Regional airtime limit reached | Oota, kuni töötsükli aken lähtestub. | . | Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. | . 💡 Vihje: Enamik kohaletoimetamise vigu laheneb iseenesest. If a node is intermittently reachable, the mesh will retry. For persistent No route errors, check that intermediate Router nodes are online. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/messages-and-channels.html#otses%C3%B5numid",
    
    "relUrl": "/et-rEE/user/messages-and-channels.html#otsesõnumid"
  },"2614": {
    "doc": "Sõnumid ja kanalid",
    "title": "Sõnumi omadused",
    "content": "Kiirvestlus . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Uus kiirvestluse dialoog nime, sõnumi ja kohese saatmise lülitiga . Otsin sõnumeid . Saad otsida mis tahes vestluse kogu ajaloost otse vestlusekraanilt: . | Ava vestlus (kanal või otsesõnum). | Puuduta ülemisel ribal otsinguikooni. | Tipi väljale Otsi sõnumeid…. Otsing toimub tippimise ajal kõigis selle vestluse salvestatud sõnumites. | Use the N / M result counter and the previous / next arrows to jump between matches, which are highlighted in the conversation. | . 💡 Vihje: Otsing toimub täisteksti põhjal ja jääb vestlusse, kust sa selle avasid – see ei otsi teistest kanalitest ega kontaktide hulgast. See võrdleb seadmesse juba salvestatud sõnumeid, seega töötab see täielikult võrguühenduseta. Sõnumimullid . Sõnumid kuvatakse vestlusmullidena – saadetud sõnumid paremal, vastuvõetud sõnumid vasakul. Iga mull näitab saatjat, ajatempli ja kohaletoimetamise olekut. Messages with replies include a quoted preview of the original message above the response. Teksti vormindamine . Messages support lightweight inline Markdown. Received messages render the styling with the syntax characters removed: . | Tüüp | Syntax | Renders as | . | Paks | **paks** | paks | . | Italic | *italic* | italic | . | Läbikriipsutatud | ~~läbikriips~~ | läbikriips | . | Inline code | `kood` | monospace code | . | Ühendus | [silt](https://example.com) | a tappable label | . When composing, focus the message field and type at least three characters to reveal a formatting toolbar below the input. Vali tekst ja puuduta stiili, et see murda (puuduta uuesti, et see eemaldada); kui valikut pole, lisab stiil tühja paari, kusjuures kursor on markerite vahel. Linginupp avab URL-i sisestamiseks dialoogiboksi. As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 Vihje: Vormindus kantakse kärgvõrgu literaalmärkidena – samad baidid, mida iOS saadab. Kliendid, mis ei toeta Markdowni (vanemad rakendused, tavalised püsivara kliendid), kuvavad toored **/~~ märgid. URL-id, e-posti aadressid ja telefoninumbrid lingitakse endiselt automaatselt olenemata sellest, kas kasutate Markdowni või mitte. Mainimine . Type @ while composing to mention a node — a picker suggests matching contacts as you type. Saadud sõnumis kuvatakse mainimine esiletõstetud kiibina, mis näitab sõlme nime; puuduta seda, et hüpata otse selle sõlme üksikasjade lehele. Reaktsioonid . React to messages with emoji: . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | Reaktsioonid kuvatakse sõnumimulli all | Mitu kasutajat saavad samale sõnumile reageerida | Reageeri oma või teiste sõnumitele | . 💡 Vihje: Reaktsioonid on kerged – need kasutavad täistekstisõnumitega võrreldes minimaalselt võrgu ribalaiust. Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. Message Actions . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | Vasta – tsiteeri oma vastuses sõnumit | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . Sõnumi prioriteet . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . Message Limits . | Maximum length: 200 bytes (approximately 200 characters for ASCII text) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | Kiiruse piiramine: Võrk tagab eetriaja õigluse; suurte sõnumite mahtu võidakse piirata | Kohaletoimetamine: Kui kinnitust ei ole saabunud, proovitakse sõnumeid automaatselt uuesti saata | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/messages-and-channels.html#s%C3%B5numi-omadused",
    
    "relUrl": "/et-rEE/user/messages-and-channels.html#sõnumi-omadused"
  },"2615": {
    "doc": "Sõnumid ja kanalid",
    "title": "Parimad tavad",
    "content": ". | Kasuta kanaleid grupi koordineerimiseks | Kasutage privaatseks inimestevaheliseks suhtluseks otsesõnumeid | Hoidke sõnumid lühikesed – võrgu ribalaius on piiratud | Configure encryption for sensitive communications | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/messages-and-channels.html#parimad-tavad",
    
    "relUrl": "/et-rEE/user/messages-and-channels.html#parimad-tavad"
  },"2616": {
    "doc": "Sõnumid ja kanalid",
    "title": "Seotud teemad",
    "content": ". | [Sõlmed] (nodes) — otsesõnumi alustamiseks puuduta sõlme | Seaded — Raadio ja kasutaja — kanalite krüpteerimise ja eelseadete konfimine | MQTT — silda kanali sõnumid internetti | Kanali konf — üksikasjalikud kanali seaded leiate aadressilt meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/messages-and-channels.html#seotud-teemad",
    
    "relUrl": "/et-rEE/user/messages-and-channels.html#seotud-teemad"
  },"2617": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": "Meshtastic supports two communication modes: channel broadcasts and direct messages. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/messages-and-channels.html#messages--channels",
    
    "relUrl": "/fr-rFR/user/messages-and-channels.html#messages--channels"
  },"2618": {
    "doc": "Messages & Channels",
    "title": "Canaux",
    "content": "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 radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. Sécurité du canal . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | Icon | What it means | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: 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 . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/messages-and-channels.html#canaux",
    
    "relUrl": "/fr-rFR/user/messages-and-channels.html#canaux"
  },"2619": {
    "doc": "Messages & Channels",
    "title": "Messages directs",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. Sending a Direct Message . | Open the Messages tab. | Select a conversation, or tap a node in the node list. | Type your message and tap Send. | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. Message States . A status label appears under your own outgoing messages only (incoming messages from others show no status label): . | State | Meaning | . | Sending… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | Delivered to recipient | The strongest confirmation for a direct message — an acknowledgment came back | . | Délivré au nœud | For a channel broadcast, the message reached the mesh (broadcasts have no per-recipient ack) | . | Relayed, not confirmed by recipient | For a direct message, shown in a warning color — the message was relayed but no acknowledgment has come back yet | . | Routage via chaîne SF++… | Being routed/buffered by the Store & Forward Plus Plus chain | . | Confirmé via chaîne SF++ | Confirmed delivered via the SF++ chain | . | Erreur | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Erreur | Meaning | What to Do | . | Pas de routage | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Rate limited | The mesh is throttling you for sending too fast | Wait before sending again. | . | Not authorized | The destination refused the request | Check you have the right channel and keys for that node. | . | Recipient needs your key | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | Recipient key unavailable | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | Could not send encrypted message | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Admin session expired | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Admin key not authorized | The target node does not accept your admin key | Verify the admin key matches on both nodes. | . | Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. | . | Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. | . | No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. | . | Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. | . | Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/messages-and-channels.html#messages-directs",
    
    "relUrl": "/fr-rFR/user/messages-and-channels.html#messages-directs"
  },"2620": {
    "doc": "Messages & Channels",
    "title": "Message Features",
    "content": "Quick Chat . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Searching Messages . You can search the full history of any conversation directly from the chat screen: . | Open a conversation (a channel or a direct message). | Tap the search icon in the top bar. | Type into the Search messages… field. The search runs as you type, across all stored messages in that conversation. | Use the N / M result counter and the previous / next arrows to jump between matches, which are highlighted in the conversation. | . 💡 Tip: Search is full-text and stays within the conversation you opened it from — it doesn’t search across other channels or contacts. It matches against the messages already stored on your device, so it works fully offline. 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. Text Formatting . Messages support lightweight inline Markdown. Received messages render the styling with the syntax characters removed: . | Type | Syntax | Renders as | . | Bold | **bold** | bold | . | Italic | *italic* | italic | . | Strikethrough | ~~strike~~ | strike | . | Inline code | `code` | monospace code | . | Link | [label](https://example.com) | a tappable label | . When composing, focus the message field and type at least three characters to reveal a formatting toolbar below the input. Select text and tap a style to wrap it (tap again to remove it); with no selection, a style inserts an empty pair with the cursor between the markers. The link button opens a dialog to enter a URL. As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 Tip: Formatting is carried as literal characters on the mesh — the same bytes iOS sends. Clients that don’t support Markdown (older apps, plain firmware clients) will show the raw **/~~ characters. URLs, email addresses, and phone numbers are still auto-linked whether or not you use Markdown. Mentions . Type @ while composing to mention a node — a picker suggests matching contacts as you type. In a received message, a mention appears as a highlighted chip showing the node’s name; tap it to jump straight to that node’s detail page. Reactions . React to messages with emoji: . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. Message Actions . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | Reply — quote the message in your response | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . Message Priority . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . Message Limits . | Maximum length: 200 bytes (approximately 200 characters for ASCII text) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | Rate limiting: The mesh enforces airtime fairness; heavy message volume may be throttled | Delivery: Messages are retried automatically if no acknowledgment is received | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/messages-and-channels.html#message-features",
    
    "relUrl": "/fr-rFR/user/messages-and-channels.html#message-features"
  },"2621": {
    "doc": "Messages & Channels",
    "title": "Best Practices",
    "content": ". | 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 | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/messages-and-channels.html#best-practices",
    
    "relUrl": "/fr-rFR/user/messages-and-channels.html#best-practices"
  },"2622": {
    "doc": "Messages & Channels",
    "title": "Related Topics",
    "content": ". | Nodes — tap a node to start a direct message | Settings — Radio & User — configure channel encryption and presets | MQTT — bridge channel messages to the internet | Channel configuration — detailed channel settings on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/messages-and-channels.html#related-topics",
    
    "relUrl": "/fr-rFR/user/messages-and-channels.html#related-topics"
  },"2623": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": " ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/messages-and-channels.html",
    
    "relUrl": "/fr-rFR/user/messages-and-channels.html"
  },"2624": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": "Meshtastic supports two communication modes: channel broadcasts and direct messages. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/messages-and-channels.html#messages--channels",
    
    "relUrl": "/tr-rTR/user/messages-and-channels.html#messages--channels"
  },"2625": {
    "doc": "Messages & Channels",
    "title": "Kanallar",
    "content": "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 radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. Channel Security . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | Icon | What it means | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: 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 . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/messages-and-channels.html#kanallar",
    
    "relUrl": "/tr-rTR/user/messages-and-channels.html#kanallar"
  },"2626": {
    "doc": "Messages & Channels",
    "title": "Direct Messages",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. Sending a Direct Message . | Open the Messages tab. | Select a conversation, or tap a node in the node list. | Type your message and tap Send. | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. Message States . A status label appears under your own outgoing messages only (incoming messages from others show no status label): . | State | Meaning | . | Sending… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | Delivered to recipient | The strongest confirmation for a direct message — an acknowledgment came back | . | Delivered to mesh | For a channel broadcast, the message reached the mesh (broadcasts have no per-recipient ack) | . | Relayed, not confirmed by recipient | For a direct message, shown in a warning color — the message was relayed but no acknowledgment has come back yet | . | Routing via SF++ chain… | Being routed/buffered by the Store & Forward Plus Plus chain | . | Confirmed on SF++ chain | Confirmed delivered via the SF++ chain | . | Hata | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Hata | Meaning | What to Do | . | Rota yok | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Rate limited | The mesh is throttling you for sending too fast | Wait before sending again. | . | Not authorized | The destination refused the request | Check you have the right channel and keys for that node. | . | Recipient needs your key | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | Recipient key unavailable | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | Could not send encrypted message | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Admin session expired | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Admin key not authorized | The target node does not accept your admin key | Verify the admin key matches on both nodes. | . | Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. | . | Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. | . | No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. | . | Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. | . | Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/messages-and-channels.html#direct-messages",
    
    "relUrl": "/tr-rTR/user/messages-and-channels.html#direct-messages"
  },"2627": {
    "doc": "Messages & Channels",
    "title": "Message Features",
    "content": "Quick Chat . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Searching Messages . You can search the full history of any conversation directly from the chat screen: . | Open a conversation (a channel or a direct message). | Tap the search icon in the top bar. | Type into the Search messages… field. The search runs as you type, across all stored messages in that conversation. | Use the N / M result counter and the previous / next arrows to jump between matches, which are highlighted in the conversation. | . 💡 Tip: Search is full-text and stays within the conversation you opened it from — it doesn’t search across other channels or contacts. It matches against the messages already stored on your device, so it works fully offline. 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. Text Formatting . Messages support lightweight inline Markdown. Received messages render the styling with the syntax characters removed: . | Tip | Syntax | Renders as | . | Bold | **bold** | bold | . | Italic | *italic* | italic | . | Strikethrough | ~~strike~~ | strike | . | Inline code | `code` | monospace code | . | Link | [label](https://example.com) | a tappable label | . When composing, focus the message field and type at least three characters to reveal a formatting toolbar below the input. Select text and tap a style to wrap it (tap again to remove it); with no selection, a style inserts an empty pair with the cursor between the markers. The link button opens a dialog to enter a URL. As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 Tip: Formatting is carried as literal characters on the mesh — the same bytes iOS sends. Clients that don’t support Markdown (older apps, plain firmware clients) will show the raw **/~~ characters. URLs, email addresses, and phone numbers are still auto-linked whether or not you use Markdown. Mentions . Type @ while composing to mention a node — a picker suggests matching contacts as you type. In a received message, a mention appears as a highlighted chip showing the node’s name; tap it to jump straight to that node’s detail page. Reactions . React to messages with emoji: . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. Message Actions . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | Reply — quote the message in your response | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . Message Priority . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . Message Limits . | Maximum length: 200 bytes (approximately 200 characters for ASCII text) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | Rate limiting: The mesh enforces airtime fairness; heavy message volume may be throttled | Delivery: Messages are retried automatically if no acknowledgment is received | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/messages-and-channels.html#message-features",
    
    "relUrl": "/tr-rTR/user/messages-and-channels.html#message-features"
  },"2628": {
    "doc": "Messages & Channels",
    "title": "Best Practices",
    "content": ". | 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 | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/messages-and-channels.html#best-practices",
    
    "relUrl": "/tr-rTR/user/messages-and-channels.html#best-practices"
  },"2629": {
    "doc": "Messages & Channels",
    "title": "Related Topics",
    "content": ". | Nodes — tap a node to start a direct message | Settings — Radio & User — configure channel encryption and presets | MQTT — bridge channel messages to the internet | Channel configuration — detailed channel settings on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/messages-and-channels.html#related-topics",
    
    "relUrl": "/tr-rTR/user/messages-and-channels.html#related-topics"
  },"2630": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": " ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/messages-and-channels.html",
    
    "relUrl": "/tr-rTR/user/messages-and-channels.html"
  },"2631": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": "Meshtastic supports two communication modes: channel broadcasts and direct messages. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/messages-and-channels.html#messages--channels",
    
    "relUrl": "/el-rGR/user/messages-and-channels.html#messages--channels"
  },"2632": {
    "doc": "Messages & Channels",
    "title": "Κανάλια",
    "content": "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 radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. Channel Security . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | Icon | What it means | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: 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 . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/messages-and-channels.html#%CE%BA%CE%B1%CE%BD%CE%AC%CE%BB%CE%B9%CE%B1",
    
    "relUrl": "/el-rGR/user/messages-and-channels.html#κανάλια"
  },"2633": {
    "doc": "Messages & Channels",
    "title": "Direct Messages",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. Sending a Direct Message . | Open the Messages tab. | Select a conversation, or tap a node in the node list. | Type your message and tap Send. | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. Message States . A status label appears under your own outgoing messages only (incoming messages from others show no status label): . | State | Meaning | . | Sending… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | Delivered to recipient | The strongest confirmation for a direct message — an acknowledgment came back | . | Delivered to mesh | For a channel broadcast, the message reached the mesh (broadcasts have no per-recipient ack) | . | Relayed, not confirmed by recipient | For a direct message, shown in a warning color — the message was relayed but no acknowledgment has come back yet | . | Routing via SF++ chain… | Being routed/buffered by the Store & Forward Plus Plus chain | . | Confirmed on SF++ chain | Confirmed delivered via the SF++ chain | . | Σφάλμα | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . 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. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Rate limited | The mesh is throttling you for sending too fast | Wait before sending again. | . | Not authorized | The destination refused the request | Check you have the right channel and keys for that node. | . | Recipient needs your key | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | Recipient key unavailable | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | Could not send encrypted message | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Admin session expired | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Admin key not authorized | The target node does not accept your admin key | Verify the admin key matches on both nodes. | . | Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. | . | Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. | . | No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. | . | Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. | . | Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/messages-and-channels.html#direct-messages",
    
    "relUrl": "/el-rGR/user/messages-and-channels.html#direct-messages"
  },"2634": {
    "doc": "Messages & Channels",
    "title": "Message Features",
    "content": "Quick Chat . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Searching Messages . You can search the full history of any conversation directly from the chat screen: . | Open a conversation (a channel or a direct message). | Tap the search icon in the top bar. | Type into the Search messages… field. The search runs as you type, across all stored messages in that conversation. | Use the N / M result counter and the previous / next arrows to jump between matches, which are highlighted in the conversation. | . 💡 Tip: Search is full-text and stays within the conversation you opened it from — it doesn’t search across other channels or contacts. It matches against the messages already stored on your device, so it works fully offline. 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. Text Formatting . Messages support lightweight inline Markdown. Received messages render the styling with the syntax characters removed: . | Type | Syntax | Renders as | . | Bold | **bold** | bold | . | Italic | *italic* | italic | . | Strikethrough | ~~strike~~ | strike | . | Inline code | `code` | monospace code | . | Link | [label](https://example.com) | a tappable label | . When composing, focus the message field and type at least three characters to reveal a formatting toolbar below the input. Select text and tap a style to wrap it (tap again to remove it); with no selection, a style inserts an empty pair with the cursor between the markers. The link button opens a dialog to enter a URL. As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 Tip: Formatting is carried as literal characters on the mesh — the same bytes iOS sends. Clients that don’t support Markdown (older apps, plain firmware clients) will show the raw **/~~ characters. URLs, email addresses, and phone numbers are still auto-linked whether or not you use Markdown. Mentions . Type @ while composing to mention a node — a picker suggests matching contacts as you type. In a received message, a mention appears as a highlighted chip showing the node’s name; tap it to jump straight to that node’s detail page. Reactions . React to messages with emoji: . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. Message Actions . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | Reply — quote the message in your response | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . Message Priority . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . Message Limits . | Maximum length: 200 bytes (approximately 200 characters for ASCII text) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | Rate limiting: The mesh enforces airtime fairness; heavy message volume may be throttled | Delivery: Messages are retried automatically if no acknowledgment is received | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/messages-and-channels.html#message-features",
    
    "relUrl": "/el-rGR/user/messages-and-channels.html#message-features"
  },"2635": {
    "doc": "Messages & Channels",
    "title": "Best Practices",
    "content": ". | 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 | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/messages-and-channels.html#best-practices",
    
    "relUrl": "/el-rGR/user/messages-and-channels.html#best-practices"
  },"2636": {
    "doc": "Messages & Channels",
    "title": "Related Topics",
    "content": ". | Nodes — tap a node to start a direct message | Settings — Radio & User — configure channel encryption and presets | MQTT — bridge channel messages to the internet | Channel configuration — detailed channel settings on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/messages-and-channels.html#related-topics",
    
    "relUrl": "/el-rGR/user/messages-and-channels.html#related-topics"
  },"2637": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": " ",
    "url": "/Meshtastic-Android/main/el-rGR/user/messages-and-channels.html",
    
    "relUrl": "/el-rGR/user/messages-and-channels.html"
  },"2638": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": "Meshtastic supports two communication modes: channel broadcasts and direct messages. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/messages-and-channels.html#messages--channels",
    
    "relUrl": "/ro-rRO/user/messages-and-channels.html#messages--channels"
  },"2639": {
    "doc": "Messages & Channels",
    "title": "Canale",
    "content": "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 radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. Securitate canal . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | Icon | What it means | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: 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 . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/messages-and-channels.html#canale",
    
    "relUrl": "/ro-rRO/user/messages-and-channels.html#canale"
  },"2640": {
    "doc": "Messages & Channels",
    "title": "Direct Messages",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. Sending a Direct Message . | Open the Messages tab. | Select a conversation, or tap a node in the node list. | Type your message and tap Send. | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. Message States . A status label appears under your own outgoing messages only (incoming messages from others show no status label): . | State | Meaning | . | Sending… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | Delivered to recipient | The strongest confirmation for a direct message — an acknowledgment came back | . | Livrat la Mesh | For a channel broadcast, the message reached the mesh (broadcasts have no per-recipient ack) | . | Relayed, not confirmed by recipient | For a direct message, shown in a warning color — the message was relayed but no acknowledgment has come back yet | . | Rutare prin lanțul SF++… | Being routed/buffered by the Store & Forward Plus Plus chain | . | Confirmat pe lanțul SF++ | Confirmed delivered via the SF++ chain | . | Eroare | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Eroare | Meaning | What to Do | . | Nici o rută | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Rate limited | The mesh is throttling you for sending too fast | Wait before sending again. | . | Not authorized | The destination refused the request | Check you have the right channel and keys for that node. | . | Recipient needs your key | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | Recipient key unavailable | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | Could not send encrypted message | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Admin session expired | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Admin key not authorized | The target node does not accept your admin key | Verify the admin key matches on both nodes. | . | Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. | . | Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. | . | No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. | . | Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. | . | Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/messages-and-channels.html#direct-messages",
    
    "relUrl": "/ro-rRO/user/messages-and-channels.html#direct-messages"
  },"2641": {
    "doc": "Messages & Channels",
    "title": "Message Features",
    "content": "Quick Chat . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Searching Messages . You can search the full history of any conversation directly from the chat screen: . | Open a conversation (a channel or a direct message). | Tap the search icon in the top bar. | Type into the Search messages… field. The search runs as you type, across all stored messages in that conversation. | Use the N / M result counter and the previous / next arrows to jump between matches, which are highlighted in the conversation. | . 💡 Tip: Search is full-text and stays within the conversation you opened it from — it doesn’t search across other channels or contacts. It matches against the messages already stored on your device, so it works fully offline. 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. Text Formatting . Messages support lightweight inline Markdown. Received messages render the styling with the syntax characters removed: . | Tip | Syntax | Renders as | . | Bold | **bold** | bold | . | Italic | *italic* | italic | . | Strikethrough | ~~strike~~ | strike | . | Inline code | `code` | monospace code | . | Link | [label](https://example.com) | a tappable label | . When composing, focus the message field and type at least three characters to reveal a formatting toolbar below the input. Select text and tap a style to wrap it (tap again to remove it); with no selection, a style inserts an empty pair with the cursor between the markers. The link button opens a dialog to enter a URL. As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 Tip: Formatting is carried as literal characters on the mesh — the same bytes iOS sends. Clients that don’t support Markdown (older apps, plain firmware clients) will show the raw **/~~ characters. URLs, email addresses, and phone numbers are still auto-linked whether or not you use Markdown. Mentions . Type @ while composing to mention a node — a picker suggests matching contacts as you type. In a received message, a mention appears as a highlighted chip showing the node’s name; tap it to jump straight to that node’s detail page. Reactions . React to messages with emoji: . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. Message Actions . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | Reply — quote the message in your response | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . Message Priority . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . Message Limits . | Maximum length: 200 bytes (approximately 200 characters for ASCII text) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | Rate limiting: The mesh enforces airtime fairness; heavy message volume may be throttled | Delivery: Messages are retried automatically if no acknowledgment is received | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/messages-and-channels.html#message-features",
    
    "relUrl": "/ro-rRO/user/messages-and-channels.html#message-features"
  },"2642": {
    "doc": "Messages & Channels",
    "title": "Best Practices",
    "content": ". | 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 | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/messages-and-channels.html#best-practices",
    
    "relUrl": "/ro-rRO/user/messages-and-channels.html#best-practices"
  },"2643": {
    "doc": "Messages & Channels",
    "title": "Related Topics",
    "content": ". | Nodes — tap a node to start a direct message | Settings — Radio & User — configure channel encryption and presets | MQTT — bridge channel messages to the internet | Channel configuration — detailed channel settings on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/messages-and-channels.html#related-topics",
    
    "relUrl": "/ro-rRO/user/messages-and-channels.html#related-topics"
  },"2644": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": " ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/messages-and-channels.html",
    
    "relUrl": "/ro-rRO/user/messages-and-channels.html"
  },"2645": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": "Meshtastic supports two communication modes: channel broadcasts and direct messages. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/messages-and-channels.html#messages--channels",
    
    "relUrl": "/iw-rIL/user/messages-and-channels.html#messages--channels"
  },"2646": {
    "doc": "Messages & Channels",
    "title": "Channels",
    "content": "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 radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. Channel Security . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | Icon | What it means | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: 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 . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/messages-and-channels.html#channels",
    
    "relUrl": "/iw-rIL/user/messages-and-channels.html#channels"
  },"2647": {
    "doc": "Messages & Channels",
    "title": "Direct Messages",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. Sending a Direct Message . | Open the Messages tab. | Select a conversation, or tap a node in the node list. | Type your message and tap Send. | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. Message States . A status label appears under your own outgoing messages only (incoming messages from others show no status label): . | State | Meaning | . | Sending… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | Delivered to recipient | The strongest confirmation for a direct message — an acknowledgment came back | . | Delivered to mesh | For a channel broadcast, the message reached the mesh (broadcasts have no per-recipient ack) | . | Relayed, not confirmed by recipient | For a direct message, shown in a warning color — the message was relayed but no acknowledgment has come back yet | . | Routing via SF++ chain… | Being routed/buffered by the Store & Forward Plus Plus chain | . | Confirmed on SF++ chain | Confirmed delivered via the SF++ chain | . | שגיאה | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . 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. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Rate limited | The mesh is throttling you for sending too fast | Wait before sending again. | . | Not authorized | The destination refused the request | Check you have the right channel and keys for that node. | . | Recipient needs your key | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | Recipient key unavailable | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | Could not send encrypted message | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Admin session expired | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Admin key not authorized | The target node does not accept your admin key | Verify the admin key matches on both nodes. | . | Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. | . | Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. | . | No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. | . | Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. | . | Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/messages-and-channels.html#direct-messages",
    
    "relUrl": "/iw-rIL/user/messages-and-channels.html#direct-messages"
  },"2648": {
    "doc": "Messages & Channels",
    "title": "Message Features",
    "content": "Quick Chat . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Searching Messages . You can search the full history of any conversation directly from the chat screen: . | Open a conversation (a channel or a direct message). | Tap the search icon in the top bar. | Type into the Search messages… field. The search runs as you type, across all stored messages in that conversation. | Use the N / M result counter and the previous / next arrows to jump between matches, which are highlighted in the conversation. | . 💡 Tip: Search is full-text and stays within the conversation you opened it from — it doesn’t search across other channels or contacts. It matches against the messages already stored on your device, so it works fully offline. 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. Text Formatting . Messages support lightweight inline Markdown. Received messages render the styling with the syntax characters removed: . | Type | Syntax | Renders as | . | Bold | **bold** | bold | . | Italic | *italic* | italic | . | Strikethrough | ~~strike~~ | strike | . | Inline code | `code` | monospace code | . | Link | [label](https://example.com) | a tappable label | . When composing, focus the message field and type at least three characters to reveal a formatting toolbar below the input. Select text and tap a style to wrap it (tap again to remove it); with no selection, a style inserts an empty pair with the cursor between the markers. The link button opens a dialog to enter a URL. As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 Tip: Formatting is carried as literal characters on the mesh — the same bytes iOS sends. Clients that don’t support Markdown (older apps, plain firmware clients) will show the raw **/~~ characters. URLs, email addresses, and phone numbers are still auto-linked whether or not you use Markdown. Mentions . Type @ while composing to mention a node — a picker suggests matching contacts as you type. In a received message, a mention appears as a highlighted chip showing the node’s name; tap it to jump straight to that node’s detail page. Reactions . React to messages with emoji: . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. Message Actions . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | Reply — quote the message in your response | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . Message Priority . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . Message Limits . | Maximum length: 200 bytes (approximately 200 characters for ASCII text) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | Rate limiting: The mesh enforces airtime fairness; heavy message volume may be throttled | Delivery: Messages are retried automatically if no acknowledgment is received | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/messages-and-channels.html#message-features",
    
    "relUrl": "/iw-rIL/user/messages-and-channels.html#message-features"
  },"2649": {
    "doc": "Messages & Channels",
    "title": "Best Practices",
    "content": ". | 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 | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/messages-and-channels.html#best-practices",
    
    "relUrl": "/iw-rIL/user/messages-and-channels.html#best-practices"
  },"2650": {
    "doc": "Messages & Channels",
    "title": "Related Topics",
    "content": ". | Nodes — tap a node to start a direct message | Settings — Radio & User — configure channel encryption and presets | MQTT — bridge channel messages to the internet | Channel configuration — detailed channel settings on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/messages-and-channels.html#related-topics",
    
    "relUrl": "/iw-rIL/user/messages-and-channels.html#related-topics"
  },"2651": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": " ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/messages-and-channels.html",
    
    "relUrl": "/iw-rIL/user/messages-and-channels.html"
  },"2652": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": "Meshtastic supports two communication modes: channel broadcasts and direct messages. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/messages-and-channels.html#messages--channels",
    
    "relUrl": "/pt-rBR/user/messages-and-channels.html#messages--channels"
  },"2653": {
    "doc": "Messages & Channels",
    "title": "Canais",
    "content": "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 radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. Segurança do Canal . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | Icon | What it means | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: 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 . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/messages-and-channels.html#canais",
    
    "relUrl": "/pt-rBR/user/messages-and-channels.html#canais"
  },"2654": {
    "doc": "Messages & Channels",
    "title": "Direct Messages",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. Sending a Direct Message . | Open the Messages tab. | Select a conversation, or tap a node in the node list. | Type your message and tap Send. | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. Message States . A status label appears under your own outgoing messages only (incoming messages from others show no status label): . | State | Meaning | . | Sending… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | Delivered to recipient | The strongest confirmation for a direct message — an acknowledgment came back | . | Delivered to mesh | For a channel broadcast, the message reached the mesh (broadcasts have no per-recipient ack) | . | Relayed, not confirmed by recipient | For a direct message, shown in a warning color — the message was relayed but no acknowledgment has come back yet | . | Routing via SF++ chain… | Being routed/buffered by the Store & Forward Plus Plus chain | . | Confirmed on SF++ chain | Confirmed delivered via the SF++ chain | . | Erro | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Erro | Meaning | What to Do | . | Sem rota | No path exists to the destination node | The recipient may be offline or out of mesh range. Try later or move closer. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Rate limited | The mesh is throttling you for sending too fast | Wait before sending again. | . | Not authorized | The destination refused the request | Check you have the right channel and keys for that node. | . | Recipient needs your key | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | Recipient key unavailable | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | Could not send encrypted message | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Admin session expired | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Admin key not authorized | The target node does not accept your admin key | Verify the admin key matches on both nodes. | . | Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. | . | Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. | . | No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. | . | Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. | . | Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/messages-and-channels.html#direct-messages",
    
    "relUrl": "/pt-rBR/user/messages-and-channels.html#direct-messages"
  },"2655": {
    "doc": "Messages & Channels",
    "title": "Message Features",
    "content": "Quick Chat . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Searching Messages . You can search the full history of any conversation directly from the chat screen: . | Open a conversation (a channel or a direct message). | Tap the search icon in the top bar. | Type into the Search messages… field. The search runs as you type, across all stored messages in that conversation. | Use the N / M result counter and the previous / next arrows to jump between matches, which are highlighted in the conversation. | . 💡 Tip: Search is full-text and stays within the conversation you opened it from — it doesn’t search across other channels or contacts. It matches against the messages already stored on your device, so it works fully offline. 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. Text Formatting . Messages support lightweight inline Markdown. Received messages render the styling with the syntax characters removed: . | Tipo | Syntax | Renders as | . | Bold | **bold** | bold | . | Italic | *italic* | italic | . | Strikethrough | ~~strike~~ | strike | . | Inline code | `code` | monospace code | . | Link | [label](https://example.com) | a tappable label | . When composing, focus the message field and type at least three characters to reveal a formatting toolbar below the input. Select text and tap a style to wrap it (tap again to remove it); with no selection, a style inserts an empty pair with the cursor between the markers. The link button opens a dialog to enter a URL. As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 Tip: Formatting is carried as literal characters on the mesh — the same bytes iOS sends. Clients that don’t support Markdown (older apps, plain firmware clients) will show the raw **/~~ characters. URLs, email addresses, and phone numbers are still auto-linked whether or not you use Markdown. Mentions . Type @ while composing to mention a node — a picker suggests matching contacts as you type. In a received message, a mention appears as a highlighted chip showing the node’s name; tap it to jump straight to that node’s detail page. Reactions . React to messages with emoji: . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. Message Actions . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | Reply — quote the message in your response | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . Message Priority . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . Message Limits . | Maximum length: 200 bytes (approximately 200 characters for ASCII text) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | Rate limiting: The mesh enforces airtime fairness; heavy message volume may be throttled | Delivery: Messages are retried automatically if no acknowledgment is received | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/messages-and-channels.html#message-features",
    
    "relUrl": "/pt-rBR/user/messages-and-channels.html#message-features"
  },"2656": {
    "doc": "Messages & Channels",
    "title": "Best Practices",
    "content": ". | 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 | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/messages-and-channels.html#best-practices",
    
    "relUrl": "/pt-rBR/user/messages-and-channels.html#best-practices"
  },"2657": {
    "doc": "Messages & Channels",
    "title": "Related Topics",
    "content": ". | Nodes — tap a node to start a direct message | Settings — Radio & User — configure channel encryption and presets | MQTT — bridge channel messages to the internet | Channel configuration — detailed channel settings on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/messages-and-channels.html#related-topics",
    
    "relUrl": "/pt-rBR/user/messages-and-channels.html#related-topics"
  },"2658": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": " ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/messages-and-channels.html",
    
    "relUrl": "/pt-rBR/user/messages-and-channels.html"
  },"2659": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": "Meshtastic supports two communication modes: channel broadcasts and direct messages. ",
    "url": "/Meshtastic-Android/main/en/user/messages-and-channels.html#messages--channels",
    
    "relUrl": "/en/user/messages-and-channels.html#messages--channels"
  },"2660": {
    "doc": "Messages & Channels",
    "title": "Channels",
    "content": "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 radio comes with a default LongFast channel. It is encrypted with a well-known default key, so anyone running Meshtastic on the same preset can read it. Channel Security . Each channel carries a lock icon that shows how well it is protected. Tap the icon to see the same explanation inside the app. | Icon | What it means | . | Green closed lock | The channel is securely encrypted, with either a 128-bit or a 256-bit AES key. | . | Yellow open lock | The channel is not securely encrypted — it uses no key at all, or a well-known one-byte key — and it does not carry precise location. | . | Red open lock | Not securely encrypted, and the channel carries precise location data. | . | Red open lock with a warning badge | Not securely encrypted, carrying precise location data, and uplinking that data to the internet over MQTT. | . Key length alone does not change the icon: a 128-bit key and a 256-bit key both show the green lock. 🔒 Security: 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 . | Connect to your radio. The Channels row stays grayed out until the app has a connection — see Connections. | Go to Settings, then tap Channels under Configuration. | Tap the + button to add a channel. The editor opens on the new entry. | Set the channel name and the PSK, and choose whether the channel uses MQTT uplink and downlink. Naming a new channel generates a fresh 256-bit key for you; the refresh icon beside PSK generates another one. | Tap Save to close the editor. The change is still only on your phone. | Tap Send at the bottom of the channel list to write the changes to the radio. Cancel, or leaving the screen without tapping Send, throws them away. | Optional: share the channel URL or QR code with the people who need access. | . Tapping an existing channel opens the same editor, where you can change the name, the PSK, MQTT uplink and downlink, and position precision. Every edit on this screen — adding, editing, deleting, or dragging a channel into a new order — waits on Send the same way. Archived Channels . A conversation belongs to the channel it was held on, not to the slot that channel occupied. When a channel leaves your radio — you scan a different channel QR, replace a channel’s key, or switch the modem preset — its conversation is archived rather than deleted or merged into whatever takes the slot. An archived conversation: . | stays in the Channels list under the name the channel had, below the channels currently on your radio, marked with a history icon; | keeps its full message history, searchable as usual; | is read-only — you cannot send, reply, or react, because the channel is no longer on the radio to send on, and it is not offered as a share target; | comes back automatically if you re-add that exact channel, taking its messages back to the live slot. | . Changing the modem preset archives the channel too: the preset is part of a default channel’s identity, so LongFast and MediumFast are different channels even though neither the name nor the key changed. Changing only the region does not archive anything. To remove an archived conversation for good, long-press it in the conversation list and delete it. ",
    "url": "/Meshtastic-Android/main/en/user/messages-and-channels.html#channels",
    
    "relUrl": "/en/user/messages-and-channels.html#channels"
  },"2661": {
    "doc": "Messages & Channels",
    "title": "Direct Messages",
    "content": "Direct messages (DMs) go to one specific node. When both radios hold each other’s public keys, your radio encrypts the message to that node’s public key, so no one else on the mesh can read it — not even nodes that share your channel. Your radio must already hold the other node’s public key before it can send a DM. Keys travel inside node info, which nodes broadcast periodically, so the key usually arrives on its own once you have heard from that node. Until it does, a radio that has its own key pair — the default — refuses the send rather than falling back to channel encryption, and the message shows Recipient key unavailable. A public-key conversation carries a key icon in its top bar. A green closed lock means the direct message is protected by public-key encryption; a red key-off icon means the node’s public key changed and no longer matches the one your radio stored. Tap the icon for the details. Sending a Direct Message . | Open the Messages tab. | Select a conversation, or tap a node in the node list. | Type your message and tap Send. | . Managing the Conversation List . The Messages tab lists your conversations. Each row shows what you need at a glance, and you can act on it directly: . | Unsent drafts survive. Type into a conversation and leave without sending, and the text is still there when you come back. The row shows it as Draft: … in place of the last message — an unsent draft is the thing the row is waiting on you for. | Unread badge. A count sits on the row until you open the conversation. | Swipe right to mute (swipe again to unmute) and swipe left to delete. Deleting asks first; muting shows a snackbar with Undo. | Touch & hold to select one or more conversations, then use the action bar to Pin, Mark unread, mute or delete them together. Pinned conversations carry a pin marker and rise to the top of their own section. | The list is split into Channels and Direct Messages, each with a collapsible header and each sorted independently — so a pinned direct message rises within its own section, not above the Channels one. | . Conversation Bubbles . On Android 11 and later, a message notification can be opened as a floating bubble that stays on top of whatever else you are doing. Tap the bubble icon on the notification to promote a conversation; Android remembers the choice per conversation, and the system Bubbles settings control whether they are offered at all. Message States . A status label appears under your own outgoing messages only (incoming messages from others show no status label): . | State | Meaning | . | Sending… | Queued or already handed to the radio, not yet resolved either way. Both stages share this text, but the icon and color change as it progresses — a yellow upload cloud while queued, a blue arrow once the radio has it | . | Delivered to recipient | The strongest confirmation for a direct message — an acknowledgment came back | . | Delivered to mesh | For a channel broadcast, the message reached the mesh (broadcasts have no per-recipient ack) | . | Relayed, not confirmed by recipient | For a direct message, shown in a warning color — the message was relayed but no acknowledgment has come back yet | . | Routing via SF++ chain… | Being routed/buffered by the Store & Forward Plus Plus chain | . | Confirmed on SF++ chain | Confirmed delivered via the SF++ chain | . | Error | Delivery failed — tap the status for the specific reason (see Delivery Errors) | . Delivery Errors . When a message fails to deliver, the error indicator shows what went wrong: . | Error | 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. | . | No radio interface | No radio interface available to send | Check that your radio is connected and available. | . | Failed to deliver to mesh | Retries exhausted. The same label covers three underlying causes — a relay refusing (NAK), a plain timeout, and running out of retransmits | Move closer, improve signal, or wait for conditions to improve. Tap the error for the specific cause. | . | Rate limited | The mesh is throttling you for sending too fast | Wait before sending again. | . | Not authorized | The destination refused the request | Check you have the right channel and keys for that node. | . | Recipient needs your key | Direct-message encryption could not complete because the other node does not have your public key yet | Exchange node info — the key travels with it. Common on a first DM to a new contact. | . | Recipient key unavailable | You do not have the recipient’s public key | Wait for their node info to arrive, or ask them to broadcast it. | . | Could not send encrypted message | Encryption failed for this direct message | Verify both nodes have exchanged keys and are on compatible firmware. | . | Admin session expired | A remote-admin session timed out | Reopen the remote node’s settings to start a new session. | . | Admin key not authorized | The target node does not accept your admin key | Verify the admin key matches on both nodes. | . | Channel/key mismatch | Destination channel/key does not match | Verify both nodes share the same channel and PSK. | . | Message is too large to send | Message exceeds maximum payload size | Shorten the message and try again. | . | No app response | App or plugin did not respond to the request | Retry or check the destination app or module state. | . | Duty cycle limit | Regional airtime limit reached | Wait for the duty cycle window to reset. | . | Invalid request | Malformed or invalid request | Retry after updating or restarting the app if this persists. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/en/user/messages-and-channels.html#direct-messages",
    
    "relUrl": "/en/user/messages-and-channels.html#direct-messages"
  },"2662": {
    "doc": "Messages & Channels",
    "title": "Message Features",
    "content": "Quick Chat . Pre-configured messages for rapid communication, useful when typing is impractical (gloves, small screen, urgent): . | The quick chat row is hidden until you turn it on. Open a conversation, tap the overflow menu in the top bar, then tap Show quick chat menu. Hide quick chat menu puts the row away again. | The row carries one built-in entry, the 🔔 alert bell. It appends an alert message that includes a bell character, which clients that support it flag as an alert. Every other button on the row is one you created. | Add, edit, reorder, and delete your own entries from the same overflow menu — tap Quick chat options. | . Each quick chat entry has a Name — the button label, capped at five characters, forced to uppercase, and filled in for you from the message text — and the Message it carries. A switch decides what tapping the button does. A new entry starts on Instantly send, so a tap sends the message straight away; turn the switch off and the label changes to Append to message, which puts the text in the input field for you to edit first. Searching Messages . You can search the full history of any conversation directly from the chat screen: . | Open a conversation (a channel or a direct message). | Tap the search icon in the top bar. | Type into the Search messages… field. The search runs as you type, across all stored messages in that conversation. | Use the N / M result counter and the previous / next arrows to jump between matches, which are highlighted in the conversation. | . 💡 Tip: Search is full-text and stays within the conversation you opened it from — it doesn’t search across other channels or contacts. It matches against the messages already stored on your device, so it works fully offline. 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. Text Formatting . Messages support lightweight inline Markdown. Received messages render the styling with the syntax characters removed: . | Type | Syntax | Renders as | . | Bold | **bold** | bold | . | Italic | *italic* | italic | . | Strikethrough | ~~strike~~ | strike | . | Inline code | `code` | monospace code | . | Link | [label](https://example.com) | a tappable label | . When composing, focus the message field and type at least three characters to reveal a formatting toolbar below the input. Select text and tap a style to wrap it (tap again to remove it); with no selection, a style inserts an empty pair with the cursor between the markers. The link button opens a dialog to enter a URL. As you type, the field shows the styled text, but the message you send still contains the Markdown characters. 💡 Tip: Formatting is carried as literal characters on the mesh — the same bytes iOS sends. Clients that don’t support Markdown (older apps, plain firmware clients) will show the raw **/~~ characters. URLs, email addresses, and phone numbers are still auto-linked whether or not you use Markdown. Mentions . Type @ while composing to mention a node — a picker suggests matching contacts as you type. In a received message, a mention appears as a highlighted chip showing the node’s name; tap it to jump straight to that node’s detail page. Reactions . React to messages with emoji: . | Touch & hold a message — or double-tap it — to raise a quick reaction bar above the bubble. Opening the bar sends nothing. | Tap an emoji in the bar to send it; tap More reactions to open the full picker, or anywhere outside the bar to dismiss it without sending. A reaction is a real mesh packet, so it only goes out when you pick an emoji. | Reactions appear below the message bubble | Multiple users can react to the same message | React to your own messages or others’ messages | . 💡 Tip: Reactions are lightweight — they use minimal mesh bandwidth compared to full text messages. Replying . Swipe a message to the right to reply to it — the composer opens with that message quoted. Swiping past the reply threshold arms the action; releasing before it springs back with nothing sent. Reply is also in the actions sheet, reached by touching & holding and then tapping More message actions. Day Separators . Messages are grouped by day. The separator above the first message of each day reads Today or Yesterday for the two most recent days, and the date itself for older ones. Jump to Latest . Scrolling back through a conversation raises a jump-to-latest control. When messages arrive while you are scrolled up, it names the most recent sender and adds a count of the other unread messages. That count is messages, not people — five unread from one person reads as their name +4. Message Actions . Touch & hold or double-tap a message to open the quick reaction bar, then tap More message actions (the overflow icon on that bar) to open the actions sheet. The emoji row runs across the top of the sheet — that is where reactions live — and beneath it, along with the message’s timestamp and delivery status, are: . | Reply — quote the message in your response | Copy — copy the message text to the clipboard | Translate — translate a received message into your device language, and toggle between the original and translated text (Google Play build only; uses on-device translation). The first translation into a language asks to download a one-time language model and tells you its size, then translates once the download finishes. If the download fails, or the message is already in your language, the app says so instead of translating | Select — start multi-select, so you can act on several messages at once | Delete — remove the message from this phone. It works on any message in the conversation, yours or not, and does not remove it from anyone else’s radio or phone | . Message Priority . The app sends every message you compose at the same, default priority — there is no emergency or alert tier to choose, and nothing in the app raises a direct message above a channel broadcast. Any prioritising between them happens in firmware, not here. (The app does mark some of its own internal traffic, such as admin and traceroute packets, as reliable or background, but that is not something you control from the message composer.) . Message Limits . | Maximum length: 200 bytes (approximately 200 characters for ASCII text) | The 200-byte cap applies to the in-app composer — the mesh payload limit itself is 233 bytes, so messages from other senders (e.g., App Functions) may arrive slightly longer | Rate limiting: The mesh enforces airtime fairness; heavy message volume may be throttled | Delivery: Messages are retried automatically if no acknowledgment is received | . ",
    "url": "/Meshtastic-Android/main/en/user/messages-and-channels.html#message-features",
    
    "relUrl": "/en/user/messages-and-channels.html#message-features"
  },"2663": {
    "doc": "Messages & Channels",
    "title": "Best Practices",
    "content": ". | 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 | . ",
    "url": "/Meshtastic-Android/main/en/user/messages-and-channels.html#best-practices",
    
    "relUrl": "/en/user/messages-and-channels.html#best-practices"
  },"2664": {
    "doc": "Messages & Channels",
    "title": "Related Topics",
    "content": ". | Nodes — tap a node to start a direct message | Settings — Radio & User — configure channel encryption and presets | MQTT — bridge channel messages to the internet | Channel configuration — detailed channel settings on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/en/user/messages-and-channels.html#related-topics",
    
    "relUrl": "/en/user/messages-and-channels.html#related-topics"
  },"2665": {
    "doc": "Messages & Channels",
    "title": "Messages & Channels",
    "content": " ",
    "url": "/Meshtastic-Android/main/en/user/messages-and-channels.html",
    
    "relUrl": "/en/user/messages-and-channels.html"
  },"2666": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/mqtt.html",
    
    "relUrl": "/sk-rSK/user/mqtt.html"
  },"2667": {
    "doc": "MQTT",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/mqtt.html#overview",
    
    "relUrl": "/sk-rSK/user/mqtt.html#overview"
  },"2668": {
    "doc": "MQTT",
    "title": "How It Works",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/mqtt.html#how-it-works",
    
    "relUrl": "/sk-rSK/user/mqtt.html#how-it-works"
  },"2669": {
    "doc": "MQTT",
    "title": "Configuration",
    "content": "Enabling MQTT . | Navigate to Settings → Module configuration → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Popis | Predvolené | . | Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root topic | Base topic for messages | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | Encrypt MQTT payload | Enabled | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | Disabled | . | TLS enabled | Secure connection to broker | Disabled | . | Map reporting | Report position to public map | Disabled | . | Proxy to client enabled | Relay MQTT through the connected phone | Disabled | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. MQTT Proxy on This Phone . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 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. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/mqtt.html#configuration",
    
    "relUrl": "/sk-rSK/user/mqtt.html#configuration"
  },"2670": {
    "doc": "MQTT",
    "title": "Map Reporting",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/mqtt.html#map-reporting",
    
    "relUrl": "/sk-rSK/user/mqtt.html#map-reporting"
  },"2671": {
    "doc": "MQTT",
    "title": "Uplink vs Downlink",
    "content": "| Direction | Popis | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/mqtt.html#uplink-vs-downlink",
    
    "relUrl": "/sk-rSK/user/mqtt.html#uplink-vs-downlink"
  },"2672": {
    "doc": "MQTT",
    "title": "Message Formats",
    "content": "MQTT carries two payload formats: . | Format | Popis | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/mqtt.html#message-formats",
    
    "relUrl": "/sk-rSK/user/mqtt.html#message-formats"
  },"2673": {
    "doc": "MQTT",
    "title": "Encryption & Privacy",
    "content": "Understanding the layered encryption model: . | 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. | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Security: 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. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/mqtt.html#encryption--privacy",
    
    "relUrl": "/sk-rSK/user/mqtt.html#encryption--privacy"
  },"2674": {
    "doc": "MQTT",
    "title": "Best Practices",
    "content": ". | Use channel-level encryption (PSK) on channels that bridge to MQTT | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes 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 | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/mqtt.html#best-practices",
    
    "relUrl": "/sk-rSK/user/mqtt.html#best-practices"
  },"2675": {
    "doc": "MQTT",
    "title": "Troubleshooting",
    "content": "MQTT Not Connecting . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | 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 — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/mqtt.html#troubleshooting",
    
    "relUrl": "/sk-rSK/user/mqtt.html#troubleshooting"
  },"2676": {
    "doc": "MQTT",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — MQTT module configuration reference | Messages & Channels — channel encryption and PSK setup | MQTT integration guide — detailed MQTT documentation on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/mqtt.html#related-topics",
    
    "relUrl": "/sk-rSK/user/mqtt.html#related-topics"
  },"2677": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/mqtt.html",
    
    "relUrl": "/be-rBY/user/mqtt.html"
  },"2678": {
    "doc": "MQTT",
    "title": "Абзор",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/mqtt.html#%D0%B0%D0%B1%D0%B7%D0%BE%D1%80",
    
    "relUrl": "/be-rBY/user/mqtt.html#абзор"
  },"2679": {
    "doc": "MQTT",
    "title": "How It Works",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/mqtt.html#how-it-works",
    
    "relUrl": "/be-rBY/user/mqtt.html#how-it-works"
  },"2680": {
    "doc": "MQTT",
    "title": "Конфигурация",
    "content": "Enabling MQTT . | Navigate to Settings → Module configuration → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Апісанне | Default | . | Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root topic | Base topic for messages | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | Encrypt MQTT payload | Уключана | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | Disabled | . | TLS enabled | Secure connection to broker | Disabled | . | Map reporting | Report position to public map | Disabled | . | Proxy to client enabled | Relay MQTT through the connected phone | Disabled | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. MQTT Proxy on This Phone . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 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. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/mqtt.html#%D0%BA%D0%BE%D0%BD%D1%84%D0%B8%D0%B3%D1%83%D1%80%D0%B0%D1%86%D0%B8%D1%8F",
    
    "relUrl": "/be-rBY/user/mqtt.html#конфигурация"
  },"2681": {
    "doc": "MQTT",
    "title": "Map Reporting",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/mqtt.html#map-reporting",
    
    "relUrl": "/be-rBY/user/mqtt.html#map-reporting"
  },"2682": {
    "doc": "MQTT",
    "title": "Uplink vs Downlink",
    "content": "| Direction | Апісанне | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/mqtt.html#uplink-vs-downlink",
    
    "relUrl": "/be-rBY/user/mqtt.html#uplink-vs-downlink"
  },"2683": {
    "doc": "MQTT",
    "title": "Message Formats",
    "content": "MQTT carries two payload formats: . | Format | Апісанне | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/mqtt.html#message-formats",
    
    "relUrl": "/be-rBY/user/mqtt.html#message-formats"
  },"2684": {
    "doc": "MQTT",
    "title": "Encryption & Privacy",
    "content": "Understanding the layered encryption model: . | 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. | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Security: 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. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/mqtt.html#encryption--privacy",
    
    "relUrl": "/be-rBY/user/mqtt.html#encryption--privacy"
  },"2685": {
    "doc": "MQTT",
    "title": "Best Practices",
    "content": ". | Use channel-level encryption (PSK) on channels that bridge to MQTT | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes 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 | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/mqtt.html#best-practices",
    
    "relUrl": "/be-rBY/user/mqtt.html#best-practices"
  },"2686": {
    "doc": "MQTT",
    "title": "Troubleshooting",
    "content": "MQTT Not Connecting . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | 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 — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/mqtt.html#troubleshooting",
    
    "relUrl": "/be-rBY/user/mqtt.html#troubleshooting"
  },"2687": {
    "doc": "MQTT",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — MQTT module configuration reference | Messages & Channels — channel encryption and PSK setup | MQTT integration guide — detailed MQTT documentation on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/mqtt.html#related-topics",
    
    "relUrl": "/be-rBY/user/mqtt.html#related-topics"
  },"2688": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/mqtt.html",
    
    "relUrl": "/it-rIT/user/mqtt.html"
  },"2689": {
    "doc": "MQTT",
    "title": "Panoramica",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/mqtt.html#panoramica",
    
    "relUrl": "/it-rIT/user/mqtt.html#panoramica"
  },"2690": {
    "doc": "MQTT",
    "title": "Come funziona",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/mqtt.html#come-funziona",
    
    "relUrl": "/it-rIT/user/mqtt.html#come-funziona"
  },"2691": {
    "doc": "MQTT",
    "title": "Configurazione",
    "content": "Enabling MQTT . | Navigate to Settings → Module configuration → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Impostazione | Descrizione | Predefinito | . | Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root topic | Base topic for messages | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | Encrypt MQTT payload | Abilitato | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | Disabled | . | TLS enabled | Secure connection to broker | Disabled | . | Map reporting | Report position to public map | Disabled | . | Proxy to client enabled | Relay MQTT through the connected phone | Disabled | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. MQTT Proxy on This Phone . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 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. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/mqtt.html#configurazione",
    
    "relUrl": "/it-rIT/user/mqtt.html#configurazione"
  },"2692": {
    "doc": "MQTT",
    "title": "Map Reporting",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/mqtt.html#map-reporting",
    
    "relUrl": "/it-rIT/user/mqtt.html#map-reporting"
  },"2693": {
    "doc": "MQTT",
    "title": "Uplink vs Downlink",
    "content": "| Direction | Descrizione | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/mqtt.html#uplink-vs-downlink",
    
    "relUrl": "/it-rIT/user/mqtt.html#uplink-vs-downlink"
  },"2694": {
    "doc": "MQTT",
    "title": "Message Formats",
    "content": "MQTT carries two payload formats: . | Format | Descrizione | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/mqtt.html#message-formats",
    
    "relUrl": "/it-rIT/user/mqtt.html#message-formats"
  },"2695": {
    "doc": "MQTT",
    "title": "Encryption & Privacy",
    "content": "Understanding the layered encryption model: . | 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. | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Security: 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. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/mqtt.html#encryption--privacy",
    
    "relUrl": "/it-rIT/user/mqtt.html#encryption--privacy"
  },"2696": {
    "doc": "MQTT",
    "title": "Buone pratiche",
    "content": ". | Use channel-level encryption (PSK) on channels that bridge to MQTT | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes 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 | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/mqtt.html#buone-pratiche",
    
    "relUrl": "/it-rIT/user/mqtt.html#buone-pratiche"
  },"2697": {
    "doc": "MQTT",
    "title": "Risoluzione problemi",
    "content": "MQTT Not Connecting . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | 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 — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/mqtt.html#risoluzione-problemi",
    
    "relUrl": "/it-rIT/user/mqtt.html#risoluzione-problemi"
  },"2698": {
    "doc": "MQTT",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — MQTT module configuration reference | Messages & Channels — channel encryption and PSK setup | MQTT integration guide — detailed MQTT documentation on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/mqtt.html#related-topics",
    
    "relUrl": "/it-rIT/user/mqtt.html#related-topics"
  },"2699": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range. ",
    "url": "/Meshtastic-Android/main/es-rES/user/mqtt.html",
    
    "relUrl": "/es-rES/user/mqtt.html"
  },"2700": {
    "doc": "MQTT",
    "title": "Visión general",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/mqtt.html#visi%C3%B3n-general",
    
    "relUrl": "/es-rES/user/mqtt.html#visión-general"
  },"2701": {
    "doc": "MQTT",
    "title": "How It Works",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ",
    "url": "/Meshtastic-Android/main/es-rES/user/mqtt.html#how-it-works",
    
    "relUrl": "/es-rES/user/mqtt.html#how-it-works"
  },"2702": {
    "doc": "MQTT",
    "title": "Configuración",
    "content": "Enabling MQTT . | Navigate to Settings → Module configuration → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Descripción | Por defecto | . | Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root topic | Base topic for messages | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | Encrypt MQTT payload | Habilitado | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | Disabled | . | TLS enabled | Secure connection to broker | Disabled | . | Map reporting | Report position to public map | Disabled | . | Proxy to client enabled | Relay MQTT through the connected phone | Disabled | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. MQTT Proxy on This Phone . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 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. ",
    "url": "/Meshtastic-Android/main/es-rES/user/mqtt.html#configuraci%C3%B3n",
    
    "relUrl": "/es-rES/user/mqtt.html#configuración"
  },"2703": {
    "doc": "MQTT",
    "title": "Map Reporting",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/es-rES/user/mqtt.html#map-reporting",
    
    "relUrl": "/es-rES/user/mqtt.html#map-reporting"
  },"2704": {
    "doc": "MQTT",
    "title": "Uplink vs Downlink",
    "content": "| Direction | Descripción | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/es-rES/user/mqtt.html#uplink-vs-downlink",
    
    "relUrl": "/es-rES/user/mqtt.html#uplink-vs-downlink"
  },"2705": {
    "doc": "MQTT",
    "title": "Message Formats",
    "content": "MQTT carries two payload formats: . | Format | Descripción | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/es-rES/user/mqtt.html#message-formats",
    
    "relUrl": "/es-rES/user/mqtt.html#message-formats"
  },"2706": {
    "doc": "MQTT",
    "title": "Encryption & Privacy",
    "content": "Understanding the layered encryption model: . | 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. | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Security: 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. ",
    "url": "/Meshtastic-Android/main/es-rES/user/mqtt.html#encryption--privacy",
    
    "relUrl": "/es-rES/user/mqtt.html#encryption--privacy"
  },"2707": {
    "doc": "MQTT",
    "title": "Best Practices",
    "content": ". | Use channel-level encryption (PSK) on channels that bridge to MQTT | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes 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 | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/mqtt.html#best-practices",
    
    "relUrl": "/es-rES/user/mqtt.html#best-practices"
  },"2708": {
    "doc": "MQTT",
    "title": "Troubleshooting",
    "content": "MQTT Not Connecting . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | 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 — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/mqtt.html#troubleshooting",
    
    "relUrl": "/es-rES/user/mqtt.html#troubleshooting"
  },"2709": {
    "doc": "MQTT",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — MQTT module configuration reference | Messages & Channels — channel encryption and PSK setup | MQTT integration guide — detailed MQTT documentation on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/mqtt.html#related-topics",
    
    "relUrl": "/es-rES/user/mqtt.html#related-topics"
  },"2710": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/mqtt.html",
    
    "relUrl": "/sl-rSI/user/mqtt.html"
  },"2711": {
    "doc": "MQTT",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/mqtt.html#overview",
    
    "relUrl": "/sl-rSI/user/mqtt.html#overview"
  },"2712": {
    "doc": "MQTT",
    "title": "How It Works",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/mqtt.html#how-it-works",
    
    "relUrl": "/sl-rSI/user/mqtt.html#how-it-works"
  },"2713": {
    "doc": "MQTT",
    "title": "Configuration",
    "content": "Enabling MQTT . | Navigate to Settings → Module configuration → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Opis | Default | . | Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root topic | Base topic for messages | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | Encrypt MQTT payload | Enabled | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | Disabled | . | TLS enabled | Secure connection to broker | Disabled | . | Map reporting | Report position to public map | Disabled | . | Proxy to client enabled | Relay MQTT through the connected phone | Disabled | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. MQTT Proxy on This Phone . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 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. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/mqtt.html#configuration",
    
    "relUrl": "/sl-rSI/user/mqtt.html#configuration"
  },"2714": {
    "doc": "MQTT",
    "title": "Map Reporting",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/mqtt.html#map-reporting",
    
    "relUrl": "/sl-rSI/user/mqtt.html#map-reporting"
  },"2715": {
    "doc": "MQTT",
    "title": "Uplink vs Downlink",
    "content": "| Direction | Opis | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/mqtt.html#uplink-vs-downlink",
    
    "relUrl": "/sl-rSI/user/mqtt.html#uplink-vs-downlink"
  },"2716": {
    "doc": "MQTT",
    "title": "Message Formats",
    "content": "MQTT carries two payload formats: . | Format | Opis | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/mqtt.html#message-formats",
    
    "relUrl": "/sl-rSI/user/mqtt.html#message-formats"
  },"2717": {
    "doc": "MQTT",
    "title": "Encryption & Privacy",
    "content": "Understanding the layered encryption model: . | 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. | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Security: 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. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/mqtt.html#encryption--privacy",
    
    "relUrl": "/sl-rSI/user/mqtt.html#encryption--privacy"
  },"2718": {
    "doc": "MQTT",
    "title": "Best Practices",
    "content": ". | Use channel-level encryption (PSK) on channels that bridge to MQTT | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes 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 | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/mqtt.html#best-practices",
    
    "relUrl": "/sl-rSI/user/mqtt.html#best-practices"
  },"2719": {
    "doc": "MQTT",
    "title": "Troubleshooting",
    "content": "MQTT Not Connecting . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | 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 — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/mqtt.html#troubleshooting",
    
    "relUrl": "/sl-rSI/user/mqtt.html#troubleshooting"
  },"2720": {
    "doc": "MQTT",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — MQTT module configuration reference | Messages & Channels — channel encryption and PSK setup | MQTT integration guide — detailed MQTT documentation on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/mqtt.html#related-topics",
    
    "relUrl": "/sl-rSI/user/mqtt.html#related-topics"
  },"2721": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/mqtt.html",
    
    "relUrl": "/no-rNO/user/mqtt.html"
  },"2722": {
    "doc": "MQTT",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/mqtt.html#overview",
    
    "relUrl": "/no-rNO/user/mqtt.html#overview"
  },"2723": {
    "doc": "MQTT",
    "title": "How It Works",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/mqtt.html#how-it-works",
    
    "relUrl": "/no-rNO/user/mqtt.html#how-it-works"
  },"2724": {
    "doc": "MQTT",
    "title": "Configuration",
    "content": "Enabling MQTT . | Navigate to Settings → Module configuration → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Beskrivelse | Default | . | Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root topic | Base topic for messages | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | Encrypt MQTT payload | Enabled | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | Disabled | . | TLS enabled | Secure connection to broker | Disabled | . | Map reporting | Report position to public map | Disabled | . | Proxy to client enabled | Relay MQTT through the connected phone | Disabled | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. MQTT Proxy on This Phone . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 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. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/mqtt.html#configuration",
    
    "relUrl": "/no-rNO/user/mqtt.html#configuration"
  },"2725": {
    "doc": "MQTT",
    "title": "Map Reporting",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/mqtt.html#map-reporting",
    
    "relUrl": "/no-rNO/user/mqtt.html#map-reporting"
  },"2726": {
    "doc": "MQTT",
    "title": "Uplink vs Downlink",
    "content": "| Direction | Beskrivelse | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/mqtt.html#uplink-vs-downlink",
    
    "relUrl": "/no-rNO/user/mqtt.html#uplink-vs-downlink"
  },"2727": {
    "doc": "MQTT",
    "title": "Message Formats",
    "content": "MQTT carries two payload formats: . | Format | Beskrivelse | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/mqtt.html#message-formats",
    
    "relUrl": "/no-rNO/user/mqtt.html#message-formats"
  },"2728": {
    "doc": "MQTT",
    "title": "Encryption & Privacy",
    "content": "Understanding the layered encryption model: . | 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. | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Security: 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. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/mqtt.html#encryption--privacy",
    
    "relUrl": "/no-rNO/user/mqtt.html#encryption--privacy"
  },"2729": {
    "doc": "MQTT",
    "title": "Best Practices",
    "content": ". | Use channel-level encryption (PSK) on channels that bridge to MQTT | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes 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 | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/mqtt.html#best-practices",
    
    "relUrl": "/no-rNO/user/mqtt.html#best-practices"
  },"2730": {
    "doc": "MQTT",
    "title": "Troubleshooting",
    "content": "MQTT Not Connecting . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | 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 — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/mqtt.html#troubleshooting",
    
    "relUrl": "/no-rNO/user/mqtt.html#troubleshooting"
  },"2731": {
    "doc": "MQTT",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — MQTT module configuration reference | Messages & Channels — channel encryption and PSK setup | MQTT integration guide — detailed MQTT documentation on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/mqtt.html#related-topics",
    
    "relUrl": "/no-rNO/user/mqtt.html#related-topics"
  },"2732": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/mqtt.html",
    
    "relUrl": "/hu-rHU/user/mqtt.html"
  },"2733": {
    "doc": "MQTT",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/mqtt.html#overview",
    
    "relUrl": "/hu-rHU/user/mqtt.html#overview"
  },"2734": {
    "doc": "MQTT",
    "title": "How It Works",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/mqtt.html#how-it-works",
    
    "relUrl": "/hu-rHU/user/mqtt.html#how-it-works"
  },"2735": {
    "doc": "MQTT",
    "title": "Configuration",
    "content": "Enabling MQTT . | Navigate to Settings → Module configuration → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Leírás | Alapértelmezett | . | Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root topic | Base topic for messages | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | Encrypt MQTT payload | Engedélyezve | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | Disabled | . | TLS enabled | Secure connection to broker | Disabled | . | Map reporting | Report position to public map | Disabled | . | Proxy to client enabled | Relay MQTT through the connected phone | Disabled | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. MQTT Proxy on This Phone . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 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. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/mqtt.html#configuration",
    
    "relUrl": "/hu-rHU/user/mqtt.html#configuration"
  },"2736": {
    "doc": "MQTT",
    "title": "Map Reporting",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/mqtt.html#map-reporting",
    
    "relUrl": "/hu-rHU/user/mqtt.html#map-reporting"
  },"2737": {
    "doc": "MQTT",
    "title": "Uplink vs Downlink",
    "content": "| Direction | Leírás | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/mqtt.html#uplink-vs-downlink",
    
    "relUrl": "/hu-rHU/user/mqtt.html#uplink-vs-downlink"
  },"2738": {
    "doc": "MQTT",
    "title": "Message Formats",
    "content": "MQTT carries two payload formats: . | Format | Leírás | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/mqtt.html#message-formats",
    
    "relUrl": "/hu-rHU/user/mqtt.html#message-formats"
  },"2739": {
    "doc": "MQTT",
    "title": "Encryption & Privacy",
    "content": "Understanding the layered encryption model: . | 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. | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Security: 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. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/mqtt.html#encryption--privacy",
    
    "relUrl": "/hu-rHU/user/mqtt.html#encryption--privacy"
  },"2740": {
    "doc": "MQTT",
    "title": "Best Practices",
    "content": ". | Use channel-level encryption (PSK) on channels that bridge to MQTT | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes 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 | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/mqtt.html#best-practices",
    
    "relUrl": "/hu-rHU/user/mqtt.html#best-practices"
  },"2741": {
    "doc": "MQTT",
    "title": "Troubleshooting",
    "content": "MQTT Not Connecting . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | 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 — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/mqtt.html#troubleshooting",
    
    "relUrl": "/hu-rHU/user/mqtt.html#troubleshooting"
  },"2742": {
    "doc": "MQTT",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — MQTT module configuration reference | Messages & Channels — channel encryption and PSK setup | MQTT integration guide — detailed MQTT documentation on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/mqtt.html#related-topics",
    
    "relUrl": "/hu-rHU/user/mqtt.html#related-topics"
  },"2743": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT соединяет твою mesh-сеть Meshtastic с интернетом, обеспечивая связь на больших расстояниях за пределами радиодиапазона. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/mqtt.html",
    
    "relUrl": "/ru-rRU/user/mqtt.html"
  },"2744": {
    "doc": "MQTT",
    "title": "Обзор",
    "content": "Модуль MQTT подключает вашу ноду к MQTT-брокеру, что позволяет: . | Сообщениям достигать нод в других физических mesh-сетях через интернет | Интегрироваться с системами домашней автоматизации и мониторинга | Публиковать местоположения нод на публичной карте Meshtastic | Создавать собственные каналы данных для журналирования и оповещений | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/mqtt.html#%D0%BE%D0%B1%D0%B7%D0%BE%D1%80",
    
    "relUrl": "/ru-rRU/user/mqtt.html#обзор"
  },"2745": {
    "doc": "MQTT",
    "title": "Как это работает",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Удалённые шлюзы, подписанные на тот же топик, передают эти сообщения в свою локальную mesh-сеть. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/mqtt.html#%D0%BA%D0%B0%D0%BA-%D1%8D%D1%82%D0%BE-%D1%80%D0%B0%D0%B1%D0%BE%D1%82%D0%B0%D0%B5%D1%82",
    
    "relUrl": "/ru-rRU/user/mqtt.html#как-это-работает"
  },"2746": {
    "doc": "MQTT",
    "title": "Настройки",
    "content": "Включение MQTT . | Navigate to Settings → Module configuration → MQTT. | Включите модуль MQTT. | Настройте подключение к брокеру: | . | Настройка | Описание | По умолчанию | . | Address | Имя хоста MQTT-брокера | mqtt.meshtastic.org | . | Username | Аутентификация брокера | meshdev | . | Password | Аутентификация брокера | large4cats | . | Root topic | Базовый топик для сообщений | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | Шифровать полезную нагрузку MQTT | Включено | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | Отключено | . | TLS enabled | Безопасное подключение к брокеру | Отключено | . | Map reporting | Сообщать о местоположении на публичную карту | Отключено | . | Proxy to client enabled | Relay MQTT through the connected phone | Включено | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. MQTT-прокси на этом телефоне . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. Стандартный брокер Meshtastic . Сообщество поддерживает публичный брокер по адресу mqtt.meshtastic.org. Он предназначен для общего использования и тестирования. When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 Приватность: Сообщения на публичном брокере доступны для чтения всем, кто подписан. Всегда используйте шифрование каналов для конфиденциальной связи. Частный брокер . Для большей приватности и контроля ты можешь запустить собственный MQTT-брокер: . | Mosquitto (легковесный, с открытым исходным кодом) | HiveMQ | EMQX | . Настройте свою ноду на подключение к частному брокеру с соответствующими учётными данными. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/mqtt.html#%D0%BD%D0%B0%D1%81%D1%82%D1%80%D0%BE%D0%B9%D0%BA%D0%B8",
    
    "relUrl": "/ru-rRU/user/mqtt.html#настройки"
  },"2747": {
    "doc": "MQTT",
    "title": "Публикация на карте",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/mqtt.html#%D0%BF%D1%83%D0%B1%D0%BB%D0%B8%D0%BA%D0%B0%D1%86%D0%B8%D1%8F-%D0%BD%D0%B0-%D0%BA%D0%B0%D1%80%D1%82%D0%B5",
    
    "relUrl": "/ru-rRU/user/mqtt.html#публикация-на-карте"
  },"2748": {
    "doc": "MQTT",
    "title": "Uplink и Downlink",
    "content": "| Направление | Описание | . | Uplink (восходящий) | Сообщения из mesh-сети → MQTT-брокер | . | Downlink (нисходящий) | Сообщения от MQTT-брокера → mesh-сеть | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/mqtt.html#uplink-%D0%B8-downlink",
    
    "relUrl": "/ru-rRU/user/mqtt.html#uplink-и-downlink"
  },"2749": {
    "doc": "MQTT",
    "title": "Форматы сообщений",
    "content": "MQTT carries two payload formats: . | Формат | Описание | Сценарий использования | . | Protobuf | Бинарное кодирование Meshtastic protobuf | Соединение нод между mesh-сетями | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/mqtt.html#%D1%84%D0%BE%D1%80%D0%BC%D0%B0%D1%82%D1%8B-%D1%81%D0%BE%D0%BE%D0%B1%D1%89%D0%B5%D0%BD%D0%B8%D0%B9",
    
    "relUrl": "/ru-rRU/user/mqtt.html#форматы-сообщений"
  },"2750": {
    "doc": "MQTT",
    "title": "Шифрование и приватность",
    "content": "Понимание многоуровневой модели шифрования: . | Шифрование канала происходит в mesh-сети до MQTT. Если твой канал использует PSK, полезная нагрузка MQTT уже зашифрована — брокер и любые подписчики видят только зашифрованный текст. | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS шифрует само TCP-соединение с брокером, предотвращая перехват на сетевом уровне. | . 🔒 Security: The default public channel has a well-known key. Сообщения в канале по умолчанию, отправленные через MQTT, фактически не зашифрованы — кто угодно может их расшифровать. Всегда используйте собственный PSK для конфиденциальной связи. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/mqtt.html#%D1%88%D0%B8%D1%84%D1%80%D0%BE%D0%B2%D0%B0%D0%BD%D0%B8%D0%B5-%D0%B8-%D0%BF%D1%80%D0%B8%D0%B2%D0%B0%D1%82%D0%BD%D0%BE%D1%81%D1%82%D1%8C",
    
    "relUrl": "/ru-rRU/user/mqtt.html#шифрование-и-приватность"
  },"2751": {
    "doc": "MQTT",
    "title": "Рекомендации",
    "content": ". | Используйте шифрование на уровне канала (PSK) на каналах, подключённых к MQTT | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory) | Используйте частный брокер для задач, требующих повышенной безопасности | Учитывайте эфирное время при передаче сообщений из загруженных MQTT-топиков — каждое такое сообщение расходует радиоэфирное время в вашей локальной mesh-сети | Рассмотрите включение режима “только uplink”, если нужно лишь удалённо наблюдать за mesh-сетью, не отправляя сообщения обратно | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/mqtt.html#%D1%80%D0%B5%D0%BA%D0%BE%D0%BC%D0%B5%D0%BD%D0%B4%D0%B0%D1%86%D0%B8%D0%B8",
    
    "relUrl": "/ru-rRU/user/mqtt.html#рекомендации"
  },"2752": {
    "doc": "MQTT",
    "title": "Устранение неполадок",
    "content": "MQTT не подключается . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT не работает через сам радиоканал LoRa. | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | Разрешение DNS — если используется имя хоста собственного брокера, убедитесь, что нода может его разрешить. Попробуйте подключиться напрямую по IP-адресу брокера. | . Сообщения не проходят через мост . | Проверьте настройки uplink/downlink — если включён только uplink, сообщения идут из mesh-сети в MQTT, но не обратно. Включите downlink на принимающем шлюзе. | Несовпадение каналов — оба шлюза должны использовать один и тот же канал с одинаковым PSK. Несовпадение означает, что сообщения зашифрованы разными ключами и выглядят как мусор. | Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/mqtt.html#%D1%83%D1%81%D1%82%D1%80%D0%B0%D0%BD%D0%B5%D0%BD%D0%B8%D0%B5-%D0%BD%D0%B5%D0%BF%D0%BE%D0%BB%D0%B0%D0%B4%D0%BE%D0%BA",
    
    "relUrl": "/ru-rRU/user/mqtt.html#устранение-неполадок"
  },"2753": {
    "doc": "MQTT",
    "title": "Связанные темы",
    "content": ". | Настройки — Модули и администрирование — справочник по конфигурации модуля MQTT | Сообщения и каналы — шифрование каналов и настройка PSK | Руководство по интеграции MQTT — подробная документация по MQTT на meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/mqtt.html#%D1%81%D0%B2%D1%8F%D0%B7%D0%B0%D0%BD%D0%BD%D1%8B%D0%B5-%D1%82%D0%B5%D0%BC%D1%8B",
    
    "relUrl": "/ru-rRU/user/mqtt.html#связанные-темы"
  },"2754": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/mqtt.html",
    
    "relUrl": "/cs-rCZ/user/mqtt.html"
  },"2755": {
    "doc": "MQTT",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/mqtt.html#overview",
    
    "relUrl": "/cs-rCZ/user/mqtt.html#overview"
  },"2756": {
    "doc": "MQTT",
    "title": "How It Works",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/mqtt.html#how-it-works",
    
    "relUrl": "/cs-rCZ/user/mqtt.html#how-it-works"
  },"2757": {
    "doc": "MQTT",
    "title": "Nastavení",
    "content": "Enabling MQTT . | Navigate to Settings → Module configuration → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Nastavení | Popis | Výchozí | . | Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root topic | Base topic for messages | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | Encrypt MQTT payload | Povoleno | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | Disabled | . | TLS enabled | Secure connection to broker | Disabled | . | Map reporting | Report position to public map | Disabled | . | Proxy to client enabled | Relay MQTT through the connected phone | Disabled | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. MQTT Proxy on This Phone . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 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. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/mqtt.html#nastaven%C3%AD",
    
    "relUrl": "/cs-rCZ/user/mqtt.html#nastavení"
  },"2758": {
    "doc": "MQTT",
    "title": "Map Reporting",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/mqtt.html#map-reporting",
    
    "relUrl": "/cs-rCZ/user/mqtt.html#map-reporting"
  },"2759": {
    "doc": "MQTT",
    "title": "Uplink vs Downlink",
    "content": "| Direction | Popis | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/mqtt.html#uplink-vs-downlink",
    
    "relUrl": "/cs-rCZ/user/mqtt.html#uplink-vs-downlink"
  },"2760": {
    "doc": "MQTT",
    "title": "Message Formats",
    "content": "MQTT carries two payload formats: . | Format | Popis | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/mqtt.html#message-formats",
    
    "relUrl": "/cs-rCZ/user/mqtt.html#message-formats"
  },"2761": {
    "doc": "MQTT",
    "title": "Encryption & Privacy",
    "content": "Understanding the layered encryption model: . | 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. | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Security: 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. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/mqtt.html#encryption--privacy",
    
    "relUrl": "/cs-rCZ/user/mqtt.html#encryption--privacy"
  },"2762": {
    "doc": "MQTT",
    "title": "Best Practices",
    "content": ". | Use channel-level encryption (PSK) on channels that bridge to MQTT | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes 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 | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/mqtt.html#best-practices",
    
    "relUrl": "/cs-rCZ/user/mqtt.html#best-practices"
  },"2763": {
    "doc": "MQTT",
    "title": "Troubleshooting",
    "content": "MQTT Not Connecting . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | 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 — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/mqtt.html#troubleshooting",
    
    "relUrl": "/cs-rCZ/user/mqtt.html#troubleshooting"
  },"2764": {
    "doc": "MQTT",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — MQTT module configuration reference | Messages & Channels — channel encryption and PSK setup | MQTT integration guide — detailed MQTT documentation on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/mqtt.html#related-topics",
    
    "relUrl": "/cs-rCZ/user/mqtt.html#related-topics"
  },"2765": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/mqtt.html",
    
    "relUrl": "/bg-rBG/user/mqtt.html"
  },"2766": {
    "doc": "MQTT",
    "title": "Преглед",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/mqtt.html#%D0%BF%D1%80%D0%B5%D0%B3%D0%BB%D0%B5%D0%B4",
    
    "relUrl": "/bg-rBG/user/mqtt.html#преглед"
  },"2767": {
    "doc": "MQTT",
    "title": "Как работи",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/mqtt.html#%D0%BA%D0%B0%D0%BA-%D1%80%D0%B0%D0%B1%D0%BE%D1%82%D0%B8",
    
    "relUrl": "/bg-rBG/user/mqtt.html#как-работи"
  },"2768": {
    "doc": "MQTT",
    "title": "Конфигурация",
    "content": "Enabling MQTT . | Navigate to Settings → Module configuration → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Настройка | Описание | По подразбиране | . | Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root topic | Base topic for messages | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | Encrypt MQTT payload | Активиран | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | Disabled | . | TLS enabled | Secure connection to broker | Disabled | . | Map reporting | Report position to public map | Disabled | . | Proxy to client enabled | Relay MQTT through the connected phone | Disabled | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. MQTT Proxy on This Phone . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 Privacy: Messages on the public broker are readable by anyone subscribed. Always use channel encryption for private communications. Private Broker . За по-добра поверителност и контрол, можете да управлявате свой собствен MQTT брокер: . | Mosquitto (lightweight, open-source) | HiveMQ | EMQX | . Configure your node to point to your private broker with appropriate credentials. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/mqtt.html#%D0%BA%D0%BE%D0%BD%D1%84%D0%B8%D0%B3%D1%83%D1%80%D0%B0%D1%86%D0%B8%D1%8F",
    
    "relUrl": "/bg-rBG/user/mqtt.html#конфигурация"
  },"2769": {
    "doc": "MQTT",
    "title": "Map Reporting",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/mqtt.html#map-reporting",
    
    "relUrl": "/bg-rBG/user/mqtt.html#map-reporting"
  },"2770": {
    "doc": "MQTT",
    "title": "Uplink vs Downlink",
    "content": "| Direction | Описание | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/mqtt.html#uplink-vs-downlink",
    
    "relUrl": "/bg-rBG/user/mqtt.html#uplink-vs-downlink"
  },"2771": {
    "doc": "MQTT",
    "title": "Message Formats",
    "content": "MQTT carries two payload formats: . | Format | Описание | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/mqtt.html#message-formats",
    
    "relUrl": "/bg-rBG/user/mqtt.html#message-formats"
  },"2772": {
    "doc": "MQTT",
    "title": "Encryption & Privacy",
    "content": "Understanding the layered encryption model: . | 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. | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Security: 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. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/mqtt.html#encryption--privacy",
    
    "relUrl": "/bg-rBG/user/mqtt.html#encryption--privacy"
  },"2773": {
    "doc": "MQTT",
    "title": "Най-добри практики",
    "content": ". | Use channel-level encryption (PSK) on channels that bridge to MQTT | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes 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 | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/mqtt.html#%D0%BD%D0%B0%D0%B9-%D0%B4%D0%BE%D0%B1%D1%80%D0%B8-%D0%BF%D1%80%D0%B0%D0%BA%D1%82%D0%B8%D0%BA%D0%B8",
    
    "relUrl": "/bg-rBG/user/mqtt.html#най-добри-практики"
  },"2774": {
    "doc": "MQTT",
    "title": "Отстраняване на неизправности",
    "content": "MQTT Not Connecting . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | 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 — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/mqtt.html#%D0%BE%D1%82%D1%81%D1%82%D1%80%D0%B0%D0%BD%D1%8F%D0%B2%D0%B0%D0%BD%D0%B5-%D0%BD%D0%B0-%D0%BD%D0%B5%D0%B8%D0%B7%D0%BF%D1%80%D0%B0%D0%B2%D0%BD%D0%BE%D1%81%D1%82%D0%B8",
    
    "relUrl": "/bg-rBG/user/mqtt.html#отстраняване-на-неизправности"
  },"2775": {
    "doc": "MQTT",
    "title": "Свързани теми",
    "content": ". | Settings — Modules & Admin — MQTT module configuration reference | Messages & Channels — channel encryption and PSK setup | MQTT integration guide — detailed MQTT documentation on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/mqtt.html#%D1%81%D0%B2%D1%8A%D1%80%D0%B7%D0%B0%D0%BD%D0%B8-%D1%82%D0%B5%D0%BC%D0%B8",
    
    "relUrl": "/bg-rBG/user/mqtt.html#свързани-теми"
  },"2776": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/mqtt.html",
    
    "relUrl": "/ga-rIE/user/mqtt.html"
  },"2777": {
    "doc": "MQTT",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/mqtt.html#overview",
    
    "relUrl": "/ga-rIE/user/mqtt.html#overview"
  },"2778": {
    "doc": "MQTT",
    "title": "How It Works",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/mqtt.html#how-it-works",
    
    "relUrl": "/ga-rIE/user/mqtt.html#how-it-works"
  },"2779": {
    "doc": "MQTT",
    "title": "Configuration",
    "content": "Enabling MQTT . | Navigate to Settings → Module configuration → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Cur síos | Default | . | Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root topic | Base topic for messages | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | Encrypt MQTT payload | Enabled | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | Disabled | . | TLS enabled | Secure connection to broker | Disabled | . | Map reporting | Report position to public map | Disabled | . | Proxy to client enabled | Relay MQTT through the connected phone | Disabled | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. MQTT Proxy on This Phone . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 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. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/mqtt.html#configuration",
    
    "relUrl": "/ga-rIE/user/mqtt.html#configuration"
  },"2780": {
    "doc": "MQTT",
    "title": "Map Reporting",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/mqtt.html#map-reporting",
    
    "relUrl": "/ga-rIE/user/mqtt.html#map-reporting"
  },"2781": {
    "doc": "MQTT",
    "title": "Uplink vs Downlink",
    "content": "| Direction | Cur síos | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/mqtt.html#uplink-vs-downlink",
    
    "relUrl": "/ga-rIE/user/mqtt.html#uplink-vs-downlink"
  },"2782": {
    "doc": "MQTT",
    "title": "Message Formats",
    "content": "MQTT carries two payload formats: . | Format | Cur síos | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/mqtt.html#message-formats",
    
    "relUrl": "/ga-rIE/user/mqtt.html#message-formats"
  },"2783": {
    "doc": "MQTT",
    "title": "Encryption & Privacy",
    "content": "Understanding the layered encryption model: . | 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. | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Security: 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. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/mqtt.html#encryption--privacy",
    
    "relUrl": "/ga-rIE/user/mqtt.html#encryption--privacy"
  },"2784": {
    "doc": "MQTT",
    "title": "Best Practices",
    "content": ". | Use channel-level encryption (PSK) on channels that bridge to MQTT | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes 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 | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/mqtt.html#best-practices",
    
    "relUrl": "/ga-rIE/user/mqtt.html#best-practices"
  },"2785": {
    "doc": "MQTT",
    "title": "Troubleshooting",
    "content": "MQTT Not Connecting . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | 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 — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/mqtt.html#troubleshooting",
    
    "relUrl": "/ga-rIE/user/mqtt.html#troubleshooting"
  },"2786": {
    "doc": "MQTT",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — MQTT module configuration reference | Messages & Channels — channel encryption and PSK setup | MQTT integration guide — detailed MQTT documentation on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/mqtt.html#related-topics",
    
    "relUrl": "/ga-rIE/user/mqtt.html#related-topics"
  },"2787": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/mqtt.html",
    
    "relUrl": "/fr-rCA/user/mqtt.html"
  },"2788": {
    "doc": "MQTT",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/mqtt.html#overview",
    
    "relUrl": "/fr-rCA/user/mqtt.html#overview"
  },"2789": {
    "doc": "MQTT",
    "title": "How It Works",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/mqtt.html#how-it-works",
    
    "relUrl": "/fr-rCA/user/mqtt.html#how-it-works"
  },"2790": {
    "doc": "MQTT",
    "title": "Configuration",
    "content": "Enabling MQTT . | Navigate to Settings → Module configuration → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Description | Par défaut | . | Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root topic | Base topic for messages | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | Encrypt MQTT payload | Activé | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | Désactivé | . | TLS enabled | Secure connection to broker | Désactivé | . | Map reporting | Report position to public map | Désactivé | . | Proxy to client enabled | Relay MQTT through the connected phone | Désactivé | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. MQTT Proxy on This Phone . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 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. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/mqtt.html#configuration",
    
    "relUrl": "/fr-rCA/user/mqtt.html#configuration"
  },"2791": {
    "doc": "MQTT",
    "title": "Map Reporting",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/mqtt.html#map-reporting",
    
    "relUrl": "/fr-rCA/user/mqtt.html#map-reporting"
  },"2792": {
    "doc": "MQTT",
    "title": "Uplink vs Downlink",
    "content": "| Direction | Description | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/mqtt.html#uplink-vs-downlink",
    
    "relUrl": "/fr-rCA/user/mqtt.html#uplink-vs-downlink"
  },"2793": {
    "doc": "MQTT",
    "title": "Message Formats",
    "content": "MQTT carries two payload formats: . | Format | Description | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/mqtt.html#message-formats",
    
    "relUrl": "/fr-rCA/user/mqtt.html#message-formats"
  },"2794": {
    "doc": "MQTT",
    "title": "Encryption & Privacy",
    "content": "Understanding the layered encryption model: . | 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. | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Security: 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. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/mqtt.html#encryption--privacy",
    
    "relUrl": "/fr-rCA/user/mqtt.html#encryption--privacy"
  },"2795": {
    "doc": "MQTT",
    "title": "Best Practices",
    "content": ". | Use channel-level encryption (PSK) on channels that bridge to MQTT | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes 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 | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/mqtt.html#best-practices",
    
    "relUrl": "/fr-rCA/user/mqtt.html#best-practices"
  },"2796": {
    "doc": "MQTT",
    "title": "Troubleshooting",
    "content": "MQTT Not Connecting . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | 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 — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/mqtt.html#troubleshooting",
    
    "relUrl": "/fr-rCA/user/mqtt.html#troubleshooting"
  },"2797": {
    "doc": "MQTT",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — MQTT module configuration reference | Messages & Channels — channel encryption and PSK setup | MQTT integration guide — detailed MQTT documentation on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/mqtt.html#related-topics",
    
    "relUrl": "/fr-rCA/user/mqtt.html#related-topics"
  },"2798": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range. ",
    "url": "/Meshtastic-Android/main/srp/user/mqtt.html",
    
    "relUrl": "/srp/user/mqtt.html"
  },"2799": {
    "doc": "MQTT",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/srp/user/mqtt.html#overview",
    
    "relUrl": "/srp/user/mqtt.html#overview"
  },"2800": {
    "doc": "MQTT",
    "title": "How It Works",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ",
    "url": "/Meshtastic-Android/main/srp/user/mqtt.html#how-it-works",
    
    "relUrl": "/srp/user/mqtt.html#how-it-works"
  },"2801": {
    "doc": "MQTT",
    "title": "Configuration",
    "content": "Enabling MQTT . | Navigate to Settings → Module configuration → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Опис | Подразумевано | . | Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root topic | Base topic for messages | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | Encrypt MQTT payload | Омогућено | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | Онемогућено | . | TLS enabled | Secure connection to broker | Онемогућено | . | Map reporting | Report position to public map | Онемогућено | . | Proxy to client enabled | Relay MQTT through the connected phone | Онемогућено | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. MQTT Proxy on This Phone . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 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. ",
    "url": "/Meshtastic-Android/main/srp/user/mqtt.html#configuration",
    
    "relUrl": "/srp/user/mqtt.html#configuration"
  },"2802": {
    "doc": "MQTT",
    "title": "Map Reporting",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/srp/user/mqtt.html#map-reporting",
    
    "relUrl": "/srp/user/mqtt.html#map-reporting"
  },"2803": {
    "doc": "MQTT",
    "title": "Uplink vs Downlink",
    "content": "| Direction | Опис | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/srp/user/mqtt.html#uplink-vs-downlink",
    
    "relUrl": "/srp/user/mqtt.html#uplink-vs-downlink"
  },"2804": {
    "doc": "MQTT",
    "title": "Message Formats",
    "content": "MQTT carries two payload formats: . | Format | Опис | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/srp/user/mqtt.html#message-formats",
    
    "relUrl": "/srp/user/mqtt.html#message-formats"
  },"2805": {
    "doc": "MQTT",
    "title": "Encryption & Privacy",
    "content": "Understanding the layered encryption model: . | 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. | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Security: 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. ",
    "url": "/Meshtastic-Android/main/srp/user/mqtt.html#encryption--privacy",
    
    "relUrl": "/srp/user/mqtt.html#encryption--privacy"
  },"2806": {
    "doc": "MQTT",
    "title": "Best Practices",
    "content": ". | Use channel-level encryption (PSK) on channels that bridge to MQTT | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes 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 | . ",
    "url": "/Meshtastic-Android/main/srp/user/mqtt.html#best-practices",
    
    "relUrl": "/srp/user/mqtt.html#best-practices"
  },"2807": {
    "doc": "MQTT",
    "title": "Troubleshooting",
    "content": "MQTT Not Connecting . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | 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 — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/srp/user/mqtt.html#troubleshooting",
    
    "relUrl": "/srp/user/mqtt.html#troubleshooting"
  },"2808": {
    "doc": "MQTT",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — MQTT module configuration reference | Messages & Channels — channel encryption and PSK setup | MQTT integration guide — detailed MQTT documentation on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/srp/user/mqtt.html#related-topics",
    
    "relUrl": "/srp/user/mqtt.html#related-topics"
  },"2809": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/mqtt.html",
    
    "relUrl": "/ca-rES/user/mqtt.html"
  },"2810": {
    "doc": "MQTT",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/mqtt.html#overview",
    
    "relUrl": "/ca-rES/user/mqtt.html#overview"
  },"2811": {
    "doc": "MQTT",
    "title": "How It Works",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/mqtt.html#how-it-works",
    
    "relUrl": "/ca-rES/user/mqtt.html#how-it-works"
  },"2812": {
    "doc": "MQTT",
    "title": "Configuration",
    "content": "Enabling MQTT . | Navigate to Settings → Module configuration → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Descripció | Default | . | Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root topic | Base topic for messages | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | Encrypt MQTT payload | Enabled | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | Disabled | . | TLS enabled | Secure connection to broker | Disabled | . | Map reporting | Report position to public map | Disabled | . | Proxy to client enabled | Relay MQTT through the connected phone | Disabled | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. MQTT Proxy on This Phone . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 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. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/mqtt.html#configuration",
    
    "relUrl": "/ca-rES/user/mqtt.html#configuration"
  },"2813": {
    "doc": "MQTT",
    "title": "Map Reporting",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/mqtt.html#map-reporting",
    
    "relUrl": "/ca-rES/user/mqtt.html#map-reporting"
  },"2814": {
    "doc": "MQTT",
    "title": "Uplink vs Downlink",
    "content": "| Direction | Descripció | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/mqtt.html#uplink-vs-downlink",
    
    "relUrl": "/ca-rES/user/mqtt.html#uplink-vs-downlink"
  },"2815": {
    "doc": "MQTT",
    "title": "Message Formats",
    "content": "MQTT carries two payload formats: . | Format | Descripció | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/mqtt.html#message-formats",
    
    "relUrl": "/ca-rES/user/mqtt.html#message-formats"
  },"2816": {
    "doc": "MQTT",
    "title": "Encryption & Privacy",
    "content": "Understanding the layered encryption model: . | 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. | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Security: 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. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/mqtt.html#encryption--privacy",
    
    "relUrl": "/ca-rES/user/mqtt.html#encryption--privacy"
  },"2817": {
    "doc": "MQTT",
    "title": "Best Practices",
    "content": ". | Use channel-level encryption (PSK) on channels that bridge to MQTT | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes 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 | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/mqtt.html#best-practices",
    
    "relUrl": "/ca-rES/user/mqtt.html#best-practices"
  },"2818": {
    "doc": "MQTT",
    "title": "Troubleshooting",
    "content": "MQTT Not Connecting . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | 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 — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/mqtt.html#troubleshooting",
    
    "relUrl": "/ca-rES/user/mqtt.html#troubleshooting"
  },"2819": {
    "doc": "MQTT",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — MQTT module configuration reference | Messages & Channels — channel encryption and PSK setup | MQTT integration guide — detailed MQTT documentation on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/mqtt.html#related-topics",
    
    "relUrl": "/ca-rES/user/mqtt.html#related-topics"
  },"2820": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/mqtt.html",
    
    "relUrl": "/ko-rKR/user/mqtt.html"
  },"2821": {
    "doc": "MQTT",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/mqtt.html#overview",
    
    "relUrl": "/ko-rKR/user/mqtt.html#overview"
  },"2822": {
    "doc": "MQTT",
    "title": "How It Works",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/mqtt.html#how-it-works",
    
    "relUrl": "/ko-rKR/user/mqtt.html#how-it-works"
  },"2823": {
    "doc": "MQTT",
    "title": "설정",
    "content": "Enabling MQTT . | Navigate to Settings → Module configuration → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | 설명 | 기본값 | . | Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root topic | Base topic for messages | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | Encrypt MQTT payload | 활성화 | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | Disabled | . | TLS enabled | Secure connection to broker | Disabled | . | Map reporting | Report position to public map | Disabled | . | Proxy to client enabled | Relay MQTT through the connected phone | Disabled | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. MQTT Proxy on This Phone . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 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. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/mqtt.html#%EC%84%A4%EC%A0%95",
    
    "relUrl": "/ko-rKR/user/mqtt.html#설정"
  },"2824": {
    "doc": "MQTT",
    "title": "Map Reporting",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/mqtt.html#map-reporting",
    
    "relUrl": "/ko-rKR/user/mqtt.html#map-reporting"
  },"2825": {
    "doc": "MQTT",
    "title": "Uplink vs Downlink",
    "content": "| Direction | 설명 | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/mqtt.html#uplink-vs-downlink",
    
    "relUrl": "/ko-rKR/user/mqtt.html#uplink-vs-downlink"
  },"2826": {
    "doc": "MQTT",
    "title": "Message Formats",
    "content": "MQTT carries two payload formats: . | Format | 설명 | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/mqtt.html#message-formats",
    
    "relUrl": "/ko-rKR/user/mqtt.html#message-formats"
  },"2827": {
    "doc": "MQTT",
    "title": "Encryption & Privacy",
    "content": "Understanding the layered encryption model: . | 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. | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Security: 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. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/mqtt.html#encryption--privacy",
    
    "relUrl": "/ko-rKR/user/mqtt.html#encryption--privacy"
  },"2828": {
    "doc": "MQTT",
    "title": "Best Practices",
    "content": ". | Use channel-level encryption (PSK) on channels that bridge to MQTT | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes 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 | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/mqtt.html#best-practices",
    
    "relUrl": "/ko-rKR/user/mqtt.html#best-practices"
  },"2829": {
    "doc": "MQTT",
    "title": "Troubleshooting",
    "content": "MQTT Not Connecting . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | 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 — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/mqtt.html#troubleshooting",
    
    "relUrl": "/ko-rKR/user/mqtt.html#troubleshooting"
  },"2830": {
    "doc": "MQTT",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — MQTT module configuration reference | Messages & Channels — channel encryption and PSK setup | MQTT integration guide — detailed MQTT documentation on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/mqtt.html#related-topics",
    
    "relUrl": "/ko-rKR/user/mqtt.html#related-topics"
  },"2831": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/mqtt.html",
    
    "relUrl": "/sv-rSE/user/mqtt.html"
  },"2832": {
    "doc": "MQTT",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/mqtt.html#overview",
    
    "relUrl": "/sv-rSE/user/mqtt.html#overview"
  },"2833": {
    "doc": "MQTT",
    "title": "How It Works",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/mqtt.html#how-it-works",
    
    "relUrl": "/sv-rSE/user/mqtt.html#how-it-works"
  },"2834": {
    "doc": "MQTT",
    "title": "Konfiguration",
    "content": "Enabling MQTT . | Navigate to Settings → Module configuration → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Beskrivning | Förvald | . | Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root topic | Base topic for messages | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | Encrypt MQTT payload | Aktiverad | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | Disabled | . | TLS enabled | Secure connection to broker | Disabled | . | Map reporting | Report position to public map | Disabled | . | Proxy to client enabled | Relay MQTT through the connected phone | Disabled | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. MQTT Proxy on This Phone . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 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. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/mqtt.html#konfiguration",
    
    "relUrl": "/sv-rSE/user/mqtt.html#konfiguration"
  },"2835": {
    "doc": "MQTT",
    "title": "Map Reporting",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/mqtt.html#map-reporting",
    
    "relUrl": "/sv-rSE/user/mqtt.html#map-reporting"
  },"2836": {
    "doc": "MQTT",
    "title": "Uplink vs Downlink",
    "content": "| Direction | Beskrivning | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/mqtt.html#uplink-vs-downlink",
    
    "relUrl": "/sv-rSE/user/mqtt.html#uplink-vs-downlink"
  },"2837": {
    "doc": "MQTT",
    "title": "Message Formats",
    "content": "MQTT carries two payload formats: . | Format | Beskrivning | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/mqtt.html#message-formats",
    
    "relUrl": "/sv-rSE/user/mqtt.html#message-formats"
  },"2838": {
    "doc": "MQTT",
    "title": "Encryption & Privacy",
    "content": "Understanding the layered encryption model: . | 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. | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Security: 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. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/mqtt.html#encryption--privacy",
    
    "relUrl": "/sv-rSE/user/mqtt.html#encryption--privacy"
  },"2839": {
    "doc": "MQTT",
    "title": "Best Practices",
    "content": ". | Use channel-level encryption (PSK) on channels that bridge to MQTT | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes 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 | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/mqtt.html#best-practices",
    
    "relUrl": "/sv-rSE/user/mqtt.html#best-practices"
  },"2840": {
    "doc": "MQTT",
    "title": "Felsökning",
    "content": "MQTT Not Connecting . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | 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 — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/mqtt.html#fels%C3%B6kning",
    
    "relUrl": "/sv-rSE/user/mqtt.html#felsökning"
  },"2841": {
    "doc": "MQTT",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — MQTT module configuration reference | Messages & Channels — channel encryption and PSK setup | MQTT integration guide — detailed MQTT documentation on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/mqtt.html#related-topics",
    
    "relUrl": "/sv-rSE/user/mqtt.html#related-topics"
  },"2842": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/mqtt.html",
    
    "relUrl": "/ht-rHT/user/mqtt.html"
  },"2843": {
    "doc": "MQTT",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/mqtt.html#overview",
    
    "relUrl": "/ht-rHT/user/mqtt.html#overview"
  },"2844": {
    "doc": "MQTT",
    "title": "How It Works",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/mqtt.html#how-it-works",
    
    "relUrl": "/ht-rHT/user/mqtt.html#how-it-works"
  },"2845": {
    "doc": "MQTT",
    "title": "Configuration",
    "content": "Enabling MQTT . | Navigate to Settings → Module configuration → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Deskripsyon | Default | . | Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root topic | Base topic for messages | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | Encrypt MQTT payload | Enabled | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | Disabled | . | TLS enabled | Secure connection to broker | Disabled | . | Map reporting | Report position to public map | Disabled | . | Proxy to client enabled | Relay MQTT through the connected phone | Disabled | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. MQTT Proxy on This Phone . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 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. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/mqtt.html#configuration",
    
    "relUrl": "/ht-rHT/user/mqtt.html#configuration"
  },"2846": {
    "doc": "MQTT",
    "title": "Map Reporting",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/mqtt.html#map-reporting",
    
    "relUrl": "/ht-rHT/user/mqtt.html#map-reporting"
  },"2847": {
    "doc": "MQTT",
    "title": "Uplink vs Downlink",
    "content": "| Direction | Deskripsyon | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/mqtt.html#uplink-vs-downlink",
    
    "relUrl": "/ht-rHT/user/mqtt.html#uplink-vs-downlink"
  },"2848": {
    "doc": "MQTT",
    "title": "Message Formats",
    "content": "MQTT carries two payload formats: . | Format | Deskripsyon | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/mqtt.html#message-formats",
    
    "relUrl": "/ht-rHT/user/mqtt.html#message-formats"
  },"2849": {
    "doc": "MQTT",
    "title": "Encryption & Privacy",
    "content": "Understanding the layered encryption model: . | 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. | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Security: 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. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/mqtt.html#encryption--privacy",
    
    "relUrl": "/ht-rHT/user/mqtt.html#encryption--privacy"
  },"2850": {
    "doc": "MQTT",
    "title": "Best Practices",
    "content": ". | Use channel-level encryption (PSK) on channels that bridge to MQTT | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes 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 | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/mqtt.html#best-practices",
    
    "relUrl": "/ht-rHT/user/mqtt.html#best-practices"
  },"2851": {
    "doc": "MQTT",
    "title": "Troubleshooting",
    "content": "MQTT Not Connecting . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | 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 — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/mqtt.html#troubleshooting",
    
    "relUrl": "/ht-rHT/user/mqtt.html#troubleshooting"
  },"2852": {
    "doc": "MQTT",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — MQTT module configuration reference | Messages & Channels — channel encryption and PSK setup | MQTT integration guide — detailed MQTT documentation on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/mqtt.html#related-topics",
    
    "relUrl": "/ht-rHT/user/mqtt.html#related-topics"
  },"2853": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/mqtt.html",
    
    "relUrl": "/sr-rLatn/user/mqtt.html"
  },"2854": {
    "doc": "MQTT",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/mqtt.html#overview",
    
    "relUrl": "/sr-rLatn/user/mqtt.html#overview"
  },"2855": {
    "doc": "MQTT",
    "title": "How It Works",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/mqtt.html#how-it-works",
    
    "relUrl": "/sr-rLatn/user/mqtt.html#how-it-works"
  },"2856": {
    "doc": "MQTT",
    "title": "Configuration",
    "content": "Enabling MQTT . | Navigate to Settings → Module configuration → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Опис | Подразумевано | . | Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root topic | Base topic for messages | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | Encrypt MQTT payload | Омогућено | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | Онемогућено | . | TLS enabled | Secure connection to broker | Онемогућено | . | Map reporting | Report position to public map | Онемогућено | . | Proxy to client enabled | Relay MQTT through the connected phone | Онемогућено | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. MQTT Proxy on This Phone . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 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. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/mqtt.html#configuration",
    
    "relUrl": "/sr-rLatn/user/mqtt.html#configuration"
  },"2857": {
    "doc": "MQTT",
    "title": "Map Reporting",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/mqtt.html#map-reporting",
    
    "relUrl": "/sr-rLatn/user/mqtt.html#map-reporting"
  },"2858": {
    "doc": "MQTT",
    "title": "Uplink vs Downlink",
    "content": "| Direction | Опис | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/mqtt.html#uplink-vs-downlink",
    
    "relUrl": "/sr-rLatn/user/mqtt.html#uplink-vs-downlink"
  },"2859": {
    "doc": "MQTT",
    "title": "Message Formats",
    "content": "MQTT carries two payload formats: . | Format | Опис | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/mqtt.html#message-formats",
    
    "relUrl": "/sr-rLatn/user/mqtt.html#message-formats"
  },"2860": {
    "doc": "MQTT",
    "title": "Encryption & Privacy",
    "content": "Understanding the layered encryption model: . | 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. | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Security: 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. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/mqtt.html#encryption--privacy",
    
    "relUrl": "/sr-rLatn/user/mqtt.html#encryption--privacy"
  },"2861": {
    "doc": "MQTT",
    "title": "Best Practices",
    "content": ". | Use channel-level encryption (PSK) on channels that bridge to MQTT | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes 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 | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/mqtt.html#best-practices",
    
    "relUrl": "/sr-rLatn/user/mqtt.html#best-practices"
  },"2862": {
    "doc": "MQTT",
    "title": "Troubleshooting",
    "content": "MQTT Not Connecting . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | 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 — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/mqtt.html#troubleshooting",
    
    "relUrl": "/sr-rLatn/user/mqtt.html#troubleshooting"
  },"2863": {
    "doc": "MQTT",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — MQTT module configuration reference | Messages & Channels — channel encryption and PSK setup | MQTT integration guide — detailed MQTT documentation on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/mqtt.html#related-topics",
    
    "relUrl": "/sr-rLatn/user/mqtt.html#related-topics"
  },"2864": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/mqtt.html",
    
    "relUrl": "/nl-rNL/user/mqtt.html"
  },"2865": {
    "doc": "MQTT",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/mqtt.html#overview",
    
    "relUrl": "/nl-rNL/user/mqtt.html#overview"
  },"2866": {
    "doc": "MQTT",
    "title": "How It Works",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/mqtt.html#how-it-works",
    
    "relUrl": "/nl-rNL/user/mqtt.html#how-it-works"
  },"2867": {
    "doc": "MQTT",
    "title": "Configuration",
    "content": "Enabling MQTT . | Navigate to Settings → Module configuration → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Beschrijving | Standaard | . | Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root topic | Base topic for messages | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | Encrypt MQTT payload | Enabled | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | Disabled | . | TLS enabled | Secure connection to broker | Disabled | . | Map reporting | Report position to public map | Disabled | . | Proxy to client enabled | Relay MQTT through the connected phone | Disabled | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. MQTT Proxy on This Phone . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 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. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/mqtt.html#configuration",
    
    "relUrl": "/nl-rNL/user/mqtt.html#configuration"
  },"2868": {
    "doc": "MQTT",
    "title": "Map Reporting",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/mqtt.html#map-reporting",
    
    "relUrl": "/nl-rNL/user/mqtt.html#map-reporting"
  },"2869": {
    "doc": "MQTT",
    "title": "Uplink vs Downlink",
    "content": "| Direction | Beschrijving | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/mqtt.html#uplink-vs-downlink",
    
    "relUrl": "/nl-rNL/user/mqtt.html#uplink-vs-downlink"
  },"2870": {
    "doc": "MQTT",
    "title": "Message Formats",
    "content": "MQTT carries two payload formats: . | Format | Beschrijving | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/mqtt.html#message-formats",
    
    "relUrl": "/nl-rNL/user/mqtt.html#message-formats"
  },"2871": {
    "doc": "MQTT",
    "title": "Encryption & Privacy",
    "content": "Understanding the layered encryption model: . | 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. | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Security: 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. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/mqtt.html#encryption--privacy",
    
    "relUrl": "/nl-rNL/user/mqtt.html#encryption--privacy"
  },"2872": {
    "doc": "MQTT",
    "title": "Best Practices",
    "content": ". | Use channel-level encryption (PSK) on channels that bridge to MQTT | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes 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 | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/mqtt.html#best-practices",
    
    "relUrl": "/nl-rNL/user/mqtt.html#best-practices"
  },"2873": {
    "doc": "MQTT",
    "title": "Troubleshooting",
    "content": "MQTT Not Connecting . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | 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 — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/mqtt.html#troubleshooting",
    
    "relUrl": "/nl-rNL/user/mqtt.html#troubleshooting"
  },"2874": {
    "doc": "MQTT",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — MQTT module configuration reference | Messages & Channels — channel encryption and PSK setup | MQTT integration guide — detailed MQTT documentation on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/mqtt.html#related-topics",
    
    "relUrl": "/nl-rNL/user/mqtt.html#related-topics"
  },"2875": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/mqtt.html",
    
    "relUrl": "/uk-rUA/user/mqtt.html"
  },"2876": {
    "doc": "MQTT",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/mqtt.html#overview",
    
    "relUrl": "/uk-rUA/user/mqtt.html#overview"
  },"2877": {
    "doc": "MQTT",
    "title": "How It Works",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/mqtt.html#how-it-works",
    
    "relUrl": "/uk-rUA/user/mqtt.html#how-it-works"
  },"2878": {
    "doc": "MQTT",
    "title": "Налаштування",
    "content": "Enabling MQTT . | Navigate to Settings → Module configuration → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Опис | За замовчуванням | . | Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root topic | Base topic for messages | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | Encrypt MQTT payload | Увімкнено | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | Disabled | . | TLS enabled | Secure connection to broker | Disabled | . | Map reporting | Report position to public map | Disabled | . | Proxy to client enabled | Relay MQTT through the connected phone | Disabled | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. MQTT Proxy on This Phone . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 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. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/mqtt.html#%D0%BD%D0%B0%D0%BB%D0%B0%D1%88%D1%82%D1%83%D0%B2%D0%B0%D0%BD%D0%BD%D1%8F",
    
    "relUrl": "/uk-rUA/user/mqtt.html#налаштування"
  },"2879": {
    "doc": "MQTT",
    "title": "Map Reporting",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/mqtt.html#map-reporting",
    
    "relUrl": "/uk-rUA/user/mqtt.html#map-reporting"
  },"2880": {
    "doc": "MQTT",
    "title": "Uplink vs Downlink",
    "content": "| Direction | Опис | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/mqtt.html#uplink-vs-downlink",
    
    "relUrl": "/uk-rUA/user/mqtt.html#uplink-vs-downlink"
  },"2881": {
    "doc": "MQTT",
    "title": "Message Formats",
    "content": "MQTT carries two payload formats: . | Format | Опис | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/mqtt.html#message-formats",
    
    "relUrl": "/uk-rUA/user/mqtt.html#message-formats"
  },"2882": {
    "doc": "MQTT",
    "title": "Encryption & Privacy",
    "content": "Understanding the layered encryption model: . | 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. | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Security: 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. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/mqtt.html#encryption--privacy",
    
    "relUrl": "/uk-rUA/user/mqtt.html#encryption--privacy"
  },"2883": {
    "doc": "MQTT",
    "title": "Best Practices",
    "content": ". | Use channel-level encryption (PSK) on channels that bridge to MQTT | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes 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 | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/mqtt.html#best-practices",
    
    "relUrl": "/uk-rUA/user/mqtt.html#best-practices"
  },"2884": {
    "doc": "MQTT",
    "title": "Troubleshooting",
    "content": "MQTT Not Connecting . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | 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 — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/mqtt.html#troubleshooting",
    
    "relUrl": "/uk-rUA/user/mqtt.html#troubleshooting"
  },"2885": {
    "doc": "MQTT",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — MQTT module configuration reference | Messages & Channels — channel encryption and PSK setup | MQTT integration guide — detailed MQTT documentation on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/mqtt.html#related-topics",
    
    "relUrl": "/uk-rUA/user/mqtt.html#related-topics"
  },"2886": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT yhdistää Meshtastic-mesh-verkkosi internetiin ja mahdollistaa pitkän kantaman viestinnän radioalueen ulkopuolella. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/mqtt.html",
    
    "relUrl": "/fi-rFI/user/mqtt.html"
  },"2887": {
    "doc": "MQTT",
    "title": "Yleiskatsaus",
    "content": "MQTT-moduuli yhdistää radion MQTT-välityspalvelimeen, mahdollistaen: . | Viestien välittymisen eri fyysisten mesh-verkkojen välillä internetin kautta | Integraation kotiautomaatio- ja valvontajärjestelmiin | Radioiden sijaintien julkaisemisen julkiseen Meshtastic-karttaan | Mukautetut dataputket tiedonkeruuta ja hälytyksiä varten | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/mqtt.html#yleiskatsaus",
    
    "relUrl": "/fi-rFI/user/mqtt.html#yleiskatsaus"
  },"2888": {
    "doc": "MQTT",
    "title": "Kuinka se toimii",
    "content": "[Oma radio] → Radio → [Yhdyskäytäväradio, jossa WiFi] → MQTT-välityspalvelin → [Etäyhdyskäytävä] → Radio → [Etäradio] . Internet-yhteydellä varustettu yhdyskäytäväradio (WiFi tai Ethernet) julkaisee mesh-verkon viestejä MQTT-aiheeseen. Etä-yhdyskäytävät, jotka ovat tilanneet saman aiheen, syöttävät viestit omaan paikalliseen mesh-verkkoonsa. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/mqtt.html#kuinka-se-toimii",
    
    "relUrl": "/fi-rFI/user/mqtt.html#kuinka-se-toimii"
  },"2889": {
    "doc": "MQTT",
    "title": "Asetukset",
    "content": "MQTT:n käyttöönotto . | Navigate to Settings → Module configuration → MQTT. | Ota MQTT-moduuli käyttöön. | Määritä välityspalvelimen yhteys: | . | Asetus | Kuvaus | Oletus | . | Address | MQTT-välityspalvelimen osoite | mqtt.meshtastic.org | . | Username | Välityspalvelimen tunnistautuminen | meshdev | . | Password | Välityspalvelimen tunnistautuminen | large4cats | . | Root topic | Viestien perusaihe | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | MQTT-viestisisällön salaus | Käytössä | . | JSON output enabled | Julkaise ja vastaanota myös /2/json/-aihetta. Merkitty protobuf-rakenteessa vanhentuneeksi, mutta tämä on edelleen ainoa asetus tähän toimintaan — ja sovelluksen oma välityspalvelin käyttää sitä | Ei käytössä | . | TLS enabled | Yhteyden suojaaminen välityspalvelimeen | Ei käytössä | . | Map reporting | Sijainnin julkaisu julkiselle kartalle | Ei käytössä | . | Proxy to client enabled | Relay MQTT through the connected phone | Ei käytössä | . Yhteyden tila ja testaa yhteys . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Testaa yhteys tarkistaa välityspalvelimen ennen asetusten tallentamista radioon ja erottaa eri virhetilanteet: palvelinnimen selvitys epäonnistui, TCP-yhteys hylättiin, TLS epäonnistui, yritys aikakatkaistiin tai välityspalvelin hylkäsi tunnistetietosi syyn kera. MQTT-välityspalvelin tässä puhelimessa . Jos radiollasi ei ole omaa internetyhteyttä, se voi käyttää yhdistettyä puhelinta MQTT-yhdyskäytävänään: ota moduulin asetuksista käyttöön MQTT ja Välityspalvelin käytössä, jolloin sovellus välittää MQTT-liikenteen radion ja välityspalvelimen välillä puhelimesi internetyhteyden kautta. ℹ️ Huomautus: MQTT-välitys toimii vain mobiilisovelluksessa. Työpöytäsovelluksessa MQTT-asetukset ovat käytettävissä, mutta niiden taustalla ei ole välityspalvelua. MQTT-asetusten yläreunassa oleva MQTT-välityspalvelin tällä puhelimella -kytkin näyttää, onko tämä välitys käytössä, ja sen avulla voit pysäyttää sen (tai käynnistää sen uudelleen) heti ilman, että radion MQTT-asetuksia tarvitsee muokata tai tallentaa uudelleen. Oletus Meshtastic-välityspalvelin . Yhteisö ylläpitää julkista välityspalvelinta osoitteessa mqtt.meshtastic.org. Tämä on tarkoitettu yleiseen käyttöön ja testaukseen. When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 Tietosuoja: Julkisen välityspalvelimen viestit ovat kaikkien tilaajien luettavissa. Käytä aina kanavasalausta yksityiseen viestintään. Oma välityspalvelin . Parempaa yksityisyyttä ja hallintaa varten voit käyttää omaa MQTT-välityspalvelinta: . | Mosquitto (kevyt, avoimen lähdekoodin) | HiveMQ | EMQX | . Määritä radiosi osoittamaan omaan välityspalvelimeesi oikeilla tunnistetiedoilla. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/mqtt.html#asetukset",
    
    "relUrl": "/fi-rFI/user/mqtt.html#asetukset"
  },"2890": {
    "doc": "MQTT",
    "title": "Karttaraportointi",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/mqtt.html#karttaraportointi",
    
    "relUrl": "/fi-rFI/user/mqtt.html#karttaraportointi"
  },"2891": {
    "doc": "MQTT",
    "title": "Lähetys vs vastaanotto",
    "content": "| Suunta | Kuvaus | . | Lähetys | Viestit mesh-verkosta → MQTT-välityspalvelimeen | . | Vastaanotto | Viestit MQTT-välityspalvelimesta → mesh-verkkoon | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/mqtt.html#l%C3%A4hetys-vs-vastaanotto",
    
    "relUrl": "/fi-rFI/user/mqtt.html#lähetys-vs-vastaanotto"
  },"2892": {
    "doc": "MQTT",
    "title": "Viestiformaatit",
    "content": "MQTT käyttää kahta viestisisällön muotoa: . | Muoto | Kuvaus | Käyttötarkoitus | . | Protobuf | Binäärinen Meshtastic protobuf -enkoodaus | Radioiden välinen mesh-siltaus | . | JSON | Ihmisen luettavissa oleva JSON /2/json/-aiheessa | Mesh-verkon ulkopuolisille sovelluksille (hallintapaneelit, kotiautomaatio) | . ℹ️ Huomautus: json_enabled on merkitty protobuf-rakenteessa vanhentuneeksi, mutta sitä ei ole korvattu eikä sitä ohiteta. Kun tämä on käytössä, sovelluksen oma MQTT-välityspalvelin tilaa /2/json/-aiheen ja purkaa sen viestisisällöt. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/mqtt.html#viestiformaatit",
    
    "relUrl": "/fi-rFI/user/mqtt.html#viestiformaatit"
  },"2893": {
    "doc": "MQTT",
    "title": "Salaus ja yksityisyys",
    "content": "Kerrostetun salausmallin ymmärtäminen: . | Kanavasalaus tapahtuu meshissä ennen MQTT:tä. Jos kanavallasi on PSK, MQTT-viestisisältö on jo salattu — välityspalvelin ja tilaajat näkevät vain salatun datan. | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS salaa TCP-yhteyden itse välityspalvelimeen estäen verkkotason salakuuntelun. | . 🔒 Tietoturva: Oletusjulkisella kanavalla on tunnettu avain. Oletuskanavan MQTT:n kautta lähetetyt viestit ovat käytännössä salaamattomia — kuka tahansa tilaaja voi purkaa ne. Käytä aina omaa PSK-avainta yksityiseen viestintään. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/mqtt.html#salaus-ja-yksityisyys",
    
    "relUrl": "/fi-rFI/user/mqtt.html#salaus-ja-yksityisyys"
  },"2894": {
    "doc": "MQTT",
    "title": "Parhaat käytännöt",
    "content": ". | Käytä kanavatasoista salausta (PSK) kanavissa, jotka yhdistetään MQTT:hen | Älä ota MQTT:tä käyttöön radioissa, joilla ei ole internetyhteyttä (radio puskuroi lähettämättä jääneet viestit ja tuhlaa muistia) | Käytä yksityistä välityspalvelinta arkaluonteisissa käyttöönotossa | Ole tarkkana lähetysajan (downlink) käyttämisessä ruuhkaisissa MQTT-aiheissa — jokainen viesti kuluttaa radio-aikaa paikallisessa meshissä | Harkitse lähetyssuunnan vaihtamista (uplink), jos haluat vain seurata verkkoa etänä ilman viestien lähettämistä verkkoon | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/mqtt.html#parhaat-k%C3%A4yt%C3%A4nn%C3%B6t",
    
    "relUrl": "/fi-rFI/user/mqtt.html#parhaat-käytännöt"
  },"2895": {
    "doc": "MQTT",
    "title": "Vianetsintä",
    "content": "MQTT ei yhdistä . | Tarkista WiFi — yhdyskäytäväradiolla on oltava toimiva internetyhteys (WiFi tai Ethernet). MQTT ei toimi LoRa-radiolinkin kautta. | Tarkista tunnistetiedot — virheellisillä tunnistetiedoilla useimmat välityspalvelimet epäonnistuvat ilman virheilmoitusta — tarkista erityisesti lopussa olevat välilyönnit. | Palomuuri — portin 1883 (MQTT) tai 8883 (MQTT TLS:n kautta) on oltava saavutettavissa. Joissakin verkoissa sallitaan vain verkkoliikenne (portit 80 ja 443). | DNS-ratkaisu – jos käytät omaa välityspalvelimen isäntänimeä, varmista että laite pystyy ratkaisemaan sen. Kokeile välityspalvelimen IP-osoitetta suoraan. | . Viestit eivät välity . | Tarkista lähetys ja vastaanotto-asetukset – jos vain lähetys on käytössä, viestit kulkevat meshistä MQTT:hen mutta eivät takaisin. Ota vastaanotto käyttöön vastaanottavassa yhdyskäytävän laitteessa. | Kanava ei täsmää – molempien gateway-laitteiden täytyy käyttää samaa kanavaa ja samaa PSK-avainta. Eroavaisuus tarkoittaa, että viestit on salattu eri avaimilla ja näyttävät roskalta. | Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/mqtt.html#vianetsint%C3%A4",
    
    "relUrl": "/fi-rFI/user/mqtt.html#vianetsintä"
  },"2896": {
    "doc": "MQTT",
    "title": "Aiheeseen liittyvät aiheet",
    "content": ". | Asetukset — Moduulit ja ylläpito — MQTT-moduulin asetusten viite | Viestit ja kanavat — kanavasalaus ja PSK-asetukset | MQTT-integraatio-opas — yksityiskohtainen MQTT-dokumentaatio meshtastic.org -sivustolla | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/mqtt.html#aiheeseen-liittyv%C3%A4t-aiheet",
    
    "relUrl": "/fi-rFI/user/mqtt.html#aiheeseen-liittyvät-aiheet"
  },"2897": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/mqtt.html",
    
    "relUrl": "/is-rIS/user/mqtt.html"
  },"2898": {
    "doc": "MQTT",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/mqtt.html#overview",
    
    "relUrl": "/is-rIS/user/mqtt.html#overview"
  },"2899": {
    "doc": "MQTT",
    "title": "How It Works",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/mqtt.html#how-it-works",
    
    "relUrl": "/is-rIS/user/mqtt.html#how-it-works"
  },"2900": {
    "doc": "MQTT",
    "title": "Configuration",
    "content": "Enabling MQTT . | Navigate to Settings → Module configuration → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Lýsing | Default | . | Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root topic | Base topic for messages | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | Encrypt MQTT payload | Enabled | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | Disabled | . | TLS enabled | Secure connection to broker | Disabled | . | Map reporting | Report position to public map | Disabled | . | Proxy to client enabled | Relay MQTT through the connected phone | Disabled | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. MQTT Proxy on This Phone . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 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. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/mqtt.html#configuration",
    
    "relUrl": "/is-rIS/user/mqtt.html#configuration"
  },"2901": {
    "doc": "MQTT",
    "title": "Map Reporting",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/mqtt.html#map-reporting",
    
    "relUrl": "/is-rIS/user/mqtt.html#map-reporting"
  },"2902": {
    "doc": "MQTT",
    "title": "Uplink vs Downlink",
    "content": "| Direction | Lýsing | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/mqtt.html#uplink-vs-downlink",
    
    "relUrl": "/is-rIS/user/mqtt.html#uplink-vs-downlink"
  },"2903": {
    "doc": "MQTT",
    "title": "Message Formats",
    "content": "MQTT carries two payload formats: . | Format | Lýsing | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/mqtt.html#message-formats",
    
    "relUrl": "/is-rIS/user/mqtt.html#message-formats"
  },"2904": {
    "doc": "MQTT",
    "title": "Encryption & Privacy",
    "content": "Understanding the layered encryption model: . | 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. | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Security: 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. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/mqtt.html#encryption--privacy",
    
    "relUrl": "/is-rIS/user/mqtt.html#encryption--privacy"
  },"2905": {
    "doc": "MQTT",
    "title": "Best Practices",
    "content": ". | Use channel-level encryption (PSK) on channels that bridge to MQTT | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes 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 | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/mqtt.html#best-practices",
    
    "relUrl": "/is-rIS/user/mqtt.html#best-practices"
  },"2906": {
    "doc": "MQTT",
    "title": "Troubleshooting",
    "content": "MQTT Not Connecting . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | 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 — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/mqtt.html#troubleshooting",
    
    "relUrl": "/is-rIS/user/mqtt.html#troubleshooting"
  },"2907": {
    "doc": "MQTT",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — MQTT module configuration reference | Messages & Channels — channel encryption and PSK setup | MQTT integration guide — detailed MQTT documentation on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/mqtt.html#related-topics",
    
    "relUrl": "/is-rIS/user/mqtt.html#related-topics"
  },"2908": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/mqtt.html",
    
    "relUrl": "/lt-rLT/user/mqtt.html"
  },"2909": {
    "doc": "MQTT",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/mqtt.html#overview",
    
    "relUrl": "/lt-rLT/user/mqtt.html#overview"
  },"2910": {
    "doc": "MQTT",
    "title": "How It Works",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/mqtt.html#how-it-works",
    
    "relUrl": "/lt-rLT/user/mqtt.html#how-it-works"
  },"2911": {
    "doc": "MQTT",
    "title": "Configuration",
    "content": "Enabling MQTT . | Navigate to Settings → Module configuration → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Aprašymas | Default | . | Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root topic | Base topic for messages | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | Encrypt MQTT payload | Enabled | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | Disabled | . | TLS enabled | Secure connection to broker | Disabled | . | Map reporting | Report position to public map | Disabled | . | Proxy to client enabled | Relay MQTT through the connected phone | Disabled | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. MQTT Proxy on This Phone . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 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. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/mqtt.html#configuration",
    
    "relUrl": "/lt-rLT/user/mqtt.html#configuration"
  },"2912": {
    "doc": "MQTT",
    "title": "Map Reporting",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/mqtt.html#map-reporting",
    
    "relUrl": "/lt-rLT/user/mqtt.html#map-reporting"
  },"2913": {
    "doc": "MQTT",
    "title": "Uplink vs Downlink",
    "content": "| Direction | Aprašymas | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/mqtt.html#uplink-vs-downlink",
    
    "relUrl": "/lt-rLT/user/mqtt.html#uplink-vs-downlink"
  },"2914": {
    "doc": "MQTT",
    "title": "Message Formats",
    "content": "MQTT carries two payload formats: . | Format | Aprašymas | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/mqtt.html#message-formats",
    
    "relUrl": "/lt-rLT/user/mqtt.html#message-formats"
  },"2915": {
    "doc": "MQTT",
    "title": "Encryption & Privacy",
    "content": "Understanding the layered encryption model: . | 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. | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Security: 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. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/mqtt.html#encryption--privacy",
    
    "relUrl": "/lt-rLT/user/mqtt.html#encryption--privacy"
  },"2916": {
    "doc": "MQTT",
    "title": "Best Practices",
    "content": ". | Use channel-level encryption (PSK) on channels that bridge to MQTT | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes 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 | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/mqtt.html#best-practices",
    
    "relUrl": "/lt-rLT/user/mqtt.html#best-practices"
  },"2917": {
    "doc": "MQTT",
    "title": "Troubleshooting",
    "content": "MQTT Not Connecting . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | 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 — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/mqtt.html#troubleshooting",
    
    "relUrl": "/lt-rLT/user/mqtt.html#troubleshooting"
  },"2918": {
    "doc": "MQTT",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — MQTT module configuration reference | Messages & Channels — channel encryption and PSK setup | MQTT integration guide — detailed MQTT documentation on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/mqtt.html#related-topics",
    
    "relUrl": "/lt-rLT/user/mqtt.html#related-topics"
  },"2919": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/mqtt.html",
    
    "relUrl": "/gl-rES/user/mqtt.html"
  },"2920": {
    "doc": "MQTT",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/mqtt.html#overview",
    
    "relUrl": "/gl-rES/user/mqtt.html#overview"
  },"2921": {
    "doc": "MQTT",
    "title": "How It Works",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/mqtt.html#how-it-works",
    
    "relUrl": "/gl-rES/user/mqtt.html#how-it-works"
  },"2922": {
    "doc": "MQTT",
    "title": "Configuration",
    "content": "Enabling MQTT . | Navigate to Settings → Module configuration → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Descrición | Default | . | Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root topic | Base topic for messages | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | Encrypt MQTT payload | Enabled | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | Disabled | . | TLS enabled | Secure connection to broker | Disabled | . | Map reporting | Report position to public map | Disabled | . | Proxy to client enabled | Relay MQTT through the connected phone | Disabled | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. MQTT Proxy on This Phone . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 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. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/mqtt.html#configuration",
    
    "relUrl": "/gl-rES/user/mqtt.html#configuration"
  },"2923": {
    "doc": "MQTT",
    "title": "Map Reporting",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/mqtt.html#map-reporting",
    
    "relUrl": "/gl-rES/user/mqtt.html#map-reporting"
  },"2924": {
    "doc": "MQTT",
    "title": "Uplink vs Downlink",
    "content": "| Direction | Descrición | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/mqtt.html#uplink-vs-downlink",
    
    "relUrl": "/gl-rES/user/mqtt.html#uplink-vs-downlink"
  },"2925": {
    "doc": "MQTT",
    "title": "Message Formats",
    "content": "MQTT carries two payload formats: . | Format | Descrición | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/mqtt.html#message-formats",
    
    "relUrl": "/gl-rES/user/mqtt.html#message-formats"
  },"2926": {
    "doc": "MQTT",
    "title": "Encryption & Privacy",
    "content": "Understanding the layered encryption model: . | 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. | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Security: 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. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/mqtt.html#encryption--privacy",
    
    "relUrl": "/gl-rES/user/mqtt.html#encryption--privacy"
  },"2927": {
    "doc": "MQTT",
    "title": "Best Practices",
    "content": ". | Use channel-level encryption (PSK) on channels that bridge to MQTT | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes 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 | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/mqtt.html#best-practices",
    
    "relUrl": "/gl-rES/user/mqtt.html#best-practices"
  },"2928": {
    "doc": "MQTT",
    "title": "Troubleshooting",
    "content": "MQTT Not Connecting . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | 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 — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/mqtt.html#troubleshooting",
    
    "relUrl": "/gl-rES/user/mqtt.html#troubleshooting"
  },"2929": {
    "doc": "MQTT",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — MQTT module configuration reference | Messages & Channels — channel encryption and PSK setup | MQTT integration guide — detailed MQTT documentation on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/mqtt.html#related-topics",
    
    "relUrl": "/gl-rES/user/mqtt.html#related-topics"
  },"2930": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT は、Meshtastic のメッシュネットワークをインターネットに橋渡しし、無線の到達範囲を超えた長距離通信を可能にします。 . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/mqtt.html",
    
    "relUrl": "/ja-rJP/user/mqtt.html"
  },"2931": {
    "doc": "MQTT",
    "title": "概要",
    "content": "MQTT モジュールは、ノードを MQTT サーバーに接続し、次のことを可能にします： . | インターネット経由で、物理的に異なるメッシュ上のノードにメッセージを届ける | ホームオートメーションや監視システムとの連携 | ノードの位置を公開の Meshtastic マップに公開する | ログ記録や通知のためのカスタムデータパイプライン | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/mqtt.html#%E6%A6%82%E8%A6%81",
    
    "relUrl": "/ja-rJP/user/mqtt.html#概要"
  },"2932": {
    "doc": "MQTT",
    "title": "仕組み",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. 同じトピックを購読しているリモートのゲートウェイが、それらのメッセージを自分のローカルメッシュに取り込みます。 . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/mqtt.html#%E4%BB%95%E7%B5%84%E3%81%BF",
    
    "relUrl": "/ja-rJP/user/mqtt.html#仕組み"
  },"2933": {
    "doc": "MQTT",
    "title": "設定",
    "content": "MQTT を有効にする . | Navigate to Settings → Module configuration → MQTT. | MQTT モジュールを有効にします。 | サーバーへの接続を設定します： | . | 設定項目 | 説明 | デフォルト | . | Address | MQTT サーバーのホスト名 | mqtt.meshtastic.org | . | Username | サーバーの認証 | meshdev | . | Password | サーバーの認証 | large4cats | . | Root topic | メッセージのベーストピック | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | MQTT ペイロードを暗号化 | 有効 | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | 無効 | . | TLS enabled | サーバーへのセキュアな接続 | 無効 | . | Map reporting | 公開マップに位置を報告 | 無効 | . | Proxy to client enabled | Relay MQTT through the connected phone | 無効 | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. このスマートフォンでの MQTT プロキシ . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. デフォルトの Meshtastic サーバー . コミュニティが mqtt.meshtastic.org で公開サーバーを運用しています。これは一般的な利用やテストを目的としています。 . When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 プライバシー： 公開サーバー上のメッセージは、購読している誰もが読めます。プライベートな通信には、必ずチャンネルの暗号化を使用してください。 . プライベートサーバー . プライバシーと制御を高めるために、独自の MQTT サーバーを運用できます： . | Mosquitto（軽量、オープンソース） | HiveMQ | EMQX | . 適切な認証情報を設定して、ノードがプライベートサーバーに接続するよう構成します。 . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/mqtt.html#%E8%A8%AD%E5%AE%9A",
    
    "relUrl": "/ja-rJP/user/mqtt.html#設定"
  },"2934": {
    "doc": "MQTT",
    "title": "マップ報告",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/mqtt.html#%E3%83%9E%E3%83%83%E3%83%97%E5%A0%B1%E5%91%8A",
    
    "relUrl": "/ja-rJP/user/mqtt.html#マップ報告"
  },"2935": {
    "doc": "MQTT",
    "title": "アップリンクとダウンリンク",
    "content": "| 方向 | 説明 | . | アップリンク | メッシュ → MQTT サーバーへのメッセージ | . | ダウンリンク | MQTT サーバー → メッシュへのメッセージ | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/mqtt.html#%E3%82%A2%E3%83%83%E3%83%97%E3%83%AA%E3%83%B3%E3%82%AF%E3%81%A8%E3%83%80%E3%82%A6%E3%83%B3%E3%83%AA%E3%83%B3%E3%82%AF",
    
    "relUrl": "/ja-rJP/user/mqtt.html#アップリンクとダウンリンク"
  },"2936": {
    "doc": "MQTT",
    "title": "メッセージ形式",
    "content": "MQTT carries two payload formats: . | 形式 | 説明 | 用途 | . | Protobuf | バイナリの Meshtastic protobuf エンコード | ノード間のメッシュ橋渡し | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/mqtt.html#%E3%83%A1%E3%83%83%E3%82%BB%E3%83%BC%E3%82%B8%E5%BD%A2%E5%BC%8F",
    
    "relUrl": "/ja-rJP/user/mqtt.html#メッセージ形式"
  },"2937": {
    "doc": "MQTT",
    "title": "暗号化とプライバシー",
    "content": "階層化された暗号化モデルを理解する： . | チャンネルの暗号化は、MQTT の前にメッシュ上で行われます。チャンネルに PSK が設定されている場合、MQTT ペイロードはすでに暗号化されています。サーバーや購読者には暗号文しか見えません。 | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS はサーバーへの TCP 接続自体を暗号化し、ネットワークレベルの盗聴を防ぎます。 | . 🔒 Security: The default public channel has a well-known key. デフォルトチャンネルで MQTT 経由で送信されるメッセージは、実質的に暗号化されていません。誰でも解読できます。プライベートな通信には、必ずカスタムの PSK を使用してください。 . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/mqtt.html#%E6%9A%97%E5%8F%B7%E5%8C%96%E3%81%A8%E3%83%97%E3%83%A9%E3%82%A4%E3%83%90%E3%82%B7%E3%83%BC",
    
    "relUrl": "/ja-rJP/user/mqtt.html#暗号化とプライバシー"
  },"2938": {
    "doc": "MQTT",
    "title": "ベストプラクティス",
    "content": ". | MQTT に橋渡しするチャンネルでは、チャンネルレベルの暗号化（PSK）を使用します | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory) | 機密性の高い運用にはプライベートサーバーを使用します | 混雑した MQTT トピックからメッセージをダウンリンクする際は、電波利用時間に注意してください。ダウンリンクされたメッセージはすべて、ローカルメッシュの無線の電波利用時間を消費します | メッセージを送り返さず、リモートでメッシュを監視するだけでよい場合は、アップリンクのみを有効にすることを検討してください | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/mqtt.html#%E3%83%99%E3%82%B9%E3%83%88%E3%83%97%E3%83%A9%E3%82%AF%E3%83%86%E3%82%A3%E3%82%B9",
    
    "relUrl": "/ja-rJP/user/mqtt.html#ベストプラクティス"
  },"2939": {
    "doc": "MQTT",
    "title": "トラブルシューティング",
    "content": "MQTT が接続できない . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT は LoRa の無線リンク自体では動作しません。 | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | DNS 解決： カスタムのサーバーホスト名を使う場合は、ノードがそれを解決できるか確認してください。サーバーの IP アドレスを直接試してみてください。 | . メッセージが橋渡しされない . | アップリンク／ダウンリンクの設定を確認： アップリンクのみが有効な場合、メッセージはメッシュから MQTT へ流れますが、戻ってきません。受信側のゲートウェイでダウンリンクを有効にしてください。 | チャンネルの不一致： 両方のゲートウェイが、同じ PSK を持つ同じチャンネルを共有している必要があります。不一致の場合、メッセージは異なる鍵で暗号化され、判読できないデータとして表示されます。 | Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/mqtt.html#%E3%83%88%E3%83%A9%E3%83%96%E3%83%AB%E3%82%B7%E3%83%A5%E3%83%BC%E3%83%86%E3%82%A3%E3%83%B3%E3%82%B0",
    
    "relUrl": "/ja-rJP/user/mqtt.html#トラブルシューティング"
  },"2940": {
    "doc": "MQTT",
    "title": "関連トピック",
    "content": ". | 設定：モジュールと管理：MQTT モジュールの設定リファレンス | メッセージとチャンネル：チャンネルの暗号化と PSK の設定 | MQTT 連携ガイド：meshtastic.org にある詳細な MQTT ドキュメント | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/mqtt.html#%E9%96%A2%E9%80%A3%E3%83%88%E3%83%94%E3%83%83%E3%82%AF",
    
    "relUrl": "/ja-rJP/user/mqtt.html#関連トピック"
  },"2941": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/mqtt.html",
    
    "relUrl": "/de-rDE/user/mqtt.html"
  },"2942": {
    "doc": "MQTT",
    "title": "Übersicht",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/mqtt.html#%C3%BCbersicht",
    
    "relUrl": "/de-rDE/user/mqtt.html#übersicht"
  },"2943": {
    "doc": "MQTT",
    "title": "So funktioniert’s",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/mqtt.html#so-funktionierts",
    
    "relUrl": "/de-rDE/user/mqtt.html#so-funktionierts"
  },"2944": {
    "doc": "MQTT",
    "title": "Einstellungen",
    "content": "MQTT aktivieren . | Navigate to Settings → Module configuration → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Einstellung | Beschreibung | Standardwert | . | Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root topic | Base topic for messages | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | Encrypt MQTT payload | Aktiviert | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | Deaktiviert | . | TLS enabled | Secure connection to broker | Deaktiviert | . | Map reporting | Report position to public map | Deaktiviert | . | Proxy to client enabled | Relay MQTT through the connected phone | Deaktiviert | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. MQTT Proxy on This Phone . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 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. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/mqtt.html#einstellungen",
    
    "relUrl": "/de-rDE/user/mqtt.html#einstellungen"
  },"2945": {
    "doc": "MQTT",
    "title": "Map Reporting",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/mqtt.html#map-reporting",
    
    "relUrl": "/de-rDE/user/mqtt.html#map-reporting"
  },"2946": {
    "doc": "MQTT",
    "title": "Uplink vs Downlink",
    "content": "| Direction | Beschreibung | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/mqtt.html#uplink-vs-downlink",
    
    "relUrl": "/de-rDE/user/mqtt.html#uplink-vs-downlink"
  },"2947": {
    "doc": "MQTT",
    "title": "Message Formats",
    "content": "MQTT carries two payload formats: . | Format | Beschreibung | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/mqtt.html#message-formats",
    
    "relUrl": "/de-rDE/user/mqtt.html#message-formats"
  },"2948": {
    "doc": "MQTT",
    "title": "Encryption & Privacy",
    "content": "Understanding the layered encryption model: . | 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. | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Security: 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. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/mqtt.html#encryption--privacy",
    
    "relUrl": "/de-rDE/user/mqtt.html#encryption--privacy"
  },"2949": {
    "doc": "MQTT",
    "title": "Bewährte Praktiken",
    "content": ". | Use channel-level encryption (PSK) on channels that bridge to MQTT | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes 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 | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/mqtt.html#bew%C3%A4hrte-praktiken",
    
    "relUrl": "/de-rDE/user/mqtt.html#bewährte-praktiken"
  },"2950": {
    "doc": "MQTT",
    "title": "Fehlerbehebung",
    "content": "MQTT Not Connecting . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | 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 — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/mqtt.html#fehlerbehebung",
    
    "relUrl": "/de-rDE/user/mqtt.html#fehlerbehebung"
  },"2951": {
    "doc": "MQTT",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — MQTT module configuration reference | Messages & Channels — channel encryption and PSK setup | MQTT integration guide — detailed MQTT documentation on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/mqtt.html#related-topics",
    
    "relUrl": "/de-rDE/user/mqtt.html#related-topics"
  },"2952": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/mqtt.html",
    
    "relUrl": "/ar-rSA/user/mqtt.html"
  },"2953": {
    "doc": "MQTT",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/mqtt.html#overview",
    
    "relUrl": "/ar-rSA/user/mqtt.html#overview"
  },"2954": {
    "doc": "MQTT",
    "title": "How It Works",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/mqtt.html#how-it-works",
    
    "relUrl": "/ar-rSA/user/mqtt.html#how-it-works"
  },"2955": {
    "doc": "MQTT",
    "title": "Configuration",
    "content": "Enabling MQTT . | Navigate to Settings → Module configuration → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | الوصف | Default | . | Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root topic | Base topic for messages | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | Encrypt MQTT payload | Enabled | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | Disabled | . | TLS enabled | Secure connection to broker | Disabled | . | Map reporting | Report position to public map | Disabled | . | Proxy to client enabled | Relay MQTT through the connected phone | Disabled | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. MQTT Proxy on This Phone . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 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. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/mqtt.html#configuration",
    
    "relUrl": "/ar-rSA/user/mqtt.html#configuration"
  },"2956": {
    "doc": "MQTT",
    "title": "Map Reporting",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/mqtt.html#map-reporting",
    
    "relUrl": "/ar-rSA/user/mqtt.html#map-reporting"
  },"2957": {
    "doc": "MQTT",
    "title": "Uplink vs Downlink",
    "content": "| Direction | الوصف | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/mqtt.html#uplink-vs-downlink",
    
    "relUrl": "/ar-rSA/user/mqtt.html#uplink-vs-downlink"
  },"2958": {
    "doc": "MQTT",
    "title": "Message Formats",
    "content": "MQTT carries two payload formats: . | Format | الوصف | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/mqtt.html#message-formats",
    
    "relUrl": "/ar-rSA/user/mqtt.html#message-formats"
  },"2959": {
    "doc": "MQTT",
    "title": "Encryption & Privacy",
    "content": "Understanding the layered encryption model: . | 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. | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Security: 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. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/mqtt.html#encryption--privacy",
    
    "relUrl": "/ar-rSA/user/mqtt.html#encryption--privacy"
  },"2960": {
    "doc": "MQTT",
    "title": "Best Practices",
    "content": ". | Use channel-level encryption (PSK) on channels that bridge to MQTT | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes 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 | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/mqtt.html#best-practices",
    
    "relUrl": "/ar-rSA/user/mqtt.html#best-practices"
  },"2961": {
    "doc": "MQTT",
    "title": "Troubleshooting",
    "content": "MQTT Not Connecting . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | 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 — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/mqtt.html#troubleshooting",
    
    "relUrl": "/ar-rSA/user/mqtt.html#troubleshooting"
  },"2962": {
    "doc": "MQTT",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — MQTT module configuration reference | Messages & Channels — channel encryption and PSK setup | MQTT integration guide — detailed MQTT documentation on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/mqtt.html#related-topics",
    
    "relUrl": "/ar-rSA/user/mqtt.html#related-topics"
  },"2963": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/mqtt.html",
    
    "relUrl": "/hr-rHR/user/mqtt.html"
  },"2964": {
    "doc": "MQTT",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/mqtt.html#overview",
    
    "relUrl": "/hr-rHR/user/mqtt.html#overview"
  },"2965": {
    "doc": "MQTT",
    "title": "How It Works",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/mqtt.html#how-it-works",
    
    "relUrl": "/hr-rHR/user/mqtt.html#how-it-works"
  },"2966": {
    "doc": "MQTT",
    "title": "Configuration",
    "content": "Enabling MQTT . | Navigate to Settings → Module configuration → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Opis | Zadano | . | Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root topic | Base topic for messages | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | Encrypt MQTT payload | Enabled | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | Disabled | . | TLS enabled | Secure connection to broker | Disabled | . | Map reporting | Report position to public map | Disabled | . | Proxy to client enabled | Relay MQTT through the connected phone | Disabled | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. MQTT Proxy on This Phone . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 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. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/mqtt.html#configuration",
    
    "relUrl": "/hr-rHR/user/mqtt.html#configuration"
  },"2967": {
    "doc": "MQTT",
    "title": "Map Reporting",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/mqtt.html#map-reporting",
    
    "relUrl": "/hr-rHR/user/mqtt.html#map-reporting"
  },"2968": {
    "doc": "MQTT",
    "title": "Uplink vs Downlink",
    "content": "| Direction | Opis | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/mqtt.html#uplink-vs-downlink",
    
    "relUrl": "/hr-rHR/user/mqtt.html#uplink-vs-downlink"
  },"2969": {
    "doc": "MQTT",
    "title": "Message Formats",
    "content": "MQTT carries two payload formats: . | Format | Opis | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/mqtt.html#message-formats",
    
    "relUrl": "/hr-rHR/user/mqtt.html#message-formats"
  },"2970": {
    "doc": "MQTT",
    "title": "Encryption & Privacy",
    "content": "Understanding the layered encryption model: . | 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. | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Security: 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. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/mqtt.html#encryption--privacy",
    
    "relUrl": "/hr-rHR/user/mqtt.html#encryption--privacy"
  },"2971": {
    "doc": "MQTT",
    "title": "Best Practices",
    "content": ". | Use channel-level encryption (PSK) on channels that bridge to MQTT | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes 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 | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/mqtt.html#best-practices",
    
    "relUrl": "/hr-rHR/user/mqtt.html#best-practices"
  },"2972": {
    "doc": "MQTT",
    "title": "Troubleshooting",
    "content": "MQTT Not Connecting . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | 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 — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/mqtt.html#troubleshooting",
    
    "relUrl": "/hr-rHR/user/mqtt.html#troubleshooting"
  },"2973": {
    "doc": "MQTT",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — MQTT module configuration reference | Messages & Channels — channel encryption and PSK setup | MQTT integration guide — detailed MQTT documentation on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/mqtt.html#related-topics",
    
    "relUrl": "/hr-rHR/user/mqtt.html#related-topics"
  },"2974": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/mqtt.html",
    
    "relUrl": "/pt-rPT/user/mqtt.html"
  },"2975": {
    "doc": "MQTT",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/mqtt.html#overview",
    
    "relUrl": "/pt-rPT/user/mqtt.html#overview"
  },"2976": {
    "doc": "MQTT",
    "title": "How It Works",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/mqtt.html#how-it-works",
    
    "relUrl": "/pt-rPT/user/mqtt.html#how-it-works"
  },"2977": {
    "doc": "MQTT",
    "title": "Configuração",
    "content": "Enabling MQTT . | Navigate to Settings → Module configuration → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Descrição | Predefinição | . | Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root topic | Base topic for messages | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | Encrypt MQTT payload | Enabled | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | Disabled | . | TLS enabled | Secure connection to broker | Disabled | . | Map reporting | Report position to public map | Disabled | . | Proxy to client enabled | Relay MQTT through the connected phone | Disabled | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. MQTT Proxy on This Phone . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 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. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/mqtt.html#configura%C3%A7%C3%A3o",
    
    "relUrl": "/pt-rPT/user/mqtt.html#configuração"
  },"2978": {
    "doc": "MQTT",
    "title": "Map Reporting",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/mqtt.html#map-reporting",
    
    "relUrl": "/pt-rPT/user/mqtt.html#map-reporting"
  },"2979": {
    "doc": "MQTT",
    "title": "Uplink vs Downlink",
    "content": "| Direction | Descrição | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/mqtt.html#uplink-vs-downlink",
    
    "relUrl": "/pt-rPT/user/mqtt.html#uplink-vs-downlink"
  },"2980": {
    "doc": "MQTT",
    "title": "Message Formats",
    "content": "MQTT carries two payload formats: . | Format | Descrição | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/mqtt.html#message-formats",
    
    "relUrl": "/pt-rPT/user/mqtt.html#message-formats"
  },"2981": {
    "doc": "MQTT",
    "title": "Encryption & Privacy",
    "content": "Understanding the layered encryption model: . | 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. | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Security: 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. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/mqtt.html#encryption--privacy",
    
    "relUrl": "/pt-rPT/user/mqtt.html#encryption--privacy"
  },"2982": {
    "doc": "MQTT",
    "title": "Best Practices",
    "content": ". | Use channel-level encryption (PSK) on channels that bridge to MQTT | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes 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 | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/mqtt.html#best-practices",
    
    "relUrl": "/pt-rPT/user/mqtt.html#best-practices"
  },"2983": {
    "doc": "MQTT",
    "title": "Troubleshooting",
    "content": "MQTT Not Connecting . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | 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 — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/mqtt.html#troubleshooting",
    
    "relUrl": "/pt-rPT/user/mqtt.html#troubleshooting"
  },"2984": {
    "doc": "MQTT",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — MQTT module configuration reference | Messages & Channels — channel encryption and PSK setup | MQTT integration guide — detailed MQTT documentation on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/mqtt.html#related-topics",
    
    "relUrl": "/pt-rPT/user/mqtt.html#related-topics"
  },"2985": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/mqtt.html",
    
    "relUrl": "/pl-rPL/user/mqtt.html"
  },"2986": {
    "doc": "MQTT",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/mqtt.html#overview",
    
    "relUrl": "/pl-rPL/user/mqtt.html#overview"
  },"2987": {
    "doc": "MQTT",
    "title": "How It Works",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/mqtt.html#how-it-works",
    
    "relUrl": "/pl-rPL/user/mqtt.html#how-it-works"
  },"2988": {
    "doc": "MQTT",
    "title": "Konfiguracja",
    "content": "Enabling MQTT . | Navigate to Settings → Module configuration → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Opis | Domyślny | . | Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root topic | Base topic for messages | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | Encrypt MQTT payload | Włączony | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | Wyłączony | . | TLS enabled | Secure connection to broker | Wyłączony | . | Map reporting | Report position to public map | Wyłączony | . | Proxy to client enabled | Relay MQTT through the connected phone | Wyłączony | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. MQTT Proxy on This Phone . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 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. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/mqtt.html#konfiguracja",
    
    "relUrl": "/pl-rPL/user/mqtt.html#konfiguracja"
  },"2989": {
    "doc": "MQTT",
    "title": "Map Reporting",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/mqtt.html#map-reporting",
    
    "relUrl": "/pl-rPL/user/mqtt.html#map-reporting"
  },"2990": {
    "doc": "MQTT",
    "title": "Uplink vs Downlink",
    "content": "| Direction | Opis | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/mqtt.html#uplink-vs-downlink",
    
    "relUrl": "/pl-rPL/user/mqtt.html#uplink-vs-downlink"
  },"2991": {
    "doc": "MQTT",
    "title": "Message Formats",
    "content": "MQTT carries two payload formats: . | Format | Opis | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/mqtt.html#message-formats",
    
    "relUrl": "/pl-rPL/user/mqtt.html#message-formats"
  },"2992": {
    "doc": "MQTT",
    "title": "Encryption & Privacy",
    "content": "Understanding the layered encryption model: . | 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. | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Security: 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. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/mqtt.html#encryption--privacy",
    
    "relUrl": "/pl-rPL/user/mqtt.html#encryption--privacy"
  },"2993": {
    "doc": "MQTT",
    "title": "Best Practices",
    "content": ". | Use channel-level encryption (PSK) on channels that bridge to MQTT | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes 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 | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/mqtt.html#best-practices",
    
    "relUrl": "/pl-rPL/user/mqtt.html#best-practices"
  },"2994": {
    "doc": "MQTT",
    "title": "Troubleshooting",
    "content": "MQTT Not Connecting . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | 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 — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/mqtt.html#troubleshooting",
    
    "relUrl": "/pl-rPL/user/mqtt.html#troubleshooting"
  },"2995": {
    "doc": "MQTT",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — MQTT module configuration reference | Messages & Channels — channel encryption and PSK setup | MQTT integration guide — detailed MQTT documentation on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/mqtt.html#related-topics",
    
    "relUrl": "/pl-rPL/user/mqtt.html#related-topics"
  },"2996": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/mqtt.html",
    
    "relUrl": "/zh-rCN/user/mqtt.html"
  },"2997": {
    "doc": "MQTT",
    "title": "总览",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/mqtt.html#%E6%80%BB%E8%A7%88",
    
    "relUrl": "/zh-rCN/user/mqtt.html#总览"
  },"2998": {
    "doc": "MQTT",
    "title": "How It Works",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/mqtt.html#how-it-works",
    
    "relUrl": "/zh-rCN/user/mqtt.html#how-it-works"
  },"2999": {
    "doc": "MQTT",
    "title": "Configuration",
    "content": "Enabling MQTT . | Navigate to Settings → Module configuration → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | 说明 | 默认 | . | Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root topic | Base topic for messages | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | Encrypt MQTT payload | Enabled | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | 禁用 | . | TLS enabled | Secure connection to broker | 禁用 | . | Map reporting | Report position to public map | 禁用 | . | Proxy to client enabled | Relay MQTT through the connected phone | 禁用 | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. MQTT Proxy on This Phone . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 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. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/mqtt.html#configuration",
    
    "relUrl": "/zh-rCN/user/mqtt.html#configuration"
  },"3000": {
    "doc": "MQTT",
    "title": "Map Reporting",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/mqtt.html#map-reporting",
    
    "relUrl": "/zh-rCN/user/mqtt.html#map-reporting"
  },"3001": {
    "doc": "MQTT",
    "title": "Uplink vs Downlink",
    "content": "| Direction | 说明 | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/mqtt.html#uplink-vs-downlink",
    
    "relUrl": "/zh-rCN/user/mqtt.html#uplink-vs-downlink"
  },"3002": {
    "doc": "MQTT",
    "title": "Message Formats",
    "content": "MQTT carries two payload formats: . | Format | 说明 | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/mqtt.html#message-formats",
    
    "relUrl": "/zh-rCN/user/mqtt.html#message-formats"
  },"3003": {
    "doc": "MQTT",
    "title": "Encryption & Privacy",
    "content": "Understanding the layered encryption model: . | 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. | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Security: 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. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/mqtt.html#encryption--privacy",
    
    "relUrl": "/zh-rCN/user/mqtt.html#encryption--privacy"
  },"3004": {
    "doc": "MQTT",
    "title": "Best Practices",
    "content": ". | Use channel-level encryption (PSK) on channels that bridge to MQTT | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes 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 | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/mqtt.html#best-practices",
    
    "relUrl": "/zh-rCN/user/mqtt.html#best-practices"
  },"3005": {
    "doc": "MQTT",
    "title": "问题排查",
    "content": "MQTT Not Connecting . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | 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 — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/mqtt.html#%E9%97%AE%E9%A2%98%E6%8E%92%E6%9F%A5",
    
    "relUrl": "/zh-rCN/user/mqtt.html#问题排查"
  },"3006": {
    "doc": "MQTT",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — MQTT module configuration reference | Messages & Channels — channel encryption and PSK setup | MQTT integration guide — detailed MQTT documentation on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/mqtt.html#related-topics",
    
    "relUrl": "/zh-rCN/user/mqtt.html#related-topics"
  },"3007": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/mqtt.html",
    
    "relUrl": "/sq-rAL/user/mqtt.html"
  },"3008": {
    "doc": "MQTT",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/mqtt.html#overview",
    
    "relUrl": "/sq-rAL/user/mqtt.html#overview"
  },"3009": {
    "doc": "MQTT",
    "title": "How It Works",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/mqtt.html#how-it-works",
    
    "relUrl": "/sq-rAL/user/mqtt.html#how-it-works"
  },"3010": {
    "doc": "MQTT",
    "title": "Configuration",
    "content": "Enabling MQTT . | Navigate to Settings → Module configuration → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Përshkrimi | Default | . | Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root topic | Base topic for messages | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | Encrypt MQTT payload | Enabled | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | Disabled | . | TLS enabled | Secure connection to broker | Disabled | . | Map reporting | Report position to public map | Disabled | . | Proxy to client enabled | Relay MQTT through the connected phone | Disabled | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. MQTT Proxy on This Phone . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 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. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/mqtt.html#configuration",
    
    "relUrl": "/sq-rAL/user/mqtt.html#configuration"
  },"3011": {
    "doc": "MQTT",
    "title": "Map Reporting",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/mqtt.html#map-reporting",
    
    "relUrl": "/sq-rAL/user/mqtt.html#map-reporting"
  },"3012": {
    "doc": "MQTT",
    "title": "Uplink vs Downlink",
    "content": "| Direction | Përshkrimi | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/mqtt.html#uplink-vs-downlink",
    
    "relUrl": "/sq-rAL/user/mqtt.html#uplink-vs-downlink"
  },"3013": {
    "doc": "MQTT",
    "title": "Message Formats",
    "content": "MQTT carries two payload formats: . | Format | Përshkrimi | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/mqtt.html#message-formats",
    
    "relUrl": "/sq-rAL/user/mqtt.html#message-formats"
  },"3014": {
    "doc": "MQTT",
    "title": "Encryption & Privacy",
    "content": "Understanding the layered encryption model: . | 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. | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Security: 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. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/mqtt.html#encryption--privacy",
    
    "relUrl": "/sq-rAL/user/mqtt.html#encryption--privacy"
  },"3015": {
    "doc": "MQTT",
    "title": "Best Practices",
    "content": ". | Use channel-level encryption (PSK) on channels that bridge to MQTT | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes 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 | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/mqtt.html#best-practices",
    
    "relUrl": "/sq-rAL/user/mqtt.html#best-practices"
  },"3016": {
    "doc": "MQTT",
    "title": "Troubleshooting",
    "content": "MQTT Not Connecting . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | 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 — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/mqtt.html#troubleshooting",
    
    "relUrl": "/sq-rAL/user/mqtt.html#troubleshooting"
  },"3017": {
    "doc": "MQTT",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — MQTT module configuration reference | Messages & Channels — channel encryption and PSK setup | MQTT integration guide — detailed MQTT documentation on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/mqtt.html#related-topics",
    
    "relUrl": "/sq-rAL/user/mqtt.html#related-topics"
  },"3018": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT 將您的 Meshtastic mesh 網路橋接至網際網路，實現超越無線電範圍的長距離通訊。 . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/mqtt.html",
    
    "relUrl": "/zh-rTW/user/mqtt.html"
  },"3019": {
    "doc": "MQTT",
    "title": "概觀",
    "content": "MQTT 模組可將您的節點連接至 MQTT 代理伺服器，實現以下功能： . | 透過網際網路傳送訊息至不同實體 mesh 網路上的節點 | 與智慧家庭自動化及監控系統整合 | 將節點位置發布至公開的 Meshtastic 地圖 | 自訂資料管線，用於記錄與警示通知 | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/mqtt.html#%E6%A6%82%E8%A7%80",
    
    "relUrl": "/zh-rTW/user/mqtt.html#概觀"
  },"3020": {
    "doc": "MQTT",
    "title": "運作方式",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. 訂閱相同主題的遠端閘道，將這些訊息注入其本地 mesh 網路。 . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/mqtt.html#%E9%81%8B%E4%BD%9C%E6%96%B9%E5%BC%8F",
    
    "relUrl": "/zh-rTW/user/mqtt.html#運作方式"
  },"3021": {
    "doc": "MQTT",
    "title": "設定",
    "content": "啟用 MQTT . | Navigate to Settings → Module configuration → MQTT. | 啟用 MQTT 模組。 | 設定代理伺服器連線： | . | 設定 | 描述說明 | 默認 | . | Address | MQTT 代理伺服器主機名稱 | mqtt.meshtastic.org | . | Username | 代理伺服器驗證 | meshdev | . | Password | 代理伺服器驗證 | large4cats | . | Root topic | 訊息的基礎主題 | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | 加密 MQTT 承載內容 | 已啟用 | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | 已停用 | . | TLS enabled | 與代理伺服器的安全連線 | 已停用 | . | Map reporting | 將位置回報至公開地圖 | 已停用 | . | Proxy to client enabled | Relay MQTT through the connected phone | 已停用 | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. MQTT Proxy on This Phone . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. 預設 Meshtastic 代理伺服器 . 社群在 mqtt.meshtastic.org 維護一個公開的代理伺服器。此伺服器供一般使用與測試之用。 . When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 隱私：公開代理伺服器上的訊息，任何訂閱者均可讀取。私人通訊請務必啟用頻道加密。 . 私有代理伺服器 . 為了獲得更好的隱私保護與控制權，您可以自行架設 MQTT 代理伺服器： . | Mosquitto（輕量、開放原始碼） | HiveMQ | EMQX | . 請將您的節點設定為指向私有代理伺服器，並輸入相應的登入憑證。 . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/mqtt.html#%E8%A8%AD%E5%AE%9A",
    
    "relUrl": "/zh-rTW/user/mqtt.html#設定"
  },"3022": {
    "doc": "MQTT",
    "title": "地圖回報",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/mqtt.html#%E5%9C%B0%E5%9C%96%E5%9B%9E%E5%A0%B1",
    
    "relUrl": "/zh-rTW/user/mqtt.html#地圖回報"
  },"3023": {
    "doc": "MQTT",
    "title": "上行 vs 下行",
    "content": "| 方向 | 描述說明 | . | 上行 | 訊息從 mesh 網路 → MQTT 代理伺服器 | . | 下行 | 訊息從 MQTT 代理伺服器 → mesh 網路 | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/mqtt.html#%E4%B8%8A%E8%A1%8C-vs-%E4%B8%8B%E8%A1%8C",
    
    "relUrl": "/zh-rTW/user/mqtt.html#上行-vs-下行"
  },"3024": {
    "doc": "MQTT",
    "title": "訊息格式",
    "content": "MQTT carries two payload formats: . | 格式 | 描述說明 | 使用情境 | . | Protobuf | 二進位 Meshtastic protobuf 編碼 | 節點間 mesh 橋接 | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/mqtt.html#%E8%A8%8A%E6%81%AF%E6%A0%BC%E5%BC%8F",
    
    "relUrl": "/zh-rTW/user/mqtt.html#訊息格式"
  },"3025": {
    "doc": "MQTT",
    "title": "加密與隱私",
    "content": "了解分層加密模型： . | 頻道加密在 mesh 網路上進行，發生於 MQTT 傳輸之前。若您的頻道已設定 PSK，MQTT 承載內容將已加密——代理伺服器及任何訂閱者只能看到密文。 | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS 對連接至代理伺服器的 TCP 連線進行加密，防止網路層級的竊聽。 | . 🔒 Security: The default public channel has a well-known key. 透過 MQTT 傳送的預設頻道訊息實際上等同於未加密 — 任何人均可解碼。私人通訊請務必使用自訂 PSK。 . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/mqtt.html#%E5%8A%A0%E5%AF%86%E8%88%87%E9%9A%B1%E7%A7%81",
    
    "relUrl": "/zh-rTW/user/mqtt.html#加密與隱私"
  },"3026": {
    "doc": "MQTT",
    "title": "最佳實踐",
    "content": ". | 在橋接至 MQTT 的頻道上使用頻道層級加密（PSK） | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory) | 敏感部署環境請使用私有代理伺服器 | 從繁忙的 MQTT 主題下行訊息時，請留意無線電佔用時間——每則下行訊息都會消耗本地 mesh 網路的無線電佔用時間 | 若僅需遠端監控 mesh 網路而不需注入訊息，建議僅啟用上行模式 | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/mqtt.html#%E6%9C%80%E4%BD%B3%E5%AF%A6%E8%B8%90",
    
    "relUrl": "/zh-rTW/user/mqtt.html#最佳實踐"
  },"3027": {
    "doc": "MQTT",
    "title": "故障排除",
    "content": "MQTT 無法連線 . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT 無法直接透過 LoRa 無線電連結運作。 | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | DNS 解析 — 若使用自訂代理伺服器主機名稱，請確認節點能夠正確解析該名稱。請嘗試直接使用代理伺服器的 IP 位址進行連線。 | . 訊息未正常橋接 . | 檢查上行／下行設定 — 若僅啟用上行，訊息只會從 mesh 網路流向 MQTT，不會反向傳送。請在接收端閘道上啟用下行功能。 | 頻道不符 — 兩個閘道必須使用相同頻道且具備相同的 PSK。不符時，訊息將以不同金鑰加密，導致對方收到的內容為亂碼。 | Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/mqtt.html#%E6%95%85%E9%9A%9C%E6%8E%92%E9%99%A4",
    
    "relUrl": "/zh-rTW/user/mqtt.html#故障排除"
  },"3028": {
    "doc": "MQTT",
    "title": "相關主題",
    "content": ". | 〔設定 — 模組與管理〕(settings-module-admin) — MQTT 模組設定參考 | 〔訊息與頻道〕(messages-and-channels) — 頻道加密與 PSK 設定 | 〔MQTT 整合指南〕(https://meshtastic.org/docs/software/integrations/mqtt) — meshtastic.org 上的完整 MQTT 說明文件 | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/mqtt.html#%E7%9B%B8%E9%97%9C%E4%B8%BB%E9%A1%8C",
    
    "relUrl": "/zh-rTW/user/mqtt.html#相關主題"
  },"3029": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT ühendab Meshtastic võrgu internetiga, võimaldades raadiolevi ulatusest kaugemale ulatuvat pikamaasidet. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/mqtt.html",
    
    "relUrl": "/et-rEE/user/mqtt.html"
  },"3030": {
    "doc": "MQTT",
    "title": "Ülevaade",
    "content": "MQTT moodul ühendab sinu sõlme MQTT vahendajaga, võimaldades: . | Sõnumid interneti kaudu erinevate füüsiliste võrkude sõlmedeni jõudmiseks | Integration with home automation and monitoring systems | Sõlmede asukoha avaldamine avalikul Meshtastic kaardil | Custom data pipelines for logging and alerting | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/mqtt.html#%C3%BClevaade",
    
    "relUrl": "/et-rEE/user/mqtt.html#ülevaade"
  },"3031": {
    "doc": "MQTT",
    "title": "Kuidas see toimib",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Sama teemaga liitunud kauglüüsid sisestavad need sõnumid oma kohalikku kärgvõrku. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/mqtt.html#kuidas-see-toimib",
    
    "relUrl": "/et-rEE/user/mqtt.html#kuidas-see-toimib"
  },"3032": {
    "doc": "MQTT",
    "title": "Sätted",
    "content": "Luba MQTT . | Navigate to Settings → Module configuration → MQTT. | Luba MQTT moodul. | Configure the broker connection: | . | Sätted | Kirjeldus | Vaikimisi | . | Address | MQTT vahendaja hostinimi | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root topic | Base topic for messages | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | Krüpteeri MQTT liiklus | Lubatud | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | Keelatud | . | TLS enabled | Secure connection to broker | Keelatud | . | Map reporting | Teavita asukoht avalikul kaardil | Keelatud | . | Proxy to client enabled | Relay MQTT through the connected phone | Keelatud | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. MQTT puhverserver sellel telefonil . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. Meshtastic vaikemaakler . Kogukond haldab avaliku vahendajat aadressil mqtt.meshtastic.org. This is intended for general use and testing. When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 Privaatsus: Avaliku vahendaja sõnumeid saavad lugeda kõik tellijad. Privaatse suhtluse jaoks kasuta alati kanali krüpteerimist. Private Broker . Parema privaatsuse ja kontrolli tagamiseks saad hallata oma MQTT maaklerit: . | Mosquitto (kerge, avatud lähtekoodiga) | HiveMQ | EMQX | . Konfigureeri oma sõlm nii, et see osutaks sinu privaatsele maaklerile sobivate volitustega. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/mqtt.html#s%C3%A4tted",
    
    "relUrl": "/et-rEE/user/mqtt.html#sätted"
  },"3033": {
    "doc": "MQTT",
    "title": "Kaardiaruannete koostamine",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/mqtt.html#kaardiaruannete-koostamine",
    
    "relUrl": "/et-rEE/user/mqtt.html#kaardiaruannete-koostamine"
  },"3034": {
    "doc": "MQTT",
    "title": "Üleslink vs allalink",
    "content": "| Suund | Kirjeldus | . | Üleslink | Sõnumid kärgvõrgust → MQTT maakler | . | Allalink | Sõnumid MQTT maaklerist → kärgvõrk | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/mqtt.html#%C3%BCleslink-vs-allalink",
    
    "relUrl": "/et-rEE/user/mqtt.html#üleslink-vs-allalink"
  },"3035": {
    "doc": "MQTT",
    "title": "Sõnumivormingud",
    "content": "MQTT carries two payload formats: . | Vorming | Kirjeldus | Kasutusjuhtum | . | Protobuf | Binaarne Meshtastic protobuf kodeering | Node-to-node mesh bridging | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/mqtt.html#s%C3%B5numivormingud",
    
    "relUrl": "/et-rEE/user/mqtt.html#sõnumivormingud"
  },"3036": {
    "doc": "MQTT",
    "title": "Encryption & Privacy",
    "content": "Understanding the layered encryption model: . | Kanali krüptimine toimub kärgvõrgus enne MQTT. Kui kanalil on PSK, on ​​MQTT liiklus juba krüptitud – maakler ja kõik tellijad näevad ainult šifriteksti. | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS krüpteerib TCP ühenduse vahendaja endaga, takistades võrgutasandil pealtkuulamist. | . 🔒 Security: The default public channel has a well-known key. MQTT kaudu saadetud vaikekanalil olevad sõnumid on sisuliselt krüpteerimata – igaüks saab neid dekodeerida. Always use a custom PSK for private communications. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/mqtt.html#encryption--privacy",
    
    "relUrl": "/et-rEE/user/mqtt.html#encryption--privacy"
  },"3037": {
    "doc": "MQTT",
    "title": "Parimad tavad",
    "content": ". | Kasuta kanali krüptimist (PSK), kanalitel mis on sillatud MQTT-ga | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes memory) | Use a private broker for sensitive deployments | MQTT sõnumite allalaadimisel arvesta eetriaja kuluga – iga allalingitud sõnum tarbib sinu kohalikus võrgus raadioeetriaega | Kaalu ainult üleslingi lubamist, kui sul on vaja oma kärgvõrku eemalt jälgida ilma sõnumeid tagasi tõmbamata | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/mqtt.html#parimad-tavad",
    
    "relUrl": "/et-rEE/user/mqtt.html#parimad-tavad"
  },"3038": {
    "doc": "MQTT",
    "title": "Veaotsing",
    "content": "MQTT ei ühendu . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT ei tööta LoRa raadiolingi enda kaudu. | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | DNS-i lahendamine – kui kasutad kohandatud maakleri hostinime, veenduge, et sõlm suudab seda lahendada. Try the broker’s IP address directly. | . Messages Not Bridging . | Kontrolli üleslingi/allalingi seadeid — kui lubatud on ainult üleslink, liiguvad sõnumid võrgust MQTT-sse, aga mitte tagasi. Luba vastuvõtval lüüsil allalink. | Kanali mittevastavus – mõlemad lüüsid peavad jagama sama kanalit sama PSK-ga. Vastuolu tähendab, et sõnumid on krüpteeritud erinevate võtmetega ja kuvatakse prügina. | Topic mismatch — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/mqtt.html#veaotsing",
    
    "relUrl": "/et-rEE/user/mqtt.html#veaotsing"
  },"3039": {
    "doc": "MQTT",
    "title": "Seotud teemad",
    "content": ". | Seaded — Moodulid ja administreerimine — MQTT mooduli konfi viide | Sõnumid ja kanalid — kanali krüptimine ja PSK seadistamine | MQTT integratsioonijuhend — üksikasjalik MQTT dokumentatsioon aadressil meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/mqtt.html#seotud-teemad",
    
    "relUrl": "/et-rEE/user/mqtt.html#seotud-teemad"
  },"3040": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/mqtt.html",
    
    "relUrl": "/fr-rFR/user/mqtt.html"
  },"3041": {
    "doc": "MQTT",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/mqtt.html#overview",
    
    "relUrl": "/fr-rFR/user/mqtt.html#overview"
  },"3042": {
    "doc": "MQTT",
    "title": "How It Works",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/mqtt.html#how-it-works",
    
    "relUrl": "/fr-rFR/user/mqtt.html#how-it-works"
  },"3043": {
    "doc": "MQTT",
    "title": "Configuration",
    "content": "Enabling MQTT . | Navigate to Settings → Module configuration → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Description | Par défaut | . | Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root topic | Base topic for messages | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | Encrypt MQTT payload | Activé | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | Désactivé | . | TLS enabled | Secure connection to broker | Désactivé | . | Map reporting | Report position to public map | Désactivé | . | Proxy to client enabled | Relay MQTT through the connected phone | Désactivé | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. MQTT Proxy on This Phone . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 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. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/mqtt.html#configuration",
    
    "relUrl": "/fr-rFR/user/mqtt.html#configuration"
  },"3044": {
    "doc": "MQTT",
    "title": "Map Reporting",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/mqtt.html#map-reporting",
    
    "relUrl": "/fr-rFR/user/mqtt.html#map-reporting"
  },"3045": {
    "doc": "MQTT",
    "title": "Uplink vs Downlink",
    "content": "| Direction | Description | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/mqtt.html#uplink-vs-downlink",
    
    "relUrl": "/fr-rFR/user/mqtt.html#uplink-vs-downlink"
  },"3046": {
    "doc": "MQTT",
    "title": "Message Formats",
    "content": "MQTT carries two payload formats: . | Format | Description | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/mqtt.html#message-formats",
    
    "relUrl": "/fr-rFR/user/mqtt.html#message-formats"
  },"3047": {
    "doc": "MQTT",
    "title": "Encryption & Privacy",
    "content": "Understanding the layered encryption model: . | 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. | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Security: 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. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/mqtt.html#encryption--privacy",
    
    "relUrl": "/fr-rFR/user/mqtt.html#encryption--privacy"
  },"3048": {
    "doc": "MQTT",
    "title": "Best Practices",
    "content": ". | Use channel-level encryption (PSK) on channels that bridge to MQTT | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes 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 | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/mqtt.html#best-practices",
    
    "relUrl": "/fr-rFR/user/mqtt.html#best-practices"
  },"3049": {
    "doc": "MQTT",
    "title": "Troubleshooting",
    "content": "MQTT Not Connecting . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | 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 — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/mqtt.html#troubleshooting",
    
    "relUrl": "/fr-rFR/user/mqtt.html#troubleshooting"
  },"3050": {
    "doc": "MQTT",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — MQTT module configuration reference | Messages & Channels — channel encryption and PSK setup | MQTT integration guide — detailed MQTT documentation on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/mqtt.html#related-topics",
    
    "relUrl": "/fr-rFR/user/mqtt.html#related-topics"
  },"3051": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/mqtt.html",
    
    "relUrl": "/tr-rTR/user/mqtt.html"
  },"3052": {
    "doc": "MQTT",
    "title": "Genel Bakış",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/mqtt.html#genel-bak%C4%B1%C5%9F",
    
    "relUrl": "/tr-rTR/user/mqtt.html#genel-bakış"
  },"3053": {
    "doc": "MQTT",
    "title": "How It Works",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/mqtt.html#how-it-works",
    
    "relUrl": "/tr-rTR/user/mqtt.html#how-it-works"
  },"3054": {
    "doc": "MQTT",
    "title": "Yapılandırma",
    "content": "Enabling MQTT . | Navigate to Settings → Module configuration → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Açıklaması | Varsayılan | . | Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root topic | Base topic for messages | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | Encrypt MQTT payload | Açık | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | Disabled | . | TLS enabled | Secure connection to broker | Disabled | . | Map reporting | Report position to public map | Disabled | . | Proxy to client enabled | Relay MQTT through the connected phone | Disabled | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. MQTT Proxy on This Phone . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 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. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/mqtt.html#yap%C4%B1land%C4%B1rma",
    
    "relUrl": "/tr-rTR/user/mqtt.html#yapılandırma"
  },"3055": {
    "doc": "MQTT",
    "title": "Map Reporting",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/mqtt.html#map-reporting",
    
    "relUrl": "/tr-rTR/user/mqtt.html#map-reporting"
  },"3056": {
    "doc": "MQTT",
    "title": "Uplink vs Downlink",
    "content": "| Direction | Açıklaması | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/mqtt.html#uplink-vs-downlink",
    
    "relUrl": "/tr-rTR/user/mqtt.html#uplink-vs-downlink"
  },"3057": {
    "doc": "MQTT",
    "title": "Message Formats",
    "content": "MQTT carries two payload formats: . | Format | Açıklaması | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/mqtt.html#message-formats",
    
    "relUrl": "/tr-rTR/user/mqtt.html#message-formats"
  },"3058": {
    "doc": "MQTT",
    "title": "Encryption & Privacy",
    "content": "Understanding the layered encryption model: . | 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. | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Security: 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. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/mqtt.html#encryption--privacy",
    
    "relUrl": "/tr-rTR/user/mqtt.html#encryption--privacy"
  },"3059": {
    "doc": "MQTT",
    "title": "Best Practices",
    "content": ". | Use channel-level encryption (PSK) on channels that bridge to MQTT | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes 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 | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/mqtt.html#best-practices",
    
    "relUrl": "/tr-rTR/user/mqtt.html#best-practices"
  },"3060": {
    "doc": "MQTT",
    "title": "Troubleshooting",
    "content": "MQTT Not Connecting . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | 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 — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/mqtt.html#troubleshooting",
    
    "relUrl": "/tr-rTR/user/mqtt.html#troubleshooting"
  },"3061": {
    "doc": "MQTT",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — MQTT module configuration reference | Messages & Channels — channel encryption and PSK setup | MQTT integration guide — detailed MQTT documentation on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/mqtt.html#related-topics",
    
    "relUrl": "/tr-rTR/user/mqtt.html#related-topics"
  },"3062": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/mqtt.html",
    
    "relUrl": "/el-rGR/user/mqtt.html"
  },"3063": {
    "doc": "MQTT",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/mqtt.html#overview",
    
    "relUrl": "/el-rGR/user/mqtt.html#overview"
  },"3064": {
    "doc": "MQTT",
    "title": "How It Works",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/mqtt.html#how-it-works",
    
    "relUrl": "/el-rGR/user/mqtt.html#how-it-works"
  },"3065": {
    "doc": "MQTT",
    "title": "Configuration",
    "content": "Enabling MQTT . | Navigate to Settings → Module configuration → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Περιγραφή | Default | . | Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root topic | Base topic for messages | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | Encrypt MQTT payload | Enabled | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | Disabled | . | TLS enabled | Secure connection to broker | Disabled | . | Map reporting | Report position to public map | Disabled | . | Proxy to client enabled | Relay MQTT through the connected phone | Disabled | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. MQTT Proxy on This Phone . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 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. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/mqtt.html#configuration",
    
    "relUrl": "/el-rGR/user/mqtt.html#configuration"
  },"3066": {
    "doc": "MQTT",
    "title": "Map Reporting",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/mqtt.html#map-reporting",
    
    "relUrl": "/el-rGR/user/mqtt.html#map-reporting"
  },"3067": {
    "doc": "MQTT",
    "title": "Uplink vs Downlink",
    "content": "| Direction | Περιγραφή | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/mqtt.html#uplink-vs-downlink",
    
    "relUrl": "/el-rGR/user/mqtt.html#uplink-vs-downlink"
  },"3068": {
    "doc": "MQTT",
    "title": "Message Formats",
    "content": "MQTT carries two payload formats: . | Format | Περιγραφή | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/mqtt.html#message-formats",
    
    "relUrl": "/el-rGR/user/mqtt.html#message-formats"
  },"3069": {
    "doc": "MQTT",
    "title": "Encryption & Privacy",
    "content": "Understanding the layered encryption model: . | 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. | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Security: 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. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/mqtt.html#encryption--privacy",
    
    "relUrl": "/el-rGR/user/mqtt.html#encryption--privacy"
  },"3070": {
    "doc": "MQTT",
    "title": "Best Practices",
    "content": ". | Use channel-level encryption (PSK) on channels that bridge to MQTT | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes 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 | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/mqtt.html#best-practices",
    
    "relUrl": "/el-rGR/user/mqtt.html#best-practices"
  },"3071": {
    "doc": "MQTT",
    "title": "Troubleshooting",
    "content": "MQTT Not Connecting . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | 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 — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/mqtt.html#troubleshooting",
    
    "relUrl": "/el-rGR/user/mqtt.html#troubleshooting"
  },"3072": {
    "doc": "MQTT",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — MQTT module configuration reference | Messages & Channels — channel encryption and PSK setup | MQTT integration guide — detailed MQTT documentation on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/mqtt.html#related-topics",
    
    "relUrl": "/el-rGR/user/mqtt.html#related-topics"
  },"3073": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/mqtt.html",
    
    "relUrl": "/ro-rRO/user/mqtt.html"
  },"3074": {
    "doc": "MQTT",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/mqtt.html#overview",
    
    "relUrl": "/ro-rRO/user/mqtt.html#overview"
  },"3075": {
    "doc": "MQTT",
    "title": "How It Works",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/mqtt.html#how-it-works",
    
    "relUrl": "/ro-rRO/user/mqtt.html#how-it-works"
  },"3076": {
    "doc": "MQTT",
    "title": "Configuration",
    "content": "Enabling MQTT . | Navigate to Settings → Module configuration → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Descriere | Prestabilit | . | Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root topic | Base topic for messages | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | Encrypt MQTT payload | Activat | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | Disabled | . | TLS enabled | Secure connection to broker | Disabled | . | Map reporting | Report position to public map | Disabled | . | Proxy to client enabled | Relay MQTT through the connected phone | Disabled | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. MQTT Proxy on This Phone . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 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. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/mqtt.html#configuration",
    
    "relUrl": "/ro-rRO/user/mqtt.html#configuration"
  },"3077": {
    "doc": "MQTT",
    "title": "Map Reporting",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/mqtt.html#map-reporting",
    
    "relUrl": "/ro-rRO/user/mqtt.html#map-reporting"
  },"3078": {
    "doc": "MQTT",
    "title": "Uplink vs Downlink",
    "content": "| Direction | Descriere | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/mqtt.html#uplink-vs-downlink",
    
    "relUrl": "/ro-rRO/user/mqtt.html#uplink-vs-downlink"
  },"3079": {
    "doc": "MQTT",
    "title": "Message Formats",
    "content": "MQTT carries two payload formats: . | Format | Descriere | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/mqtt.html#message-formats",
    
    "relUrl": "/ro-rRO/user/mqtt.html#message-formats"
  },"3080": {
    "doc": "MQTT",
    "title": "Encryption & Privacy",
    "content": "Understanding the layered encryption model: . | 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. | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Security: 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. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/mqtt.html#encryption--privacy",
    
    "relUrl": "/ro-rRO/user/mqtt.html#encryption--privacy"
  },"3081": {
    "doc": "MQTT",
    "title": "Best Practices",
    "content": ". | Use channel-level encryption (PSK) on channels that bridge to MQTT | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes 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 | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/mqtt.html#best-practices",
    
    "relUrl": "/ro-rRO/user/mqtt.html#best-practices"
  },"3082": {
    "doc": "MQTT",
    "title": "Troubleshooting",
    "content": "MQTT Not Connecting . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | 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 — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/mqtt.html#troubleshooting",
    
    "relUrl": "/ro-rRO/user/mqtt.html#troubleshooting"
  },"3083": {
    "doc": "MQTT",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — MQTT module configuration reference | Messages & Channels — channel encryption and PSK setup | MQTT integration guide — detailed MQTT documentation on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/mqtt.html#related-topics",
    
    "relUrl": "/ro-rRO/user/mqtt.html#related-topics"
  },"3084": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/mqtt.html",
    
    "relUrl": "/iw-rIL/user/mqtt.html"
  },"3085": {
    "doc": "MQTT",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/mqtt.html#overview",
    
    "relUrl": "/iw-rIL/user/mqtt.html#overview"
  },"3086": {
    "doc": "MQTT",
    "title": "How It Works",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/mqtt.html#how-it-works",
    
    "relUrl": "/iw-rIL/user/mqtt.html#how-it-works"
  },"3087": {
    "doc": "MQTT",
    "title": "Configuration",
    "content": "Enabling MQTT . | Navigate to Settings → Module configuration → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | תיאור | Default | . | Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root topic | Base topic for messages | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | Encrypt MQTT payload | Enabled | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | Disabled | . | TLS enabled | Secure connection to broker | Disabled | . | Map reporting | Report position to public map | Disabled | . | Proxy to client enabled | Relay MQTT through the connected phone | Disabled | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. MQTT Proxy on This Phone . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 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. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/mqtt.html#configuration",
    
    "relUrl": "/iw-rIL/user/mqtt.html#configuration"
  },"3088": {
    "doc": "MQTT",
    "title": "Map Reporting",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/mqtt.html#map-reporting",
    
    "relUrl": "/iw-rIL/user/mqtt.html#map-reporting"
  },"3089": {
    "doc": "MQTT",
    "title": "Uplink vs Downlink",
    "content": "| Direction | תיאור | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/mqtt.html#uplink-vs-downlink",
    
    "relUrl": "/iw-rIL/user/mqtt.html#uplink-vs-downlink"
  },"3090": {
    "doc": "MQTT",
    "title": "Message Formats",
    "content": "MQTT carries two payload formats: . | Format | תיאור | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/mqtt.html#message-formats",
    
    "relUrl": "/iw-rIL/user/mqtt.html#message-formats"
  },"3091": {
    "doc": "MQTT",
    "title": "Encryption & Privacy",
    "content": "Understanding the layered encryption model: . | 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. | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Security: 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. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/mqtt.html#encryption--privacy",
    
    "relUrl": "/iw-rIL/user/mqtt.html#encryption--privacy"
  },"3092": {
    "doc": "MQTT",
    "title": "Best Practices",
    "content": ". | Use channel-level encryption (PSK) on channels that bridge to MQTT | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes 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 | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/mqtt.html#best-practices",
    
    "relUrl": "/iw-rIL/user/mqtt.html#best-practices"
  },"3093": {
    "doc": "MQTT",
    "title": "Troubleshooting",
    "content": "MQTT Not Connecting . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | 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 — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/mqtt.html#troubleshooting",
    
    "relUrl": "/iw-rIL/user/mqtt.html#troubleshooting"
  },"3094": {
    "doc": "MQTT",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — MQTT module configuration reference | Messages & Channels — channel encryption and PSK setup | MQTT integration guide — detailed MQTT documentation on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/mqtt.html#related-topics",
    
    "relUrl": "/iw-rIL/user/mqtt.html#related-topics"
  },"3095": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/mqtt.html",
    
    "relUrl": "/pt-rBR/user/mqtt.html"
  },"3096": {
    "doc": "MQTT",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/mqtt.html#overview",
    
    "relUrl": "/pt-rBR/user/mqtt.html#overview"
  },"3097": {
    "doc": "MQTT",
    "title": "How It Works",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/mqtt.html#how-it-works",
    
    "relUrl": "/pt-rBR/user/mqtt.html#how-it-works"
  },"3098": {
    "doc": "MQTT",
    "title": "Configuration",
    "content": "Enabling MQTT . | Navigate to Settings → Module configuration → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Descrição | Padrão | . | Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root topic | Base topic for messages | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | Encrypt MQTT payload | Enabled | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | Disabled | . | TLS enabled | Secure connection to broker | Disabled | . | Map reporting | Report position to public map | Disabled | . | Proxy to client enabled | Relay MQTT through the connected phone | Disabled | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. MQTT Proxy on This Phone . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 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. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/mqtt.html#configuration",
    
    "relUrl": "/pt-rBR/user/mqtt.html#configuration"
  },"3099": {
    "doc": "MQTT",
    "title": "Map Reporting",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/mqtt.html#map-reporting",
    
    "relUrl": "/pt-rBR/user/mqtt.html#map-reporting"
  },"3100": {
    "doc": "MQTT",
    "title": "Uplink vs Downlink",
    "content": "| Direction | Descrição | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/mqtt.html#uplink-vs-downlink",
    
    "relUrl": "/pt-rBR/user/mqtt.html#uplink-vs-downlink"
  },"3101": {
    "doc": "MQTT",
    "title": "Message Formats",
    "content": "MQTT carries two payload formats: . | Format | Descrição | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/mqtt.html#message-formats",
    
    "relUrl": "/pt-rBR/user/mqtt.html#message-formats"
  },"3102": {
    "doc": "MQTT",
    "title": "Encryption & Privacy",
    "content": "Understanding the layered encryption model: . | 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. | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Security: 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. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/mqtt.html#encryption--privacy",
    
    "relUrl": "/pt-rBR/user/mqtt.html#encryption--privacy"
  },"3103": {
    "doc": "MQTT",
    "title": "Best Practices",
    "content": ". | Use channel-level encryption (PSK) on channels that bridge to MQTT | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes 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 | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/mqtt.html#best-practices",
    
    "relUrl": "/pt-rBR/user/mqtt.html#best-practices"
  },"3104": {
    "doc": "MQTT",
    "title": "Troubleshooting",
    "content": "MQTT Not Connecting . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | 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 — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/mqtt.html#troubleshooting",
    
    "relUrl": "/pt-rBR/user/mqtt.html#troubleshooting"
  },"3105": {
    "doc": "MQTT",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — MQTT module configuration reference | Messages & Channels — channel encryption and PSK setup | MQTT integration guide — detailed MQTT documentation on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/mqtt.html#related-topics",
    
    "relUrl": "/pt-rBR/user/mqtt.html#related-topics"
  },"3106": {
    "doc": "MQTT",
    "title": "MQTT",
    "content": "MQTT bridges your Meshtastic mesh network to the internet, enabling long-range communication beyond radio range. ",
    "url": "/Meshtastic-Android/main/en/user/mqtt.html",
    
    "relUrl": "/en/user/mqtt.html"
  },"3107": {
    "doc": "MQTT",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/en/user/mqtt.html#overview",
    
    "relUrl": "/en/user/mqtt.html#overview"
  },"3108": {
    "doc": "MQTT",
    "title": "How It Works",
    "content": "[Your Node] → Radio → [Gateway Node with Wi-Fi] → MQTT Broker → [Remote Gateway] → Radio → [Remote Node] . A gateway node with internet access (Wi-Fi or Ethernet) publishes mesh messages to an MQTT topic. Remote gateways subscribed to the same topic inject those messages into their local mesh. ",
    "url": "/Meshtastic-Android/main/en/user/mqtt.html#how-it-works",
    
    "relUrl": "/en/user/mqtt.html#how-it-works"
  },"3109": {
    "doc": "MQTT",
    "title": "Configuration",
    "content": "Enabling MQTT . | Navigate to Settings → Module configuration → MQTT. | Enable the MQTT module. | Configure the broker connection: | . | Setting | Description | Default | . | Address | MQTT broker hostname | mqtt.meshtastic.org | . | Username | Broker authentication | meshdev | . | Password | Broker authentication | large4cats | . | Root topic | Base topic for messages | msh, which the radio rewrites to msh/<REGION> once you set a region | . | Encryption enabled | Encrypt MQTT payload | Enabled | . | JSON output enabled | Also publish and consume the /2/json/ topic. Deprecated in the protobuf schema, but still the only toggle for this behavior — and the app’s own proxy honors it | Disabled | . | TLS enabled | Secure connection to broker | Disabled | . | Map reporting | Report position to public map | Disabled | . | Proxy to client enabled | Relay MQTT through the connected phone | Disabled | . Connection Status and Test Connection . The top of the MQTT settings screen shows the status of the relay this phone runs — Connected, Connecting, Reconnecting, Disconnected, or Inactive. It reads Inactive whenever the phone is not relaying, which includes the normal case of a radio reaching the broker over its own Wi-Fi or Ethernet. The radio’s own connection to the broker is not reported here. Test connection probes the broker before you commit the settings to the radio, and distinguishes the failure modes: the hostname not resolving, the TCP connection being refused, TLS failing, the attempt timing out, or the broker rejecting your credentials with a reason. MQTT Proxy on This Phone . If your radio has no internet access of its own, it can use the connected phone as its MQTT gateway: enable MQTT and Proxy to client enabled in the module config, and the app relays MQTT traffic between the radio and the broker over your phone’s internet connection. ℹ️ Note: The proxy relay is mobile-only. On the Desktop app the MQTT settings are present, but no relay runs behind them. The MQTT proxy on this phone toggle at the top of the MQTT settings screen shows whether this relay is running and lets you cut it off (or restart it) immediately — without editing and re-saving the radio’s MQTT configuration. Default Meshtastic Broker . The community maintains a public broker at mqtt.meshtastic.org. This is intended for general use and testing. When this phone relays MQTT for the radio, connections to that broker always use TLS on port 8883 even if TLS enabled is off — that upgrade is the app’s own, and the switch says so. A radio that reaches the broker over its own Wi-Fi or Ethernet forces nothing: it uses TLS enabled as stored, so turn it on yourself or the radio connects in the clear on port 1883. For any other broker the toggle decides in both cases (port 8883 with TLS, 1883 without). 🔒 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. ",
    "url": "/Meshtastic-Android/main/en/user/mqtt.html#configuration",
    
    "relUrl": "/en/user/mqtt.html#configuration"
  },"3110": {
    "doc": "MQTT",
    "title": "Map Reporting",
    "content": "When Map reporting is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name. Turning it on opens a consent card. Turn on I agree. and choose a Map reporting interval (seconds) of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one. Reports appear at meshmap.net and similar community map services. 🔒 Privacy: A map report is readable by anyone subscribed to the broker. Leave Map reporting off if you do not want your approximate location published. ",
    "url": "/Meshtastic-Android/main/en/user/mqtt.html#map-reporting",
    
    "relUrl": "/en/user/mqtt.html#map-reporting"
  },"3111": {
    "doc": "MQTT",
    "title": "Uplink vs Downlink",
    "content": "| Direction | Description | . | Uplink | Messages from mesh → MQTT broker | . | Downlink | Messages from MQTT broker → mesh | . Uplink and downlink are per-channel settings, not MQTT module settings. Open Settings → Channels, tap the channel, and use MQTT Uplink Enabled and MQTT Downlink Enabled. Every channel you want bridged out needs uplink on, and every channel you want MQTT traffic injected into needs downlink on. ",
    "url": "/Meshtastic-Android/main/en/user/mqtt.html#uplink-vs-downlink",
    
    "relUrl": "/en/user/mqtt.html#uplink-vs-downlink"
  },"3112": {
    "doc": "MQTT",
    "title": "Message Formats",
    "content": "MQTT carries two payload formats: . | Format | Description | Use case | . | Protobuf | Binary Meshtastic protobuf encoding | Node-to-node mesh bridging | . | JSON | Human-readable JSON on the /2/json/ topic | Consumers outside the mesh (dashboards, home automation) | . ℹ️ Note: json_enabled is marked deprecated in the protobuf schema, but it has not been replaced and it is not ignored. When it is on, the app’s own MQTT proxy subscribes to the /2/json/ topic and decodes those payloads. ",
    "url": "/Meshtastic-Android/main/en/user/mqtt.html#message-formats",
    
    "relUrl": "/en/user/mqtt.html#message-formats"
  },"3113": {
    "doc": "MQTT",
    "title": "Encryption & Privacy",
    "content": "Understanding the layered encryption model: . | 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. | Encryption enabled (the module setting) decides which copy of the packet the gateway publishes — it is not an extra layer. Leave it on and the broker receives the packet still encrypted with your channel key. Turn it off and the gateway publishes the decrypted packet, so anyone subscribed to the topic reads your messages in the clear. Turn it off only when you own the broker and want plain payloads for a dashboard. | TLS encrypts the TCP connection to the broker itself, preventing network-level eavesdropping. | . 🔒 Security: 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. ",
    "url": "/Meshtastic-Android/main/en/user/mqtt.html#encryption--privacy",
    
    "relUrl": "/en/user/mqtt.html#encryption--privacy"
  },"3114": {
    "doc": "MQTT",
    "title": "Best Practices",
    "content": ". | Use channel-level encryption (PSK) on channels that bridge to MQTT | Don’t enable MQTT on nodes without internet access (the radio buffers unsendable messages and wastes 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 | . ",
    "url": "/Meshtastic-Android/main/en/user/mqtt.html#best-practices",
    
    "relUrl": "/en/user/mqtt.html#best-practices"
  },"3115": {
    "doc": "MQTT",
    "title": "Troubleshooting",
    "content": "MQTT Not Connecting . | Check Wi-Fi — the gateway node must have an active internet connection (Wi-Fi or Ethernet). MQTT does not work over the LoRa radio link itself. | Verify credentials — with incorrect credentials, most brokers fail silently — double-check for trailing spaces. | Firewall — port 1883 (MQTT) or 8883 (MQTT over TLS) must be reachable. Some networks allow only web traffic (ports 80 and 443). | 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 — both gateways must use exactly the same root topic. Setting a region rewrites a default root to msh/<REGION> (for example msh/US), so gateways in different regions do not meet until you give both the same explicit root. | Ignore MQTT is on — in a region with a duty-cycle limit, the radio turns on Ignore MQTT (LoRa config, Advanced) when you set the region, and then drops every packet that reached it via MQTT. Turn it off on the receiving nodes, not only on the gateway. | Ok to MQTT is off — on a public broker a gateway uplinks other nodes’ packets only when the sending node has Ok to MQTT (LoRa config, Advanced) on. Your own traffic bridges either way; your neighbors’ does not until they opt in. | . ",
    "url": "/Meshtastic-Android/main/en/user/mqtt.html#troubleshooting",
    
    "relUrl": "/en/user/mqtt.html#troubleshooting"
  },"3116": {
    "doc": "MQTT",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — MQTT module configuration reference | Messages & Channels — channel encryption and PSK setup | MQTT integration guide — detailed MQTT documentation on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/en/user/mqtt.html#related-topics",
    
    "relUrl": "/en/user/mqtt.html#related-topics"
  },"3117": {
    "doc": "Navigation & Deep Links",
    "title": "Navigation & Deep Links",
    "content": "The app uses Navigation 3 with typed, serializable routes and centralized deep link resolution. ",
    "url": "/Meshtastic-Android/main/en/developer/navigation-and-deep-links.html#navigation--deep-links",
    
    "relUrl": "/en/developer/navigation-and-deep-links.html#navigation--deep-links"
  },"3118": {
    "doc": "Navigation & Deep Links",
    "title": "Route architecture",
    "content": "All routes are defined in core/navigation/src/commonMain/kotlin/org/meshtastic/core/navigation/Routes.kt. Route hierarchy . interface Route : NavKey // All routes implement NavKey interface Graph : Route // Graph roots for navigation hierarchies @Serializable sealed interface SettingsRoute : Route { @Serializable data class Settings(val destNum: Int? = null) : SettingsRoute, Graph @Serializable data object DeviceConfiguration : SettingsRoute @Serializable data object HelpDocs : SettingsRoute @Serializable data class HelpDocPage(val pageId: String) : SettingsRoute // ... } . Conventions . | Routes are @Serializable for state restoration | Use data object for routes without parameters | Use data class for parameterized routes | Group related routes under a sealed interface | Graph entry points implement both the route interface and Graph | . ",
    "url": "/Meshtastic-Android/main/en/developer/navigation-and-deep-links.html#route-architecture",
    
    "relUrl": "/en/developer/navigation-and-deep-links.html#route-architecture"
  },"3119": {
    "doc": "Navigation & Deep Links",
    "title": "Deep link router",
    "content": "DeepLinkRouter in core/navigation maps URI deep links to typed backstack lists. Each supported link is a Navigation 3 UriDeepLinkMatcher pattern whose placeholders decode into the target route’s fields, wrapped in withBackStack to synthesize the parents. Patterns are anchored, so a path the patterns don’t model returns null rather than falling back to the family root: /firmware/anything-else no longer opens the firmware screen. URI format . Both forms resolve through the same DeepLinkRouter, so any deep link path works with either scheme: . meshtastic://meshtastic/{path} https://meshtastic.org/{path} # App Link, android:autoVerify — also opens in-app on a real device/adb . adb shell am start -a android.intent.action.VIEW -d \"meshtastic://meshtastic/{path}\" is the fastest way to trigger any route in the Supported Deep Links table from a shell or automation script without touching the UI. For the https form to open in-app, each top-level path segment must also be declared as an android:pathPrefix in the android:autoVerify intent-filter in androidApp/src/main/AndroidManifest.xml — otherwise the link opens in the browser. Adding a new top-level route therefore takes three steps: add the segment to DeepLinkRouter.topLevelPathSegments (the router refuses to dispatch segments outside that set), add its matcher to DeepLinkRouter.matchers, and add the matching pathPrefix to the manifest. DeepLinkManifestConsistencyTest (androidApp unit tests) checks the manifest against the set, so a missing manifest entry fails CI. Source of truth: . | The always-current list of top-level segments is topLevelPathSegments in DeepLinkRouter. | Sub-paths live in the matchers list plus its helper maps (settingsSubRoutes, nodeDetailSubRoutes). | The class-level KDoc on the DeepLinkRouter object lists example mappings, but it’s illustrative, not exhaustive. | The executable spec is DeepLinkRouterTest.kt. | The following table is a snapshot for quick reference — check those two files if it looks out of date. | . Supported deep links . | URI Path | Route | Notes | . | /connections | ConnectionsRoute.Connections(null) | Connections screen | . | /connections?address={prefixedAddress} | ConnectionsRoute.Connections(address) | Auto-connects to a node without manual selection — the address uses the app’s internal transport-prefixed format: t192.168.1.1:4403 (TCP), xAA:BB:CC:DD:EE:FF (BLE), s/dev/ttyUSB0 (serial). Intended for scripts/AI tooling driving the app. | . | /connections?address=n | ConnectionsRoute.Connections(\"n\") | Disconnects the current node instead of connecting (n = the internal “no device selected” sentinel). | . | /wifi-provision | WifiProvisionRoute.WifiProvision(null) | Wi-Fi provisioning screen | . | /wifi-provision?address={mac} | WifiProvisionRoute.WifiProvision(mac) | Provisioning targeting a specific node MAC | . | /settings | SettingsRoute.Settings(null) | Settings root | . | /settings/helpDocs | SettingsRoute.HelpDocs | Docs browser | . | /settings/helpDocs/{pageId} | SettingsRoute.HelpDocPage(pageId) | Specific doc page | . | /settings/help-docs | SettingsRoute.HelpDocs | Compatibility alias | . | /discovery | DiscoveryRoute.DiscoveryGraph | Local Mesh Discovery entry point | . | /settings/local-mesh-discovery/session/{sessionId} | DiscoveryRoute.DiscoverySummary(sessionId) | Discovery session result | . | /nodes | NodesRoute.Nodes | Node list | . | /nodes/{destNum} | NodesRoute.NodeDetail(destNum) | Node detail | . | /nodes/{destNum}/{metric} | e.g. NodeDetailRoute.DeviceMetrics(destNum) | Specific node metric tab (device-metrics, signal, power, traceroute, pax, neighbors, …) | . | /messages | ContactsRoute.Contacts | Conversation list | . | /messages/{contactKey} | ContactsRoute.Messages(contactKey) | Specific conversation | . | /share?message={text} | ContactsRoute.Share(message) | Share-to-contact composer | . | /quickchat | ContactsRoute.QuickChat | Quick chat picker | . | /map | MapRoute.Map(null) | Map view | . | /map/{waypointId} | MapRoute.Map(waypointId) | Map centered on a waypoint | . | /channels | ChannelsRoute.Channels | Channel list | . | /firmware | FirmwareRoute.FirmwareGraph | Firmware screen | . | /firmware/update | FirmwareRoute.FirmwareUpdate | Firmware update flow | . Backstack synthesis . Deep links synthesize a full backstack, not just the target screen: . // /settings/helpDocs/messages-and-channels produces: listOf( SettingsRoute.Settings(null), SettingsRoute.HelpDocs, SettingsRoute.HelpDocPage(\"messages-and-channels\"), ) . This ensures the user can navigate “up” correctly. ",
    "url": "/Meshtastic-Android/main/en/developer/navigation-and-deep-links.html#deep-link-router",
    
    "relUrl": "/en/developer/navigation-and-deep-links.html#deep-link-router"
  },"3120": {
    "doc": "Navigation & Deep Links",
    "title": "Adding a deep link",
    "content": ". | Define the typed route in Routes.kt. | Add the mapping in DeepLinkRouter.settingsSubRoutes (or equivalent for other graphs), and a matcher in DeepLinkRouter.matchers if the path shape is new. | Add a test in DeepLinkRouterTest.kt. | Register the navigation entry in the appropriate feature module. | Update the illustrative KDoc list on the DeepLinkRouter object (the class-level doc comment, not route()’s own KDoc) and the preceding table — both are quick-reference snapshots, not the source of truth. See the Source of Truth list earlier in this page for the authoritative places. | . ",
    "url": "/Meshtastic-Android/main/en/developer/navigation-and-deep-links.html#adding-a-deep-link",
    
    "relUrl": "/en/developer/navigation-and-deep-links.html#adding-a-deep-link"
  },"3121": {
    "doc": "Navigation & Deep Links",
    "title": "Navigation entry registration",
    "content": "Each feature module provides entries via an extension function: . fun EntryProviderScope<NavKey>.docsEntries(backStack: NavBackStack<NavKey>) { entry<SettingsRoute.HelpDocs> { DocsBrowserScreen(backStack) } entry<SettingsRoute.HelpDocPage> { route -> DocsPageRouteScreen(route.pageId, backStack) } } . These are called from the settings navigation composition. ",
    "url": "/Meshtastic-Android/main/en/developer/navigation-and-deep-links.html#navigation-entry-registration",
    
    "relUrl": "/en/developer/navigation-and-deep-links.html#navigation-entry-registration"
  },"3122": {
    "doc": "Navigation & Deep Links",
    "title": "Testing",
    "content": "Deep link routing is tested in: . core/navigation/src/commonTest/kotlin/org/meshtastic/core/navigation/DeepLinkRouterTest.kt . ",
    "url": "/Meshtastic-Android/main/en/developer/navigation-and-deep-links.html#testing",
    
    "relUrl": "/en/developer/navigation-and-deep-links.html#testing"
  },"3123": {
    "doc": "Navigation & Deep Links",
    "title": "Navigation & Deep Links",
    "content": " ",
    "url": "/Meshtastic-Android/main/en/developer/navigation-and-deep-links.html",
    
    "relUrl": "/en/developer/navigation-and-deep-links.html"
  },"3124": {
    "doc": "Node Metrics",
    "title": "Node Metrics",
    "content": "The node detail screen provides comprehensive telemetry and metrics for each node on your mesh. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/node-metrics.html",
    
    "relUrl": "/sk-rSK/user/node-metrics.html"
  },"3125": {
    "doc": "Node Metrics",
    "title": "Viewing Metrics",
    "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/node-metrics.html#viewing-metrics",
    
    "relUrl": "/sk-rSK/user/node-metrics.html#viewing-metrics"
  },"3126": {
    "doc": "Node Metrics",
    "title": "Device Metrics",
    "content": "Basic operating information reported by each node: . | Metric | Popis | . | Battery Level | Current battery percentage | . | Napätie | Battery voltage reading | . | ChUtil | Percentage of local airtime in use | . | AirUtil | Percentage of the last hour this node spent transmitting | . | Doba prevádzky | Time since last reboot | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/node-metrics.html#device-metrics",
    
    "relUrl": "/sk-rSK/user/node-metrics.html#device-metrics"
  },"3127": {
    "doc": "Node Metrics",
    "title": "Environment Metrics",
    "content": "Environmental sensor data (requires compatible hardware): . | Metric | Sensor Examples | . | Teplota | BME280, BME680, SHT31 | . | Vlhkosť | BME280, BME680, SHT31 | . | Barometrický tlak | BME280, BMP280 | . | Gas Resistance | BME680 | . | IAQ (Air Quality) | BME680 | . Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted: . 💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/node-metrics.html#environment-metrics",
    
    "relUrl": "/sk-rSK/user/node-metrics.html#environment-metrics"
  },"3128": {
    "doc": "Node Metrics",
    "title": "Air Quality Metrics",
    "content": "Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. | Metric | Unit | Popis | . | PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | . | PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | . | PM10 | µg/m³ | Particulate matter up to 10 microns | . | AQI | EPA index | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated. | . | CO₂ | ppm | Carbon dioxide concentration | . | CO₂ temperature | °C / °F | Temperature reported by the CO₂ sensor itself (e.g. SCD4x) | . | CO₂ humidity | % | Relative humidity reported by the CO₂ sensor | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | Band | CO₂ Range (ppm) | Color | . | Dobrý | < 1000 | Zelená | . | Stuffy | < 2000 | Amber | . | Poor | < 5000 | Orange | . | Unsafe | < 30000 | Červená | . | Evacuate | ≥ 30000 | Dark red | . An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can: . | Select a time frame for the charts. | Filter with metric chips — only metrics that have data are shown. | Refresh / request the latest air-quality telemetry. | Export to CSV for analysis in a spreadsheet. | . 💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/node-metrics.html#air-quality-metrics",
    
    "relUrl": "/sk-rSK/user/node-metrics.html#air-quality-metrics"
  },"3129": {
    "doc": "Node Metrics",
    "title": "Kvalita signálu",
    "content": "Radio signal quality information: . | Metric | Popis | . | SNR | Signal-to-Noise Ratio (higher is better) | . | RSSI | Received Signal Strength Indicator (closer to 0 is better) | . | Noise Floor | Local background RF noise in dBm (more negative is quieter) | . | Hop Count | Number of mesh hops for last message | . Signal Quality Reference . Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | Quality | Criteria | . | Dobrý | SNR above the preset’s limit | . | Primeraný | less than 5.5 dB below the limit | . | Zlý | 5.5 dB to 7.5 dB below the limit | . | Žiadny | more than 7.5 dB below the limit | . See Understanding the Signal Meter for the full explanation. Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment. | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/node-metrics.html#kvalita-sign%C3%A1lu",
    
    "relUrl": "/sk-rSK/user/node-metrics.html#kvalita-signálu"
  },"3130": {
    "doc": "Node Metrics",
    "title": "Power Metrics",
    "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Popis | . | Napätie | Per-channel voltage reading | . | Prúd | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/node-metrics.html#power-metrics",
    
    "relUrl": "/sk-rSK/user/node-metrics.html#power-metrics"
  },"3131": {
    "doc": "Node Metrics",
    "title": "Trasovanie",
    "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | The app sends a traceroute request to the target node. | Results show each hop with its SNR. | . Reading Traceroute Results . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/node-metrics.html#trasovanie",
    
    "relUrl": "/sk-rSK/user/node-metrics.html#trasovanie"
  },"3132": {
    "doc": "Node Metrics",
    "title": "Log pozície",
    "content": "Historical position data for nodes that share their location: . | GPS coordinates | Nadmorská výška | Speed (if moving) | Timestamp for each position report | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/node-metrics.html#log-poz%C3%ADcie",
    
    "relUrl": "/sk-rSK/user/node-metrics.html#log-pozície"
  },"3133": {
    "doc": "Node Metrics",
    "title": "Informácia o susedoch",
    "content": "Shows which nodes a given node can directly hear, useful for understanding mesh topology. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/node-metrics.html#inform%C3%A1cia-o-susedoch",
    
    "relUrl": "/sk-rSK/user/node-metrics.html#informácia-o-susedoch"
  },"3134": {
    "doc": "Node Metrics",
    "title": "Host Metrics",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/node-metrics.html#host-metrics",
    
    "relUrl": "/sk-rSK/user/node-metrics.html#host-metrics"
  },"3135": {
    "doc": "Node Metrics",
    "title": "PAX Metrics",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/node-metrics.html#pax-metrics",
    
    "relUrl": "/sk-rSK/user/node-metrics.html#pax-metrics"
  },"3136": {
    "doc": "Node Metrics",
    "title": "Related Topics",
    "content": ". | Nodes — node list, filtering, and sorting | Telemetry & Sensors — supported sensors and configuration | Signal Meter — how signal quality is calculated from SNR and RSSI | Local Mesh Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/node-metrics.html#related-topics",
    
    "relUrl": "/sk-rSK/user/node-metrics.html#related-topics"
  },"3137": {
    "doc": "Node Metrics",
    "title": "Node Metrics",
    "content": "The node detail screen provides comprehensive telemetry and metrics for each node on your mesh. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/node-metrics.html",
    
    "relUrl": "/be-rBY/user/node-metrics.html"
  },"3138": {
    "doc": "Node Metrics",
    "title": "Viewing Metrics",
    "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/node-metrics.html#viewing-metrics",
    
    "relUrl": "/be-rBY/user/node-metrics.html#viewing-metrics"
  },"3139": {
    "doc": "Node Metrics",
    "title": "Device Metrics",
    "content": "Basic operating information reported by each node: . | Metric | Апісанне | . | Battery Level | Current battery percentage | . | Voltage | Battery voltage reading | . | ChUtil | Percentage of local airtime in use | . | AirUtil | Percentage of the last hour this node spent transmitting | . | Uptime | Time since last reboot | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/node-metrics.html#device-metrics",
    
    "relUrl": "/be-rBY/user/node-metrics.html#device-metrics"
  },"3140": {
    "doc": "Node Metrics",
    "title": "Environment Metrics",
    "content": "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 — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted: . 💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/node-metrics.html#environment-metrics",
    
    "relUrl": "/be-rBY/user/node-metrics.html#environment-metrics"
  },"3141": {
    "doc": "Node Metrics",
    "title": "Air Quality Metrics",
    "content": "Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. | Metric | Unit | Апісанне | . | PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | . | PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | . | PM10 | µg/m³ | Particulate matter up to 10 microns | . | AQI | EPA index | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated. | . | CO₂ | ppm | Carbon dioxide concentration | . | CO₂ temperature | °C / °F | Temperature reported by the CO₂ sensor itself (e.g. SCD4x) | . | CO₂ humidity | % | Relative humidity reported by the CO₂ sensor | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | Band | CO₂ Range (ppm) | Color | . | Good | < 1000 | Зялёны | . | Stuffy | < 2000 | Amber | . | Poor | < 5000 | Orange | . | Unsafe | < 30000 | Чырвоны | . | Evacuate | ≥ 30000 | Dark red | . An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can: . | Select a time frame for the charts. | Filter with metric chips — only metrics that have data are shown. | Refresh / request the latest air-quality telemetry. | Export to CSV for analysis in a spreadsheet. | . 💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/node-metrics.html#air-quality-metrics",
    
    "relUrl": "/be-rBY/user/node-metrics.html#air-quality-metrics"
  },"3142": {
    "doc": "Node Metrics",
    "title": "Якасць сігнала",
    "content": "Radio signal quality information: . | Metric | Апісанне | . | сігнал-шум | Signal-to-Noise Ratio (higher is better) | . | адносная магутнасць | Received Signal Strength Indicator (closer to 0 is better) | . | Noise Floor | Local background RF noise in dBm (more negative is quieter) | . | Hop Count | Number of mesh hops for last message | . Signal Quality Reference . Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | Quality | Criteria | . | Good | SNR above the preset’s limit | . | Fair | less than 5.5 dB below the limit | . | Bad | 5.5 dB to 7.5 dB below the limit | . | Нічога | more than 7.5 dB below the limit | . See Understanding the Signal Meter for the full explanation. Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment. | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/node-metrics.html#%D1%8F%D0%BA%D0%B0%D1%81%D1%86%D1%8C-%D1%81%D1%96%D0%B3%D0%BD%D0%B0%D0%BB%D0%B0",
    
    "relUrl": "/be-rBY/user/node-metrics.html#якасць-сігнала"
  },"3143": {
    "doc": "Node Metrics",
    "title": "Power Metrics",
    "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Апісанне | . | Voltage | Per-channel voltage reading | . | 3 | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/node-metrics.html#power-metrics",
    
    "relUrl": "/be-rBY/user/node-metrics.html#power-metrics"
  },"3144": {
    "doc": "Node Metrics",
    "title": "Traceroute",
    "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | The app sends a traceroute request to the target node. | Results show each hop with its SNR. | . Reading Traceroute Results . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/node-metrics.html#traceroute",
    
    "relUrl": "/be-rBY/user/node-metrics.html#traceroute"
  },"3145": {
    "doc": "Node Metrics",
    "title": "Гісторыя месцазнаходжання",
    "content": "Historical position data for nodes that share their location: . | GPS coordinates | Altitude | Speed (if moving) | Timestamp for each position report | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/node-metrics.html#%D0%B3%D1%96%D1%81%D1%82%D0%BE%D1%80%D1%8B%D1%8F-%D0%BC%D0%B5%D1%81%D1%86%D0%B0%D0%B7%D0%BD%D0%B0%D1%85%D0%BE%D0%B4%D0%B6%D0%B0%D0%BD%D0%BD%D1%8F",
    
    "relUrl": "/be-rBY/user/node-metrics.html#гісторыя-месцазнаходжання"
  },"3146": {
    "doc": "Node Metrics",
    "title": "Neighbor Info",
    "content": "Shows which nodes a given node can directly hear, useful for understanding mesh topology. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/node-metrics.html#neighbor-info",
    
    "relUrl": "/be-rBY/user/node-metrics.html#neighbor-info"
  },"3147": {
    "doc": "Node Metrics",
    "title": "Host Metrics",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/node-metrics.html#host-metrics",
    
    "relUrl": "/be-rBY/user/node-metrics.html#host-metrics"
  },"3148": {
    "doc": "Node Metrics",
    "title": "PAX Metrics",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/node-metrics.html#pax-metrics",
    
    "relUrl": "/be-rBY/user/node-metrics.html#pax-metrics"
  },"3149": {
    "doc": "Node Metrics",
    "title": "Related Topics",
    "content": ". | Nodes — node list, filtering, and sorting | Telemetry & Sensors — supported sensors and configuration | Signal Meter — how signal quality is calculated from SNR and RSSI | Local Mesh Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/node-metrics.html#related-topics",
    
    "relUrl": "/be-rBY/user/node-metrics.html#related-topics"
  },"3150": {
    "doc": "Node Metrics",
    "title": "Node Metrics",
    "content": "The node detail screen provides comprehensive telemetry and metrics for each node on your mesh. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/node-metrics.html",
    
    "relUrl": "/it-rIT/user/node-metrics.html"
  },"3151": {
    "doc": "Node Metrics",
    "title": "Viewing Metrics",
    "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/node-metrics.html#viewing-metrics",
    
    "relUrl": "/it-rIT/user/node-metrics.html#viewing-metrics"
  },"3152": {
    "doc": "Node Metrics",
    "title": "Metriche Dispositivo",
    "content": "Basic operating information reported by each node: . | Metrico | Descrizione | . | Battery Level | Current battery percentage | . | Tensione | Battery voltage reading | . | ChUtil | Percentage of local airtime in use | . | AirUtil | Percentage of the last hour this node spent transmitting | . | Tempo di attività | Time since last reboot | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/node-metrics.html#metriche-dispositivo",
    
    "relUrl": "/it-rIT/user/node-metrics.html#metriche-dispositivo"
  },"3153": {
    "doc": "Node Metrics",
    "title": "Metriche Ambientali",
    "content": "Environmental sensor data (requires compatible hardware): . | Metrico | Sensor Examples | . | Temperatura | BME280, BME680, SHT31 | . | Umidità | BME280, BME680, SHT31 | . | Pressione barometrica | BME280, BMP280 | . | Resistenza Ai Gas | BME680 | . | IAQ (Air Quality) | BME680 | . Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted: . 💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/node-metrics.html#metriche-ambientali",
    
    "relUrl": "/it-rIT/user/node-metrics.html#metriche-ambientali"
  },"3154": {
    "doc": "Node Metrics",
    "title": "Air Quality Metrics",
    "content": "Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. | Metrico | Unit | Descrizione | . | PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | . | PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | . | PM10 | µg/m³ | Particulate matter up to 10 microns | . | AQI | EPA index | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated. | . | CO₂ | ppm | Carbon dioxide concentration | . | CO₂ temperature | °C / °F | Temperature reported by the CO₂ sensor itself (e.g. SCD4x) | . | CO₂ humidity | % | Relative humidity reported by the CO₂ sensor | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | Band | CO₂ Range (ppm) | Color | . | Buono | < 1000 | Verde | . | Stuffy | < 2000 | Amber | . | Poor | < 5000 | Orange | . | Unsafe | < 30000 | Rosso | . | Evacuate | ≥ 30000 | Dark red | . An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can: . | Select a time frame for the charts. | Filter with metric chips — only metrics that have data are shown. | Refresh / request the latest air-quality telemetry. | Export to CSV for analysis in a spreadsheet. | . 💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/node-metrics.html#air-quality-metrics",
    
    "relUrl": "/it-rIT/user/node-metrics.html#air-quality-metrics"
  },"3155": {
    "doc": "Node Metrics",
    "title": "Qualità Segnale",
    "content": "Radio signal quality information: . | Metrico | Descrizione | . | SNR | Signal-to-Noise Ratio (higher is better) | . | RSSI | Received Signal Strength Indicator (closer to 0 is better) | . | Noise Floor | Local background RF noise in dBm (more negative is quieter) | . | Conteggio Hop | Number of mesh hops for last message | . Signal Quality Reference . Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | Quality | Criteria | . | Buono | SNR above the preset’s limit | . | Discreto | less than 5.5 dB below the limit | . | Scarso | 5.5 dB to 7.5 dB below the limit | . | Nessuno | more than 7.5 dB below the limit | . See Understanding the Signal Meter for the full explanation. Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment. | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/node-metrics.html#qualit%C3%A0-segnale",
    
    "relUrl": "/it-rIT/user/node-metrics.html#qualità-segnale"
  },"3156": {
    "doc": "Node Metrics",
    "title": "Metriche Alimentazione",
    "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metrico | Descrizione | . | Tensione | Per-channel voltage reading | . | Attuale | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/node-metrics.html#metriche-alimentazione",
    
    "relUrl": "/it-rIT/user/node-metrics.html#metriche-alimentazione"
  },"3157": {
    "doc": "Node Metrics",
    "title": "Traceroute",
    "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | The app sends a traceroute request to the target node. | Results show each hop with its SNR. | . Reading Traceroute Results . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/node-metrics.html#traceroute",
    
    "relUrl": "/it-rIT/user/node-metrics.html#traceroute"
  },"3158": {
    "doc": "Node Metrics",
    "title": "Registro Posizione",
    "content": "Historical position data for nodes that share their location: . | GPS coordinates | Altitudine | Speed (if moving) | Timestamp for each position report | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/node-metrics.html#registro-posizione",
    
    "relUrl": "/it-rIT/user/node-metrics.html#registro-posizione"
  },"3159": {
    "doc": "Node Metrics",
    "title": "Informazioni Vicinato",
    "content": "Shows which nodes a given node can directly hear, useful for understanding mesh topology. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/node-metrics.html#informazioni-vicinato",
    
    "relUrl": "/it-rIT/user/node-metrics.html#informazioni-vicinato"
  },"3160": {
    "doc": "Node Metrics",
    "title": "Metriche Host",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/node-metrics.html#metriche-host",
    
    "relUrl": "/it-rIT/user/node-metrics.html#metriche-host"
  },"3161": {
    "doc": "Node Metrics",
    "title": "Metriche PAX",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/node-metrics.html#metriche-pax",
    
    "relUrl": "/it-rIT/user/node-metrics.html#metriche-pax"
  },"3162": {
    "doc": "Node Metrics",
    "title": "Related Topics",
    "content": ". | Nodes — node list, filtering, and sorting | Telemetry & Sensors — supported sensors and configuration | Signal Meter — how signal quality is calculated from SNR and RSSI | Local Mesh Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/node-metrics.html#related-topics",
    
    "relUrl": "/it-rIT/user/node-metrics.html#related-topics"
  },"3163": {
    "doc": "Node Metrics",
    "title": "Node Metrics",
    "content": "The node detail screen provides comprehensive telemetry and metrics for each node on your mesh. ",
    "url": "/Meshtastic-Android/main/es-rES/user/node-metrics.html",
    
    "relUrl": "/es-rES/user/node-metrics.html"
  },"3164": {
    "doc": "Node Metrics",
    "title": "Viewing Metrics",
    "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings. ",
    "url": "/Meshtastic-Android/main/es-rES/user/node-metrics.html#viewing-metrics",
    
    "relUrl": "/es-rES/user/node-metrics.html#viewing-metrics"
  },"3165": {
    "doc": "Node Metrics",
    "title": "Métricas de Dispositivo",
    "content": "Basic operating information reported by each node: . | Métrico | Descripción | . | Battery Level | Current battery percentage | . | Tensión | Battery voltage reading | . | ChUtil | Percentage of local airtime in use | . | AirUtil | Percentage of the last hour this node spent transmitting | . | Tiempo encendido | Time since last reboot | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/es-rES/user/node-metrics.html#m%C3%A9tricas-de-dispositivo",
    
    "relUrl": "/es-rES/user/node-metrics.html#métricas-de-dispositivo"
  },"3166": {
    "doc": "Node Metrics",
    "title": "Métricas de Entorno",
    "content": "Environmental sensor data (requires compatible hardware): . | Métrico | Sensor Examples | . | Temperatura: | BME280, BME680, SHT31 | . | Humedad | BME280, BME680, SHT31 | . | Presión Barométrica | BME280, BMP280 | . | Resistencia del Gas | BME680 | . | IAQ (Air Quality) | BME680 | . Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted: . 💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors. ",
    "url": "/Meshtastic-Android/main/es-rES/user/node-metrics.html#m%C3%A9tricas-de-entorno",
    
    "relUrl": "/es-rES/user/node-metrics.html#métricas-de-entorno"
  },"3167": {
    "doc": "Node Metrics",
    "title": "Air Quality Metrics",
    "content": "Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. | Métrico | Unit | Descripción | . | PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | . | PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | . | PM10 | µg/m³ | Particulate matter up to 10 microns | . | AQI | EPA index | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated. | . | CO₂ | ppm | Carbon dioxide concentration | . | CO₂ temperature | °C / °F | Temperature reported by the CO₂ sensor itself (e.g. SCD4x) | . | CO₂ humidity | % | Relative humidity reported by the CO₂ sensor | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | Band | CO₂ Range (ppm) | Color | . | Bien | < 1000 | Verde | . | Stuffy | < 2000 | Amber | . | Poor | < 5000 | Orange | . | Unsafe | < 30000 | Rojo | . | Evacuate | ≥ 30000 | Dark red | . An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can: . | Select a time frame for the charts. | Filter with metric chips — only metrics that have data are shown. | Refresh / request the latest air-quality telemetry. | Export to CSV for analysis in a spreadsheet. | . 💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware. ",
    "url": "/Meshtastic-Android/main/es-rES/user/node-metrics.html#air-quality-metrics",
    
    "relUrl": "/es-rES/user/node-metrics.html#air-quality-metrics"
  },"3168": {
    "doc": "Node Metrics",
    "title": "Calidad de señal",
    "content": "Radio signal quality information: . | Métrico | Descripción | . | SNR | Signal-to-Noise Ratio (higher is better) | . | RSSI | Received Signal Strength Indicator (closer to 0 is better) | . | Noise Floor | Local background RF noise in dBm (more negative is quieter) | . | Hop Count | Number of mesh hops for last message | . Signal Quality Reference . Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | Quality | Criteria | . | Bien | SNR above the preset’s limit | . | Aceptable | less than 5.5 dB below the limit | . | Mal | 5.5 dB to 7.5 dB below the limit | . | Ninguna | more than 7.5 dB below the limit | . See Understanding the Signal Meter for the full explanation. Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment. | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/node-metrics.html#calidad-de-se%C3%B1al",
    
    "relUrl": "/es-rES/user/node-metrics.html#calidad-de-señal"
  },"3169": {
    "doc": "Node Metrics",
    "title": "Métricas de Energía",
    "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Métrico | Descripción | . | Tensión | Per-channel voltage reading | . | Intensidad | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/es-rES/user/node-metrics.html#m%C3%A9tricas-de-energ%C3%ADa",
    
    "relUrl": "/es-rES/user/node-metrics.html#métricas-de-energía"
  },"3170": {
    "doc": "Node Metrics",
    "title": "Traceroute",
    "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | The app sends a traceroute request to the target node. | Results show each hop with its SNR. | . Reading Traceroute Results . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/es-rES/user/node-metrics.html#traceroute",
    
    "relUrl": "/es-rES/user/node-metrics.html#traceroute"
  },"3171": {
    "doc": "Node Metrics",
    "title": "Registro de Posiciones",
    "content": "Historical position data for nodes that share their location: . | GPS coordinates | Altitud | Speed (if moving) | Timestamp for each position report | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/node-metrics.html#registro-de-posiciones",
    
    "relUrl": "/es-rES/user/node-metrics.html#registro-de-posiciones"
  },"3172": {
    "doc": "Node Metrics",
    "title": "Información de Vecinos",
    "content": "Shows which nodes a given node can directly hear, useful for understanding mesh topology. ",
    "url": "/Meshtastic-Android/main/es-rES/user/node-metrics.html#informaci%C3%B3n-de-vecinos",
    
    "relUrl": "/es-rES/user/node-metrics.html#información-de-vecinos"
  },"3173": {
    "doc": "Node Metrics",
    "title": "Métricas del anfitrión",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/es-rES/user/node-metrics.html#m%C3%A9tricas-del-anfitri%C3%B3n",
    
    "relUrl": "/es-rES/user/node-metrics.html#métricas-del-anfitrión"
  },"3174": {
    "doc": "Node Metrics",
    "title": "PAX Metrics",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/es-rES/user/node-metrics.html#pax-metrics",
    
    "relUrl": "/es-rES/user/node-metrics.html#pax-metrics"
  },"3175": {
    "doc": "Node Metrics",
    "title": "Related Topics",
    "content": ". | Nodes — node list, filtering, and sorting | Telemetry & Sensors — supported sensors and configuration | Signal Meter — how signal quality is calculated from SNR and RSSI | Local Mesh Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/node-metrics.html#related-topics",
    
    "relUrl": "/es-rES/user/node-metrics.html#related-topics"
  },"3176": {
    "doc": "Node Metrics",
    "title": "Node Metrics",
    "content": "The node detail screen provides comprehensive telemetry and metrics for each node on your mesh. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/node-metrics.html",
    
    "relUrl": "/sl-rSI/user/node-metrics.html"
  },"3177": {
    "doc": "Node Metrics",
    "title": "Viewing Metrics",
    "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/node-metrics.html#viewing-metrics",
    
    "relUrl": "/sl-rSI/user/node-metrics.html#viewing-metrics"
  },"3178": {
    "doc": "Node Metrics",
    "title": "Device Metrics",
    "content": "Basic operating information reported by each node: . | Metric | Opis | . | Battery Level | Current battery percentage | . | Voltage | Battery voltage reading | . | ChUtil | Percentage of local airtime in use | . | AirUtil | Percentage of the last hour this node spent transmitting | . | Uptime | Time since last reboot | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/node-metrics.html#device-metrics",
    
    "relUrl": "/sl-rSI/user/node-metrics.html#device-metrics"
  },"3179": {
    "doc": "Node Metrics",
    "title": "Environment Metrics",
    "content": "Environmental sensor data (requires compatible hardware): . | Metric | Sensor Examples | . | Temperatura | BME280, BME680, SHT31 | . | Vlaga | BME280, BME680, SHT31 | . | Barometric Pressure | BME280, BMP280 | . | Gas Resistance | BME680 | . | IAQ (Air Quality) | BME680 | . Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted: . 💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/node-metrics.html#environment-metrics",
    
    "relUrl": "/sl-rSI/user/node-metrics.html#environment-metrics"
  },"3180": {
    "doc": "Node Metrics",
    "title": "Air Quality Metrics",
    "content": "Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. | Metric | Unit | Opis | . | PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | . | PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | . | PM10 | µg/m³ | Particulate matter up to 10 microns | . | AQI | EPA index | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated. | . | CO₂ | ppm | Carbon dioxide concentration | . | CO₂ temperature | °C / °F | Temperature reported by the CO₂ sensor itself (e.g. SCD4x) | . | CO₂ humidity | % | Relative humidity reported by the CO₂ sensor | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | Band | CO₂ Range (ppm) | Color | . | Dober | < 1000 | Green | . | Stuffy | < 2000 | Amber | . | Poor | < 5000 | Orange | . | Unsafe | < 30000 | Red | . | Evacuate | ≥ 30000 | Dark red | . An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can: . | Select a time frame for the charts. | Filter with metric chips — only metrics that have data are shown. | Refresh / request the latest air-quality telemetry. | Export to CSV for analysis in a spreadsheet. | . 💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/node-metrics.html#air-quality-metrics",
    
    "relUrl": "/sl-rSI/user/node-metrics.html#air-quality-metrics"
  },"3181": {
    "doc": "Node Metrics",
    "title": "Kakovost signala",
    "content": "Radio signal quality information: . | Metric | Opis | . | SNR | Signal-to-Noise Ratio (higher is better) | . | RSSI | Received Signal Strength Indicator (closer to 0 is better) | . | Noise Floor | Local background RF noise in dBm (more negative is quieter) | . | Hop Count | Number of mesh hops for last message | . Signal Quality Reference . Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | Quality | Criteria | . | Dober | SNR above the preset’s limit | . | Precejšen | less than 5.5 dB below the limit | . | Slab | 5.5 dB to 7.5 dB below the limit | . | Brez | more than 7.5 dB below the limit | . See Understanding the Signal Meter for the full explanation. Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment. | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/node-metrics.html#kakovost-signala",
    
    "relUrl": "/sl-rSI/user/node-metrics.html#kakovost-signala"
  },"3182": {
    "doc": "Node Metrics",
    "title": "Power Metrics",
    "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Opis | . | Voltage | Per-channel voltage reading | . | Current | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/node-metrics.html#power-metrics",
    
    "relUrl": "/sl-rSI/user/node-metrics.html#power-metrics"
  },"3183": {
    "doc": "Node Metrics",
    "title": "Pot",
    "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | The app sends a traceroute request to the target node. | Results show each hop with its SNR. | . Reading Traceroute Results . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/node-metrics.html#pot",
    
    "relUrl": "/sl-rSI/user/node-metrics.html#pot"
  },"3184": {
    "doc": "Node Metrics",
    "title": "Dnevnik lokacije",
    "content": "Historical position data for nodes that share their location: . | GPS coordinates | Altitude | Speed (if moving) | Timestamp for each position report | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/node-metrics.html#dnevnik-lokacije",
    
    "relUrl": "/sl-rSI/user/node-metrics.html#dnevnik-lokacije"
  },"3185": {
    "doc": "Node Metrics",
    "title": "Neighbor Info",
    "content": "Shows which nodes a given node can directly hear, useful for understanding mesh topology. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/node-metrics.html#neighbor-info",
    
    "relUrl": "/sl-rSI/user/node-metrics.html#neighbor-info"
  },"3186": {
    "doc": "Node Metrics",
    "title": "Host Metrics",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/node-metrics.html#host-metrics",
    
    "relUrl": "/sl-rSI/user/node-metrics.html#host-metrics"
  },"3187": {
    "doc": "Node Metrics",
    "title": "PAX Metrics",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/node-metrics.html#pax-metrics",
    
    "relUrl": "/sl-rSI/user/node-metrics.html#pax-metrics"
  },"3188": {
    "doc": "Node Metrics",
    "title": "Related Topics",
    "content": ". | Nodes — node list, filtering, and sorting | Telemetry & Sensors — supported sensors and configuration | Signal Meter — how signal quality is calculated from SNR and RSSI | Local Mesh Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/node-metrics.html#related-topics",
    
    "relUrl": "/sl-rSI/user/node-metrics.html#related-topics"
  },"3189": {
    "doc": "Node Metrics",
    "title": "Node Metrics",
    "content": "The node detail screen provides comprehensive telemetry and metrics for each node on your mesh. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/node-metrics.html",
    
    "relUrl": "/no-rNO/user/node-metrics.html"
  },"3190": {
    "doc": "Node Metrics",
    "title": "Viewing Metrics",
    "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/node-metrics.html#viewing-metrics",
    
    "relUrl": "/no-rNO/user/node-metrics.html#viewing-metrics"
  },"3191": {
    "doc": "Node Metrics",
    "title": "Device Metrics",
    "content": "Basic operating information reported by each node: . | Metric | Beskrivelse | . | Battery Level | Current battery percentage | . | Voltage | Battery voltage reading | . | ChUtil | Percentage of local airtime in use | . | AirUtil | Percentage of the last hour this node spent transmitting | . | Uptime | Time since last reboot | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/node-metrics.html#device-metrics",
    
    "relUrl": "/no-rNO/user/node-metrics.html#device-metrics"
  },"3192": {
    "doc": "Node Metrics",
    "title": "Environment Metrics",
    "content": "Environmental sensor data (requires compatible hardware): . | Metric | Sensor Examples | . | Temperatur | BME280, BME680, SHT31 | . | Luftfuktighet | BME280, BME680, SHT31 | . | Barometric Pressure | BME280, BMP280 | . | Gas Resistance | BME680 | . | IAQ (Air Quality) | BME680 | . Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted: . 💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/node-metrics.html#environment-metrics",
    
    "relUrl": "/no-rNO/user/node-metrics.html#environment-metrics"
  },"3193": {
    "doc": "Node Metrics",
    "title": "Air Quality Metrics",
    "content": "Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. | Metric | Unit | Beskrivelse | . | PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | . | PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | . | PM10 | µg/m³ | Particulate matter up to 10 microns | . | AQI | EPA index | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated. | . | CO₂ | ppm | Carbon dioxide concentration | . | CO₂ temperature | °C / °F | Temperature reported by the CO₂ sensor itself (e.g. SCD4x) | . | CO₂ humidity | % | Relative humidity reported by the CO₂ sensor | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | Band | CO₂ Range (ppm) | Color | . | Godt | < 1000 | Green | . | Stuffy | < 2000 | Amber | . | Poor | < 5000 | Orange | . | Unsafe | < 30000 | Red | . | Evacuate | ≥ 30000 | Dark red | . An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can: . | Select a time frame for the charts. | Filter with metric chips — only metrics that have data are shown. | Refresh / request the latest air-quality telemetry. | Export to CSV for analysis in a spreadsheet. | . 💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/node-metrics.html#air-quality-metrics",
    
    "relUrl": "/no-rNO/user/node-metrics.html#air-quality-metrics"
  },"3194": {
    "doc": "Node Metrics",
    "title": "Signalstyrke",
    "content": "Radio signal quality information: . | Metric | Beskrivelse | . | SNR | Signal-to-Noise Ratio (higher is better) | . | RSSI | Received Signal Strength Indicator (closer to 0 is better) | . | Noise Floor | Local background RF noise in dBm (more negative is quieter) | . | Hop Count | Number of mesh hops for last message | . Signal Quality Reference . Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | Quality | Criteria | . | Godt | SNR above the preset’s limit | . | Middelmådig | less than 5.5 dB below the limit | . | Dårlig | 5.5 dB to 7.5 dB below the limit | . | Ingen | more than 7.5 dB below the limit | . See Understanding the Signal Meter for the full explanation. Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment. | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/node-metrics.html#signalstyrke",
    
    "relUrl": "/no-rNO/user/node-metrics.html#signalstyrke"
  },"3195": {
    "doc": "Node Metrics",
    "title": "Power Metrics",
    "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Beskrivelse | . | Voltage | Per-channel voltage reading | . | Current | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/node-metrics.html#power-metrics",
    
    "relUrl": "/no-rNO/user/node-metrics.html#power-metrics"
  },"3196": {
    "doc": "Node Metrics",
    "title": "Traceroute",
    "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | The app sends a traceroute request to the target node. | Results show each hop with its SNR. | . Reading Traceroute Results . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/node-metrics.html#traceroute",
    
    "relUrl": "/no-rNO/user/node-metrics.html#traceroute"
  },"3197": {
    "doc": "Node Metrics",
    "title": "Posisjonslogg",
    "content": "Historical position data for nodes that share their location: . | GPS coordinates | Altitude | Speed (if moving) | Timestamp for each position report | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/node-metrics.html#posisjonslogg",
    
    "relUrl": "/no-rNO/user/node-metrics.html#posisjonslogg"
  },"3198": {
    "doc": "Node Metrics",
    "title": "Neighbor Info",
    "content": "Shows which nodes a given node can directly hear, useful for understanding mesh topology. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/node-metrics.html#neighbor-info",
    
    "relUrl": "/no-rNO/user/node-metrics.html#neighbor-info"
  },"3199": {
    "doc": "Node Metrics",
    "title": "Host Metrics",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/node-metrics.html#host-metrics",
    
    "relUrl": "/no-rNO/user/node-metrics.html#host-metrics"
  },"3200": {
    "doc": "Node Metrics",
    "title": "PAX Metrics",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/node-metrics.html#pax-metrics",
    
    "relUrl": "/no-rNO/user/node-metrics.html#pax-metrics"
  },"3201": {
    "doc": "Node Metrics",
    "title": "Related Topics",
    "content": ". | Nodes — node list, filtering, and sorting | Telemetry & Sensors — supported sensors and configuration | Signal Meter — how signal quality is calculated from SNR and RSSI | Local Mesh Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/node-metrics.html#related-topics",
    
    "relUrl": "/no-rNO/user/node-metrics.html#related-topics"
  },"3202": {
    "doc": "Node Metrics",
    "title": "Node Metrics",
    "content": "The node detail screen provides comprehensive telemetry and metrics for each node on your mesh. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/node-metrics.html",
    
    "relUrl": "/hu-rHU/user/node-metrics.html"
  },"3203": {
    "doc": "Node Metrics",
    "title": "Viewing Metrics",
    "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/node-metrics.html#viewing-metrics",
    
    "relUrl": "/hu-rHU/user/node-metrics.html#viewing-metrics"
  },"3204": {
    "doc": "Node Metrics",
    "title": "Eszközmetrikák",
    "content": "Basic operating information reported by each node: . | Metric | Leírás | . | Battery Level | Current battery percentage | . | Feszültség | Battery voltage reading | . | ChUtil | Percentage of local airtime in use | . | AirUtil | Percentage of the last hour this node spent transmitting | . | Működési idő | Time since last reboot | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/node-metrics.html#eszk%C3%B6zmetrik%C3%A1k",
    
    "relUrl": "/hu-rHU/user/node-metrics.html#eszközmetrikák"
  },"3205": {
    "doc": "Node Metrics",
    "title": "Környezeti metrikák",
    "content": "Environmental sensor data (requires compatible hardware): . | Metric | Sensor Examples | . | Hőmérséklet | BME280, BME680, SHT31 | . | Páratartalom | BME280, BME680, SHT31 | . | Légnyomás | BME280, BMP280 | . | Gázellenállás | BME680 | . | IAQ (Air Quality) | BME680 | . Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted: . 💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/node-metrics.html#k%C3%B6rnyezeti-metrik%C3%A1k",
    
    "relUrl": "/hu-rHU/user/node-metrics.html#környezeti-metrikák"
  },"3206": {
    "doc": "Node Metrics",
    "title": "Air Quality Metrics",
    "content": "Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. | Metric | Unit | Leírás | . | PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | . | PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | . | PM10 | µg/m³ | Particulate matter up to 10 microns | . | AQI | EPA index | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated. | . | CO₂ | ppm | Carbon dioxide concentration | . | CO₂ temperature | °C / °F | Temperature reported by the CO₂ sensor itself (e.g. SCD4x) | . | CO₂ humidity | % | Relative humidity reported by the CO₂ sensor | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | Band | CO₂ Range (ppm) | Color | . | Jó | < 1000 | Zöld | . | Stuffy | < 2000 | Amber | . | Poor | < 5000 | Orange | . | Unsafe | < 30000 | Piros | . | Evacuate | ≥ 30000 | Dark red | . An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can: . | Select a time frame for the charts. | Filter with metric chips — only metrics that have data are shown. | Refresh / request the latest air-quality telemetry. | Export to CSV for analysis in a spreadsheet. | . 💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/node-metrics.html#air-quality-metrics",
    
    "relUrl": "/hu-rHU/user/node-metrics.html#air-quality-metrics"
  },"3207": {
    "doc": "Node Metrics",
    "title": "Jelminőség",
    "content": "Radio signal quality information: . | Metric | Leírás | . | SNR | Signal-to-Noise Ratio (higher is better) | . | RSSI | Received Signal Strength Indicator (closer to 0 is better) | . | Noise Floor | Local background RF noise in dBm (more negative is quieter) | . | Hop Count | Number of mesh hops for last message | . Signal Quality Reference . Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | Quality | Criteria | . | Jó | SNR above the preset’s limit | . | Megfelelő | less than 5.5 dB below the limit | . | Rossz | 5.5 dB to 7.5 dB below the limit | . | Semmi | more than 7.5 dB below the limit | . See Understanding the Signal Meter for the full explanation. Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment. | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/node-metrics.html#jelmin%C5%91s%C3%A9g",
    
    "relUrl": "/hu-rHU/user/node-metrics.html#jelminőség"
  },"3208": {
    "doc": "Node Metrics",
    "title": "Tápellátási metrikák",
    "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Leírás | . | Feszültség | Per-channel voltage reading | . | Áramerősség | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/node-metrics.html#t%C3%A1pell%C3%A1t%C3%A1si-metrik%C3%A1k",
    
    "relUrl": "/hu-rHU/user/node-metrics.html#tápellátási-metrikák"
  },"3209": {
    "doc": "Node Metrics",
    "title": "Traceroute",
    "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | The app sends a traceroute request to the target node. | Results show each hop with its SNR. | . Reading Traceroute Results . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/node-metrics.html#traceroute",
    
    "relUrl": "/hu-rHU/user/node-metrics.html#traceroute"
  },"3210": {
    "doc": "Node Metrics",
    "title": "Pozíciónapló",
    "content": "Historical position data for nodes that share their location: . | GPS coordinates | Magasság | Speed (if moving) | Timestamp for each position report | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/node-metrics.html#poz%C3%ADci%C3%B3napl%C3%B3",
    
    "relUrl": "/hu-rHU/user/node-metrics.html#pozíciónapló"
  },"3211": {
    "doc": "Node Metrics",
    "title": "Szomszéd-információ",
    "content": "Shows which nodes a given node can directly hear, useful for understanding mesh topology. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/node-metrics.html#szomsz%C3%A9d-inform%C3%A1ci%C3%B3",
    
    "relUrl": "/hu-rHU/user/node-metrics.html#szomszéd-információ"
  },"3212": {
    "doc": "Node Metrics",
    "title": "Host Metrics",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/node-metrics.html#host-metrics",
    
    "relUrl": "/hu-rHU/user/node-metrics.html#host-metrics"
  },"3213": {
    "doc": "Node Metrics",
    "title": "PAX Metrics",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/node-metrics.html#pax-metrics",
    
    "relUrl": "/hu-rHU/user/node-metrics.html#pax-metrics"
  },"3214": {
    "doc": "Node Metrics",
    "title": "Related Topics",
    "content": ". | Nodes — node list, filtering, and sorting | Telemetry & Sensors — supported sensors and configuration | Signal Meter — how signal quality is calculated from SNR and RSSI | Local Mesh Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/node-metrics.html#related-topics",
    
    "relUrl": "/hu-rHU/user/node-metrics.html#related-topics"
  },"3215": {
    "doc": "Метрики ноды",
    "title": "Метрики ноды",
    "content": "Экран сведений о ноде предоставляет подробную телеметрию и метрики для каждой ноды твоей mesh-сети. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/node-metrics.html",
    
    "relUrl": "/ru-rRU/user/node-metrics.html"
  },"3216": {
    "doc": "Метрики ноды",
    "title": "Просмотр метрик",
    "content": ". | Перейдите в раздел Ноды. | Нажмите на ноду, которую хотите просмотреть. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. Метрики обновляются с интервалами, настроенными в параметрах телеметрии каждой ноды. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/node-metrics.html#%D0%BF%D1%80%D0%BE%D1%81%D0%BC%D0%BE%D1%82%D1%80-%D0%BC%D0%B5%D1%82%D1%80%D0%B8%D0%BA",
    
    "relUrl": "/ru-rRU/user/node-metrics.html#просмотр-метрик"
  },"3217": {
    "doc": "Метрики ноды",
    "title": "Интервал передачи",
    "content": "Основная информация о работе, сообщаемая каждой нодой: . | Метрическая | Описание | . | Уровень заряда | Текущий процент заряда батареи | . | Напряжение | Показания напряжения батареи | . | ChUtil | Percentage of local airtime in use | . | AirUtil | Percentage of the last hour this node spent transmitting | . | Аптайм | Время с момента последней перезагрузки | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/node-metrics.html#%D0%B8%D0%BD%D1%82%D0%B5%D1%80%D0%B2%D0%B0%D0%BB-%D0%BF%D0%B5%D1%80%D0%B5%D0%B4%D0%B0%D1%87%D0%B8",
    
    "relUrl": "/ru-rRU/user/node-metrics.html#интервал-передачи"
  },"3218": {
    "doc": "Метрики ноды",
    "title": "Метрики окружения",
    "content": "Данные датчиков окружающей среды (требуется совместимое оборудование): . | Метрическая | Примеры сенсоров | . | Температура | BME280, BME680, SHT31 | . | Влажность | BME280, BME680, SHT31 | . | Давление на барометре | BME280, BMP280 | . | Сопротивление газа | BME680 | . | IAQ (Качества воздуха) | BME680 | . Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. Индекс IAQ (качество воздуха в помещении) датчика BME680 представляет собой единое значение от 0 до 500+, полученное на основе сопротивления газа, и отображается на цветовой шкале от “Отлично” до “Опасно загрязнён”: . 💡 Совет: Для получения метрик окружающей среды к удалённой ноде должен быть подключён датчик. Не все ноды передают данные об окружающей среде. См. Телеметрия и датчики для получения полного списка поддерживаемых датчиков. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/node-metrics.html#%D0%BC%D0%B5%D1%82%D1%80%D0%B8%D0%BA%D0%B8-%D0%BE%D0%BA%D1%80%D1%83%D0%B6%D0%B5%D0%BD%D0%B8%D1%8F",
    
    "relUrl": "/ru-rRU/user/node-metrics.html#метрики-окружения"
  },"3219": {
    "doc": "Метрики ноды",
    "title": "Метрики качества воздуха",
    "content": "Качество воздуха — это отдельный экран метрик для нод, оснащённых датчиком взвешенных частиц и/или CO₂. Этот экран отделён от показателя IAQ датчика BME680, отображаемого в разделе “Метрики окружающей среды” — IAQ представляет собой единый индекс, основанный на сопротивлении газа, тогда как экран качества воздуха показывает графики исходных измерений взвешенных частиц и CO₂. | Метрическая | Единица | Описание | . | PM1.0 | мкг/м³ | Взвешенные частицы размером до 1,0 микрона | . | PM2.5 | мкг/м³ | Взвешенные частицы размером до 2,5 микрона | . | PM10 | мкг/м³ | Взвешенные частицы размером до 10 микронов | . | AQI | Индекс EPA | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Отображается рядом с PM2.5, как только накопится достаточно показаний. | . | CO₂ | ppm | Концентрация углекислого газа | . | Температура CO₂ | °C / °F | Температура, сообщаемая самим датчиком CO₂ (например, SCD4x) | . | Влажность CO₂ | % | Относительная влажность, сообщаемая датчиком CO₂ | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | Диапазон | Диапазон CO₂ (ppm) | Цвет | . | Хороший | < 1000 | Зеленый | . | Душно | < 2000 | Янтарный | . | Плохо | < 5000 | Оранжевый | . | Небезопасно | < 30000 | Красный | . | Эвакуация | ≥ 30000 | Тёмно-красный | . Кнопка журнала/метрик качества воздуха появляется на экране сведений о ноде только в том случае, если нода передала телеметрию о качестве воздуха. В режиме просмотра качества воздуха ты можешь: . | Выбрать временной интервал для графиков. | Фильтровать с помощью кнопок метрик — отображаются только те метрики, по которым есть данные. | Обновить / запросить последнюю телеметрию о качестве воздуха. | Экспортировать в CSV для анализа в электронных таблицах. | . 💡 Совет: Для получения метрик качества воздуха на удалённой ноде должен быть установлен совместимый датчик. См. Телеметрия и датчики для получения информации о поддерживаемом оборудовании. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/node-metrics.html#%D0%BC%D0%B5%D1%82%D1%80%D0%B8%D0%BA%D0%B8-%D0%BA%D0%B0%D1%87%D0%B5%D1%81%D1%82%D0%B2%D0%B0-%D0%B2%D0%BE%D0%B7%D0%B4%D1%83%D1%85%D0%B0",
    
    "relUrl": "/ru-rRU/user/node-metrics.html#метрики-качества-воздуха"
  },"3220": {
    "doc": "Метрики ноды",
    "title": "Качество сигнала",
    "content": "Информация о качестве радиосигнала: . | Метрическая | Описание | . | Сигнал/шум | Отношение сигнал/шум (SNR) (чем выше, тем лучше) | . | RSSI | Индикатор уровня принимаемого сигнала (Rssi) (чем ближе к 0, тем лучше) | . | Уровень собственных шумов | Местный фоновый радиочастотный шум в дБм (чем более отрицательное значение, тем тише) | . | Количество хопов | Количество хопов в mesh-сети для последнего сообщения | . Оценка качества сигнала . Качество сигнала оценивается по SNR относительно минимального уровня демодуляции активного пресета LoRa-модема, а не по фиксированным порогам — конкретное значение SNR означает разное на разных пресетах (например, −15 дБ нормально для LongSlow, но неприемлемо для ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | Качество | Критерии | . | Хороший | SNR выше предела пресета | . | Средний | менее чем на 5,5 дБ ниже предела | . | Плохой | от 5,5 до 7,5 дБ ниже предела | . | Отсутствует | более чем на 7,5 дБ ниже предела | . См. Понимание измерителя сигнала для полного объяснения. Локальная статистика твоего подключённого радио также отображается в разделе “Качество сигнала”, когда она доступна. Эти журналы включают уровень шума, счётчики трафика, счётчики ретрансляций, количество нод в сети и время работы радио. График уровня шума использует пунктирную опорную линию на уровне -85 дБм, чтобы помочь определить загруженность радиоэфира. | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/node-metrics.html#%D0%BA%D0%B0%D1%87%D0%B5%D1%81%D1%82%D0%B2%D0%BE-%D1%81%D0%B8%D0%B3%D0%BD%D0%B0%D0%BB%D0%B0",
    
    "relUrl": "/ru-rRU/user/node-metrics.html#качество-сигнала"
  },"3221": {
    "doc": "Метрики ноды",
    "title": "Метрики питания",
    "content": "Телеметрия управления питанием (требуется датчик INA или совместимое оборудование): . | Метрическая | Описание | . | Напряжение | Per-channel voltage reading | . | Ток | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/node-metrics.html#%D0%BC%D0%B5%D1%82%D1%80%D0%B8%D0%BA%D0%B8-%D0%BF%D0%B8%D1%82%D0%B0%D0%BD%D0%B8%D1%8F",
    
    "relUrl": "/ru-rRU/user/node-metrics.html#метрики-питания"
  },"3222": {
    "doc": "Метрики ноды",
    "title": "Трассировка маршрута",
    "content": "Трассировка показывает путь сообщения через mesh-сеть: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | Приложение отправляет запрос трассировки целевой ноде. | Results show each hop with its SNR. | . Чтение результатов трассировки . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/node-metrics.html#%D1%82%D1%80%D0%B0%D1%81%D1%81%D0%B8%D1%80%D0%BE%D0%B2%D0%BA%D0%B0-%D0%BC%D0%B0%D1%80%D1%88%D1%80%D1%83%D1%82%D0%B0",
    
    "relUrl": "/ru-rRU/user/node-metrics.html#трассировка-маршрута"
  },"3223": {
    "doc": "Метрики ноды",
    "title": "Журнал местоположения",
    "content": "Исторические данные о местоположении для нод, которые делятся своими координатами: . | GPS координаты | Высота | Скорость (при движении) | Временная метка для каждого отчёта о местоположении | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/node-metrics.html#%D0%B6%D1%83%D1%80%D0%BD%D0%B0%D0%BB-%D0%BC%D0%B5%D1%81%D1%82%D0%BE%D0%BF%D0%BE%D0%BB%D0%BE%D0%B6%D0%B5%D0%BD%D0%B8%D1%8F",
    
    "relUrl": "/ru-rRU/user/node-metrics.html#журнал-местоположения"
  },"3224": {
    "doc": "Метрики ноды",
    "title": "Информация об окружении",
    "content": "Показывает, какие ноды данная нода может слышать напрямую — полезно для понимания топологии mesh-сети. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/node-metrics.html#%D0%B8%D0%BD%D1%84%D0%BE%D1%80%D0%BC%D0%B0%D1%86%D0%B8%D1%8F-%D0%BE%D0%B1-%D0%BE%D0%BA%D1%80%D1%83%D0%B6%D0%B5%D0%BD%D0%B8%D0%B8",
    
    "relUrl": "/ru-rRU/user/node-metrics.html#информация-об-окружении"
  },"3225": {
    "doc": "Метрики ноды",
    "title": "Метрики хоста",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/node-metrics.html#%D0%BC%D0%B5%D1%82%D1%80%D0%B8%D0%BA%D0%B8-%D1%85%D0%BE%D1%81%D1%82%D0%B0",
    
    "relUrl": "/ru-rRU/user/node-metrics.html#метрики-хоста"
  },"3226": {
    "doc": "Метрики ноды",
    "title": "Метрика прохожих",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/node-metrics.html#%D0%BC%D0%B5%D1%82%D1%80%D0%B8%D0%BA%D0%B0-%D0%BF%D1%80%D0%BE%D1%85%D0%BE%D0%B6%D0%B8%D1%85",
    
    "relUrl": "/ru-rRU/user/node-metrics.html#метрика-прохожих"
  },"3227": {
    "doc": "Метрики ноды",
    "title": "Связанные темы",
    "content": ". | Ноды — список нод, фильтрация и сортировка | Телеметрия и датчики — поддерживаемые датчики и настройка | Измеритель сигнал — как рассчитывается качество сигнала на основе SNR и RSSI | Local Mesh Discovery — traceroute details and neighbor info | Единицы измерения и регион — форматы отображения температуры, расстояния и скорости | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/node-metrics.html#%D1%81%D0%B2%D1%8F%D0%B7%D0%B0%D0%BD%D0%BD%D1%8B%D0%B5-%D1%82%D0%B5%D0%BC%D1%8B",
    
    "relUrl": "/ru-rRU/user/node-metrics.html#связанные-темы"
  },"3228": {
    "doc": "Node Metrics",
    "title": "Node Metrics",
    "content": "The node detail screen provides comprehensive telemetry and metrics for each node on your mesh. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/node-metrics.html",
    
    "relUrl": "/cs-rCZ/user/node-metrics.html"
  },"3229": {
    "doc": "Node Metrics",
    "title": "Viewing Metrics",
    "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/node-metrics.html#viewing-metrics",
    
    "relUrl": "/cs-rCZ/user/node-metrics.html#viewing-metrics"
  },"3230": {
    "doc": "Node Metrics",
    "title": "Metriky zařízení",
    "content": "Basic operating information reported by each node: . | Metrický | Popis | . | Battery Level | Current battery percentage | . | Napětí | Battery voltage reading | . | ChUtil | Percentage of local airtime in use | . | AirUtil | Percentage of the last hour this node spent transmitting | . | Doba provozu | Time since last reboot | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/node-metrics.html#metriky-za%C5%99%C3%ADzen%C3%AD",
    
    "relUrl": "/cs-rCZ/user/node-metrics.html#metriky-zařízení"
  },"3231": {
    "doc": "Node Metrics",
    "title": "Metriky prostředí",
    "content": "Environmental sensor data (requires compatible hardware): . | Metrický | Sensor Examples | . | Teplota | BME280, BME680, SHT31 | . | Vlhkost | BME280, BME680, SHT31 | . | Barometrický tlak | BME280, BMP280 | . | Odpor plynu | BME680 | . | IAQ (Air Quality) | BME680 | . Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted: . 💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/node-metrics.html#metriky-prost%C5%99ed%C3%AD",
    
    "relUrl": "/cs-rCZ/user/node-metrics.html#metriky-prostředí"
  },"3232": {
    "doc": "Node Metrics",
    "title": "Air Quality Metrics",
    "content": "Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. | Metrický | Unit | Popis | . | PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | . | PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | . | PM10 | µg/m³ | Particulate matter up to 10 microns | . | AQI | EPA index | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated. | . | CO₂ | ppm | Carbon dioxide concentration | . | CO₂ temperature | °C / °F | Temperature reported by the CO₂ sensor itself (e.g. SCD4x) | . | CO₂ humidity | % | Relative humidity reported by the CO₂ sensor | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | Band | CO₂ Range (ppm) | Color | . | Silný | < 1000 | Zelená | . | Stuffy | < 2000 | Amber | . | Poor | < 5000 | Orange | . | Unsafe | < 30000 | Červená | . | Evacuate | ≥ 30000 | Dark red | . An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can: . | Select a time frame for the charts. | Filter with metric chips — only metrics that have data are shown. | Refresh / request the latest air-quality telemetry. | Export to CSV for analysis in a spreadsheet. | . 💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/node-metrics.html#air-quality-metrics",
    
    "relUrl": "/cs-rCZ/user/node-metrics.html#air-quality-metrics"
  },"3233": {
    "doc": "Node Metrics",
    "title": "Kvalita signálu",
    "content": "Radio signal quality information: . | Metrický | Popis | . | SNR | Signal-to-Noise Ratio (higher is better) | . | RSSI | Received Signal Strength Indicator (closer to 0 is better) | . | Noise Floor | Local background RF noise in dBm (more negative is quieter) | . | Hop Count | Number of mesh hops for last message | . Signal Quality Reference . Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | Quality | Criteria | . | Silný | SNR above the preset’s limit | . | Slabý | less than 5.5 dB below the limit | . | Špatný | 5.5 dB to 7.5 dB below the limit | . | Žádný | more than 7.5 dB below the limit | . See Understanding the Signal Meter for the full explanation. Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment. | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/node-metrics.html#kvalita-sign%C3%A1lu",
    
    "relUrl": "/cs-rCZ/user/node-metrics.html#kvalita-signálu"
  },"3234": {
    "doc": "Node Metrics",
    "title": "Metriky napájení",
    "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metrický | Popis | . | Napětí | Per-channel voltage reading | . | Proud | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/node-metrics.html#metriky-nap%C3%A1jen%C3%AD",
    
    "relUrl": "/cs-rCZ/user/node-metrics.html#metriky-napájení"
  },"3235": {
    "doc": "Node Metrics",
    "title": "Traceroute",
    "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | The app sends a traceroute request to the target node. | Results show each hop with its SNR. | . Reading Traceroute Results . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/node-metrics.html#traceroute",
    
    "relUrl": "/cs-rCZ/user/node-metrics.html#traceroute"
  },"3236": {
    "doc": "Node Metrics",
    "title": "Protokol pozic",
    "content": "Historical position data for nodes that share their location: . | GPS coordinates | Nadm. výška | Speed (if moving) | Timestamp for each position report | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/node-metrics.html#protokol-pozic",
    
    "relUrl": "/cs-rCZ/user/node-metrics.html#protokol-pozic"
  },"3237": {
    "doc": "Node Metrics",
    "title": "Informace o sousedech",
    "content": "Shows which nodes a given node can directly hear, useful for understanding mesh topology. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/node-metrics.html#informace-o-sousedech",
    
    "relUrl": "/cs-rCZ/user/node-metrics.html#informace-o-sousedech"
  },"3238": {
    "doc": "Node Metrics",
    "title": "Metriky hostitele",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/node-metrics.html#metriky-hostitele",
    
    "relUrl": "/cs-rCZ/user/node-metrics.html#metriky-hostitele"
  },"3239": {
    "doc": "Node Metrics",
    "title": "Metriky PAX",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/node-metrics.html#metriky-pax",
    
    "relUrl": "/cs-rCZ/user/node-metrics.html#metriky-pax"
  },"3240": {
    "doc": "Node Metrics",
    "title": "Related Topics",
    "content": ". | Nodes — node list, filtering, and sorting | Telemetry & Sensors — supported sensors and configuration | Signal Meter — how signal quality is calculated from SNR and RSSI | Local Mesh Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/node-metrics.html#related-topics",
    
    "relUrl": "/cs-rCZ/user/node-metrics.html#related-topics"
  },"3241": {
    "doc": "Node Metrics",
    "title": "Node Metrics",
    "content": "The node detail screen provides comprehensive telemetry and metrics for each node on your mesh. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/node-metrics.html",
    
    "relUrl": "/bg-rBG/user/node-metrics.html"
  },"3242": {
    "doc": "Node Metrics",
    "title": "Viewing Metrics",
    "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/node-metrics.html#viewing-metrics",
    
    "relUrl": "/bg-rBG/user/node-metrics.html#viewing-metrics"
  },"3243": {
    "doc": "Node Metrics",
    "title": "Метрики на устройството",
    "content": "Basic operating information reported by each node: . | Метрични | Описание | . | Battery Level | Current battery percentage | . | Напрежение | Battery voltage reading | . | Изпол. на канала | Percentage of local airtime in use | . | Изпол. на ефира | Percentage of the last hour this node spent transmitting | . | Време на работа | Time since last reboot | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/node-metrics.html#%D0%BC%D0%B5%D1%82%D1%80%D0%B8%D0%BA%D0%B8-%D0%BD%D0%B0-%D1%83%D1%81%D1%82%D1%80%D0%BE%D0%B9%D1%81%D1%82%D0%B2%D0%BE%D1%82%D0%BE",
    
    "relUrl": "/bg-rBG/user/node-metrics.html#метрики-на-устройството"
  },"3244": {
    "doc": "Node Metrics",
    "title": "Показатели на околната среда",
    "content": "Environmental sensor data (requires compatible hardware): . | Метрични | Sensor Examples | . | Температура | BME280, BME680, SHT31 | . | Влажност | BME280, BME680, SHT31 | . | Барометрично налягане | BME280, BMP280 | . | Gas Resistance | BME680 | . | IAQ (Air Quality) | BME680 | . Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted: . 💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/node-metrics.html#%D0%BF%D0%BE%D0%BA%D0%B0%D0%B7%D0%B0%D1%82%D0%B5%D0%BB%D0%B8-%D0%BD%D0%B0-%D0%BE%D0%BA%D0%BE%D0%BB%D0%BD%D0%B0%D1%82%D0%B0-%D1%81%D1%80%D0%B5%D0%B4%D0%B0",
    
    "relUrl": "/bg-rBG/user/node-metrics.html#показатели-на-околната-среда"
  },"3245": {
    "doc": "Node Metrics",
    "title": "Air Quality Metrics",
    "content": "Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. | Метрични | Unit | Описание | . | PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | . | PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | . | PM10 | µg/m³ | Particulate matter up to 10 microns | . | AQI | EPA index | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated. | . | CO₂ | ppm | Carbon dioxide concentration | . | CO₂ temperature | °C / °F | Temperature reported by the CO₂ sensor itself (e.g. SCD4x) | . | CO₂ humidity | % | Relative humidity reported by the CO₂ sensor | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | Band | CO₂ Range (ppm) | Цвят | . | Добър | < 1000 | Зелен | . | Stuffy | < 2000 | Amber | . | Poor | < 5000 | Оранжев | . | Unsafe | < 30000 | Червен | . | Evacuate | ≥ 30000 | Dark red | . An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can: . | Select a time frame for the charts. | Filter with metric chips — only metrics that have data are shown. | Refresh / request the latest air-quality telemetry. | Export to CSV for analysis in a spreadsheet. | . 💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/node-metrics.html#air-quality-metrics",
    
    "relUrl": "/bg-rBG/user/node-metrics.html#air-quality-metrics"
  },"3246": {
    "doc": "Node Metrics",
    "title": "Качество на сигнала",
    "content": "Radio signal quality information: . | Метрични | Описание | . | SNR | Signal-to-Noise Ratio (higher is better) | . | RSSI | Received Signal Strength Indicator (closer to 0 is better) | . | Noise Floor | Local background RF noise in dBm (more negative is quieter) | . | Hop Count | Number of mesh hops for last message | . Signal Quality Reference . Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | Quality | Criteria | . | Добър | SNR above the preset’s limit | . | Задоволителен | less than 5.5 dB below the limit | . | Лош | 5.5 dB to 7.5 dB below the limit | . | Няма | more than 7.5 dB below the limit | . See Understanding the Signal Meter for the full explanation. Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment. | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/node-metrics.html#%D0%BA%D0%B0%D1%87%D0%B5%D1%81%D1%82%D0%B2%D0%BE-%D0%BD%D0%B0-%D1%81%D0%B8%D0%B3%D0%BD%D0%B0%D0%BB%D0%B0",
    
    "relUrl": "/bg-rBG/user/node-metrics.html#качество-на-сигнала"
  },"3247": {
    "doc": "Node Metrics",
    "title": "Показатели на мощност",
    "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Метрични | Описание | . | Напрежение | Per-channel voltage reading | . | Текущ | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/node-metrics.html#%D0%BF%D0%BE%D0%BA%D0%B0%D0%B7%D0%B0%D1%82%D0%B5%D0%BB%D0%B8-%D0%BD%D0%B0-%D0%BC%D0%BE%D1%89%D0%BD%D0%BE%D1%81%D1%82",
    
    "relUrl": "/bg-rBG/user/node-metrics.html#показатели-на-мощност"
  },"3248": {
    "doc": "Node Metrics",
    "title": "Трасиране на маршрут",
    "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | The app sends a traceroute request to the target node. | Results show each hop with its SNR. | . Reading Traceroute Results . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/node-metrics.html#%D1%82%D1%80%D0%B0%D1%81%D0%B8%D1%80%D0%B0%D0%BD%D0%B5-%D0%BD%D0%B0-%D0%BC%D0%B0%D1%80%D1%88%D1%80%D1%83%D1%82",
    
    "relUrl": "/bg-rBG/user/node-metrics.html#трасиране-на-маршрут"
  },"3249": {
    "doc": "Node Metrics",
    "title": "Журнал на позициите",
    "content": "Historical position data for nodes that share their location: . | GPS coordinates | Надморска височина | Speed (if moving) | Timestamp for each position report | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/node-metrics.html#%D0%B6%D1%83%D1%80%D0%BD%D0%B0%D0%BB-%D0%BD%D0%B0-%D0%BF%D0%BE%D0%B7%D0%B8%D1%86%D0%B8%D0%B8%D1%82%D0%B5",
    
    "relUrl": "/bg-rBG/user/node-metrics.html#журнал-на-позициите"
  },"3250": {
    "doc": "Node Metrics",
    "title": "Neighbor Info",
    "content": "Shows which nodes a given node can directly hear, useful for understanding mesh topology. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/node-metrics.html#neighbor-info",
    
    "relUrl": "/bg-rBG/user/node-metrics.html#neighbor-info"
  },"3251": {
    "doc": "Node Metrics",
    "title": "Host Metrics",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/node-metrics.html#host-metrics",
    
    "relUrl": "/bg-rBG/user/node-metrics.html#host-metrics"
  },"3252": {
    "doc": "Node Metrics",
    "title": "Показатели на PAX",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/node-metrics.html#%D0%BF%D0%BE%D0%BA%D0%B0%D0%B7%D0%B0%D1%82%D0%B5%D0%BB%D0%B8-%D0%BD%D0%B0-pax",
    
    "relUrl": "/bg-rBG/user/node-metrics.html#показатели-на-pax"
  },"3253": {
    "doc": "Node Metrics",
    "title": "Свързани теми",
    "content": ". | Nodes — node list, filtering, and sorting | Telemetry & Sensors — supported sensors and configuration | Signal Meter — how signal quality is calculated from SNR and RSSI | Local Mesh Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/node-metrics.html#%D1%81%D0%B2%D1%8A%D1%80%D0%B7%D0%B0%D0%BD%D0%B8-%D1%82%D0%B5%D0%BC%D0%B8",
    
    "relUrl": "/bg-rBG/user/node-metrics.html#свързани-теми"
  },"3254": {
    "doc": "Node Metrics",
    "title": "Node Metrics",
    "content": "The node detail screen provides comprehensive telemetry and metrics for each node on your mesh. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/node-metrics.html",
    
    "relUrl": "/ga-rIE/user/node-metrics.html"
  },"3255": {
    "doc": "Node Metrics",
    "title": "Viewing Metrics",
    "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/node-metrics.html#viewing-metrics",
    
    "relUrl": "/ga-rIE/user/node-metrics.html#viewing-metrics"
  },"3256": {
    "doc": "Node Metrics",
    "title": "Device Metrics",
    "content": "Basic operating information reported by each node: . | Metric | Cur síos | . | Battery Level | Current battery percentage | . | Voltage | Battery voltage reading | . | ChUtil | Percentage of local airtime in use | . | AirUtil | Percentage of the last hour this node spent transmitting | . | Uptime | Time since last reboot | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/node-metrics.html#device-metrics",
    
    "relUrl": "/ga-rIE/user/node-metrics.html#device-metrics"
  },"3257": {
    "doc": "Node Metrics",
    "title": "Environment Metrics",
    "content": "Environmental sensor data (requires compatible hardware): . | Metric | Sensor Examples | . | Teocht | BME280, BME680, SHT31 | . | Laige | BME280, BME680, SHT31 | . | Barometric Pressure | BME280, BMP280 | . | Gas Resistance | BME680 | . | IAQ (Air Quality) | BME680 | . Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted: . 💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/node-metrics.html#environment-metrics",
    
    "relUrl": "/ga-rIE/user/node-metrics.html#environment-metrics"
  },"3258": {
    "doc": "Node Metrics",
    "title": "Air Quality Metrics",
    "content": "Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. | Metric | Unit | Cur síos | . | PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | . | PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | . | PM10 | µg/m³ | Particulate matter up to 10 microns | . | AQI | EPA index | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated. | . | CO₂ | ppm | Carbon dioxide concentration | . | CO₂ temperature | °C / °F | Temperature reported by the CO₂ sensor itself (e.g. SCD4x) | . | CO₂ humidity | % | Relative humidity reported by the CO₂ sensor | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | Band | CO₂ Range (ppm) | Color | . | Maith | < 1000 | Green | . | Stuffy | < 2000 | Amber | . | Poor | < 5000 | Orange | . | Unsafe | < 30000 | Red | . | Evacuate | ≥ 30000 | Dark red | . An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can: . | Select a time frame for the charts. | Filter with metric chips — only metrics that have data are shown. | Refresh / request the latest air-quality telemetry. | Export to CSV for analysis in a spreadsheet. | . 💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/node-metrics.html#air-quality-metrics",
    
    "relUrl": "/ga-rIE/user/node-metrics.html#air-quality-metrics"
  },"3259": {
    "doc": "Node Metrics",
    "title": "Cáilíocht na Sígneal",
    "content": "Radio signal quality information: . | Metric | Cur síos | . | SNR | Signal-to-Noise Ratio (higher is better) | . | RSSI | Received Signal Strength Indicator (closer to 0 is better) | . | Noise Floor | Local background RF noise in dBm (more negative is quieter) | . | Hop Count | Number of mesh hops for last message | . Signal Quality Reference . Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | Quality | Criteria | . | Maith | SNR above the preset’s limit | . | Ceart go leor | less than 5.5 dB below the limit | . | Go dona | 5.5 dB to 7.5 dB below the limit | . | Ní dhéanfaidh sé | more than 7.5 dB below the limit | . See Understanding the Signal Meter for the full explanation. Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment. | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/node-metrics.html#c%C3%A1il%C3%ADocht-na-s%C3%ADgneal",
    
    "relUrl": "/ga-rIE/user/node-metrics.html#cáilíocht-na-sígneal"
  },"3260": {
    "doc": "Node Metrics",
    "title": "Power Metrics",
    "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Cur síos | . | Voltage | Per-channel voltage reading | . | Current | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/node-metrics.html#power-metrics",
    
    "relUrl": "/ga-rIE/user/node-metrics.html#power-metrics"
  },"3261": {
    "doc": "Node Metrics",
    "title": "Céim rianadóireachta",
    "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | The app sends a traceroute request to the target node. | Results show each hop with its SNR. | . Reading Traceroute Results . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/node-metrics.html#c%C3%A9im-rianad%C3%B3ireachta",
    
    "relUrl": "/ga-rIE/user/node-metrics.html#céim-rianadóireachta"
  },"3262": {
    "doc": "Node Metrics",
    "title": "Lógáil Seirbhís",
    "content": "Historical position data for nodes that share their location: . | GPS coordinates | Altitude | Speed (if moving) | Timestamp for each position report | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/node-metrics.html#l%C3%B3g%C3%A1il-seirbh%C3%ADs",
    
    "relUrl": "/ga-rIE/user/node-metrics.html#lógáil-seirbhís"
  },"3263": {
    "doc": "Node Metrics",
    "title": "Neighbor Info",
    "content": "Shows which nodes a given node can directly hear, useful for understanding mesh topology. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/node-metrics.html#neighbor-info",
    
    "relUrl": "/ga-rIE/user/node-metrics.html#neighbor-info"
  },"3264": {
    "doc": "Node Metrics",
    "title": "Host Metrics",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/node-metrics.html#host-metrics",
    
    "relUrl": "/ga-rIE/user/node-metrics.html#host-metrics"
  },"3265": {
    "doc": "Node Metrics",
    "title": "PAX Metrics",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/node-metrics.html#pax-metrics",
    
    "relUrl": "/ga-rIE/user/node-metrics.html#pax-metrics"
  },"3266": {
    "doc": "Node Metrics",
    "title": "Related Topics",
    "content": ". | Nodes — node list, filtering, and sorting | Telemetry & Sensors — supported sensors and configuration | Signal Meter — how signal quality is calculated from SNR and RSSI | Local Mesh Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/node-metrics.html#related-topics",
    
    "relUrl": "/ga-rIE/user/node-metrics.html#related-topics"
  },"3267": {
    "doc": "Node Metrics",
    "title": "Node Metrics",
    "content": "The node detail screen provides comprehensive telemetry and metrics for each node on your mesh. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/node-metrics.html",
    
    "relUrl": "/fr-rCA/user/node-metrics.html"
  },"3268": {
    "doc": "Node Metrics",
    "title": "Viewing Metrics",
    "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/node-metrics.html#viewing-metrics",
    
    "relUrl": "/fr-rCA/user/node-metrics.html#viewing-metrics"
  },"3269": {
    "doc": "Node Metrics",
    "title": "Métriques de l’appareil",
    "content": "Basic operating information reported by each node: . | Metric | Description | . | Niveau de batterie | Current battery percentage | . | Tension | Battery voltage reading | . | UtilCanal | Percentage of local airtime in use | . | UtilAir | Percentage of the last hour this node spent transmitting | . | Durée de fonctionnement | Time since last reboot | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/node-metrics.html#m%C3%A9triques-de-lappareil",
    
    "relUrl": "/fr-rCA/user/node-metrics.html#métriques-de-lappareil"
  },"3270": {
    "doc": "Node Metrics",
    "title": "Métriques d’environnement",
    "content": "Environmental sensor data (requires compatible hardware): . | Metric | Sensor Examples | . | Température | BME280, BME680, SHT31 | . | Humidité | BME280, BME680, SHT31 | . | Pression Barométrique | BME280, BMP280 | . | Résistance au gaz | BME680 | . | IAQ (Air Quality) | BME680 | . Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted: . 💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/node-metrics.html#m%C3%A9triques-denvironnement",
    
    "relUrl": "/fr-rCA/user/node-metrics.html#métriques-denvironnement"
  },"3271": {
    "doc": "Node Metrics",
    "title": "Air Quality Metrics",
    "content": "Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. | Metric | Unit | Description | . | PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | . | PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | . | PM10 | µg/m³ | Particulate matter up to 10 microns | . | AQI | EPA index | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated. | . | CO₂ | ppm | Carbon dioxide concentration | . | CO₂ temperature | °C / °F | Temperature reported by the CO₂ sensor itself (e.g. SCD4x) | . | CO₂ humidity | % | Relative humidity reported by the CO₂ sensor | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | Band | CO₂ Range (ppm) | Color | . | Bon | < 1000 | Vert | . | Stuffy | < 2000 | Amber | . | Poor | < 5000 | Orange | . | Unsafe | < 30000 | Rouge | . | Evacuate | ≥ 30000 | Dark red | . An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can: . | Select a time frame for the charts. | Filter with metric chips — only metrics that have data are shown. | Refresh / request the latest air-quality telemetry. | Export to CSV for analysis in a spreadsheet. | . 💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/node-metrics.html#air-quality-metrics",
    
    "relUrl": "/fr-rCA/user/node-metrics.html#air-quality-metrics"
  },"3272": {
    "doc": "Node Metrics",
    "title": "Qualité du signal",
    "content": "Radio signal quality information: . | Metric | Description | . | SNR | Signal-to-Noise Ratio (higher is better) | . | RSSI | Received Signal Strength Indicator (closer to 0 is better) | . | Noise Floor | Local background RF noise in dBm (more negative is quieter) | . | Hop Count | Number of mesh hops for last message | . Signal Quality Reference . Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | Quality | Criteria | . | Bon | SNR above the preset’s limit | . | Passable | less than 5.5 dB below the limit | . | Mauvais | 5.5 dB to 7.5 dB below the limit | . | Aucun | more than 7.5 dB below the limit | . See Understanding the Signal Meter for the full explanation. Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment. | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/node-metrics.html#qualit%C3%A9-du-signal",
    
    "relUrl": "/fr-rCA/user/node-metrics.html#qualité-du-signal"
  },"3273": {
    "doc": "Node Metrics",
    "title": "Métriques d’alimentation",
    "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Description | . | Tension | Per-channel voltage reading | . | Actif | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/node-metrics.html#m%C3%A9triques-dalimentation",
    
    "relUrl": "/fr-rCA/user/node-metrics.html#métriques-dalimentation"
  },"3274": {
    "doc": "Node Metrics",
    "title": "Traceroute",
    "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | The app sends a traceroute request to the target node. | Results show each hop with its SNR. | . Reading Traceroute Results . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/node-metrics.html#traceroute",
    
    "relUrl": "/fr-rCA/user/node-metrics.html#traceroute"
  },"3275": {
    "doc": "Node Metrics",
    "title": "Journal des positions",
    "content": "Historical position data for nodes that share their location: . | Coordonnées GPS | Altitude | Speed (if moving) | Timestamp for each position report | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/node-metrics.html#journal-des-positions",
    
    "relUrl": "/fr-rCA/user/node-metrics.html#journal-des-positions"
  },"3276": {
    "doc": "Node Metrics",
    "title": "Informations sur les voisins",
    "content": "Shows which nodes a given node can directly hear, useful for understanding mesh topology. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/node-metrics.html#informations-sur-les-voisins",
    
    "relUrl": "/fr-rCA/user/node-metrics.html#informations-sur-les-voisins"
  },"3277": {
    "doc": "Node Metrics",
    "title": "Métriques de l’hôte",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/node-metrics.html#m%C3%A9triques-de-lh%C3%B4te",
    
    "relUrl": "/fr-rCA/user/node-metrics.html#métriques-de-lhôte"
  },"3278": {
    "doc": "Node Metrics",
    "title": "Métriques de PAX",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/node-metrics.html#m%C3%A9triques-de-pax",
    
    "relUrl": "/fr-rCA/user/node-metrics.html#métriques-de-pax"
  },"3279": {
    "doc": "Node Metrics",
    "title": "Related Topics",
    "content": ". | Nodes — node list, filtering, and sorting | Telemetry & Sensors — supported sensors and configuration | Signal Meter — how signal quality is calculated from SNR and RSSI | Local Mesh Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/node-metrics.html#related-topics",
    
    "relUrl": "/fr-rCA/user/node-metrics.html#related-topics"
  },"3280": {
    "doc": "Node Metrics",
    "title": "Node Metrics",
    "content": "The node detail screen provides comprehensive telemetry and metrics for each node on your mesh. ",
    "url": "/Meshtastic-Android/main/srp/user/node-metrics.html",
    
    "relUrl": "/srp/user/node-metrics.html"
  },"3281": {
    "doc": "Node Metrics",
    "title": "Viewing Metrics",
    "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings. ",
    "url": "/Meshtastic-Android/main/srp/user/node-metrics.html#viewing-metrics",
    
    "relUrl": "/srp/user/node-metrics.html#viewing-metrics"
  },"3282": {
    "doc": "Node Metrics",
    "title": "Метрика уређаја",
    "content": "Basic operating information reported by each node: . | Метрика | Опис | . | Ниво батерије | Current battery percentage | . | Напон | Battery voltage reading | . | ChUtil | Percentage of local airtime in use | . | AirUtil | Percentage of the last hour this node spent transmitting | . | Време рада | Time since last reboot | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/srp/user/node-metrics.html#%D0%BC%D0%B5%D1%82%D1%80%D0%B8%D0%BA%D0%B0-%D1%83%D1%80%D0%B5%D1%92%D0%B0%D1%98%D0%B0",
    
    "relUrl": "/srp/user/node-metrics.html#метрика-уређаја"
  },"3283": {
    "doc": "Node Metrics",
    "title": "Метрике сензора",
    "content": "Environmental sensor data (requires compatible hardware): . | Метрика | Sensor Examples | . | Температура | BME280, BME680, SHT31 | . | Влажност | BME280, BME680, SHT31 | . | Барометарски притисак | BME280, BMP280 | . | Gas Resistance | BME680 | . | IAQ (Air Quality) | BME680 | . Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted: . 💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors. ",
    "url": "/Meshtastic-Android/main/srp/user/node-metrics.html#%D0%BC%D0%B5%D1%82%D1%80%D0%B8%D0%BA%D0%B5-%D1%81%D0%B5%D0%BD%D0%B7%D0%BE%D1%80%D0%B0",
    
    "relUrl": "/srp/user/node-metrics.html#метрике-сензора"
  },"3284": {
    "doc": "Node Metrics",
    "title": "Air Quality Metrics",
    "content": "Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. | Метрика | Unit | Опис | . | PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | . | PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | . | PM10 | µg/m³ | Particulate matter up to 10 microns | . | AQI | EPA index | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated. | . | CO₂ | ppm | Carbon dioxide concentration | . | CO₂ temperature | °C / °F | Temperature reported by the CO₂ sensor itself (e.g. SCD4x) | . | CO₂ humidity | % | Relative humidity reported by the CO₂ sensor | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | Band | CO₂ Range (ppm) | Боја | . | Добро | < 1000 | Green | . | Stuffy | < 2000 | Amber | . | Poor | < 5000 | Orange | . | Unsafe | < 30000 | Red | . | Evacuate | ≥ 30000 | Dark red | . An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can: . | Select a time frame for the charts. | Filter with metric chips — only metrics that have data are shown. | Refresh / request the latest air-quality telemetry. | Export to CSV for analysis in a spreadsheet. | . 💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware. ",
    "url": "/Meshtastic-Android/main/srp/user/node-metrics.html#air-quality-metrics",
    
    "relUrl": "/srp/user/node-metrics.html#air-quality-metrics"
  },"3285": {
    "doc": "Node Metrics",
    "title": "Квалитет сигнала",
    "content": "Radio signal quality information: . | Метрика | Опис | . | SNR | Signal-to-Noise Ratio (higher is better) | . | RSSI | Received Signal Strength Indicator (closer to 0 is better) | . | Noise Floor | Local background RF noise in dBm (more negative is quieter) | . | Hop Count | Number of mesh hops for last message | . Signal Quality Reference . Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | Quality | Criteria | . | Добро | SNR above the preset’s limit | . | Прихватљив | less than 5.5 dB below the limit | . | Лош | 5.5 dB to 7.5 dB below the limit | . | Ништа | more than 7.5 dB below the limit | . See Understanding the Signal Meter for the full explanation. Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment. | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/srp/user/node-metrics.html#%D0%BA%D0%B2%D0%B0%D0%BB%D0%B8%D1%82%D0%B5%D1%82-%D1%81%D0%B8%D0%B3%D0%BD%D0%B0%D0%BB%D0%B0",
    
    "relUrl": "/srp/user/node-metrics.html#квалитет-сигнала"
  },"3286": {
    "doc": "Node Metrics",
    "title": "Мерни подаци о снази",
    "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Метрика | Опис | . | Напон | Per-channel voltage reading | . | Струја | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/srp/user/node-metrics.html#%D0%BC%D0%B5%D1%80%D0%BD%D0%B8-%D0%BF%D0%BE%D0%B4%D0%B0%D1%86%D0%B8-%D0%BE-%D1%81%D0%BD%D0%B0%D0%B7%D0%B8",
    
    "relUrl": "/srp/user/node-metrics.html#мерни-подаци-о-снази"
  },"3287": {
    "doc": "Node Metrics",
    "title": "Праћење руте",
    "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | The app sends a traceroute request to the target node. | Results show each hop with its SNR. | . Reading Traceroute Results . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/srp/user/node-metrics.html#%D0%BF%D1%80%D0%B0%D1%9B%D0%B5%D1%9A%D0%B5-%D1%80%D1%83%D1%82%D0%B5",
    
    "relUrl": "/srp/user/node-metrics.html#праћење-руте"
  },"3288": {
    "doc": "Node Metrics",
    "title": "Логови позиција",
    "content": "Historical position data for nodes that share their location: . | GPS coordinates | Висина | Speed (if moving) | Timestamp for each position report | . ",
    "url": "/Meshtastic-Android/main/srp/user/node-metrics.html#%D0%BB%D0%BE%D0%B3%D0%BE%D0%B2%D0%B8-%D0%BF%D0%BE%D0%B7%D0%B8%D1%86%D0%B8%D1%98%D0%B0",
    
    "relUrl": "/srp/user/node-metrics.html#логови-позиција"
  },"3289": {
    "doc": "Node Metrics",
    "title": "Neighbor Info",
    "content": "Shows which nodes a given node can directly hear, useful for understanding mesh topology. ",
    "url": "/Meshtastic-Android/main/srp/user/node-metrics.html#neighbor-info",
    
    "relUrl": "/srp/user/node-metrics.html#neighbor-info"
  },"3290": {
    "doc": "Node Metrics",
    "title": "Host Metrics",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/srp/user/node-metrics.html#host-metrics",
    
    "relUrl": "/srp/user/node-metrics.html#host-metrics"
  },"3291": {
    "doc": "Node Metrics",
    "title": "PAX Metrics",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/srp/user/node-metrics.html#pax-metrics",
    
    "relUrl": "/srp/user/node-metrics.html#pax-metrics"
  },"3292": {
    "doc": "Node Metrics",
    "title": "Related Topics",
    "content": ". | Nodes — node list, filtering, and sorting | Telemetry & Sensors — supported sensors and configuration | Signal Meter — how signal quality is calculated from SNR and RSSI | Local Mesh Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ",
    "url": "/Meshtastic-Android/main/srp/user/node-metrics.html#related-topics",
    
    "relUrl": "/srp/user/node-metrics.html#related-topics"
  },"3293": {
    "doc": "Node Metrics",
    "title": "Node Metrics",
    "content": "The node detail screen provides comprehensive telemetry and metrics for each node on your mesh. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/node-metrics.html",
    
    "relUrl": "/ca-rES/user/node-metrics.html"
  },"3294": {
    "doc": "Node Metrics",
    "title": "Viewing Metrics",
    "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/node-metrics.html#viewing-metrics",
    
    "relUrl": "/ca-rES/user/node-metrics.html#viewing-metrics"
  },"3295": {
    "doc": "Node Metrics",
    "title": "Device Metrics",
    "content": "Basic operating information reported by each node: . | Metric | Descripció | . | Battery Level | Current battery percentage | . | Voltage | Battery voltage reading | . | ChUtil | Percentage of local airtime in use | . | AirUtil | Percentage of the last hour this node spent transmitting | . | Uptime | Time since last reboot | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/node-metrics.html#device-metrics",
    
    "relUrl": "/ca-rES/user/node-metrics.html#device-metrics"
  },"3296": {
    "doc": "Node Metrics",
    "title": "Environment Metrics",
    "content": "Environmental sensor data (requires compatible hardware): . | Metric | Sensor Examples | . | Temperature | BME280, BME680, SHT31 | . | Humidity | BME280, BME680, SHT31 | . | Barometric Pressure | BME280, BMP280 | . | Gas Resistance | BME680 | . | IAQ (Air Quality) | BME680 | . Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted: . 💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/node-metrics.html#environment-metrics",
    
    "relUrl": "/ca-rES/user/node-metrics.html#environment-metrics"
  },"3297": {
    "doc": "Node Metrics",
    "title": "Air Quality Metrics",
    "content": "Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. | Metric | Unit | Descripció | . | PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | . | PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | . | PM10 | µg/m³ | Particulate matter up to 10 microns | . | AQI | EPA index | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated. | . | CO₂ | ppm | Carbon dioxide concentration | . | CO₂ temperature | °C / °F | Temperature reported by the CO₂ sensor itself (e.g. SCD4x) | . | CO₂ humidity | % | Relative humidity reported by the CO₂ sensor | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | Band | CO₂ Range (ppm) | Color | . | Good | < 1000 | Green | . | Stuffy | < 2000 | Amber | . | Poor | < 5000 | Orange | . | Unsafe | < 30000 | Red | . | Evacuate | ≥ 30000 | Dark red | . An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can: . | Select a time frame for the charts. | Filter with metric chips — only metrics that have data are shown. | Refresh / request the latest air-quality telemetry. | Export to CSV for analysis in a spreadsheet. | . 💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/node-metrics.html#air-quality-metrics",
    
    "relUrl": "/ca-rES/user/node-metrics.html#air-quality-metrics"
  },"3298": {
    "doc": "Node Metrics",
    "title": "Signal Quality",
    "content": "Radio signal quality information: . | Metric | Descripció | . | SNR | Signal-to-Noise Ratio (higher is better) | . | RSSI | Received Signal Strength Indicator (closer to 0 is better) | . | Noise Floor | Local background RF noise in dBm (more negative is quieter) | . | Hop Count | Number of mesh hops for last message | . Signal Quality Reference . Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | Quality | Criteria | . | Good | SNR above the preset’s limit | . | Fair | less than 5.5 dB below the limit | . | Bad | 5.5 dB to 7.5 dB below the limit | . | None | more than 7.5 dB below the limit | . See Understanding the Signal Meter for the full explanation. Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment. | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/node-metrics.html#signal-quality",
    
    "relUrl": "/ca-rES/user/node-metrics.html#signal-quality"
  },"3299": {
    "doc": "Node Metrics",
    "title": "Power Metrics",
    "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Descripció | . | Voltage | Per-channel voltage reading | . | Current | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/node-metrics.html#power-metrics",
    
    "relUrl": "/ca-rES/user/node-metrics.html#power-metrics"
  },"3300": {
    "doc": "Node Metrics",
    "title": "Traçar ruta",
    "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | The app sends a traceroute request to the target node. | Results show each hop with its SNR. | . Reading Traceroute Results . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/node-metrics.html#tra%C3%A7ar-ruta",
    
    "relUrl": "/ca-rES/user/node-metrics.html#traçar-ruta"
  },"3301": {
    "doc": "Node Metrics",
    "title": "Position Log",
    "content": "Historical position data for nodes that share their location: . | GPS coordinates | Altitude | Speed (if moving) | Timestamp for each position report | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/node-metrics.html#position-log",
    
    "relUrl": "/ca-rES/user/node-metrics.html#position-log"
  },"3302": {
    "doc": "Node Metrics",
    "title": "Neighbor Info",
    "content": "Shows which nodes a given node can directly hear, useful for understanding mesh topology. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/node-metrics.html#neighbor-info",
    
    "relUrl": "/ca-rES/user/node-metrics.html#neighbor-info"
  },"3303": {
    "doc": "Node Metrics",
    "title": "Host Metrics",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/node-metrics.html#host-metrics",
    
    "relUrl": "/ca-rES/user/node-metrics.html#host-metrics"
  },"3304": {
    "doc": "Node Metrics",
    "title": "PAX Metrics",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/node-metrics.html#pax-metrics",
    
    "relUrl": "/ca-rES/user/node-metrics.html#pax-metrics"
  },"3305": {
    "doc": "Node Metrics",
    "title": "Related Topics",
    "content": ". | Nodes — node list, filtering, and sorting | Telemetry & Sensors — supported sensors and configuration | Signal Meter — how signal quality is calculated from SNR and RSSI | Local Mesh Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/node-metrics.html#related-topics",
    
    "relUrl": "/ca-rES/user/node-metrics.html#related-topics"
  },"3306": {
    "doc": "Node Metrics",
    "title": "Node Metrics",
    "content": "The node detail screen provides comprehensive telemetry and metrics for each node on your mesh. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/node-metrics.html",
    
    "relUrl": "/ko-rKR/user/node-metrics.html"
  },"3307": {
    "doc": "Node Metrics",
    "title": "Viewing Metrics",
    "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/node-metrics.html#viewing-metrics",
    
    "relUrl": "/ko-rKR/user/node-metrics.html#viewing-metrics"
  },"3308": {
    "doc": "Node Metrics",
    "title": "Device Metrics",
    "content": "Basic operating information reported by each node: . | Metric | 설명 | . | Battery Level | Current battery percentage | . | 전압 | Battery voltage reading | . | ChUtil | Percentage of local airtime in use | . | AirUtil | Percentage of the last hour this node spent transmitting | . | 업타임 | Time since last reboot | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/node-metrics.html#device-metrics",
    
    "relUrl": "/ko-rKR/user/node-metrics.html#device-metrics"
  },"3309": {
    "doc": "Node Metrics",
    "title": "Environment Metrics",
    "content": "Environmental sensor data (requires compatible hardware): . | Metric | Sensor Examples | . | 온도 | BME280, BME680, SHT31 | . | 습도 | BME280, BME680, SHT31 | . | 기압 | BME280, BMP280 | . | 가스 저항 | BME680 | . | IAQ (Air Quality) | BME680 | . Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted: . 💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/node-metrics.html#environment-metrics",
    
    "relUrl": "/ko-rKR/user/node-metrics.html#environment-metrics"
  },"3310": {
    "doc": "Node Metrics",
    "title": "Air Quality Metrics",
    "content": "Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. | Metric | Unit | 설명 | . | PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | . | PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | . | PM10 | µg/m³ | Particulate matter up to 10 microns | . | AQI | EPA index | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated. | . | CO₂ | ppm | Carbon dioxide concentration | . | CO₂ temperature | °C / °F | Temperature reported by the CO₂ sensor itself (e.g. SCD4x) | . | CO₂ humidity | % | Relative humidity reported by the CO₂ sensor | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | Band | CO₂ Range (ppm) | Color | . | 좋음 | < 1000 | 초록 | . | Stuffy | < 2000 | Amber | . | Poor | < 5000 | Orange | . | Unsafe | < 30000 | 빨강 | . | Evacuate | ≥ 30000 | Dark red | . An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can: . | Select a time frame for the charts. | Filter with metric chips — only metrics that have data are shown. | Refresh / request the latest air-quality telemetry. | Export to CSV for analysis in a spreadsheet. | . 💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/node-metrics.html#air-quality-metrics",
    
    "relUrl": "/ko-rKR/user/node-metrics.html#air-quality-metrics"
  },"3311": {
    "doc": "Node Metrics",
    "title": "신호 감도",
    "content": "Radio signal quality information: . | Metric | 설명 | . | SNR | Signal-to-Noise Ratio (higher is better) | . | RSSI | Received Signal Strength Indicator (closer to 0 is better) | . | Noise Floor | Local background RF noise in dBm (more negative is quieter) | . | Hop Count | Number of mesh hops for last message | . Signal Quality Reference . Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | Quality | Criteria | . | 좋음 | SNR above the preset’s limit | . | 보통 | less than 5.5 dB below the limit | . | 나쁨 | 5.5 dB to 7.5 dB below the limit | . | 없음 | more than 7.5 dB below the limit | . See Understanding the Signal Meter for the full explanation. Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment. | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/node-metrics.html#%EC%8B%A0%ED%98%B8-%EA%B0%90%EB%8F%84",
    
    "relUrl": "/ko-rKR/user/node-metrics.html#신호-감도"
  },"3312": {
    "doc": "Node Metrics",
    "title": "Power Metrics",
    "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | 설명 | . | 전압 | Per-channel voltage reading | . | 전류 | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/node-metrics.html#power-metrics",
    
    "relUrl": "/ko-rKR/user/node-metrics.html#power-metrics"
  },"3313": {
    "doc": "Node Metrics",
    "title": "추적 루트",
    "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | The app sends a traceroute request to the target node. | Results show each hop with its SNR. | . Reading Traceroute Results . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/node-metrics.html#%EC%B6%94%EC%A0%81-%EB%A3%A8%ED%8A%B8",
    
    "relUrl": "/ko-rKR/user/node-metrics.html#추적-루트"
  },"3314": {
    "doc": "Node Metrics",
    "title": "위치 로그",
    "content": "Historical position data for nodes that share their location: . | GPS coordinates | Altitude | Speed (if moving) | Timestamp for each position report | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/node-metrics.html#%EC%9C%84%EC%B9%98-%EB%A1%9C%EA%B7%B8",
    
    "relUrl": "/ko-rKR/user/node-metrics.html#위치-로그"
  },"3315": {
    "doc": "Node Metrics",
    "title": "이웃 정보",
    "content": "Shows which nodes a given node can directly hear, useful for understanding mesh topology. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/node-metrics.html#%EC%9D%B4%EC%9B%83-%EC%A0%95%EB%B3%B4",
    
    "relUrl": "/ko-rKR/user/node-metrics.html#이웃-정보"
  },"3316": {
    "doc": "Node Metrics",
    "title": "Host Metrics",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/node-metrics.html#host-metrics",
    
    "relUrl": "/ko-rKR/user/node-metrics.html#host-metrics"
  },"3317": {
    "doc": "Node Metrics",
    "title": "PAX Metrics",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/node-metrics.html#pax-metrics",
    
    "relUrl": "/ko-rKR/user/node-metrics.html#pax-metrics"
  },"3318": {
    "doc": "Node Metrics",
    "title": "Related Topics",
    "content": ". | Nodes — node list, filtering, and sorting | Telemetry & Sensors — supported sensors and configuration | Signal Meter — how signal quality is calculated from SNR and RSSI | Local Mesh Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/node-metrics.html#related-topics",
    
    "relUrl": "/ko-rKR/user/node-metrics.html#related-topics"
  },"3319": {
    "doc": "Node Metrics",
    "title": "Node Metrics",
    "content": "The node detail screen provides comprehensive telemetry and metrics for each node on your mesh. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/node-metrics.html",
    
    "relUrl": "/sv-rSE/user/node-metrics.html"
  },"3320": {
    "doc": "Node Metrics",
    "title": "Viewing Metrics",
    "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/node-metrics.html#viewing-metrics",
    
    "relUrl": "/sv-rSE/user/node-metrics.html#viewing-metrics"
  },"3321": {
    "doc": "Node Metrics",
    "title": "Enhetens mätvärden",
    "content": "Basic operating information reported by each node: . | Metric | Beskrivning | . | Battery Level | Current battery percentage | . | Spänning | Battery voltage reading | . | ChUtil | Percentage of local airtime in use | . | AirUtil | Percentage of the last hour this node spent transmitting | . | Upptid | Time since last reboot | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/node-metrics.html#enhetens-m%C3%A4tv%C3%A4rden",
    
    "relUrl": "/sv-rSE/user/node-metrics.html#enhetens-mätvärden"
  },"3322": {
    "doc": "Node Metrics",
    "title": "Miljövärden",
    "content": "Environmental sensor data (requires compatible hardware): . | Metric | Sensor Examples | . | Temperatur | BME280, BME680, SHT31 | . | Luftfuktighet | BME280, BME680, SHT31 | . | Lufttryck | BME280, BMP280 | . | Gasmotstånd | BME680 | . | IAQ (Air Quality) | BME680 | . Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted: . 💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/node-metrics.html#milj%C3%B6v%C3%A4rden",
    
    "relUrl": "/sv-rSE/user/node-metrics.html#miljövärden"
  },"3323": {
    "doc": "Node Metrics",
    "title": "Air Quality Metrics",
    "content": "Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. | Metric | Unit | Beskrivning | . | PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | . | PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | . | PM10 | µg/m³ | Particulate matter up to 10 microns | . | AQI | EPA index | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated. | . | CO₂ | ppm | Carbon dioxide concentration | . | CO₂ temperature | °C / °F | Temperature reported by the CO₂ sensor itself (e.g. SCD4x) | . | CO₂ humidity | % | Relative humidity reported by the CO₂ sensor | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | Band | CO₂ Range (ppm) | Color | . | Bra | < 1000 | Grönt | . | Stuffy | < 2000 | Amber | . | Poor | < 5000 | Orange | . | Unsafe | < 30000 | Rött | . | Evacuate | ≥ 30000 | Dark red | . An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can: . | Select a time frame for the charts. | Filter with metric chips — only metrics that have data are shown. | Refresh / request the latest air-quality telemetry. | Export to CSV for analysis in a spreadsheet. | . 💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/node-metrics.html#air-quality-metrics",
    
    "relUrl": "/sv-rSE/user/node-metrics.html#air-quality-metrics"
  },"3324": {
    "doc": "Node Metrics",
    "title": "Signalkvalité",
    "content": "Radio signal quality information: . | Metric | Beskrivning | . | SNR | Signal-to-Noise Ratio (higher is better) | . | RSSI | Received Signal Strength Indicator (closer to 0 is better) | . | Noise Floor | Local background RF noise in dBm (more negative is quieter) | . | Hop Count | Number of mesh hops for last message | . Signal Quality Reference . Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | Quality | Criteria | . | Bra | SNR above the preset’s limit | . | Ok | less than 5.5 dB below the limit | . | Dålig | 5.5 dB to 7.5 dB below the limit | . | Ingen | more than 7.5 dB below the limit | . See Understanding the Signal Meter for the full explanation. Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment. | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/node-metrics.html#signalkvalit%C3%A9",
    
    "relUrl": "/sv-rSE/user/node-metrics.html#signalkvalité"
  },"3325": {
    "doc": "Node Metrics",
    "title": "Strömdata",
    "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Beskrivning | . | Spänning | Per-channel voltage reading | . | Ström | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/node-metrics.html#str%C3%B6mdata",
    
    "relUrl": "/sv-rSE/user/node-metrics.html#strömdata"
  },"3326": {
    "doc": "Node Metrics",
    "title": "Traceroute (spåra rutt)",
    "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | The app sends a traceroute request to the target node. | Results show each hop with its SNR. | . Reading Traceroute Results . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/node-metrics.html#traceroute-sp%C3%A5ra-rutt",
    
    "relUrl": "/sv-rSE/user/node-metrics.html#traceroute-spåra-rutt"
  },"3327": {
    "doc": "Node Metrics",
    "title": "Position Loggbok",
    "content": "Historical position data for nodes that share their location: . | GPS coordinates | Altitud | Speed (if moving) | Timestamp for each position report | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/node-metrics.html#position-loggbok",
    
    "relUrl": "/sv-rSE/user/node-metrics.html#position-loggbok"
  },"3328": {
    "doc": "Node Metrics",
    "title": "Granninformation",
    "content": "Shows which nodes a given node can directly hear, useful for understanding mesh topology. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/node-metrics.html#granninformation",
    
    "relUrl": "/sv-rSE/user/node-metrics.html#granninformation"
  },"3329": {
    "doc": "Node Metrics",
    "title": "Begär värdens värden",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/node-metrics.html#beg%C3%A4r-v%C3%A4rdens-v%C3%A4rden",
    
    "relUrl": "/sv-rSE/user/node-metrics.html#begär-värdens-värden"
  },"3330": {
    "doc": "Node Metrics",
    "title": "PAX nyckeltal",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/node-metrics.html#pax-nyckeltal",
    
    "relUrl": "/sv-rSE/user/node-metrics.html#pax-nyckeltal"
  },"3331": {
    "doc": "Node Metrics",
    "title": "Related Topics",
    "content": ". | Nodes — node list, filtering, and sorting | Telemetry & Sensors — supported sensors and configuration | Signal Meter — how signal quality is calculated from SNR and RSSI | Local Mesh Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/node-metrics.html#related-topics",
    
    "relUrl": "/sv-rSE/user/node-metrics.html#related-topics"
  },"3332": {
    "doc": "Node Metrics",
    "title": "Node Metrics",
    "content": "The node detail screen provides comprehensive telemetry and metrics for each node on your mesh. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/node-metrics.html",
    
    "relUrl": "/ht-rHT/user/node-metrics.html"
  },"3333": {
    "doc": "Node Metrics",
    "title": "Viewing Metrics",
    "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/node-metrics.html#viewing-metrics",
    
    "relUrl": "/ht-rHT/user/node-metrics.html#viewing-metrics"
  },"3334": {
    "doc": "Node Metrics",
    "title": "Device Metrics",
    "content": "Basic operating information reported by each node: . | Metric | Deskripsyon | . | Battery Level | Current battery percentage | . | Voltage | Battery voltage reading | . | ChUtil | Percentage of local airtime in use | . | AirUtil | Percentage of the last hour this node spent transmitting | . | Uptime | Time since last reboot | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/node-metrics.html#device-metrics",
    
    "relUrl": "/ht-rHT/user/node-metrics.html#device-metrics"
  },"3335": {
    "doc": "Node Metrics",
    "title": "Environment Metrics",
    "content": "Environmental sensor data (requires compatible hardware): . | Metric | Sensor Examples | . | Tanperati | BME280, BME680, SHT31 | . | Imidite | BME280, BME680, SHT31 | . | Barometric Pressure | BME280, BMP280 | . | Gas Resistance | BME680 | . | IAQ (Air Quality) | BME680 | . Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted: . 💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/node-metrics.html#environment-metrics",
    
    "relUrl": "/ht-rHT/user/node-metrics.html#environment-metrics"
  },"3336": {
    "doc": "Node Metrics",
    "title": "Air Quality Metrics",
    "content": "Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. | Metric | Unit | Deskripsyon | . | PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | . | PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | . | PM10 | µg/m³ | Particulate matter up to 10 microns | . | AQI | EPA index | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated. | . | CO₂ | ppm | Carbon dioxide concentration | . | CO₂ temperature | °C / °F | Temperature reported by the CO₂ sensor itself (e.g. SCD4x) | . | CO₂ humidity | % | Relative humidity reported by the CO₂ sensor | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | Band | CO₂ Range (ppm) | Color | . | Bon | < 1000 | Green | . | Stuffy | < 2000 | Amber | . | Poor | < 5000 | Orange | . | Unsafe | < 30000 | Red | . | Evacuate | ≥ 30000 | Dark red | . An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can: . | Select a time frame for the charts. | Filter with metric chips — only metrics that have data are shown. | Refresh / request the latest air-quality telemetry. | Export to CSV for analysis in a spreadsheet. | . 💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/node-metrics.html#air-quality-metrics",
    
    "relUrl": "/ht-rHT/user/node-metrics.html#air-quality-metrics"
  },"3337": {
    "doc": "Node Metrics",
    "title": "Kalite Siynal",
    "content": "Radio signal quality information: . | Metric | Deskripsyon | . | SNR | Signal-to-Noise Ratio (higher is better) | . | RSSI | Received Signal Strength Indicator (closer to 0 is better) | . | Noise Floor | Local background RF noise in dBm (more negative is quieter) | . | Hop Count | Number of mesh hops for last message | . Signal Quality Reference . Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | Quality | Criteria | . | Bon | SNR above the preset’s limit | . | Mwayen | less than 5.5 dB below the limit | . | Move | 5.5 dB to 7.5 dB below the limit | . | Pa gen | more than 7.5 dB below the limit | . See Understanding the Signal Meter for the full explanation. Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment. | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/node-metrics.html#kalite-siynal",
    
    "relUrl": "/ht-rHT/user/node-metrics.html#kalite-siynal"
  },"3338": {
    "doc": "Node Metrics",
    "title": "Power Metrics",
    "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Deskripsyon | . | Voltage | Per-channel voltage reading | . | Current | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/node-metrics.html#power-metrics",
    
    "relUrl": "/ht-rHT/user/node-metrics.html#power-metrics"
  },"3339": {
    "doc": "Node Metrics",
    "title": "Traceroute",
    "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | The app sends a traceroute request to the target node. | Results show each hop with its SNR. | . Reading Traceroute Results . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/node-metrics.html#traceroute",
    
    "relUrl": "/ht-rHT/user/node-metrics.html#traceroute"
  },"3340": {
    "doc": "Node Metrics",
    "title": "Jounal Pozisyon",
    "content": "Historical position data for nodes that share their location: . | GPS coordinates | Altitude | Speed (if moving) | Timestamp for each position report | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/node-metrics.html#jounal-pozisyon",
    
    "relUrl": "/ht-rHT/user/node-metrics.html#jounal-pozisyon"
  },"3341": {
    "doc": "Node Metrics",
    "title": "Neighbor Info",
    "content": "Shows which nodes a given node can directly hear, useful for understanding mesh topology. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/node-metrics.html#neighbor-info",
    
    "relUrl": "/ht-rHT/user/node-metrics.html#neighbor-info"
  },"3342": {
    "doc": "Node Metrics",
    "title": "Host Metrics",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/node-metrics.html#host-metrics",
    
    "relUrl": "/ht-rHT/user/node-metrics.html#host-metrics"
  },"3343": {
    "doc": "Node Metrics",
    "title": "PAX Metrics",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/node-metrics.html#pax-metrics",
    
    "relUrl": "/ht-rHT/user/node-metrics.html#pax-metrics"
  },"3344": {
    "doc": "Node Metrics",
    "title": "Related Topics",
    "content": ". | Nodes — node list, filtering, and sorting | Telemetry & Sensors — supported sensors and configuration | Signal Meter — how signal quality is calculated from SNR and RSSI | Local Mesh Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/node-metrics.html#related-topics",
    
    "relUrl": "/ht-rHT/user/node-metrics.html#related-topics"
  },"3345": {
    "doc": "Node Metrics",
    "title": "Node Metrics",
    "content": "The node detail screen provides comprehensive telemetry and metrics for each node on your mesh. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/node-metrics.html",
    
    "relUrl": "/sr-rLatn/user/node-metrics.html"
  },"3346": {
    "doc": "Node Metrics",
    "title": "Viewing Metrics",
    "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/node-metrics.html#viewing-metrics",
    
    "relUrl": "/sr-rLatn/user/node-metrics.html#viewing-metrics"
  },"3347": {
    "doc": "Node Metrics",
    "title": "Метрика уређаја",
    "content": "Basic operating information reported by each node: . | Метрика | Опис | . | Ниво батерије | Current battery percentage | . | Напон | Battery voltage reading | . | ChUtil | Percentage of local airtime in use | . | AirUtil | Percentage of the last hour this node spent transmitting | . | Време рада | Time since last reboot | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/node-metrics.html#%D0%BC%D0%B5%D1%82%D1%80%D0%B8%D0%BA%D0%B0-%D1%83%D1%80%D0%B5%D1%92%D0%B0%D1%98%D0%B0",
    
    "relUrl": "/sr-rLatn/user/node-metrics.html#метрика-уређаја"
  },"3348": {
    "doc": "Node Metrics",
    "title": "Метрике сензора",
    "content": "Environmental sensor data (requires compatible hardware): . | Метрика | Sensor Examples | . | Температура | BME280, BME680, SHT31 | . | Влажност | BME280, BME680, SHT31 | . | Барометарски притисак | BME280, BMP280 | . | Gas Resistance | BME680 | . | IAQ (Air Quality) | BME680 | . Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted: . 💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/node-metrics.html#%D0%BC%D0%B5%D1%82%D1%80%D0%B8%D0%BA%D0%B5-%D1%81%D0%B5%D0%BD%D0%B7%D0%BE%D1%80%D0%B0",
    
    "relUrl": "/sr-rLatn/user/node-metrics.html#метрике-сензора"
  },"3349": {
    "doc": "Node Metrics",
    "title": "Air Quality Metrics",
    "content": "Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. | Метрика | Unit | Опис | . | PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | . | PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | . | PM10 | µg/m³ | Particulate matter up to 10 microns | . | AQI | EPA index | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated. | . | CO₂ | ppm | Carbon dioxide concentration | . | CO₂ temperature | °C / °F | Temperature reported by the CO₂ sensor itself (e.g. SCD4x) | . | CO₂ humidity | % | Relative humidity reported by the CO₂ sensor | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | Band | CO₂ Range (ppm) | Боја | . | Dobro | < 1000 | Green | . | Stuffy | < 2000 | Amber | . | Poor | < 5000 | Orange | . | Unsafe | < 30000 | Red | . | Evacuate | ≥ 30000 | Dark red | . An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can: . | Select a time frame for the charts. | Filter with metric chips — only metrics that have data are shown. | Refresh / request the latest air-quality telemetry. | Export to CSV for analysis in a spreadsheet. | . 💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/node-metrics.html#air-quality-metrics",
    
    "relUrl": "/sr-rLatn/user/node-metrics.html#air-quality-metrics"
  },"3350": {
    "doc": "Node Metrics",
    "title": "Kvalitet signala",
    "content": "Radio signal quality information: . | Метрика | Опис | . | SNR | Signal-to-Noise Ratio (higher is better) | . | RSSI | Received Signal Strength Indicator (closer to 0 is better) | . | Noise Floor | Local background RF noise in dBm (more negative is quieter) | . | Hop Count | Number of mesh hops for last message | . Signal Quality Reference . Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | Quality | Criteria | . | Dobro | SNR above the preset’s limit | . | Prihvatljiv | less than 5.5 dB below the limit | . | Loš | 5.5 dB to 7.5 dB below the limit | . | Bez | more than 7.5 dB below the limit | . See Understanding the Signal Meter for the full explanation. Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment. | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/node-metrics.html#kvalitet-signala",
    
    "relUrl": "/sr-rLatn/user/node-metrics.html#kvalitet-signala"
  },"3351": {
    "doc": "Node Metrics",
    "title": "Мерни подаци о снази",
    "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Метрика | Опис | . | Напон | Per-channel voltage reading | . | Струја | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/node-metrics.html#%D0%BC%D0%B5%D1%80%D0%BD%D0%B8-%D0%BF%D0%BE%D0%B4%D0%B0%D1%86%D0%B8-%D0%BE-%D1%81%D0%BD%D0%B0%D0%B7%D0%B8",
    
    "relUrl": "/sr-rLatn/user/node-metrics.html#мерни-подаци-о-снази"
  },"3352": {
    "doc": "Node Metrics",
    "title": "Праћење руте",
    "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | The app sends a traceroute request to the target node. | Results show each hop with its SNR. | . Reading Traceroute Results . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/node-metrics.html#%D0%BF%D1%80%D0%B0%D1%9B%D0%B5%D1%9A%D0%B5-%D1%80%D1%83%D1%82%D0%B5",
    
    "relUrl": "/sr-rLatn/user/node-metrics.html#праћење-руте"
  },"3353": {
    "doc": "Node Metrics",
    "title": "Dnevnik lokacija",
    "content": "Historical position data for nodes that share their location: . | GPS coordinates | Висина | Speed (if moving) | Timestamp for each position report | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/node-metrics.html#dnevnik-lokacija",
    
    "relUrl": "/sr-rLatn/user/node-metrics.html#dnevnik-lokacija"
  },"3354": {
    "doc": "Node Metrics",
    "title": "Neighbor Info",
    "content": "Shows which nodes a given node can directly hear, useful for understanding mesh topology. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/node-metrics.html#neighbor-info",
    
    "relUrl": "/sr-rLatn/user/node-metrics.html#neighbor-info"
  },"3355": {
    "doc": "Node Metrics",
    "title": "Host Metrics",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/node-metrics.html#host-metrics",
    
    "relUrl": "/sr-rLatn/user/node-metrics.html#host-metrics"
  },"3356": {
    "doc": "Node Metrics",
    "title": "PAX Metrics",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/node-metrics.html#pax-metrics",
    
    "relUrl": "/sr-rLatn/user/node-metrics.html#pax-metrics"
  },"3357": {
    "doc": "Node Metrics",
    "title": "Related Topics",
    "content": ". | Nodes — node list, filtering, and sorting | Telemetry & Sensors — supported sensors and configuration | Signal Meter — how signal quality is calculated from SNR and RSSI | Local Mesh Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/node-metrics.html#related-topics",
    
    "relUrl": "/sr-rLatn/user/node-metrics.html#related-topics"
  },"3358": {
    "doc": "Node Metrics",
    "title": "Node Metrics",
    "content": "The node detail screen provides comprehensive telemetry and metrics for each node on your mesh. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/node-metrics.html",
    
    "relUrl": "/nl-rNL/user/node-metrics.html"
  },"3359": {
    "doc": "Node Metrics",
    "title": "Viewing Metrics",
    "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/node-metrics.html#viewing-metrics",
    
    "relUrl": "/nl-rNL/user/node-metrics.html#viewing-metrics"
  },"3360": {
    "doc": "Node Metrics",
    "title": "Device Metrics",
    "content": "Basic operating information reported by each node: . | Metric | Beschrijving | . | Battery Level | Current battery percentage | . | Spanning | Battery voltage reading | . | ChUtil | Percentage of local airtime in use | . | AirUtil | Percentage of the last hour this node spent transmitting | . | Tijd online | Time since last reboot | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/node-metrics.html#device-metrics",
    
    "relUrl": "/nl-rNL/user/node-metrics.html#device-metrics"
  },"3361": {
    "doc": "Node Metrics",
    "title": "Environment Metrics",
    "content": "Environmental sensor data (requires compatible hardware): . | Metric | Sensor Examples | . | Temperatuur | BME280, BME680, SHT31 | . | Vochtigheid | BME280, BME680, SHT31 | . | Luchtdruk | BME280, BMP280 | . | Gas Resistance | BME680 | . | IAQ (Air Quality) | BME680 | . Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted: . 💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/node-metrics.html#environment-metrics",
    
    "relUrl": "/nl-rNL/user/node-metrics.html#environment-metrics"
  },"3362": {
    "doc": "Node Metrics",
    "title": "Air Quality Metrics",
    "content": "Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. | Metric | Unit | Beschrijving | . | PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | . | PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | . | PM10 | µg/m³ | Particulate matter up to 10 microns | . | AQI | EPA index | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated. | . | CO₂ | ppm | Carbon dioxide concentration | . | CO₂ temperature | °C / °F | Temperature reported by the CO₂ sensor itself (e.g. SCD4x) | . | CO₂ humidity | % | Relative humidity reported by the CO₂ sensor | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | Band | CO₂ Range (ppm) | Color | . | Goed | < 1000 | Groen | . | Stuffy | < 2000 | Amber | . | Poor | < 5000 | Orange | . | Unsafe | < 30000 | Rood | . | Evacuate | ≥ 30000 | Dark red | . An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can: . | Select a time frame for the charts. | Filter with metric chips — only metrics that have data are shown. | Refresh / request the latest air-quality telemetry. | Export to CSV for analysis in a spreadsheet. | . 💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/node-metrics.html#air-quality-metrics",
    
    "relUrl": "/nl-rNL/user/node-metrics.html#air-quality-metrics"
  },"3363": {
    "doc": "Node Metrics",
    "title": "Signaalkwaliteit",
    "content": "Radio signal quality information: . | Metric | Beschrijving | . | SNR | Signal-to-Noise Ratio (higher is better) | . | RSSI | Received Signal Strength Indicator (closer to 0 is better) | . | Noise Floor | Local background RF noise in dBm (more negative is quieter) | . | Hop Count | Number of mesh hops for last message | . Signal Quality Reference . Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | Quality | Criteria | . | Goed | SNR above the preset’s limit | . | Matig | less than 5.5 dB below the limit | . | Slecht | 5.5 dB to 7.5 dB below the limit | . | Geen | more than 7.5 dB below the limit | . See Understanding the Signal Meter for the full explanation. Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment. | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/node-metrics.html#signaalkwaliteit",
    
    "relUrl": "/nl-rNL/user/node-metrics.html#signaalkwaliteit"
  },"3364": {
    "doc": "Node Metrics",
    "title": "Power Metrics",
    "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Beschrijving | . | Spanning | Per-channel voltage reading | . | Huidige | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/node-metrics.html#power-metrics",
    
    "relUrl": "/nl-rNL/user/node-metrics.html#power-metrics"
  },"3365": {
    "doc": "Node Metrics",
    "title": "Traceroute",
    "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | The app sends a traceroute request to the target node. | Results show each hop with its SNR. | . Reading Traceroute Results . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/node-metrics.html#traceroute",
    
    "relUrl": "/nl-rNL/user/node-metrics.html#traceroute"
  },"3366": {
    "doc": "Node Metrics",
    "title": "Positie Logboek",
    "content": "Historical position data for nodes that share their location: . | GPS coordinates | Altitude | Speed (if moving) | Timestamp for each position report | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/node-metrics.html#positie-logboek",
    
    "relUrl": "/nl-rNL/user/node-metrics.html#positie-logboek"
  },"3367": {
    "doc": "Node Metrics",
    "title": "Neighbor Info",
    "content": "Shows which nodes a given node can directly hear, useful for understanding mesh topology. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/node-metrics.html#neighbor-info",
    
    "relUrl": "/nl-rNL/user/node-metrics.html#neighbor-info"
  },"3368": {
    "doc": "Node Metrics",
    "title": "Host Metrics",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/node-metrics.html#host-metrics",
    
    "relUrl": "/nl-rNL/user/node-metrics.html#host-metrics"
  },"3369": {
    "doc": "Node Metrics",
    "title": "PAX Metrics",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/node-metrics.html#pax-metrics",
    
    "relUrl": "/nl-rNL/user/node-metrics.html#pax-metrics"
  },"3370": {
    "doc": "Node Metrics",
    "title": "Related Topics",
    "content": ". | Nodes — node list, filtering, and sorting | Telemetry & Sensors — supported sensors and configuration | Signal Meter — how signal quality is calculated from SNR and RSSI | Local Mesh Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/node-metrics.html#related-topics",
    
    "relUrl": "/nl-rNL/user/node-metrics.html#related-topics"
  },"3371": {
    "doc": "Node Metrics",
    "title": "Node Metrics",
    "content": "The node detail screen provides comprehensive telemetry and metrics for each node on your mesh. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/node-metrics.html",
    
    "relUrl": "/uk-rUA/user/node-metrics.html"
  },"3372": {
    "doc": "Node Metrics",
    "title": "Viewing Metrics",
    "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/node-metrics.html#viewing-metrics",
    
    "relUrl": "/uk-rUA/user/node-metrics.html#viewing-metrics"
  },"3373": {
    "doc": "Node Metrics",
    "title": "Показники пристрою",
    "content": "Basic operating information reported by each node: . | Metric | Опис | . | Battery Level | Current battery percentage | . | Напруга | Battery voltage reading | . | Завантаженість каналу | Percentage of local airtime in use | . | Завантаженість ефіру | Percentage of the last hour this node spent transmitting | . | Час роботи | Time since last reboot | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/node-metrics.html#%D0%BF%D0%BE%D0%BA%D0%B0%D0%B7%D0%BD%D0%B8%D0%BA%D0%B8-%D0%BF%D1%80%D0%B8%D1%81%D1%82%D1%80%D0%BE%D1%8E",
    
    "relUrl": "/uk-rUA/user/node-metrics.html#показники-пристрою"
  },"3374": {
    "doc": "Node Metrics",
    "title": "Показники довкілля",
    "content": "Environmental sensor data (requires compatible hardware): . | Metric | Sensor Examples | . | Температура | BME280, BME680, SHT31 | . | Вологість | BME280, BME680, SHT31 | . | Атмосферний тиск | BME280, BMP280 | . | Опір газового сенсора | BME680 | . | IAQ (Air Quality) | BME680 | . Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted: . 💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/node-metrics.html#%D0%BF%D0%BE%D0%BA%D0%B0%D0%B7%D0%BD%D0%B8%D0%BA%D0%B8-%D0%B4%D0%BE%D0%B2%D0%BA%D1%96%D0%BB%D0%BB%D1%8F",
    
    "relUrl": "/uk-rUA/user/node-metrics.html#показники-довкілля"
  },"3375": {
    "doc": "Node Metrics",
    "title": "Air Quality Metrics",
    "content": "Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. | Metric | Unit | Опис | . | PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | . | PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | . | PM10 | µg/m³ | Particulate matter up to 10 microns | . | AQI | EPA index | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated. | . | CO₂ | ppm | Carbon dioxide concentration | . | CO₂ temperature | °C / °F | Temperature reported by the CO₂ sensor itself (e.g. SCD4x) | . | CO₂ humidity | % | Relative humidity reported by the CO₂ sensor | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | Band | CO₂ Range (ppm) | Color | . | Хороший | < 1000 | Зелений | . | Stuffy | < 2000 | Amber | . | Poor | < 5000 | Помаранчевий | . | Unsafe | < 30000 | Червоний | . | Evacuate | ≥ 30000 | Dark red | . An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can: . | Select a time frame for the charts. | Filter with metric chips — only metrics that have data are shown. | Refresh / request the latest air-quality telemetry. | Export to CSV for analysis in a spreadsheet. | . 💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/node-metrics.html#air-quality-metrics",
    
    "relUrl": "/uk-rUA/user/node-metrics.html#air-quality-metrics"
  },"3376": {
    "doc": "Node Metrics",
    "title": "Якість сигналу",
    "content": "Radio signal quality information: . | Metric | Опис | . | SNR | Signal-to-Noise Ratio (higher is better) | . | RSSI | Received Signal Strength Indicator (closer to 0 is better) | . | Noise Floor | Local background RF noise in dBm (more negative is quieter) | . | Hop Count | Number of mesh hops for last message | . Signal Quality Reference . Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | Quality | Criteria | . | Хороший | SNR above the preset’s limit | . | Задовільний | less than 5.5 dB below the limit | . | Поганий | 5.5 dB to 7.5 dB below the limit | . | Жоден | more than 7.5 dB below the limit | . See Understanding the Signal Meter for the full explanation. Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment. | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/node-metrics.html#%D1%8F%D0%BA%D1%96%D1%81%D1%82%D1%8C-%D1%81%D0%B8%D0%B3%D0%BD%D0%B0%D0%BB%D1%83",
    
    "relUrl": "/uk-rUA/user/node-metrics.html#якість-сигналу"
  },"3377": {
    "doc": "Node Metrics",
    "title": "Показники живлення",
    "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Опис | . | Напруга | Per-channel voltage reading | . | Поточний | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/node-metrics.html#%D0%BF%D0%BE%D0%BA%D0%B0%D0%B7%D0%BD%D0%B8%D0%BA%D0%B8-%D0%B6%D0%B8%D0%B2%D0%BB%D0%B5%D0%BD%D0%BD%D1%8F",
    
    "relUrl": "/uk-rUA/user/node-metrics.html#показники-живлення"
  },"3378": {
    "doc": "Node Metrics",
    "title": "Маршрут",
    "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | The app sends a traceroute request to the target node. | Results show each hop with its SNR. | . Reading Traceroute Results . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/node-metrics.html#%D0%BC%D0%B0%D1%80%D1%88%D1%80%D1%83%D1%82",
    
    "relUrl": "/uk-rUA/user/node-metrics.html#маршрут"
  },"3379": {
    "doc": "Node Metrics",
    "title": "Position Log",
    "content": "Historical position data for nodes that share their location: . | GPS coordinates | Висота | Speed (if moving) | Timestamp for each position report | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/node-metrics.html#position-log",
    
    "relUrl": "/uk-rUA/user/node-metrics.html#position-log"
  },"3380": {
    "doc": "Node Metrics",
    "title": "Інформація про сусідів",
    "content": "Shows which nodes a given node can directly hear, useful for understanding mesh topology. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/node-metrics.html#%D1%96%D0%BD%D1%84%D0%BE%D1%80%D0%BC%D0%B0%D1%86%D1%96%D1%8F-%D0%BF%D1%80%D0%BE-%D1%81%D1%83%D1%81%D1%96%D0%B4%D1%96%D0%B2",
    
    "relUrl": "/uk-rUA/user/node-metrics.html#інформація-про-сусідів"
  },"3381": {
    "doc": "Node Metrics",
    "title": "Показники хоста",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/node-metrics.html#%D0%BF%D0%BE%D0%BA%D0%B0%D0%B7%D0%BD%D0%B8%D0%BA%D0%B8-%D1%85%D0%BE%D1%81%D1%82%D0%B0",
    
    "relUrl": "/uk-rUA/user/node-metrics.html#показники-хоста"
  },"3382": {
    "doc": "Node Metrics",
    "title": "Показники PAX",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/node-metrics.html#%D0%BF%D0%BE%D0%BA%D0%B0%D0%B7%D0%BD%D0%B8%D0%BA%D0%B8-pax",
    
    "relUrl": "/uk-rUA/user/node-metrics.html#показники-pax"
  },"3383": {
    "doc": "Node Metrics",
    "title": "Related Topics",
    "content": ". | Nodes — node list, filtering, and sorting | Telemetry & Sensors — supported sensors and configuration | Signal Meter — how signal quality is calculated from SNR and RSSI | Local Mesh Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/node-metrics.html#related-topics",
    
    "relUrl": "/uk-rUA/user/node-metrics.html#related-topics"
  },"3384": {
    "doc": "Radion mittarit",
    "title": "Radion mittarit",
    "content": "Radion tietonäyttö tarjoaa kattavat telemetria- ja mittaritiedot jokaiselle verkon radiolle. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/node-metrics.html",
    
    "relUrl": "/fi-rFI/user/node-metrics.html"
  },"3385": {
    "doc": "Radion mittarit",
    "title": "Mittareiden tarkastelu",
    "content": ". | Siirry kohtaan Radiot. | Napauta radiota, jota haluat tarkastella. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Huomautus: Mittarit näkyvät vain, jos etäradio on lähettänyt ne. Mittarit päivittyvät kunkin radion telemetria-asetuksissa määritetyin väliajoin. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/node-metrics.html#mittareiden-tarkastelu",
    
    "relUrl": "/fi-rFI/user/node-metrics.html#mittareiden-tarkastelu"
  },"3386": {
    "doc": "Radion mittarit",
    "title": "Laitteen mittausloki",
    "content": "Perustoimintatiedot, jotka jokainen radio raportoi: . | Metrijärjestelmä | Kuvaus | . | Akun varaustaso | Nykyinen akun varaustaso | . | Jännite | Akun jännitelukema | . | Kanavan käyttöaste | Percentage of local airtime in use | . | Lähetysajan käyttöaste | Percentage of the last hour this node spent transmitting | . | Käyttöaika | Aika viimeisestä uudelleenkäynnistyksestä | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/node-metrics.html#laitteen-mittausloki",
    
    "relUrl": "/fi-rFI/user/node-metrics.html#laitteen-mittausloki"
  },"3387": {
    "doc": "Radion mittarit",
    "title": "Ympäristöarvot",
    "content": "Ympäristöanturien tiedot (edellyttää yhteensopivaa laitteistoa): . | Metrijärjestelmä | Anturiesimerkkejä | . | Lämpötila | BME280, BME680, SHT31 | . | Kosteus | BME280, BME680, SHT31 | . | Barometrinen paine | BME280, BMP280 | . | Kaasuvastus | BME680 | . | IAQ (ilmanlaatu) | BME680 | . Ympäristömittareista piirretään aikasarjat — lämpötila, ilmankosteus ja ilmanpaine näytetään kukin omana viivakaavionaan, ja mittayksikkö näkyy Y-akselilla. BME680:n IAQ (Indoor Air Quality) -indeksi on yksi arvo väliltä 0–500+, joka perustuu kaasun resistanssiin. Se näytetään värikoodatulla asteikolla välillä Erinomainen–Vaarallisen saastunut: . 💡 Vinkki: Ympäristömittarit edellyttävät etäradioon liitettyä anturia. Kaikki radiot eivät raportoi ympäristötietoja. Katso Telemetria ja anturit saadaksesi täydellisen luettelon tuetuista antureista. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/node-metrics.html#ymp%C3%A4rist%C3%B6arvot",
    
    "relUrl": "/fi-rFI/user/node-metrics.html#ympäristöarvot"
  },"3388": {
    "doc": "Radion mittarit",
    "title": "Ilmanlaatumittarit",
    "content": "Ilmanlaatu on erillinen mittarinäkymä radioille, joissa on hiukkas- ja/tai CO₂-anturi. Se on erillinen BME680:n IAQ-lukemasta, joka on lueteltu ympäristömittareissa — IAQ on yksittäinen kaasuvastukseen perustuva indeksi, kun taas ilmanlaatunäkymä esittää varsinaiset hiukkas- ja CO₂-mittaukset kaavioina. | Metrijärjestelmä | Yksikkö | Kuvaus | . | PM1.0 | µg/m³ | Enintään 1,0 mikrometrin kokoiset hiukkaset | . | PM2.5 | µg/m³ | Enintään 2,5 mikrometrin kokoiset hiukkaset | . | PM10 | µg/m³ | Enintään 10 mikrometrin kokoiset hiukkaset | . | AQI | EPA-indeksi | EPA:n NowCast-ilmanlaatuindeksi lasketaan radion viimeaikaisen PM2.5-historian perusteella, ja sen vakavuus näytetään värikoodattuna. Näytetään PM2.5-arvon yhteydessä, kun mittauksia on kertynyt riittävästi. | . | CO₂ | ppm | Hiilidioksidipitoisuus | . | CO₂ lämpötila | °C / °F | CO₂ anturin ilmoittama lämpötila (esim. SCD4x) | . | CO₂ kosteus | % | CO₂ anturin ilmoittama suhteellinen ilmankosteus | . CO₂-lukemat on värikoodattu vakavuuden mukaan, joten ilmanlaadun näkee yhdellä silmäyksellä: . | Taajuusalue | CO₂-pitoisuus (ppm) | Väri | . | Hyvä | < 1000 | Vihreä | . | Tunkkainen | < 2000 | Keltainen | . | Huono | < 5000 | Oranssi | . | Vaarallinen | < 30000 | Punainen | . | Evakuoi | ≥ 30000 | Tummanpunainen | . Ilmanlaatu tai mittaripainike näkyy radion tietonäytössä vain silloin, kun radio on raportoinut ilmanlaatutelemetriaa. Ilmanlaatu-näkymässä voit: . | Valita kaavioille aikajakson. | Suodattaa mittarisiruilla — vain mittarit, joista on dataa, näytetään. | Päivittää ja pyytää uusimmat ilmanlaatutelemetriatiedot. | Viedä CSV-tiedostoon analysoitavaksi taulukkolaskentaohjelmassa. | . 💡 Vinkki: Ilmanlaatumittarit edellyttävät yhteensopivaa ilmanlaatuanturia etäradiossa. Katso Telemetria ja anturit saadaksesi lisätietoja tuetusta laitteistosta. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/node-metrics.html#ilmanlaatumittarit",
    
    "relUrl": "/fi-rFI/user/node-metrics.html#ilmanlaatumittarit"
  },"3389": {
    "doc": "Radion mittarit",
    "title": "Signaalin laatu",
    "content": "Radiosignaalin laatutiedot: . | Metrijärjestelmä | Kuvaus | . | SNR | Signaali-kohinasuhde (suurempi SNR on parempi) | . | RSSI | Vastaanotetun signaalin voimakkuusindikaattori (RSSI) (lähempänä nollaa on parempi) | . | Kohinataso | Paikallinen taustakohina dBm-arvona (negatiivisempi on hiljaisempi) | . | Hyppylaskuri | Verkon hyppymäärä viimeisimmälle viestille | . Signaalin laadun viitearvot . Signaalin laatu arvioidaan SNR-arvon perusteella suhteessa käytössä olevan LoRa-modeemiesiasetuksen demodulaation alarajaan, ei kiinteiden raja-arvojen perusteella. Sama SNR-arvo voi tarkoittaa eri asioita eri esiasetuksilla (esim. -15 dB on hyvä LongSlow-esiasetuksella, mutta käyttökelvoton ShortFast-esiasetuksella). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. Taulukossa raja tarkoittaa esiasetuksen SNR-rajaa. | Laatu | Kriteerit | . | Hyvä | SNR esiasetuksen rajan yläpuolella | . | Kohtalainen | alle 5,5 dB rajan alapuolella | . | Huono | 5,5–7,5 dB rajan alapuolella | . | ei mitään | yli 7,5 dB rajan alapuolella | . Katso Signaalimittarin toiminta, jos haluat täydellisen selityksen. Yhdistetyn radion paikalliset tilastot näytetään myös Signaalin laatu -näkymässä silloin, kun ne ovat saatavilla. Nämä kerätyt tiedot sisältävät kohinatason, liikennelaskurit, välityslaskurit, verkossa olevien radioiden määrän sekä radion käyttöajan. Kohinatason kaaviossa käytetään katkoviivalla merkittyä viiteviivaa arvossa -85 dBm, jotta kuormittunut RF-ympäristö on helpompi tunnistaa. | Pyydä — pyydä yhdistettyä radiota lähettämään uusi Local Stats -telemetriaraportti | Tyhjennä — poista tämän radion Local Stats -lokit | Tallenna — vie näkyvä Local Stats -historia CSV-tiedostoon | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/node-metrics.html#signaalin-laatu",
    
    "relUrl": "/fi-rFI/user/node-metrics.html#signaalin-laatu"
  },"3390": {
    "doc": "Radion mittarit",
    "title": "Virranhallinnan arvot",
    "content": "Virranhallintatelemetria (edellyttää INA-anturia tai yhteensopivaa laitteistoa): . | Metrijärjestelmä | Kuvaus | . | Jännite | Kanavakohtainen jännitelukema | . | Virta | Kanavakohtainen virrankulutus milliampeereina | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/node-metrics.html#virranhallinnan-arvot",
    
    "relUrl": "/fi-rFI/user/node-metrics.html#virranhallinnan-arvot"
  },"3391": {
    "doc": "Radion mittarit",
    "title": "Reitinselvitys",
    "content": "Reitinselvitys näyttää viestin kulkeman reitin verkossa: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | Sovellus lähettää reitinselvityspyynnön kohderadiolle. | Results show each hop with its SNR. | . Reitinselvityksen tulosten lukeminen . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/node-metrics.html#reitinselvitys",
    
    "relUrl": "/fi-rFI/user/node-metrics.html#reitinselvitys"
  },"3392": {
    "doc": "Radion mittarit",
    "title": "Sijainnin Loki",
    "content": "Historialliset sijaintitiedot radioille, jotka jakavat sijaintinsa: . | GPS-koordinaatit | Korkeus | Nopeus (jos radio liikkuu) | Aikaleima jokaiselle sijaintiraportille | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/node-metrics.html#sijainnin-loki",
    
    "relUrl": "/fi-rFI/user/node-metrics.html#sijainnin-loki"
  },"3393": {
    "doc": "Radion mittarit",
    "title": "Naapuritieto",
    "content": "Näyttää, mitkä radiot tietty radio voi kuulla suoraan, mikä auttaa ymmärtämään verkon topologiaa. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/node-metrics.html#naapuritieto",
    
    "relUrl": "/fi-rFI/user/node-metrics.html#naapuritieto"
  },"3394": {
    "doc": "Radion mittarit",
    "title": "Isäntälaitteen mittausarvot",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/node-metrics.html#is%C3%A4nt%C3%A4laitteen-mittausarvot",
    
    "relUrl": "/fi-rFI/user/node-metrics.html#isäntälaitteen-mittausarvot"
  },"3395": {
    "doc": "Radion mittarit",
    "title": "Pax mittarit",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/node-metrics.html#pax-mittarit",
    
    "relUrl": "/fi-rFI/user/node-metrics.html#pax-mittarit"
  },"3396": {
    "doc": "Radion mittarit",
    "title": "Aiheeseen liittyvät aiheet",
    "content": ". | Radiot — radioluettelo, suodatus ja lajittelu | Telemetria ja anturit — tuetut anturit ja määritykset | Signaalimittari — miten signaalin laatu lasketaan SNR- ja RSSI-arvoista | Paikallinen mesh-verkon etsintä — reitiselvityksen tiedot ja naapuritiedot | Yksiköt ja aluekohtaiset asetukset — lämpötilan, etäisyyden ja nopeuden näyttömuodot | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/node-metrics.html#aiheeseen-liittyv%C3%A4t-aiheet",
    
    "relUrl": "/fi-rFI/user/node-metrics.html#aiheeseen-liittyvät-aiheet"
  },"3397": {
    "doc": "Node Metrics",
    "title": "Node Metrics",
    "content": "The node detail screen provides comprehensive telemetry and metrics for each node on your mesh. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/node-metrics.html",
    
    "relUrl": "/is-rIS/user/node-metrics.html"
  },"3398": {
    "doc": "Node Metrics",
    "title": "Viewing Metrics",
    "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/node-metrics.html#viewing-metrics",
    
    "relUrl": "/is-rIS/user/node-metrics.html#viewing-metrics"
  },"3399": {
    "doc": "Node Metrics",
    "title": "Device Metrics",
    "content": "Basic operating information reported by each node: . | Metric | Lýsing | . | Battery Level | Current battery percentage | . | Voltage | Battery voltage reading | . | ChUtil | Percentage of local airtime in use | . | AirUtil | Percentage of the last hour this node spent transmitting | . | Uptime | Time since last reboot | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/node-metrics.html#device-metrics",
    
    "relUrl": "/is-rIS/user/node-metrics.html#device-metrics"
  },"3400": {
    "doc": "Node Metrics",
    "title": "Environment Metrics",
    "content": "Environmental sensor data (requires compatible hardware): . | Metric | Sensor Examples | . | Temperature | BME280, BME680, SHT31 | . | Humidity | BME280, BME680, SHT31 | . | Barometric Pressure | BME280, BMP280 | . | Gas Resistance | BME680 | . | IAQ (Air Quality) | BME680 | . Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted: . 💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/node-metrics.html#environment-metrics",
    
    "relUrl": "/is-rIS/user/node-metrics.html#environment-metrics"
  },"3401": {
    "doc": "Node Metrics",
    "title": "Air Quality Metrics",
    "content": "Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. | Metric | Unit | Lýsing | . | PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | . | PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | . | PM10 | µg/m³ | Particulate matter up to 10 microns | . | AQI | EPA index | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated. | . | CO₂ | ppm | Carbon dioxide concentration | . | CO₂ temperature | °C / °F | Temperature reported by the CO₂ sensor itself (e.g. SCD4x) | . | CO₂ humidity | % | Relative humidity reported by the CO₂ sensor | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | Band | CO₂ Range (ppm) | Color | . | Good | < 1000 | Green | . | Stuffy | < 2000 | Amber | . | Poor | < 5000 | Orange | . | Unsafe | < 30000 | Red | . | Evacuate | ≥ 30000 | Dark red | . An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can: . | Select a time frame for the charts. | Filter with metric chips — only metrics that have data are shown. | Refresh / request the latest air-quality telemetry. | Export to CSV for analysis in a spreadsheet. | . 💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/node-metrics.html#air-quality-metrics",
    
    "relUrl": "/is-rIS/user/node-metrics.html#air-quality-metrics"
  },"3402": {
    "doc": "Node Metrics",
    "title": "Signal Quality",
    "content": "Radio signal quality information: . | Metric | Lýsing | . | SNR | Signal-to-Noise Ratio (higher is better) | . | RSSI | Received Signal Strength Indicator (closer to 0 is better) | . | Noise Floor | Local background RF noise in dBm (more negative is quieter) | . | Hop Count | Number of mesh hops for last message | . Signal Quality Reference . Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | Quality | Criteria | . | Good | SNR above the preset’s limit | . | Fair | less than 5.5 dB below the limit | . | Bad | 5.5 dB to 7.5 dB below the limit | . | None | more than 7.5 dB below the limit | . See Understanding the Signal Meter for the full explanation. Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment. | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/node-metrics.html#signal-quality",
    
    "relUrl": "/is-rIS/user/node-metrics.html#signal-quality"
  },"3403": {
    "doc": "Node Metrics",
    "title": "Power Metrics",
    "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Lýsing | . | Voltage | Per-channel voltage reading | . | Current | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/node-metrics.html#power-metrics",
    
    "relUrl": "/is-rIS/user/node-metrics.html#power-metrics"
  },"3404": {
    "doc": "Node Metrics",
    "title": "Ferilkönnun",
    "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | The app sends a traceroute request to the target node. | Results show each hop with its SNR. | . Reading Traceroute Results . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/node-metrics.html#ferilk%C3%B6nnun",
    
    "relUrl": "/is-rIS/user/node-metrics.html#ferilkönnun"
  },"3405": {
    "doc": "Node Metrics",
    "title": "Position Log",
    "content": "Historical position data for nodes that share their location: . | GPS coordinates | Altitude | Speed (if moving) | Timestamp for each position report | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/node-metrics.html#position-log",
    
    "relUrl": "/is-rIS/user/node-metrics.html#position-log"
  },"3406": {
    "doc": "Node Metrics",
    "title": "Neighbor Info",
    "content": "Shows which nodes a given node can directly hear, useful for understanding mesh topology. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/node-metrics.html#neighbor-info",
    
    "relUrl": "/is-rIS/user/node-metrics.html#neighbor-info"
  },"3407": {
    "doc": "Node Metrics",
    "title": "Host Metrics",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/node-metrics.html#host-metrics",
    
    "relUrl": "/is-rIS/user/node-metrics.html#host-metrics"
  },"3408": {
    "doc": "Node Metrics",
    "title": "PAX Metrics",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/node-metrics.html#pax-metrics",
    
    "relUrl": "/is-rIS/user/node-metrics.html#pax-metrics"
  },"3409": {
    "doc": "Node Metrics",
    "title": "Related Topics",
    "content": ". | Nodes — node list, filtering, and sorting | Telemetry & Sensors — supported sensors and configuration | Signal Meter — how signal quality is calculated from SNR and RSSI | Local Mesh Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/node-metrics.html#related-topics",
    
    "relUrl": "/is-rIS/user/node-metrics.html#related-topics"
  },"3410": {
    "doc": "Node Metrics",
    "title": "Node Metrics",
    "content": "The node detail screen provides comprehensive telemetry and metrics for each node on your mesh. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/node-metrics.html",
    
    "relUrl": "/lt-rLT/user/node-metrics.html"
  },"3411": {
    "doc": "Node Metrics",
    "title": "Viewing Metrics",
    "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/node-metrics.html#viewing-metrics",
    
    "relUrl": "/lt-rLT/user/node-metrics.html#viewing-metrics"
  },"3412": {
    "doc": "Node Metrics",
    "title": "Device Metrics",
    "content": "Basic operating information reported by each node: . | Metric | Aprašymas | . | Battery Level | Current battery percentage | . | Voltage | Battery voltage reading | . | ChUtil | Percentage of local airtime in use | . | AirUtil | Percentage of the last hour this node spent transmitting | . | Uptime | Time since last reboot | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/node-metrics.html#device-metrics",
    
    "relUrl": "/lt-rLT/user/node-metrics.html#device-metrics"
  },"3413": {
    "doc": "Node Metrics",
    "title": "Environment Metrics",
    "content": "Environmental sensor data (requires compatible hardware): . | Metric | Sensor Examples | . | Temperatūra | BME280, BME680, SHT31 | . | Drėgmė | BME280, BME680, SHT31 | . | Barometric Pressure | BME280, BMP280 | . | Gas Resistance | BME680 | . | IAQ (Air Quality) | BME680 | . Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted: . 💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/node-metrics.html#environment-metrics",
    
    "relUrl": "/lt-rLT/user/node-metrics.html#environment-metrics"
  },"3414": {
    "doc": "Node Metrics",
    "title": "Air Quality Metrics",
    "content": "Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. | Metric | Unit | Aprašymas | . | PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | . | PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | . | PM10 | µg/m³ | Particulate matter up to 10 microns | . | AQI | EPA index | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated. | . | CO₂ | ppm | Carbon dioxide concentration | . | CO₂ temperature | °C / °F | Temperature reported by the CO₂ sensor itself (e.g. SCD4x) | . | CO₂ humidity | % | Relative humidity reported by the CO₂ sensor | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | Band | CO₂ Range (ppm) | Color | . | Geras | < 1000 | Green | . | Stuffy | < 2000 | Amber | . | Poor | < 5000 | Orange | . | Unsafe | < 30000 | Raudona | . | Evacuate | ≥ 30000 | Dark red | . An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can: . | Select a time frame for the charts. | Filter with metric chips — only metrics that have data are shown. | Refresh / request the latest air-quality telemetry. | Export to CSV for analysis in a spreadsheet. | . 💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/node-metrics.html#air-quality-metrics",
    
    "relUrl": "/lt-rLT/user/node-metrics.html#air-quality-metrics"
  },"3415": {
    "doc": "Node Metrics",
    "title": "Signalo kokybė",
    "content": "Radio signal quality information: . | Metric | Aprašymas | . | SNR | Signal-to-Noise Ratio (higher is better) | . | RSSI | Received Signal Strength Indicator (closer to 0 is better) | . | Noise Floor | Local background RF noise in dBm (more negative is quieter) | . | Hop Count | Number of mesh hops for last message | . Signal Quality Reference . Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | Quality | Criteria | . | Geras | SNR above the preset’s limit | . | Pakankamas | less than 5.5 dB below the limit | . | Silpnas | 5.5 dB to 7.5 dB below the limit | . | Nėra | more than 7.5 dB below the limit | . See Understanding the Signal Meter for the full explanation. Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment. | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/node-metrics.html#signalo-kokyb%C4%97",
    
    "relUrl": "/lt-rLT/user/node-metrics.html#signalo-kokybė"
  },"3416": {
    "doc": "Node Metrics",
    "title": "Power Metrics",
    "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Aprašymas | . | Voltage | Per-channel voltage reading | . | Current | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/node-metrics.html#power-metrics",
    
    "relUrl": "/lt-rLT/user/node-metrics.html#power-metrics"
  },"3417": {
    "doc": "Node Metrics",
    "title": "Žinutės kelias",
    "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | The app sends a traceroute request to the target node. | Results show each hop with its SNR. | . Reading Traceroute Results . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/node-metrics.html#%C5%BEinut%C4%97s-kelias",
    
    "relUrl": "/lt-rLT/user/node-metrics.html#žinutės-kelias"
  },"3418": {
    "doc": "Node Metrics",
    "title": "Pozicijos  duomenų žurnalas",
    "content": "Historical position data for nodes that share their location: . | GPS coordinates | Altitude | Speed (if moving) | Timestamp for each position report | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/node-metrics.html#pozicijos--duomen%C5%B3-%C5%BEurnalas",
    
    "relUrl": "/lt-rLT/user/node-metrics.html#pozicijos--duomenų-žurnalas"
  },"3419": {
    "doc": "Node Metrics",
    "title": "Neighbor Info",
    "content": "Shows which nodes a given node can directly hear, useful for understanding mesh topology. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/node-metrics.html#neighbor-info",
    
    "relUrl": "/lt-rLT/user/node-metrics.html#neighbor-info"
  },"3420": {
    "doc": "Node Metrics",
    "title": "Host Metrics",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/node-metrics.html#host-metrics",
    
    "relUrl": "/lt-rLT/user/node-metrics.html#host-metrics"
  },"3421": {
    "doc": "Node Metrics",
    "title": "PAX Metrics",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/node-metrics.html#pax-metrics",
    
    "relUrl": "/lt-rLT/user/node-metrics.html#pax-metrics"
  },"3422": {
    "doc": "Node Metrics",
    "title": "Related Topics",
    "content": ". | Nodes — node list, filtering, and sorting | Telemetry & Sensors — supported sensors and configuration | Signal Meter — how signal quality is calculated from SNR and RSSI | Local Mesh Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/node-metrics.html#related-topics",
    
    "relUrl": "/lt-rLT/user/node-metrics.html#related-topics"
  },"3423": {
    "doc": "Node Metrics",
    "title": "Node Metrics",
    "content": "The node detail screen provides comprehensive telemetry and metrics for each node on your mesh. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/node-metrics.html",
    
    "relUrl": "/gl-rES/user/node-metrics.html"
  },"3424": {
    "doc": "Node Metrics",
    "title": "Viewing Metrics",
    "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/node-metrics.html#viewing-metrics",
    
    "relUrl": "/gl-rES/user/node-metrics.html#viewing-metrics"
  },"3425": {
    "doc": "Node Metrics",
    "title": "Device Metrics",
    "content": "Basic operating information reported by each node: . | Metric | Descrición | . | Battery Level | Current battery percentage | . | Voltage | Battery voltage reading | . | ChUtil | Percentage of local airtime in use | . | AirUtil | Percentage of the last hour this node spent transmitting | . | Uptime | Time since last reboot | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/node-metrics.html#device-metrics",
    
    "relUrl": "/gl-rES/user/node-metrics.html#device-metrics"
  },"3426": {
    "doc": "Node Metrics",
    "title": "Environment Metrics",
    "content": "Environmental sensor data (requires compatible hardware): . | Metric | Sensor Examples | . | Temperature | BME280, BME680, SHT31 | . | Humidity | BME280, BME680, SHT31 | . | Barometric Pressure | BME280, BMP280 | . | Gas Resistance | BME680 | . | IAQ (Air Quality) | BME680 | . Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted: . 💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/node-metrics.html#environment-metrics",
    
    "relUrl": "/gl-rES/user/node-metrics.html#environment-metrics"
  },"3427": {
    "doc": "Node Metrics",
    "title": "Air Quality Metrics",
    "content": "Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. | Metric | Unit | Descrición | . | PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | . | PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | . | PM10 | µg/m³ | Particulate matter up to 10 microns | . | AQI | EPA index | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated. | . | CO₂ | ppm | Carbon dioxide concentration | . | CO₂ temperature | °C / °F | Temperature reported by the CO₂ sensor itself (e.g. SCD4x) | . | CO₂ humidity | % | Relative humidity reported by the CO₂ sensor | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | Band | CO₂ Range (ppm) | Color | . | Good | < 1000 | Green | . | Stuffy | < 2000 | Amber | . | Poor | < 5000 | Orange | . | Unsafe | < 30000 | Red | . | Evacuate | ≥ 30000 | Dark red | . An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can: . | Select a time frame for the charts. | Filter with metric chips — only metrics that have data are shown. | Refresh / request the latest air-quality telemetry. | Export to CSV for analysis in a spreadsheet. | . 💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/node-metrics.html#air-quality-metrics",
    
    "relUrl": "/gl-rES/user/node-metrics.html#air-quality-metrics"
  },"3428": {
    "doc": "Node Metrics",
    "title": "Signal Quality",
    "content": "Radio signal quality information: . | Metric | Descrición | . | SNR | Signal-to-Noise Ratio (higher is better) | . | RSSI | Received Signal Strength Indicator (closer to 0 is better) | . | Noise Floor | Local background RF noise in dBm (more negative is quieter) | . | Hop Count | Number of mesh hops for last message | . Signal Quality Reference . Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | Quality | Criteria | . | Good | SNR above the preset’s limit | . | Fair | less than 5.5 dB below the limit | . | Bad | 5.5 dB to 7.5 dB below the limit | . | None | more than 7.5 dB below the limit | . See Understanding the Signal Meter for the full explanation. Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment. | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/node-metrics.html#signal-quality",
    
    "relUrl": "/gl-rES/user/node-metrics.html#signal-quality"
  },"3429": {
    "doc": "Node Metrics",
    "title": "Power Metrics",
    "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Descrición | . | Voltage | Per-channel voltage reading | . | Current | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/node-metrics.html#power-metrics",
    
    "relUrl": "/gl-rES/user/node-metrics.html#power-metrics"
  },"3430": {
    "doc": "Node Metrics",
    "title": "Traza-ruta",
    "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | The app sends a traceroute request to the target node. | Results show each hop with its SNR. | . Reading Traceroute Results . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/node-metrics.html#traza-ruta",
    
    "relUrl": "/gl-rES/user/node-metrics.html#traza-ruta"
  },"3431": {
    "doc": "Node Metrics",
    "title": "Position Log",
    "content": "Historical position data for nodes that share their location: . | GPS coordinates | Altitude | Speed (if moving) | Timestamp for each position report | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/node-metrics.html#position-log",
    
    "relUrl": "/gl-rES/user/node-metrics.html#position-log"
  },"3432": {
    "doc": "Node Metrics",
    "title": "Neighbor Info",
    "content": "Shows which nodes a given node can directly hear, useful for understanding mesh topology. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/node-metrics.html#neighbor-info",
    
    "relUrl": "/gl-rES/user/node-metrics.html#neighbor-info"
  },"3433": {
    "doc": "Node Metrics",
    "title": "Host Metrics",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/node-metrics.html#host-metrics",
    
    "relUrl": "/gl-rES/user/node-metrics.html#host-metrics"
  },"3434": {
    "doc": "Node Metrics",
    "title": "PAX Metrics",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/node-metrics.html#pax-metrics",
    
    "relUrl": "/gl-rES/user/node-metrics.html#pax-metrics"
  },"3435": {
    "doc": "Node Metrics",
    "title": "Related Topics",
    "content": ". | Nodes — node list, filtering, and sorting | Telemetry & Sensors — supported sensors and configuration | Signal Meter — how signal quality is calculated from SNR and RSSI | Local Mesh Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/node-metrics.html#related-topics",
    
    "relUrl": "/gl-rES/user/node-metrics.html#related-topics"
  },"3436": {
    "doc": "ノードメトリクス",
    "title": "ノードメトリクス",
    "content": "ノードの詳細画面では、メッシュ上の各ノードについて、包括的なテレメトリとメトリクスを確認できます。 . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/node-metrics.html",
    
    "relUrl": "/ja-rJP/user/node-metrics.html"
  },"3437": {
    "doc": "ノードメトリクス",
    "title": "メトリクスを表示する",
    "content": ". | 「ノード」に移動します。 | 確認したいノードをタップします。 | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. メトリクスは、各ノードのテレメトリ設定で構成された間隔で更新されます。 . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/node-metrics.html#%E3%83%A1%E3%83%88%E3%83%AA%E3%82%AF%E3%82%B9%E3%82%92%E8%A1%A8%E7%A4%BA%E3%81%99%E3%82%8B",
    
    "relUrl": "/ja-rJP/user/node-metrics.html#メトリクスを表示する"
  },"3438": {
    "doc": "ノードメトリクス",
    "title": "デバイスメトリクス",
    "content": "各ノードが報告する基本的な動作情報です： . | メトリクス | 説明 | . | バッテリー残量 | 現在のバッテリー残量（％） | . | 電圧 | バッテリー電圧の測定値 | . | ChUtil | Percentage of local airtime in use | . | AirUtil | Percentage of the last hour this node spent transmitting | . | 連続稼働時間 | 前回の再起動からの経過時間 | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/node-metrics.html#%E3%83%87%E3%83%90%E3%82%A4%E3%82%B9%E3%83%A1%E3%83%88%E3%83%AA%E3%82%AF%E3%82%B9",
    
    "relUrl": "/ja-rJP/user/node-metrics.html#デバイスメトリクス"
  },"3439": {
    "doc": "ノードメトリクス",
    "title": "環境メトリクス",
    "content": "環境センサーのデータです（対応ハードウェアが必要）： . | メトリクス | センサーの例 | . | 温度 | BME280, BME680, SHT31 | . | 湿度 | BME280, BME680, SHT31 | . | 大気圧 | BME280, BMP280 | . | ガス抵抗 | BME680 | . | IAQ（大気質） | BME680 | . Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. BME680 の **IAQ（室内空気質）**指数は、ガス抵抗から算出される 0〜500+ の単一の値で、非常に良い から 危険なほど汚染 までの色分けされたスケールで表示されます： . 💡 ヒント： 環境メトリクスには、リモートノードに接続されたセンサーが必要です。すべてのノードが環境データを報告するわけではありません。対応センサーの一覧については、テレメトリとセンサー を参照してください。 . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/node-metrics.html#%E7%92%B0%E5%A2%83%E3%83%A1%E3%83%88%E3%83%AA%E3%82%AF%E3%82%B9",
    
    "relUrl": "/ja-rJP/user/node-metrics.html#環境メトリクス"
  },"3440": {
    "doc": "ノードメトリクス",
    "title": "大気質メトリクス",
    "content": "大気質は、粒子状物質センサーや CO₂ センサーを搭載したノード向けの専用メトリクスビューです。これは、環境メトリクスに記載されている BME680 の IAQ の測定値とは別のものです。IAQ はガス抵抗から算出される単一の指数であるのに対し、大気質ビューはその基となる粒子状物質と CO₂ の測定値をグラフ化します。 . | メトリクス | 単位 | 説明 | . | PM1.0 | µg/m³ | 1.0 ミクロンまでの粒子状物質 | . | PM2.5 | µg/m³ | 2.5 ミクロンまでの粒子状物質 | . | PM10 | µg/m³ | 10 ミクロンまでの粒子状物質 | . | AQI | EPA 指数 | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. 十分な測定値が蓄積されると、PM2.5 の横に表示されます。 | . | CO₂ | ppm | 二酸化炭素の濃度 | . | CO₂ 温度 | °C / °F | CO₂ センサー自体が報告する温度（例：SCD4x） | . | CO₂ 湿度 | % | CO₂ センサーが報告する相対湿度 | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | 区分 | CO₂ の範囲（ppm） | 色 | . | 良 | < 1000 | 緑 | . | 空気がこもる | < 2000 | 黄色 | . | 不良 | < 5000 | オレンジ | . | 危険 | < 30000 | 赤 | . | 退避 | ≥ 30000 | 濃い赤 | . 大気質のログ／メトリクスボタンは、ノードが大気質のテレメトリを報告したときにのみ、ノードの詳細画面に表示されます。大気質ビューでは、次のことができます： . | グラフの期間を選択します。 | メトリクスチップで絞り込みます。データがあるメトリクスのみが表示されます。 | 最新の大気質テレメトリを更新／要求します。 | 表計算ソフトで分析できるよう、CSV にエクスポートします。 | . 💡 ヒント： 大気質メトリクスには、リモートノードに対応する大気質センサーが必要です。対応ハードウェアについては、テレメトリとセンサー を参照してください。 . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/node-metrics.html#%E5%A4%A7%E6%B0%97%E8%B3%AA%E3%83%A1%E3%83%88%E3%83%AA%E3%82%AF%E3%82%B9",
    
    "relUrl": "/ja-rJP/user/node-metrics.html#大気質メトリクス"
  },"3441": {
    "doc": "ノードメトリクス",
    "title": "信号品質",
    "content": "無線信号の品質に関する情報です： . | メトリクス | 説明 | . | SN比 | 信号対ノイズ比（高いほど良い） | . | RSSI | 受信信号強度インジケーター（0 に近いほど良い） | . | ノイズフロア | ローカルの背景 RF ノイズ（dBm、値が小さい（負が大きい）ほど静か） | . | ホップ数 | 直前のメッセージのメッシュホップ数 | . 信号品質の目安 . 信号品質は、固定のしきい値ではなく、現在の LoRa モデムプリセットの復調限界に対する SNR で評価されます。同じ SNR でもプリセットによって意味が異なります（例：−15 dB は LongSlow では問題ありませんが、ShortFast では使い物になりません）。 When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | 品質 | 基準 | . | 良 | SNR がプリセットの限界を上回る | . | 普通 | 限界より 5.5 dB 未満低い | . | 不良 | 限界より 5.5 dB〜7.5 dB 低い | . | なし | 限界より 7.5 dB を超えて低い | . 詳しい説明は、信号メーターを理解する を参照してください。 . 接続中の無線機のローカル統計も、利用可能な場合は信号品質に表示されます。これらのログには、ノイズフロア、トラフィックカウンター、中継カウンター、オンラインノード数、無線機の連続稼働時間が含まれます。ノイズフロアのグラフでは、混雑した RF 環境を見分けやすいよう、-85 dBm に破線の基準線が引かれます。 . | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/node-metrics.html#%E4%BF%A1%E5%8F%B7%E5%93%81%E8%B3%AA",
    
    "relUrl": "/ja-rJP/user/node-metrics.html#信号品質"
  },"3442": {
    "doc": "ノードメトリクス",
    "title": "電力メトリクス",
    "content": "電力管理のテレメトリです（INA センサーまたは対応ハードウェアが必要）： . | メトリクス | 説明 | . | 電圧 | Per-channel voltage reading | . | 電流 | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/node-metrics.html#%E9%9B%BB%E5%8A%9B%E3%83%A1%E3%83%88%E3%83%AA%E3%82%AF%E3%82%B9",
    
    "relUrl": "/ja-rJP/user/node-metrics.html#電力メトリクス"
  },"3443": {
    "doc": "ノードメトリクス",
    "title": "ルート追跡",
    "content": "ルート追跡は、メッセージがメッシュ内を通る経路を表示します： . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | アプリが対象のノードにルート追跡の要求を送信します。 | Results show each hop with its SNR. | . ルート追跡の結果の見方 . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/node-metrics.html#%E3%83%AB%E3%83%BC%E3%83%88%E8%BF%BD%E8%B7%A1",
    
    "relUrl": "/ja-rJP/user/node-metrics.html#ルート追跡"
  },"3444": {
    "doc": "ノードメトリクス",
    "title": "位置ログ",
    "content": "位置情報を共有しているノードの、過去の位置データです： . | GPS 座標 | 標高 | 速度（移動中の場合） | 各位置報告のタイムスタンプ | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/node-metrics.html#%E4%BD%8D%E7%BD%AE%E3%83%AD%E3%82%B0",
    
    "relUrl": "/ja-rJP/user/node-metrics.html#位置ログ"
  },"3445": {
    "doc": "ノードメトリクス",
    "title": "隣接ノード情報",
    "content": "あるノードが直接受信できるノードを表示します。メッシュのトポロジーを把握するのに役立ちます。 . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/node-metrics.html#%E9%9A%A3%E6%8E%A5%E3%83%8E%E3%83%BC%E3%83%89%E6%83%85%E5%A0%B1",
    
    "relUrl": "/ja-rJP/user/node-metrics.html#隣接ノード情報"
  },"3446": {
    "doc": "ノードメトリクス",
    "title": "ホストのメトリクス",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/node-metrics.html#%E3%83%9B%E3%82%B9%E3%83%88%E3%81%AE%E3%83%A1%E3%83%88%E3%83%AA%E3%82%AF%E3%82%B9",
    
    "relUrl": "/ja-rJP/user/node-metrics.html#ホストのメトリクス"
  },"3447": {
    "doc": "ノードメトリクス",
    "title": "PAX メトリクス",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/node-metrics.html#pax-%E3%83%A1%E3%83%88%E3%83%AA%E3%82%AF%E3%82%B9",
    
    "relUrl": "/ja-rJP/user/node-metrics.html#pax-メトリクス"
  },"3448": {
    "doc": "ノードメトリクス",
    "title": "関連トピック",
    "content": ". | ノード：ノードリスト、絞り込み、並べ替え | テレメトリとセンサー：対応センサーと設定 | 信号メーター：SNR と RSSI から信号品質を計算する方法 | Local Mesh Discovery — traceroute details and neighbor info | 単位とロケール：温度・距離・速度の表示形式 | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/node-metrics.html#%E9%96%A2%E9%80%A3%E3%83%88%E3%83%94%E3%83%83%E3%82%AF",
    
    "relUrl": "/ja-rJP/user/node-metrics.html#関連トピック"
  },"3449": {
    "doc": "Node Metrics",
    "title": "Node Metrics",
    "content": "The node detail screen provides comprehensive telemetry and metrics for each node on your mesh. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/node-metrics.html",
    
    "relUrl": "/de-rDE/user/node-metrics.html"
  },"3450": {
    "doc": "Node Metrics",
    "title": "Viewing Metrics",
    "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/node-metrics.html#viewing-metrics",
    
    "relUrl": "/de-rDE/user/node-metrics.html#viewing-metrics"
  },"3451": {
    "doc": "Node Metrics",
    "title": "Gerätedaten",
    "content": "Basic operating information reported by each node: . | Metrisch | Beschreibung | . | Batterie Ladung | Current battery percentage | . | Spannung | Battery voltage reading | . | Kanalauslastung | Percentage of local airtime in use | . | Sendezeit | Percentage of the last hour this node spent transmitting | . | Laufzeit | Time since last reboot | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/node-metrics.html#ger%C3%A4tedaten",
    
    "relUrl": "/de-rDE/user/node-metrics.html#gerätedaten"
  },"3452": {
    "doc": "Node Metrics",
    "title": "Umweltdaten",
    "content": "Environmental sensor data (requires compatible hardware): . | Metrisch | Sensor Examples | . | Temperatur | BME280, BME680, SHT31 | . | Luftfeuchtigkeit | BME280, BME680, SHT31 | . | Luftdruck | BME280, BMP280 | . | Gaswiderstand | BME680 | . | IAQ (Air Quality) | BME680 | . Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. Der IAQ-Index (Indoor Air Quality / Raumluftqualität) des BME680 ist ein einzelner Wert im Bereich von 0 bis über 500, der aus dem Gaswiderstand abgeleitet und auf einer farbcodierten Skala von Ausgezeichnet bis Gefährlich belastet dargestellt wird: . 💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/node-metrics.html#umweltdaten",
    
    "relUrl": "/de-rDE/user/node-metrics.html#umweltdaten"
  },"3453": {
    "doc": "Node Metrics",
    "title": "Air Quality Metrics",
    "content": "Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. Dies ist unabhängig vom BME680-IAQ-Messwert, der unter „Environment Metrics“ (Umgebungsmesswerte) aufgeführt ist – IAQ ist ein einzelner, aus dem Gaswiderstand abgeleiteter Index, während die Luftqualitätsansicht die zugrundeliegenden Messwerte für Feinstaub und CO₂ grafisch darstellt. | Metrisch | Einheit | Beschreibung | . | PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | . | PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | . | PM10 | µg/m³ | Particulate matter up to 10 microns | . | AQI | EPA index | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated. | . | CO₂ | ppm | Carbon dioxide concentration | . | CO₂ temperature | °C / °F | Temperature reported by the CO₂ sensor itself (e.g. SCD4x) | . | CO₂ humidity | % | Relative humidity reported by the CO₂ sensor | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | Band | CO₂ Range (ppm) | Farbe | . | Gut | < 1000 | Grün | . | Stuffy | < 2000 | Gelb | . | Schlecht | < 5000 | Orange | . | Unsafe | < 30000 | Rot | . | Evacuate | ≥ 30000 | Dark red | . An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can: . | Select a time frame for the charts. | Filter with metric chips — only metrics that have data are shown. | Refresh / request the latest air-quality telemetry. | Export to CSV for analysis in a spreadsheet. | . 💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/node-metrics.html#air-quality-metrics",
    
    "relUrl": "/de-rDE/user/node-metrics.html#air-quality-metrics"
  },"3454": {
    "doc": "Node Metrics",
    "title": "Signalqualität",
    "content": "Radio signal quality information: . | Metrisch | Beschreibung | . | SNR | Signal-to-Noise Ratio (higher is better) | . | RSSI | Received Signal Strength Indicator (closer to 0 is better) | . | Noise Floor | Local background RF noise in dBm (more negative is quieter) | . | Sprungweite | Number of mesh hops for last message | . Signal Quality Reference . Die Signalqualität wird auf der Grundlage des Signal-Rauschabstand im Verhältnis zur Demodulationsschwelle der aktiven LoRa-Modem-Voreinstellung bewertet, nicht anhand fester Schwellenwerte – ein bestimmter Wert des Signal-Rauschabstand hat je nach Voreinstellung unterschiedliche Bedeutungen (z. B. sind −15 dB bei „LongSlow“ in Ordnung, bei „ShortFast“ jedoch unbrauchbar). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | Quality | Criteria | . | Gut | SNR above the preset’s limit | . | Ordentliche Signalstärke | less than 5.5 dB below the limit | . | Schlecht | 5.5 dB to 7.5 dB below the limit | . | Keins | more than 7.5 dB below the limit | . See Understanding the Signal Meter for the full explanation. Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment. | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/node-metrics.html#signalqualit%C3%A4t",
    
    "relUrl": "/de-rDE/user/node-metrics.html#signalqualität"
  },"3455": {
    "doc": "Node Metrics",
    "title": "Energiedaten",
    "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metrisch | Beschreibung | . | Spannung | Per-channel voltage reading | . | Stromstärke | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/node-metrics.html#energiedaten",
    
    "relUrl": "/de-rDE/user/node-metrics.html#energiedaten"
  },"3456": {
    "doc": "Node Metrics",
    "title": "Traceroute",
    "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | The app sends a traceroute request to the target node. | Results show each hop with its SNR. | . Reading Traceroute Results . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/node-metrics.html#traceroute",
    
    "relUrl": "/de-rDE/user/node-metrics.html#traceroute"
  },"3457": {
    "doc": "Node Metrics",
    "title": "Standortprotokoll",
    "content": "Historical position data for nodes that share their location: . | GPS coordinates | Höhe | Speed (if moving) | Timestamp for each position report | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/node-metrics.html#standortprotokoll",
    
    "relUrl": "/de-rDE/user/node-metrics.html#standortprotokoll"
  },"3458": {
    "doc": "Node Metrics",
    "title": "Nachbarinformation",
    "content": "Shows which nodes a given node can directly hear, useful for understanding mesh topology. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/node-metrics.html#nachbarinformation",
    
    "relUrl": "/de-rDE/user/node-metrics.html#nachbarinformation"
  },"3459": {
    "doc": "Node Metrics",
    "title": "Host Kennzahlen",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/node-metrics.html#host-kennzahlen",
    
    "relUrl": "/de-rDE/user/node-metrics.html#host-kennzahlen"
  },"3460": {
    "doc": "Node Metrics",
    "title": "Benutzerzählerdaten",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/node-metrics.html#benutzerz%C3%A4hlerdaten",
    
    "relUrl": "/de-rDE/user/node-metrics.html#benutzerzählerdaten"
  },"3461": {
    "doc": "Node Metrics",
    "title": "Verwandte Themen",
    "content": ". | Nodes — node list, filtering, and sorting | Telemetry & Sensors — supported sensors and configuration | Signal Meter — how signal quality is calculated from SNR and RSSI | Local Mesh Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/node-metrics.html#verwandte-themen",
    
    "relUrl": "/de-rDE/user/node-metrics.html#verwandte-themen"
  },"3462": {
    "doc": "Node Metrics",
    "title": "Node Metrics",
    "content": "The node detail screen provides comprehensive telemetry and metrics for each node on your mesh. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/node-metrics.html",
    
    "relUrl": "/ar-rSA/user/node-metrics.html"
  },"3463": {
    "doc": "Node Metrics",
    "title": "Viewing Metrics",
    "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/node-metrics.html#viewing-metrics",
    
    "relUrl": "/ar-rSA/user/node-metrics.html#viewing-metrics"
  },"3464": {
    "doc": "Node Metrics",
    "title": "Device Metrics",
    "content": "Basic operating information reported by each node: . | Metric | الوصف | . | Battery Level | Current battery percentage | . | شدة التيار | Battery voltage reading | . | ChUtil | Percentage of local airtime in use | . | AirUtil | Percentage of the last hour this node spent transmitting | . | Uptime | Time since last reboot | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/node-metrics.html#device-metrics",
    
    "relUrl": "/ar-rSA/user/node-metrics.html#device-metrics"
  },"3465": {
    "doc": "Node Metrics",
    "title": "Environment Metrics",
    "content": "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 — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted: . 💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/node-metrics.html#environment-metrics",
    
    "relUrl": "/ar-rSA/user/node-metrics.html#environment-metrics"
  },"3466": {
    "doc": "Node Metrics",
    "title": "Air Quality Metrics",
    "content": "Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. | Metric | Unit | الوصف | . | PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | . | PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | . | PM10 | µg/m³ | Particulate matter up to 10 microns | . | AQI | EPA index | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated. | . | CO₂ | ppm | Carbon dioxide concentration | . | CO₂ temperature | °C / °F | Temperature reported by the CO₂ sensor itself (e.g. SCD4x) | . | CO₂ humidity | % | Relative humidity reported by the CO₂ sensor | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | Band | CO₂ Range (ppm) | Color | . | جيد | < 1000 | Green | . | Stuffy | < 2000 | Amber | . | Poor | < 5000 | Orange | . | Unsafe | < 30000 | Red | . | Evacuate | ≥ 30000 | Dark red | . An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can: . | Select a time frame for the charts. | Filter with metric chips — only metrics that have data are shown. | Refresh / request the latest air-quality telemetry. | Export to CSV for analysis in a spreadsheet. | . 💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/node-metrics.html#air-quality-metrics",
    
    "relUrl": "/ar-rSA/user/node-metrics.html#air-quality-metrics"
  },"3467": {
    "doc": "Node Metrics",
    "title": "جودة الإشارة",
    "content": "Radio signal quality information: . | Metric | الوصف | . | SNR | Signal-to-Noise Ratio (higher is better) | . | مؤشر القوة النسبية | Received Signal Strength Indicator (closer to 0 is better) | . | Noise Floor | Local background RF noise in dBm (more negative is quieter) | . | Hop Count | Number of mesh hops for last message | . Signal Quality Reference . Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | Quality | Criteria | . | جيد | SNR above the preset’s limit | . | مناسب | less than 5.5 dB below the limit | . | سيئ | 5.5 dB to 7.5 dB below the limit | . | لا يوجد | more than 7.5 dB below the limit | . See Understanding the Signal Meter for the full explanation. Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment. | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/node-metrics.html#%D8%AC%D9%88%D8%AF%D8%A9-%D8%A7%D9%84%D8%A5%D8%B4%D8%A7%D8%B1%D8%A9",
    
    "relUrl": "/ar-rSA/user/node-metrics.html#جودة-الإشارة"
  },"3468": {
    "doc": "Node Metrics",
    "title": "Power Metrics",
    "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | الوصف | . | شدة التيار | Per-channel voltage reading | . | الحالي | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/node-metrics.html#power-metrics",
    
    "relUrl": "/ar-rSA/user/node-metrics.html#power-metrics"
  },"3469": {
    "doc": "Node Metrics",
    "title": "Traceroute",
    "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | The app sends a traceroute request to the target node. | Results show each hop with its SNR. | . Reading Traceroute Results . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/node-metrics.html#traceroute",
    
    "relUrl": "/ar-rSA/user/node-metrics.html#traceroute"
  },"3470": {
    "doc": "Node Metrics",
    "title": "سجل الموقع",
    "content": "Historical position data for nodes that share their location: . | GPS coordinates | Altitude | Speed (if moving) | Timestamp for each position report | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/node-metrics.html#%D8%B3%D8%AC%D9%84-%D8%A7%D9%84%D9%85%D9%88%D9%82%D8%B9",
    
    "relUrl": "/ar-rSA/user/node-metrics.html#سجل-الموقع"
  },"3471": {
    "doc": "Node Metrics",
    "title": "Neighbor Info",
    "content": "Shows which nodes a given node can directly hear, useful for understanding mesh topology. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/node-metrics.html#neighbor-info",
    
    "relUrl": "/ar-rSA/user/node-metrics.html#neighbor-info"
  },"3472": {
    "doc": "Node Metrics",
    "title": "Host Metrics",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/node-metrics.html#host-metrics",
    
    "relUrl": "/ar-rSA/user/node-metrics.html#host-metrics"
  },"3473": {
    "doc": "Node Metrics",
    "title": "PAX Metrics",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/node-metrics.html#pax-metrics",
    
    "relUrl": "/ar-rSA/user/node-metrics.html#pax-metrics"
  },"3474": {
    "doc": "Node Metrics",
    "title": "Related Topics",
    "content": ". | Nodes — node list, filtering, and sorting | Telemetry & Sensors — supported sensors and configuration | Signal Meter — how signal quality is calculated from SNR and RSSI | Local Mesh Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/node-metrics.html#related-topics",
    
    "relUrl": "/ar-rSA/user/node-metrics.html#related-topics"
  },"3475": {
    "doc": "Node Metrics",
    "title": "Node Metrics",
    "content": "The node detail screen provides comprehensive telemetry and metrics for each node on your mesh. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/node-metrics.html",
    
    "relUrl": "/hr-rHR/user/node-metrics.html"
  },"3476": {
    "doc": "Node Metrics",
    "title": "Viewing Metrics",
    "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/node-metrics.html#viewing-metrics",
    
    "relUrl": "/hr-rHR/user/node-metrics.html#viewing-metrics"
  },"3477": {
    "doc": "Node Metrics",
    "title": "Device Metrics",
    "content": "Basic operating information reported by each node: . | Metric | Opis | . | Battery Level | Current battery percentage | . | Voltage | Battery voltage reading | . | ChUtil | Percentage of local airtime in use | . | AirUtil | Percentage of the last hour this node spent transmitting | . | Uptime | Time since last reboot | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/node-metrics.html#device-metrics",
    
    "relUrl": "/hr-rHR/user/node-metrics.html#device-metrics"
  },"3478": {
    "doc": "Node Metrics",
    "title": "Environment Metrics",
    "content": "Environmental sensor data (requires compatible hardware): . | Metric | Sensor Examples | . | Temperature | BME280, BME680, SHT31 | . | Humidity | BME280, BME680, SHT31 | . | Barometric Pressure | BME280, BMP280 | . | Gas Resistance | BME680 | . | IAQ (Air Quality) | BME680 | . Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted: . 💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/node-metrics.html#environment-metrics",
    
    "relUrl": "/hr-rHR/user/node-metrics.html#environment-metrics"
  },"3479": {
    "doc": "Node Metrics",
    "title": "Air Quality Metrics",
    "content": "Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. | Metric | Unit | Opis | . | PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | . | PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | . | PM10 | µg/m³ | Particulate matter up to 10 microns | . | AQI | EPA index | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated. | . | CO₂ | ppm | Carbon dioxide concentration | . | CO₂ temperature | °C / °F | Temperature reported by the CO₂ sensor itself (e.g. SCD4x) | . | CO₂ humidity | % | Relative humidity reported by the CO₂ sensor | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | Band | CO₂ Range (ppm) | Color | . | Good | < 1000 | Green | . | Stuffy | < 2000 | Amber | . | Poor | < 5000 | Orange | . | Unsafe | < 30000 | Crveno | . | Evacuate | ≥ 30000 | Dark red | . An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can: . | Select a time frame for the charts. | Filter with metric chips — only metrics that have data are shown. | Refresh / request the latest air-quality telemetry. | Export to CSV for analysis in a spreadsheet. | . 💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/node-metrics.html#air-quality-metrics",
    
    "relUrl": "/hr-rHR/user/node-metrics.html#air-quality-metrics"
  },"3480": {
    "doc": "Node Metrics",
    "title": "Signal Quality",
    "content": "Radio signal quality information: . | Metric | Opis | . | SNR | Signal-to-Noise Ratio (higher is better) | . | RSSI | Received Signal Strength Indicator (closer to 0 is better) | . | Noise Floor | Local background RF noise in dBm (more negative is quieter) | . | Hop Count | Number of mesh hops for last message | . Signal Quality Reference . Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | Quality | Criteria | . | Good | SNR above the preset’s limit | . | Fair | less than 5.5 dB below the limit | . | Bad | 5.5 dB to 7.5 dB below the limit | . | None | more than 7.5 dB below the limit | . See Understanding the Signal Meter for the full explanation. Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment. | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/node-metrics.html#signal-quality",
    
    "relUrl": "/hr-rHR/user/node-metrics.html#signal-quality"
  },"3481": {
    "doc": "Node Metrics",
    "title": "Power Metrics",
    "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Opis | . | Voltage | Per-channel voltage reading | . | Current | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/node-metrics.html#power-metrics",
    
    "relUrl": "/hr-rHR/user/node-metrics.html#power-metrics"
  },"3482": {
    "doc": "Node Metrics",
    "title": "Traceroute",
    "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | The app sends a traceroute request to the target node. | Results show each hop with its SNR. | . Reading Traceroute Results . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/node-metrics.html#traceroute",
    
    "relUrl": "/hr-rHR/user/node-metrics.html#traceroute"
  },"3483": {
    "doc": "Node Metrics",
    "title": "Position Log",
    "content": "Historical position data for nodes that share their location: . | GPS coordinates | Altitude | Speed (if moving) | Timestamp for each position report | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/node-metrics.html#position-log",
    
    "relUrl": "/hr-rHR/user/node-metrics.html#position-log"
  },"3484": {
    "doc": "Node Metrics",
    "title": "Neighbor Info",
    "content": "Shows which nodes a given node can directly hear, useful for understanding mesh topology. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/node-metrics.html#neighbor-info",
    
    "relUrl": "/hr-rHR/user/node-metrics.html#neighbor-info"
  },"3485": {
    "doc": "Node Metrics",
    "title": "Host Metrics",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/node-metrics.html#host-metrics",
    
    "relUrl": "/hr-rHR/user/node-metrics.html#host-metrics"
  },"3486": {
    "doc": "Node Metrics",
    "title": "PAX Metrics",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/node-metrics.html#pax-metrics",
    
    "relUrl": "/hr-rHR/user/node-metrics.html#pax-metrics"
  },"3487": {
    "doc": "Node Metrics",
    "title": "Related Topics",
    "content": ". | Nodes — node list, filtering, and sorting | Telemetry & Sensors — supported sensors and configuration | Signal Meter — how signal quality is calculated from SNR and RSSI | Local Mesh Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/node-metrics.html#related-topics",
    
    "relUrl": "/hr-rHR/user/node-metrics.html#related-topics"
  },"3488": {
    "doc": "Node Metrics",
    "title": "Node Metrics",
    "content": "The node detail screen provides comprehensive telemetry and metrics for each node on your mesh. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/node-metrics.html",
    
    "relUrl": "/pt-rPT/user/node-metrics.html"
  },"3489": {
    "doc": "Node Metrics",
    "title": "Viewing Metrics",
    "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/node-metrics.html#viewing-metrics",
    
    "relUrl": "/pt-rPT/user/node-metrics.html#viewing-metrics"
  },"3490": {
    "doc": "Node Metrics",
    "title": "Device Metrics",
    "content": "Basic operating information reported by each node: . | Metric | Descrição | . | Battery Level | Current battery percentage | . | Voltagem | Battery voltage reading | . | ChUtil | Percentage of local airtime in use | . | AirUtil | Percentage of the last hour this node spent transmitting | . | Tempo ativo | Time since last reboot | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/node-metrics.html#device-metrics",
    
    "relUrl": "/pt-rPT/user/node-metrics.html#device-metrics"
  },"3491": {
    "doc": "Node Metrics",
    "title": "Environment Metrics",
    "content": "Environmental sensor data (requires compatible hardware): . | Metric | Sensor Examples | . | Temperatura | BME280, BME680, SHT31 | . | Humidade | BME280, BME680, SHT31 | . | Pressão atmosférica | BME280, BMP280 | . | Gas Resistance | BME680 | . | IAQ (Air Quality) | BME680 | . Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted: . 💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/node-metrics.html#environment-metrics",
    
    "relUrl": "/pt-rPT/user/node-metrics.html#environment-metrics"
  },"3492": {
    "doc": "Node Metrics",
    "title": "Air Quality Metrics",
    "content": "Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. | Metric | Unit | Descrição | . | PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | . | PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | . | PM10 | µg/m³ | Particulate matter up to 10 microns | . | AQI | EPA index | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated. | . | CO₂ | ppm | Carbon dioxide concentration | . | CO₂ temperature | °C / °F | Temperature reported by the CO₂ sensor itself (e.g. SCD4x) | . | CO₂ humidity | % | Relative humidity reported by the CO₂ sensor | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | Band | CO₂ Range (ppm) | Color | . | Bom | < 1000 | Verde | . | Stuffy | < 2000 | Amber | . | Poor | < 5000 | Orange | . | Unsafe | < 30000 | Vermelho | . | Evacuate | ≥ 30000 | Dark red | . An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can: . | Select a time frame for the charts. | Filter with metric chips — only metrics that have data are shown. | Refresh / request the latest air-quality telemetry. | Export to CSV for analysis in a spreadsheet. | . 💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/node-metrics.html#air-quality-metrics",
    
    "relUrl": "/pt-rPT/user/node-metrics.html#air-quality-metrics"
  },"3493": {
    "doc": "Node Metrics",
    "title": "Qualidade do Sinal",
    "content": "Radio signal quality information: . | Metric | Descrição | . | SNR | Signal-to-Noise Ratio (higher is better) | . | RSSI | Received Signal Strength Indicator (closer to 0 is better) | . | Noise Floor | Local background RF noise in dBm (more negative is quieter) | . | Hop Count | Number of mesh hops for last message | . Signal Quality Reference . Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | Quality | Criteria | . | Bom | SNR above the preset’s limit | . | Razoável | less than 5.5 dB below the limit | . | Mau | 5.5 dB to 7.5 dB below the limit | . | Nenhum | more than 7.5 dB below the limit | . See Understanding the Signal Meter for the full explanation. Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment. | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/node-metrics.html#qualidade-do-sinal",
    
    "relUrl": "/pt-rPT/user/node-metrics.html#qualidade-do-sinal"
  },"3494": {
    "doc": "Node Metrics",
    "title": "Power Metrics",
    "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Descrição | . | Voltagem | Per-channel voltage reading | . | Atual | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/node-metrics.html#power-metrics",
    
    "relUrl": "/pt-rPT/user/node-metrics.html#power-metrics"
  },"3495": {
    "doc": "Node Metrics",
    "title": "Traçar rota",
    "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | The app sends a traceroute request to the target node. | Results show each hop with its SNR. | . Reading Traceroute Results . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/node-metrics.html#tra%C3%A7ar-rota",
    
    "relUrl": "/pt-rPT/user/node-metrics.html#traçar-rota"
  },"3496": {
    "doc": "Node Metrics",
    "title": "Histórico de posição",
    "content": "Historical position data for nodes that share their location: . | GPS coordinates | Altitude | Speed (if moving) | Timestamp for each position report | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/node-metrics.html#hist%C3%B3rico-de-posi%C3%A7%C3%A3o",
    
    "relUrl": "/pt-rPT/user/node-metrics.html#histórico-de-posição"
  },"3497": {
    "doc": "Node Metrics",
    "title": "Informações da vizinhança",
    "content": "Shows which nodes a given node can directly hear, useful for understanding mesh topology. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/node-metrics.html#informa%C3%A7%C3%B5es-da-vizinhan%C3%A7a",
    
    "relUrl": "/pt-rPT/user/node-metrics.html#informações-da-vizinhança"
  },"3498": {
    "doc": "Node Metrics",
    "title": "Host Metrics",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/node-metrics.html#host-metrics",
    
    "relUrl": "/pt-rPT/user/node-metrics.html#host-metrics"
  },"3499": {
    "doc": "Node Metrics",
    "title": "PAX Metrics",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/node-metrics.html#pax-metrics",
    
    "relUrl": "/pt-rPT/user/node-metrics.html#pax-metrics"
  },"3500": {
    "doc": "Node Metrics",
    "title": "Related Topics",
    "content": ". | Nodes — node list, filtering, and sorting | Telemetry & Sensors — supported sensors and configuration | Signal Meter — how signal quality is calculated from SNR and RSSI | Local Mesh Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/node-metrics.html#related-topics",
    
    "relUrl": "/pt-rPT/user/node-metrics.html#related-topics"
  },"3501": {
    "doc": "Node Metrics",
    "title": "Node Metrics",
    "content": "The node detail screen provides comprehensive telemetry and metrics for each node on your mesh. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/node-metrics.html",
    
    "relUrl": "/pl-rPL/user/node-metrics.html"
  },"3502": {
    "doc": "Node Metrics",
    "title": "Viewing Metrics",
    "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/node-metrics.html#viewing-metrics",
    
    "relUrl": "/pl-rPL/user/node-metrics.html#viewing-metrics"
  },"3503": {
    "doc": "Node Metrics",
    "title": "Metryka urządzenia",
    "content": "Basic operating information reported by each node: . | Metric | Opis | . | Poziom naładowania baterii | Current battery percentage | . | Napięcie | Battery voltage reading | . | ChUtil | Percentage of local airtime in use | . | AirUtil | Percentage of the last hour this node spent transmitting | . | Czas pracy | Time since last reboot | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/node-metrics.html#metryka-urz%C4%85dzenia",
    
    "relUrl": "/pl-rPL/user/node-metrics.html#metryka-urządzenia"
  },"3504": {
    "doc": "Node Metrics",
    "title": "Metryki środowiskowe",
    "content": "Environmental sensor data (requires compatible hardware): . | Metric | Sensor Examples | . | Temperatura | BME280, BME680, SHT31 | . | Wilgotność | BME280, BME680, SHT31 | . | Ciśnienie barometryczne | BME280, BMP280 | . | Rezystancja gazu | BME680 | . | IAQ (Air Quality) | BME680 | . Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted: . 💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/node-metrics.html#metryki-%C5%9Brodowiskowe",
    
    "relUrl": "/pl-rPL/user/node-metrics.html#metryki-środowiskowe"
  },"3505": {
    "doc": "Node Metrics",
    "title": "Air Quality Metrics",
    "content": "Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. | Metric | Unit | Opis | . | PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | . | PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | . | PM10 | µg/m³ | Particulate matter up to 10 microns | . | AQI | EPA index | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated. | . | CO₂ | ppm | Carbon dioxide concentration | . | CO₂ temperature | °C / °F | Temperature reported by the CO₂ sensor itself (e.g. SCD4x) | . | CO₂ humidity | % | Relative humidity reported by the CO₂ sensor | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | Band | CO₂ Range (ppm) | Color | . | dobry | < 1000 | Zielony | . | Stuffy | < 2000 | Amber | . | Poor | < 5000 | Orange | . | Unsafe | < 30000 | Czerwony | . | Evacuate | ≥ 30000 | Dark red | . An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can: . | Select a time frame for the charts. | Filter with metric chips — only metrics that have data are shown. | Refresh / request the latest air-quality telemetry. | Export to CSV for analysis in a spreadsheet. | . 💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/node-metrics.html#air-quality-metrics",
    
    "relUrl": "/pl-rPL/user/node-metrics.html#air-quality-metrics"
  },"3506": {
    "doc": "Node Metrics",
    "title": "Jakość sygnału",
    "content": "Radio signal quality information: . | Metric | Opis | . | SNR: | Signal-to-Noise Ratio (higher is better) | . | RSSI: | Received Signal Strength Indicator (closer to 0 is better) | . | Noise Floor | Local background RF noise in dBm (more negative is quieter) | . | Hop Count | Number of mesh hops for last message | . Signal Quality Reference . Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | Quality | Criteria | . | dobry | SNR above the preset’s limit | . | wystarczający | less than 5.5 dB below the limit | . | słaby | 5.5 dB to 7.5 dB below the limit | . | Brak | more than 7.5 dB below the limit | . See Understanding the Signal Meter for the full explanation. Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment. | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/node-metrics.html#jako%C5%9B%C4%87-sygna%C5%82u",
    
    "relUrl": "/pl-rPL/user/node-metrics.html#jakość-sygnału"
  },"3507": {
    "doc": "Node Metrics",
    "title": "Metryki zasilania",
    "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Opis | . | Napięcie | Per-channel voltage reading | . | Natężenie | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/node-metrics.html#metryki-zasilania",
    
    "relUrl": "/pl-rPL/user/node-metrics.html#metryki-zasilania"
  },"3508": {
    "doc": "Node Metrics",
    "title": "Pokaż trasę",
    "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | The app sends a traceroute request to the target node. | Results show each hop with its SNR. | . Reading Traceroute Results . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/node-metrics.html#poka%C5%BC-tras%C4%99",
    
    "relUrl": "/pl-rPL/user/node-metrics.html#pokaż-trasę"
  },"3509": {
    "doc": "Node Metrics",
    "title": "Historia pozycji",
    "content": "Historical position data for nodes that share their location: . | GPS coordinates | Wysokość | Speed (if moving) | Timestamp for each position report | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/node-metrics.html#historia-pozycji",
    
    "relUrl": "/pl-rPL/user/node-metrics.html#historia-pozycji"
  },"3510": {
    "doc": "Node Metrics",
    "title": "Informacje o sąsiadze",
    "content": "Shows which nodes a given node can directly hear, useful for understanding mesh topology. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/node-metrics.html#informacje-o-s%C4%85siadze",
    
    "relUrl": "/pl-rPL/user/node-metrics.html#informacje-o-sąsiadze"
  },"3511": {
    "doc": "Node Metrics",
    "title": "Statystyki hosta",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/node-metrics.html#statystyki-hosta",
    
    "relUrl": "/pl-rPL/user/node-metrics.html#statystyki-hosta"
  },"3512": {
    "doc": "Node Metrics",
    "title": "PAX Metrics",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/node-metrics.html#pax-metrics",
    
    "relUrl": "/pl-rPL/user/node-metrics.html#pax-metrics"
  },"3513": {
    "doc": "Node Metrics",
    "title": "Related Topics",
    "content": ". | Nodes — node list, filtering, and sorting | Telemetry & Sensors — supported sensors and configuration | Signal Meter — how signal quality is calculated from SNR and RSSI | Local Mesh Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/node-metrics.html#related-topics",
    
    "relUrl": "/pl-rPL/user/node-metrics.html#related-topics"
  },"3514": {
    "doc": "Node Metrics",
    "title": "Node Metrics",
    "content": "The node detail screen provides comprehensive telemetry and metrics for each node on your mesh. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/node-metrics.html",
    
    "relUrl": "/zh-rCN/user/node-metrics.html"
  },"3515": {
    "doc": "Node Metrics",
    "title": "Viewing Metrics",
    "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/node-metrics.html#viewing-metrics",
    
    "relUrl": "/zh-rCN/user/node-metrics.html#viewing-metrics"
  },"3516": {
    "doc": "Node Metrics",
    "title": "设备数据",
    "content": "Basic operating information reported by each node: . | 公制 | 说明 | . | 电池电量 | Current battery percentage | . | 电压 | Battery voltage reading | . | ChUtil | Percentage of local airtime in use | . | AirUtil | Percentage of the last hour this node spent transmitting | . | 正常运行时间 | Time since last reboot | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/node-metrics.html#%E8%AE%BE%E5%A4%87%E6%95%B0%E6%8D%AE",
    
    "relUrl": "/zh-rCN/user/node-metrics.html#设备数据"
  },"3517": {
    "doc": "Node Metrics",
    "title": "传感器指标",
    "content": "Environmental sensor data (requires compatible hardware): . | 公制 | Sensor Examples | . | 温度 | BME280, BME680, SHT31 | . | 湿度 | BME280, BME680, SHT31 | . | 气压 | BME280, BMP280 | . | 气体电阻性 | BME680 | . | IAQ (Air Quality) | BME680 | . Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted: . 💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/node-metrics.html#%E4%BC%A0%E6%84%9F%E5%99%A8%E6%8C%87%E6%A0%87",
    
    "relUrl": "/zh-rCN/user/node-metrics.html#传感器指标"
  },"3518": {
    "doc": "Node Metrics",
    "title": "Air Quality Metrics",
    "content": "Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. | 公制 | Unit | 说明 | . | PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | . | PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | . | PM10 | µg/m³ | Particulate matter up to 10 microns | . | AQI | EPA index | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated. | . | CO₂ | ppm | Carbon dioxide concentration | . | CO₂ temperature | °C / °F | Temperature reported by the CO₂ sensor itself (e.g. SCD4x) | . | CO₂ humidity | % | Relative humidity reported by the CO₂ sensor | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | Band | CO₂ Range (ppm) | 颜色 | . | 良好 | < 1000 | 绿 | . | Stuffy | < 2000 | Amber | . | Poor | < 5000 | 橙色 | . | Unsafe | < 30000 | 红 | . | Evacuate | ≥ 30000 | Dark red | . An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can: . | Select a time frame for the charts. | Filter with metric chips — only metrics that have data are shown. | Refresh / request the latest air-quality telemetry. | Export to CSV for analysis in a spreadsheet. | . 💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/node-metrics.html#air-quality-metrics",
    
    "relUrl": "/zh-rCN/user/node-metrics.html#air-quality-metrics"
  },"3519": {
    "doc": "Node Metrics",
    "title": "信号质量",
    "content": "Radio signal quality information: . | 公制 | 说明 | . | SNR | Signal-to-Noise Ratio (higher is better) | . | RSSI | Received Signal Strength Indicator (closer to 0 is better) | . | Noise Floor | Local background RF noise in dBm (more negative is quieter) | . | Hop Count | Number of mesh hops for last message | . Signal Quality Reference . Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | Quality | Criteria | . | 良好 | SNR above the preset’s limit | . | 一般 | less than 5.5 dB below the limit | . | 差 | 5.5 dB to 7.5 dB below the limit | . | 无 | more than 7.5 dB below the limit | . See Understanding the Signal Meter for the full explanation. Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment. | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/node-metrics.html#%E4%BF%A1%E5%8F%B7%E8%B4%A8%E9%87%8F",
    
    "relUrl": "/zh-rCN/user/node-metrics.html#信号质量"
  },"3520": {
    "doc": "Node Metrics",
    "title": "电源计量",
    "content": "Power management telemetry (requires INA sensor or compatible hardware): . | 公制 | 说明 | . | 电压 | Per-channel voltage reading | . | 电流 | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/node-metrics.html#%E7%94%B5%E6%BA%90%E8%AE%A1%E9%87%8F",
    
    "relUrl": "/zh-rCN/user/node-metrics.html#电源计量"
  },"3521": {
    "doc": "Node Metrics",
    "title": "追踪器",
    "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | The app sends a traceroute request to the target node. | Results show each hop with its SNR. | . Reading Traceroute Results . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/node-metrics.html#%E8%BF%BD%E8%B8%AA%E5%99%A8",
    
    "relUrl": "/zh-rCN/user/node-metrics.html#追踪器"
  },"3522": {
    "doc": "Node Metrics",
    "title": "定位日志",
    "content": "Historical position data for nodes that share their location: . | GPS coordinates | 海拔高度 | Speed (if moving) | Timestamp for each position report | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/node-metrics.html#%E5%AE%9A%E4%BD%8D%E6%97%A5%E5%BF%97",
    
    "relUrl": "/zh-rCN/user/node-metrics.html#定位日志"
  },"3523": {
    "doc": "Node Metrics",
    "title": "邻居信息",
    "content": "Shows which nodes a given node can directly hear, useful for understanding mesh topology. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/node-metrics.html#%E9%82%BB%E5%B1%85%E4%BF%A1%E6%81%AF",
    
    "relUrl": "/zh-rCN/user/node-metrics.html#邻居信息"
  },"3524": {
    "doc": "Node Metrics",
    "title": "主机测量",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/node-metrics.html#%E4%B8%BB%E6%9C%BA%E6%B5%8B%E9%87%8F",
    
    "relUrl": "/zh-rCN/user/node-metrics.html#主机测量"
  },"3525": {
    "doc": "Node Metrics",
    "title": "PAX 计量",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/node-metrics.html#pax-%E8%AE%A1%E9%87%8F",
    
    "relUrl": "/zh-rCN/user/node-metrics.html#pax-计量"
  },"3526": {
    "doc": "Node Metrics",
    "title": "Related Topics",
    "content": ". | Nodes — node list, filtering, and sorting | Telemetry & Sensors — supported sensors and configuration | Signal Meter — how signal quality is calculated from SNR and RSSI | Local Mesh Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/node-metrics.html#related-topics",
    
    "relUrl": "/zh-rCN/user/node-metrics.html#related-topics"
  },"3527": {
    "doc": "Node Metrics",
    "title": "Node Metrics",
    "content": "The node detail screen provides comprehensive telemetry and metrics for each node on your mesh. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/node-metrics.html",
    
    "relUrl": "/sq-rAL/user/node-metrics.html"
  },"3528": {
    "doc": "Node Metrics",
    "title": "Viewing Metrics",
    "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/node-metrics.html#viewing-metrics",
    
    "relUrl": "/sq-rAL/user/node-metrics.html#viewing-metrics"
  },"3529": {
    "doc": "Node Metrics",
    "title": "Device Metrics",
    "content": "Basic operating information reported by each node: . | Metric | Përshkrimi | . | Battery Level | Current battery percentage | . | Voltage | Battery voltage reading | . | ChUtil | Percentage of local airtime in use | . | AirUtil | Percentage of the last hour this node spent transmitting | . | Uptime | Time since last reboot | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/node-metrics.html#device-metrics",
    
    "relUrl": "/sq-rAL/user/node-metrics.html#device-metrics"
  },"3530": {
    "doc": "Node Metrics",
    "title": "Environment Metrics",
    "content": "Environmental sensor data (requires compatible hardware): . | Metric | Sensor Examples | . | Temperatura | BME280, BME680, SHT31 | . | Lagështia | BME280, BME680, SHT31 | . | Barometric Pressure | BME280, BMP280 | . | Gas Resistance | BME680 | . | IAQ (Air Quality) | BME680 | . Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted: . 💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/node-metrics.html#environment-metrics",
    
    "relUrl": "/sq-rAL/user/node-metrics.html#environment-metrics"
  },"3531": {
    "doc": "Node Metrics",
    "title": "Air Quality Metrics",
    "content": "Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. | Metric | Unit | Përshkrimi | . | PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | . | PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | . | PM10 | µg/m³ | Particulate matter up to 10 microns | . | AQI | EPA index | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated. | . | CO₂ | ppm | Carbon dioxide concentration | . | CO₂ temperature | °C / °F | Temperature reported by the CO₂ sensor itself (e.g. SCD4x) | . | CO₂ humidity | % | Relative humidity reported by the CO₂ sensor | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | Band | CO₂ Range (ppm) | Color | . | Mirë | < 1000 | Green | . | Stuffy | < 2000 | Amber | . | Poor | < 5000 | Orange | . | Unsafe | < 30000 | Red | . | Evacuate | ≥ 30000 | Dark red | . An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can: . | Select a time frame for the charts. | Filter with metric chips — only metrics that have data are shown. | Refresh / request the latest air-quality telemetry. | Export to CSV for analysis in a spreadsheet. | . 💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/node-metrics.html#air-quality-metrics",
    
    "relUrl": "/sq-rAL/user/node-metrics.html#air-quality-metrics"
  },"3532": {
    "doc": "Node Metrics",
    "title": "Cilësia e Sinjalit",
    "content": "Radio signal quality information: . | Metric | Përshkrimi | . | SNR | Signal-to-Noise Ratio (higher is better) | . | RSSI | Received Signal Strength Indicator (closer to 0 is better) | . | Noise Floor | Local background RF noise in dBm (more negative is quieter) | . | Hop Count | Number of mesh hops for last message | . Signal Quality Reference . Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | Quality | Criteria | . | Mirë | SNR above the preset’s limit | . | Mesatar | less than 5.5 dB below the limit | . | I Keq | 5.5 dB to 7.5 dB below the limit | . | Asnjë | more than 7.5 dB below the limit | . See Understanding the Signal Meter for the full explanation. Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment. | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/node-metrics.html#cil%C3%ABsia-e-sinjalit",
    
    "relUrl": "/sq-rAL/user/node-metrics.html#cilësia-e-sinjalit"
  },"3533": {
    "doc": "Node Metrics",
    "title": "Power Metrics",
    "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Përshkrimi | . | Voltage | Per-channel voltage reading | . | Current | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/node-metrics.html#power-metrics",
    
    "relUrl": "/sq-rAL/user/node-metrics.html#power-metrics"
  },"3534": {
    "doc": "Node Metrics",
    "title": "Traceroute",
    "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | The app sends a traceroute request to the target node. | Results show each hop with its SNR. | . Reading Traceroute Results . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/node-metrics.html#traceroute",
    
    "relUrl": "/sq-rAL/user/node-metrics.html#traceroute"
  },"3535": {
    "doc": "Node Metrics",
    "title": "Regjistri i Pozitës",
    "content": "Historical position data for nodes that share their location: . | GPS coordinates | Altitude | Speed (if moving) | Timestamp for each position report | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/node-metrics.html#regjistri-i-pozit%C3%ABs",
    
    "relUrl": "/sq-rAL/user/node-metrics.html#regjistri-i-pozitës"
  },"3536": {
    "doc": "Node Metrics",
    "title": "Neighbor Info",
    "content": "Shows which nodes a given node can directly hear, useful for understanding mesh topology. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/node-metrics.html#neighbor-info",
    
    "relUrl": "/sq-rAL/user/node-metrics.html#neighbor-info"
  },"3537": {
    "doc": "Node Metrics",
    "title": "Host Metrics",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/node-metrics.html#host-metrics",
    
    "relUrl": "/sq-rAL/user/node-metrics.html#host-metrics"
  },"3538": {
    "doc": "Node Metrics",
    "title": "PAX Metrics",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/node-metrics.html#pax-metrics",
    
    "relUrl": "/sq-rAL/user/node-metrics.html#pax-metrics"
  },"3539": {
    "doc": "Node Metrics",
    "title": "Related Topics",
    "content": ". | Nodes — node list, filtering, and sorting | Telemetry & Sensors — supported sensors and configuration | Signal Meter — how signal quality is calculated from SNR and RSSI | Local Mesh Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/node-metrics.html#related-topics",
    
    "relUrl": "/sq-rAL/user/node-metrics.html#related-topics"
  },"3540": {
    "doc": "Node Metrics",
    "title": "Node Metrics",
    "content": "The node detail screen provides comprehensive telemetry and metrics for each node on your mesh. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/node-metrics.html",
    
    "relUrl": "/zh-rTW/user/node-metrics.html"
  },"3541": {
    "doc": "Node Metrics",
    "title": "Viewing Metrics",
    "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/node-metrics.html#viewing-metrics",
    
    "relUrl": "/zh-rTW/user/node-metrics.html#viewing-metrics"
  },"3542": {
    "doc": "Node Metrics",
    "title": "裝置計量資料",
    "content": "Basic operating information reported by each node: . | 公制（公里/公尺） | 描述說明 | . | Battery Level | Current battery percentage | . | 電壓 | Battery voltage reading | . | 頻道利用率 | Percentage of local airtime in use | . | 空中時間使用率 | Percentage of the last hour this node spent transmitting | . | 運行時間 | Time since last reboot | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/node-metrics.html#%E8%A3%9D%E7%BD%AE%E8%A8%88%E9%87%8F%E8%B3%87%E6%96%99",
    
    "relUrl": "/zh-rTW/user/node-metrics.html#裝置計量資料"
  },"3543": {
    "doc": "Node Metrics",
    "title": "環境計量資料",
    "content": "Environmental sensor data (requires compatible hardware): . | 公制（公里/公尺） | Sensor Examples | . | 溫度 | BME280, BME680, SHT31 | . | 濕度 | BME280, BME680, SHT31 | . | 大氣壓力 | BME280, BMP280 | . | 氣體感測器 | BME680 | . | IAQ (Air Quality) | BME680 | . Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted: . 💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/node-metrics.html#%E7%92%B0%E5%A2%83%E8%A8%88%E9%87%8F%E8%B3%87%E6%96%99",
    
    "relUrl": "/zh-rTW/user/node-metrics.html#環境計量資料"
  },"3544": {
    "doc": "Node Metrics",
    "title": "Air Quality Metrics",
    "content": "Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. | 公制（公里/公尺） | 單位 | 描述說明 | . | PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | . | PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | . | PM10 | µg/m³ | Particulate matter up to 10 microns | . | AQI | EPA index | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated. | . | CO₂ | ppm | Carbon dioxide concentration | . | CO₂ temperature | °C / °F | Temperature reported by the CO₂ sensor itself (e.g. SCD4x) | . | CO₂ humidity | % | Relative humidity reported by the CO₂ sensor | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | Band | CO₂ Range (ppm) | 顏色 | . | 良好 | < 1000 | Green - 綠色 | . | Stuffy | < 2000 | Amber | . | Poor | < 5000 | 橙色 | . | Unsafe | < 30000 | Red - 紅色 | . | Evacuate | ≥ 30000 | Dark red | . An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can: . | Select a time frame for the charts. | Filter with metric chips — only metrics that have data are shown. | Refresh / request the latest air-quality telemetry. | Export to CSV for analysis in a spreadsheet. | . 💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/node-metrics.html#air-quality-metrics",
    
    "relUrl": "/zh-rTW/user/node-metrics.html#air-quality-metrics"
  },"3545": {
    "doc": "Node Metrics",
    "title": "信號品質",
    "content": "Radio signal quality information: . | 公制（公里/公尺） | 描述說明 | . | SNR | Signal-to-Noise Ratio (higher is better) | . | RSSI | Received Signal Strength Indicator (closer to 0 is better) | . | Noise Floor | Local background RF noise in dBm (more negative is quieter) | . | 跳躍次數 | Number of mesh hops for last message | . Signal Quality Reference . Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | Quality | Criteria | . | 良好 | SNR above the preset’s limit | . | 普通 | less than 5.5 dB below the limit | . | 不良 | 5.5 dB to 7.5 dB below the limit | . | 無 | more than 7.5 dB below the limit | . See Understanding the Signal Meter for the full explanation. Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment. | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/node-metrics.html#%E4%BF%A1%E8%99%9F%E5%93%81%E8%B3%AA",
    
    "relUrl": "/zh-rTW/user/node-metrics.html#信號品質"
  },"3546": {
    "doc": "Node Metrics",
    "title": "電源計量資料",
    "content": "Power management telemetry (requires INA sensor or compatible hardware): . | 公制（公里/公尺） | 描述說明 | . | 電壓 | Per-channel voltage reading | . | 目前 | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/node-metrics.html#%E9%9B%BB%E6%BA%90%E8%A8%88%E9%87%8F%E8%B3%87%E6%96%99",
    
    "relUrl": "/zh-rTW/user/node-metrics.html#電源計量資料"
  },"3547": {
    "doc": "Node Metrics",
    "title": "路由追蹤",
    "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | The app sends a traceroute request to the target node. | Results show each hop with its SNR. | . Reading Traceroute Results . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/node-metrics.html#%E8%B7%AF%E7%94%B1%E8%BF%BD%E8%B9%A4",
    
    "relUrl": "/zh-rTW/user/node-metrics.html#路由追蹤"
  },"3548": {
    "doc": "Node Metrics",
    "title": "定位日誌",
    "content": "Historical position data for nodes that share their location: . | GPS 座標 | 海拔高度 | Speed (if moving) | Timestamp for each position report | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/node-metrics.html#%E5%AE%9A%E4%BD%8D%E6%97%A5%E8%AA%8C",
    
    "relUrl": "/zh-rTW/user/node-metrics.html#定位日誌"
  },"3549": {
    "doc": "Node Metrics",
    "title": "鄰近節點資訊",
    "content": "Shows which nodes a given node can directly hear, useful for understanding mesh topology. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/node-metrics.html#%E9%84%B0%E8%BF%91%E7%AF%80%E9%BB%9E%E8%B3%87%E8%A8%8A",
    
    "relUrl": "/zh-rTW/user/node-metrics.html#鄰近節點資訊"
  },"3550": {
    "doc": "Node Metrics",
    "title": "主機資訊",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/node-metrics.html#%E4%B8%BB%E6%A9%9F%E8%B3%87%E8%A8%8A",
    
    "relUrl": "/zh-rTW/user/node-metrics.html#主機資訊"
  },"3551": {
    "doc": "Node Metrics",
    "title": "PAX 人流計量",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/node-metrics.html#pax-%E4%BA%BA%E6%B5%81%E8%A8%88%E9%87%8F",
    
    "relUrl": "/zh-rTW/user/node-metrics.html#pax-人流計量"
  },"3552": {
    "doc": "Node Metrics",
    "title": "相關主題",
    "content": ". | Nodes — node list, filtering, and sorting | Telemetry & Sensors — supported sensors and configuration | Signal Meter — how signal quality is calculated from SNR and RSSI | Local Mesh Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/node-metrics.html#%E7%9B%B8%E9%97%9C%E4%B8%BB%E9%A1%8C",
    
    "relUrl": "/zh-rTW/user/node-metrics.html#相關主題"
  },"3553": {
    "doc": "Sõlme mõõdikud",
    "title": "Sõlme mõõdikud",
    "content": "Sõlme detailvaates on iga kärgvõrgu sõlme kohta põhjalikud telemeetria ja mõõdikud. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/node-metrics.html",
    
    "relUrl": "/et-rEE/user/node-metrics.html"
  },"3554": {
    "doc": "Sõlme mõõdikud",
    "title": "Viewing Metrics",
    "content": ". | Mine Seadmed. | Puuduta sõlme, mida soovite kontrollida. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. Mõõdikud värskendatakse iga sõlme telemeetria sätetes seadistatud intervallidega. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/node-metrics.html#viewing-metrics",
    
    "relUrl": "/et-rEE/user/node-metrics.html#viewing-metrics"
  },"3555": {
    "doc": "Sõlme mõõdikud",
    "title": "Seadme mõõdikud",
    "content": "Basic operating information reported by each node: . | Meetriline | Kirjeldus | . | Aku tase | Praegune aku protsent | . | Vool | Aku pinge näit | . | Kanali kasutus | Percentage of local airtime in use | . | Saate kasutus | Percentage of the last hour this node spent transmitting | . | Töötamise aeg | Viimasest taaskäivitamisest möödunud aeg | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/node-metrics.html#seadme-m%C3%B5%C3%B5dikud",
    
    "relUrl": "/et-rEE/user/node-metrics.html#seadme-mõõdikud"
  },"3556": {
    "doc": "Sõlme mõõdikud",
    "title": "Keskkonnamõõdikud",
    "content": "Environmental sensor data (requires compatible hardware): . | Meetriline | Sensor Examples | . | Temperatuur | BME280, BME680, SHT31 | . | Niiskus | BME280, BME680, SHT31 | . | Baromeetri rõhk | BME280, BMP280 | . | Gaasi surve | BME680 | . | IAQ (Air Quality) | BME680 | . Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. BME680 IAQ (siseõhu kvaliteet) indeks on üksik väärtus vahemikus 0–500+, mis on tuletatud gaasitakistusest ja näidatud värvikoodiga skaalal Suurepärane kuni Ohtlikult saastunud: . 💡 Vihje: Keskkonnamõõdikute jaoks on vaja kaugsõlmega ühendatud andurit. Not all nodes report environmental data. Vaata Telemeetria & Sensorid, et näha toetatud andurite täieliku loendit. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/node-metrics.html#keskkonnam%C3%B5%C3%B5dikud",
    
    "relUrl": "/et-rEE/user/node-metrics.html#keskkonnamõõdikud"
  },"3557": {
    "doc": "Sõlme mõõdikud",
    "title": "Air Quality Metrics",
    "content": "Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. See on eraldi BME680 siseõhu kvaliteedi näidust, mis on loetletud keskkonnamõõdikute all – siseõhu kvaliteet on ühtne gaasitakistusest tuletatud indeks, samas kui õhukvaliteedi vaade diagrammib aluseks olevaid tahkete osakeste ja CO₂ mõõtmisi. | Meetriline | Unit | Kirjeldus | . | PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | . | PM2,5 | µg/m³ | Particulate matter up to 2.5 microns | . | PM10 | µg/m³ | Particulate matter up to 10 microns | . | AQI | EPA indeks | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Kuvatakse PM2.5 kõrval, kui on kogunenud piisavalt näite. | . | CO₂ | ppm | Süsinikdioksiidi kontsentratsioon | . | CO₂ temperatuur | °C / °F | Temperature reported by the CO₂ sensor itself (e.g. SCD4x) | . | CO₂ niiskus | % | Relative humidity reported by the CO₂ sensor | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | Band | CO₂ ulatus (ppm) | Värv | . | Hea | < 1000 | Roheline | . | Stuffy | < 2000 | Merevaik | . | Kehv | < 5000 | Oranž | . | Ebaturvaline | < 30000 | Punane | . | Evakueeru | ≥ 30000 | Tume punane | . An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can: . | Vali diagrammide jaoks ajaraam. | Filtreeri mõõdikute kiipide abil — kuvatakse ainult andmeid sisaldavad mõõdikud. | Refresh / request the latest air-quality telemetry. | Ekspordi CSV analüüsimiseks arvutustabeli vaates. | . 💡 Vihje: Õhukvaliteedi mõõdikute jaoks on vaja kaugsõlmega ühendatud andurit. Vaata Telemeetria & Sensorid toetatud raudvara kohta. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/node-metrics.html#air-quality-metrics",
    
    "relUrl": "/et-rEE/user/node-metrics.html#air-quality-metrics"
  },"3558": {
    "doc": "Sõlme mõõdikud",
    "title": "Levi Kvaliteet",
    "content": "Radio signal quality information: . | Meetriline | Kirjeldus | . | SNR | Signal-to-Noise Ratio (higher is better) | . | RSSI | Received Signal Strength Indicator (closer to 0 is better) | . | Noise Floor | Local background RF noise in dBm (more negative is quieter) | . | Hüppete loendur | Viimase sõnumi kärgvõrgu hüpete arv | . Signal Quality Reference . Signaali kvaliteeti hinnatakse SNR-i põhjal, mis on seotud aktiivse LoRa modemi eelseadistuse demodulatsiooni alumise piiriga, mitte fikseeritud läviväärtuste põhjal – antud SNR tähendab erinevatel eelseadistustel erinevat väärtust (nt −15 dB on LongSlow režiimil hea, kuid ShortFast režiimil mittekasutatav). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | Kvaliteet | Kriteerium | . | Hea | SNR above the preset’s limit | . | Rahuldav | vähem kui 5,5 dB piirväärtusest allpool | . | Halb | 5,5 dB kuni 7,5 dB piirväärtusest allpool | . | Puudub | üle 7,5 dB piirväärtusest allpool | . See Understanding the Signal Meter for the full explanation. Kohalik statistika ühendatud raadiost kuvatakse ka signaali kvaliteedi all, kui see on saadaval. Need logid sisaldavad mürataset, liiklusloendureid, edastusloendureid, võrgus olevate sõlmede arvu ja raadio tööaega. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment. | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/node-metrics.html#levi-kvaliteet",
    
    "relUrl": "/et-rEE/user/node-metrics.html#levi-kvaliteet"
  },"3559": {
    "doc": "Sõlme mõõdikud",
    "title": "Võimsusnäitajad",
    "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Meetriline | Kirjeldus | . | Vool | Per-channel voltage reading | . | Pinge | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/node-metrics.html#v%C3%B5imsusn%C3%A4itajad",
    
    "relUrl": "/et-rEE/user/node-metrics.html#võimsusnäitajad"
  },"3560": {
    "doc": "Sõlme mõõdikud",
    "title": "Marsruudi",
    "content": "Traceroute näitab sõnumi teed läbi kärgvõrgu: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | Rakendus saadab sihtsõlmele traceroute-päringu. | Results show each hop with its SNR. | . Traceroute’i tulemuste lugemine . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/node-metrics.html#marsruudi",
    
    "relUrl": "/et-rEE/user/node-metrics.html#marsruudi"
  },"3561": {
    "doc": "Sõlme mõõdikud",
    "title": "Asukoha logi",
    "content": "Asukohta jagavate sõlmede ajaloolised asukohaandmed: . | GPS koordinaadid | Kõrgus | Kiirus (kui liigub) | Timestamp for each position report | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/node-metrics.html#asukoha-logi",
    
    "relUrl": "/et-rEE/user/node-metrics.html#asukoha-logi"
  },"3562": {
    "doc": "Sõlme mõõdikud",
    "title": "Naabruse teave",
    "content": "Näitab, milliseid sõlmi antud sõlm otse kuuleb, kasulik kärgvõrgu topoloogia mõistmiseks. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/node-metrics.html#naabruse-teave",
    
    "relUrl": "/et-rEE/user/node-metrics.html#naabruse-teave"
  },"3563": {
    "doc": "Sõlme mõõdikud",
    "title": "Hosti mõõdik",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/node-metrics.html#hosti-m%C3%B5%C3%B5dik",
    
    "relUrl": "/et-rEE/user/node-metrics.html#hosti-mõõdik"
  },"3564": {
    "doc": "Sõlme mõõdikud",
    "title": "Pax mõõdiku logi",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/node-metrics.html#pax-m%C3%B5%C3%B5diku-logi",
    
    "relUrl": "/et-rEE/user/node-metrics.html#pax-mõõdiku-logi"
  },"3565": {
    "doc": "Sõlme mõõdikud",
    "title": "Seotud teemad",
    "content": ". | Nodes — node list, filtering, and sorting | Telemeetria & Sensorid — toetatud andurid ja seadistus | Signal Meter — how signal quality is calculated from SNR and RSSI | Local Mesh Discovery — traceroute details and neighbor info | Ühikud ja lokaat — temperatuuri, kauguse ja kiiruse kuvamise ühikud | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/node-metrics.html#seotud-teemad",
    
    "relUrl": "/et-rEE/user/node-metrics.html#seotud-teemad"
  },"3566": {
    "doc": "Node Metrics",
    "title": "Node Metrics",
    "content": "The node detail screen provides comprehensive telemetry and metrics for each node on your mesh. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/node-metrics.html",
    
    "relUrl": "/fr-rFR/user/node-metrics.html"
  },"3567": {
    "doc": "Node Metrics",
    "title": "Viewing Metrics",
    "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/node-metrics.html#viewing-metrics",
    
    "relUrl": "/fr-rFR/user/node-metrics.html#viewing-metrics"
  },"3568": {
    "doc": "Node Metrics",
    "title": "Métriques de l’appareil",
    "content": "Basic operating information reported by each node: . | Metric | Description | . | Niveau de batterie | Current battery percentage | . | Tension | Battery voltage reading | . | UtilCanal | Percentage of local airtime in use | . | UtilAir | Percentage of the last hour this node spent transmitting | . | Durée de fonctionnement | Time since last reboot | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/node-metrics.html#m%C3%A9triques-de-lappareil",
    
    "relUrl": "/fr-rFR/user/node-metrics.html#métriques-de-lappareil"
  },"3569": {
    "doc": "Node Metrics",
    "title": "Métriques d’environnement",
    "content": "Environmental sensor data (requires compatible hardware): . | Metric | Sensor Examples | . | Température | BME280, BME680, SHT31 | . | Humidité | BME280, BME680, SHT31 | . | Pression Barométrique | BME280, BMP280 | . | Résistance au gaz | BME680 | . | IAQ (Air Quality) | BME680 | . Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted: . 💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/node-metrics.html#m%C3%A9triques-denvironnement",
    
    "relUrl": "/fr-rFR/user/node-metrics.html#métriques-denvironnement"
  },"3570": {
    "doc": "Node Metrics",
    "title": "Air Quality Metrics",
    "content": "Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. | Metric | Unit | Description | . | PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | . | PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | . | PM10 | µg/m³ | Particulate matter up to 10 microns | . | AQI | EPA index | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated. | . | CO₂ | ppm | Carbon dioxide concentration | . | CO₂ temperature | °C / °F | Temperature reported by the CO₂ sensor itself (e.g. SCD4x) | . | CO₂ humidity | % | Relative humidity reported by the CO₂ sensor | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | Band | CO₂ Range (ppm) | Color | . | Bon | < 1000 | Vert | . | Stuffy | < 2000 | Amber | . | Poor | < 5000 | Orange | . | Unsafe | < 30000 | Rouge | . | Evacuate | ≥ 30000 | Dark red | . An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can: . | Select a time frame for the charts. | Filter with metric chips — only metrics that have data are shown. | Refresh / request the latest air-quality telemetry. | Export to CSV for analysis in a spreadsheet. | . 💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/node-metrics.html#air-quality-metrics",
    
    "relUrl": "/fr-rFR/user/node-metrics.html#air-quality-metrics"
  },"3571": {
    "doc": "Node Metrics",
    "title": "Qualité du signal",
    "content": "Radio signal quality information: . | Metric | Description | . | SNR | Signal-to-Noise Ratio (higher is better) | . | RSSI | Received Signal Strength Indicator (closer to 0 is better) | . | Noise Floor | Local background RF noise in dBm (more negative is quieter) | . | Hop Count | Number of mesh hops for last message | . Signal Quality Reference . Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | Quality | Criteria | . | Bon | SNR above the preset’s limit | . | Passable | less than 5.5 dB below the limit | . | Mauvais | 5.5 dB to 7.5 dB below the limit | . | Aucun | more than 7.5 dB below the limit | . See Understanding the Signal Meter for the full explanation. Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment. | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/node-metrics.html#qualit%C3%A9-du-signal",
    
    "relUrl": "/fr-rFR/user/node-metrics.html#qualité-du-signal"
  },"3572": {
    "doc": "Node Metrics",
    "title": "Métriques d’alimentation",
    "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Description | . | Tension | Per-channel voltage reading | . | Actif | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/node-metrics.html#m%C3%A9triques-dalimentation",
    
    "relUrl": "/fr-rFR/user/node-metrics.html#métriques-dalimentation"
  },"3573": {
    "doc": "Node Metrics",
    "title": "Traceroute",
    "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | The app sends a traceroute request to the target node. | Results show each hop with its SNR. | . Reading Traceroute Results . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/node-metrics.html#traceroute",
    
    "relUrl": "/fr-rFR/user/node-metrics.html#traceroute"
  },"3574": {
    "doc": "Node Metrics",
    "title": "Journal des positions",
    "content": "Historical position data for nodes that share their location: . | Coordonnées GPS | Altitude | Speed (if moving) | Timestamp for each position report | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/node-metrics.html#journal-des-positions",
    
    "relUrl": "/fr-rFR/user/node-metrics.html#journal-des-positions"
  },"3575": {
    "doc": "Node Metrics",
    "title": "Informations sur les voisins",
    "content": "Shows which nodes a given node can directly hear, useful for understanding mesh topology. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/node-metrics.html#informations-sur-les-voisins",
    
    "relUrl": "/fr-rFR/user/node-metrics.html#informations-sur-les-voisins"
  },"3576": {
    "doc": "Node Metrics",
    "title": "Métriques de l’hôte",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/node-metrics.html#m%C3%A9triques-de-lh%C3%B4te",
    
    "relUrl": "/fr-rFR/user/node-metrics.html#métriques-de-lhôte"
  },"3577": {
    "doc": "Node Metrics",
    "title": "Métriques de PAX",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/node-metrics.html#m%C3%A9triques-de-pax",
    
    "relUrl": "/fr-rFR/user/node-metrics.html#métriques-de-pax"
  },"3578": {
    "doc": "Node Metrics",
    "title": "Related Topics",
    "content": ". | Nodes — node list, filtering, and sorting | Telemetry & Sensors — supported sensors and configuration | Signal Meter — how signal quality is calculated from SNR and RSSI | Local Mesh Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/node-metrics.html#related-topics",
    
    "relUrl": "/fr-rFR/user/node-metrics.html#related-topics"
  },"3579": {
    "doc": "Node Metrics",
    "title": "Node Metrics",
    "content": "The node detail screen provides comprehensive telemetry and metrics for each node on your mesh. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/node-metrics.html",
    
    "relUrl": "/tr-rTR/user/node-metrics.html"
  },"3580": {
    "doc": "Node Metrics",
    "title": "Viewing Metrics",
    "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/node-metrics.html#viewing-metrics",
    
    "relUrl": "/tr-rTR/user/node-metrics.html#viewing-metrics"
  },"3581": {
    "doc": "Node Metrics",
    "title": "Device Metrics",
    "content": "Basic operating information reported by each node: . | Metric | Açıklaması | . | Battery Level | Current battery percentage | . | Voltaj | Battery voltage reading | . | ChUtil | Percentage of local airtime in use | . | AirUtil | Percentage of the last hour this node spent transmitting | . | Çalışma Süresi | Time since last reboot | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/node-metrics.html#device-metrics",
    
    "relUrl": "/tr-rTR/user/node-metrics.html#device-metrics"
  },"3582": {
    "doc": "Node Metrics",
    "title": "Environment Metrics",
    "content": "Environmental sensor data (requires compatible hardware): . | Metric | Sensor Examples | . | Sıcaklık | BME280, BME680, SHT31 | . | Nem | BME280, BME680, SHT31 | . | Barometrik Basınç | BME280, BMP280 | . | Gaz Direnci | BME680 | . | IAQ (Air Quality) | BME680 | . Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted: . 💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/node-metrics.html#environment-metrics",
    
    "relUrl": "/tr-rTR/user/node-metrics.html#environment-metrics"
  },"3583": {
    "doc": "Node Metrics",
    "title": "Air Quality Metrics",
    "content": "Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. | Metric | Unit | Açıklaması | . | PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | . | PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | . | PM10 | µg/m³ | Particulate matter up to 10 microns | . | AQI | EPA index | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated. | . | CO₂ | ppm | Carbon dioxide concentration | . | CO₂ temperature | °C / °F | Temperature reported by the CO₂ sensor itself (e.g. SCD4x) | . | CO₂ humidity | % | Relative humidity reported by the CO₂ sensor | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | Band | CO₂ Range (ppm) | Color | . | İyi | < 1000 | Yeşil | . | Stuffy | < 2000 | Amber | . | Poor | < 5000 | Orange | . | Unsafe | < 30000 | Kırmızı | . | Evacuate | ≥ 30000 | Dark red | . An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can: . | Select a time frame for the charts. | Filter with metric chips — only metrics that have data are shown. | Refresh / request the latest air-quality telemetry. | Export to CSV for analysis in a spreadsheet. | . 💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/node-metrics.html#air-quality-metrics",
    
    "relUrl": "/tr-rTR/user/node-metrics.html#air-quality-metrics"
  },"3584": {
    "doc": "Node Metrics",
    "title": "Sinyal Kalitesi",
    "content": "Radio signal quality information: . | Metric | Açıklaması | . | SNR | Signal-to-Noise Ratio (higher is better) | . | RSSI | Received Signal Strength Indicator (closer to 0 is better) | . | Noise Floor | Local background RF noise in dBm (more negative is quieter) | . | Hop Count | Number of mesh hops for last message | . Signal Quality Reference . Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | Quality | Criteria | . | İyi | SNR above the preset’s limit | . | İdare Eder | less than 5.5 dB below the limit | . | Kötü | 5.5 dB to 7.5 dB below the limit | . | Yok | more than 7.5 dB below the limit | . See Understanding the Signal Meter for the full explanation. Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment. | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/node-metrics.html#sinyal-kalitesi",
    
    "relUrl": "/tr-rTR/user/node-metrics.html#sinyal-kalitesi"
  },"3585": {
    "doc": "Node Metrics",
    "title": "Power Metrics",
    "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Açıklaması | . | Voltaj | Per-channel voltage reading | . | Akım | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/node-metrics.html#power-metrics",
    
    "relUrl": "/tr-rTR/user/node-metrics.html#power-metrics"
  },"3586": {
    "doc": "Node Metrics",
    "title": "Yol izle",
    "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | The app sends a traceroute request to the target node. | Results show each hop with its SNR. | . Reading Traceroute Results . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/node-metrics.html#yol-izle",
    
    "relUrl": "/tr-rTR/user/node-metrics.html#yol-izle"
  },"3587": {
    "doc": "Node Metrics",
    "title": "Konum Kayıtları",
    "content": "Historical position data for nodes that share their location: . | GPS coordinates | Rakım | Speed (if moving) | Timestamp for each position report | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/node-metrics.html#konum-kay%C4%B1tlar%C4%B1",
    
    "relUrl": "/tr-rTR/user/node-metrics.html#konum-kayıtları"
  },"3588": {
    "doc": "Node Metrics",
    "title": "Komşu Bilgisi",
    "content": "Shows which nodes a given node can directly hear, useful for understanding mesh topology. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/node-metrics.html#kom%C5%9Fu-bilgisi",
    
    "relUrl": "/tr-rTR/user/node-metrics.html#komşu-bilgisi"
  },"3589": {
    "doc": "Node Metrics",
    "title": "Sunucu Ölçümleri",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/node-metrics.html#sunucu-%C3%B6l%C3%A7%C3%BCmleri",
    
    "relUrl": "/tr-rTR/user/node-metrics.html#sunucu-ölçümleri"
  },"3590": {
    "doc": "Node Metrics",
    "title": "PAX Metrics",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/node-metrics.html#pax-metrics",
    
    "relUrl": "/tr-rTR/user/node-metrics.html#pax-metrics"
  },"3591": {
    "doc": "Node Metrics",
    "title": "Related Topics",
    "content": ". | Nodes — node list, filtering, and sorting | Telemetry & Sensors — supported sensors and configuration | Signal Meter — how signal quality is calculated from SNR and RSSI | Local Mesh Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/node-metrics.html#related-topics",
    
    "relUrl": "/tr-rTR/user/node-metrics.html#related-topics"
  },"3592": {
    "doc": "Node Metrics",
    "title": "Node Metrics",
    "content": "The node detail screen provides comprehensive telemetry and metrics for each node on your mesh. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/node-metrics.html",
    
    "relUrl": "/el-rGR/user/node-metrics.html"
  },"3593": {
    "doc": "Node Metrics",
    "title": "Viewing Metrics",
    "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/node-metrics.html#viewing-metrics",
    
    "relUrl": "/el-rGR/user/node-metrics.html#viewing-metrics"
  },"3594": {
    "doc": "Node Metrics",
    "title": "Device Metrics",
    "content": "Basic operating information reported by each node: . | Metric | Περιγραφή | . | Battery Level | Current battery percentage | . | Τάση | Battery voltage reading | . | ChUtil | Percentage of local airtime in use | . | AirUtil | Percentage of the last hour this node spent transmitting | . | Uptime | Time since last reboot | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/node-metrics.html#device-metrics",
    
    "relUrl": "/el-rGR/user/node-metrics.html#device-metrics"
  },"3595": {
    "doc": "Node Metrics",
    "title": "Environment Metrics",
    "content": "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 — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted: . 💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/node-metrics.html#environment-metrics",
    
    "relUrl": "/el-rGR/user/node-metrics.html#environment-metrics"
  },"3596": {
    "doc": "Node Metrics",
    "title": "Air Quality Metrics",
    "content": "Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. | Metric | Unit | Περιγραφή | . | PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | . | PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | . | PM10 | µg/m³ | Particulate matter up to 10 microns | . | AQI | EPA index | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated. | . | CO₂ | ppm | Carbon dioxide concentration | . | CO₂ temperature | °C / °F | Temperature reported by the CO₂ sensor itself (e.g. SCD4x) | . | CO₂ humidity | % | Relative humidity reported by the CO₂ sensor | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | Band | CO₂ Range (ppm) | Color | . | Good | < 1000 | Πράσινο | . | Stuffy | < 2000 | Amber | . | Poor | < 5000 | Orange | . | Unsafe | < 30000 | Κόκκινο | . | Evacuate | ≥ 30000 | Dark red | . An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can: . | Select a time frame for the charts. | Filter with metric chips — only metrics that have data are shown. | Refresh / request the latest air-quality telemetry. | Export to CSV for analysis in a spreadsheet. | . 💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/node-metrics.html#air-quality-metrics",
    
    "relUrl": "/el-rGR/user/node-metrics.html#air-quality-metrics"
  },"3597": {
    "doc": "Node Metrics",
    "title": "Signal Quality",
    "content": "Radio signal quality information: . | Metric | Περιγραφή | . | SNR | Signal-to-Noise Ratio (higher is better) | . | RSSI | Received Signal Strength Indicator (closer to 0 is better) | . | Noise Floor | Local background RF noise in dBm (more negative is quieter) | . | Hop Count | Number of mesh hops for last message | . Signal Quality Reference . Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | Quality | Criteria | . | Good | SNR above the preset’s limit | . | Fair | less than 5.5 dB below the limit | . | Bad | 5.5 dB to 7.5 dB below the limit | . | None | more than 7.5 dB below the limit | . See Understanding the Signal Meter for the full explanation. Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment. | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/node-metrics.html#signal-quality",
    
    "relUrl": "/el-rGR/user/node-metrics.html#signal-quality"
  },"3598": {
    "doc": "Node Metrics",
    "title": "Power Metrics",
    "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Περιγραφή | . | Τάση | Per-channel voltage reading | . | Current | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/node-metrics.html#power-metrics",
    
    "relUrl": "/el-rGR/user/node-metrics.html#power-metrics"
  },"3599": {
    "doc": "Node Metrics",
    "title": "Traceroute",
    "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | The app sends a traceroute request to the target node. | Results show each hop with its SNR. | . Reading Traceroute Results . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/node-metrics.html#traceroute",
    
    "relUrl": "/el-rGR/user/node-metrics.html#traceroute"
  },"3600": {
    "doc": "Node Metrics",
    "title": "Αρχείο Καταγραφής Τοποθεσίας",
    "content": "Historical position data for nodes that share their location: . | GPS coordinates | Altitude | Speed (if moving) | Timestamp for each position report | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/node-metrics.html#%CE%B1%CF%81%CF%87%CE%B5%CE%AF%CE%BF-%CE%BA%CE%B1%CF%84%CE%B1%CE%B3%CF%81%CE%B1%CF%86%CE%AE%CF%82-%CF%84%CE%BF%CF%80%CE%BF%CE%B8%CE%B5%CF%83%CE%AF%CE%B1%CF%82",
    
    "relUrl": "/el-rGR/user/node-metrics.html#αρχείο-καταγραφής-τοποθεσίας"
  },"3601": {
    "doc": "Node Metrics",
    "title": "Neighbor Info",
    "content": "Shows which nodes a given node can directly hear, useful for understanding mesh topology. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/node-metrics.html#neighbor-info",
    
    "relUrl": "/el-rGR/user/node-metrics.html#neighbor-info"
  },"3602": {
    "doc": "Node Metrics",
    "title": "Host Metrics",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/node-metrics.html#host-metrics",
    
    "relUrl": "/el-rGR/user/node-metrics.html#host-metrics"
  },"3603": {
    "doc": "Node Metrics",
    "title": "PAX Metrics",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/node-metrics.html#pax-metrics",
    
    "relUrl": "/el-rGR/user/node-metrics.html#pax-metrics"
  },"3604": {
    "doc": "Node Metrics",
    "title": "Related Topics",
    "content": ". | Nodes — node list, filtering, and sorting | Telemetry & Sensors — supported sensors and configuration | Signal Meter — how signal quality is calculated from SNR and RSSI | Local Mesh Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/node-metrics.html#related-topics",
    
    "relUrl": "/el-rGR/user/node-metrics.html#related-topics"
  },"3605": {
    "doc": "Node Metrics",
    "title": "Node Metrics",
    "content": "The node detail screen provides comprehensive telemetry and metrics for each node on your mesh. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/node-metrics.html",
    
    "relUrl": "/ro-rRO/user/node-metrics.html"
  },"3606": {
    "doc": "Node Metrics",
    "title": "Viewing Metrics",
    "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/node-metrics.html#viewing-metrics",
    
    "relUrl": "/ro-rRO/user/node-metrics.html#viewing-metrics"
  },"3607": {
    "doc": "Node Metrics",
    "title": "Valori dispozitiv",
    "content": "Basic operating information reported by each node: . | Metric | Descriere | . | Battery Level | Current battery percentage | . | Tensiune | Battery voltage reading | . | ChUtil | Percentage of local airtime in use | . | AirUtil | Percentage of the last hour this node spent transmitting | . | Timp de functionare | Time since last reboot | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/node-metrics.html#valori-dispozitiv",
    
    "relUrl": "/ro-rRO/user/node-metrics.html#valori-dispozitiv"
  },"3608": {
    "doc": "Node Metrics",
    "title": "Indicatori de mediu",
    "content": "Environmental sensor data (requires compatible hardware): . | Metric | Sensor Examples | . | Temperature | BME280, BME680, SHT31 | . | Humidity | BME280, BME680, SHT31 | . | Barometric Pressure | BME280, BMP280 | . | Rezistența la gaz | BME680 | . | IAQ (Air Quality) | BME680 | . Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted: . 💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/node-metrics.html#indicatori-de-mediu",
    
    "relUrl": "/ro-rRO/user/node-metrics.html#indicatori-de-mediu"
  },"3609": {
    "doc": "Node Metrics",
    "title": "Air Quality Metrics",
    "content": "Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. | Metric | Unit | Descriere | . | PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | . | PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | . | PM10 | µg/m³ | Particulate matter up to 10 microns | . | AQI | EPA index | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated. | . | CO₂ | ppm | Carbon dioxide concentration | . | CO₂ temperature | °C / °F | Temperature reported by the CO₂ sensor itself (e.g. SCD4x) | . | CO₂ humidity | % | Relative humidity reported by the CO₂ sensor | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | Band | CO₂ Range (ppm) | Color | . | Bun | < 1000 | Verde | . | Stuffy | < 2000 | Amber | . | Poor | < 5000 | Portocaliu | . | Unsafe | < 30000 | Roșu | . | Evacuate | ≥ 30000 | Dark red | . An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can: . | Select a time frame for the charts. | Filter with metric chips — only metrics that have data are shown. | Refresh / request the latest air-quality telemetry. | Export to CSV for analysis in a spreadsheet. | . 💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/node-metrics.html#air-quality-metrics",
    
    "relUrl": "/ro-rRO/user/node-metrics.html#air-quality-metrics"
  },"3610": {
    "doc": "Node Metrics",
    "title": "Calitatea semnalului",
    "content": "Radio signal quality information: . | Metric | Descriere | . | SNR | Signal-to-Noise Ratio (higher is better) | . | RSSI | Received Signal Strength Indicator (closer to 0 is better) | . | Noise Floor | Local background RF noise in dBm (more negative is quieter) | . | Hop Count | Number of mesh hops for last message | . Signal Quality Reference . Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | Quality | Criteria | . | Bun | SNR above the preset’s limit | . | Acceptabil | less than 5.5 dB below the limit | . | Slab | 5.5 dB to 7.5 dB below the limit | . | Niciunul | more than 7.5 dB below the limit | . See Understanding the Signal Meter for the full explanation. Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment. | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/node-metrics.html#calitatea-semnalului",
    
    "relUrl": "/ro-rRO/user/node-metrics.html#calitatea-semnalului"
  },"3611": {
    "doc": "Node Metrics",
    "title": "Valori putere",
    "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Descriere | . | Tensiune | Per-channel voltage reading | . | Actual | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/node-metrics.html#valori-putere",
    
    "relUrl": "/ro-rRO/user/node-metrics.html#valori-putere"
  },"3612": {
    "doc": "Node Metrics",
    "title": "Trasare traseu",
    "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | The app sends a traceroute request to the target node. | Results show each hop with its SNR. | . Reading Traceroute Results . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/node-metrics.html#trasare-traseu",
    
    "relUrl": "/ro-rRO/user/node-metrics.html#trasare-traseu"
  },"3613": {
    "doc": "Node Metrics",
    "title": "Position Log",
    "content": "Historical position data for nodes that share their location: . | GPS coordinates | Altitudine | Speed (if moving) | Timestamp for each position report | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/node-metrics.html#position-log",
    
    "relUrl": "/ro-rRO/user/node-metrics.html#position-log"
  },"3614": {
    "doc": "Node Metrics",
    "title": "Informații vecin",
    "content": "Shows which nodes a given node can directly hear, useful for understanding mesh topology. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/node-metrics.html#informa%C8%9Bii-vecin",
    
    "relUrl": "/ro-rRO/user/node-metrics.html#informații-vecin"
  },"3615": {
    "doc": "Node Metrics",
    "title": "Valori Gazdă",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/node-metrics.html#valori-gazd%C4%83",
    
    "relUrl": "/ro-rRO/user/node-metrics.html#valori-gazdă"
  },"3616": {
    "doc": "Node Metrics",
    "title": "Măsurători PAX",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/node-metrics.html#m%C4%83sur%C4%83tori-pax",
    
    "relUrl": "/ro-rRO/user/node-metrics.html#măsurători-pax"
  },"3617": {
    "doc": "Node Metrics",
    "title": "Related Topics",
    "content": ". | Nodes — node list, filtering, and sorting | Telemetry & Sensors — supported sensors and configuration | Signal Meter — how signal quality is calculated from SNR and RSSI | Local Mesh Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/node-metrics.html#related-topics",
    
    "relUrl": "/ro-rRO/user/node-metrics.html#related-topics"
  },"3618": {
    "doc": "Node Metrics",
    "title": "Node Metrics",
    "content": "The node detail screen provides comprehensive telemetry and metrics for each node on your mesh. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/node-metrics.html",
    
    "relUrl": "/iw-rIL/user/node-metrics.html"
  },"3619": {
    "doc": "Node Metrics",
    "title": "Viewing Metrics",
    "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/node-metrics.html#viewing-metrics",
    
    "relUrl": "/iw-rIL/user/node-metrics.html#viewing-metrics"
  },"3620": {
    "doc": "Node Metrics",
    "title": "Device Metrics",
    "content": "Basic operating information reported by each node: . | Metric | תיאור | . | Battery Level | Current battery percentage | . | Voltage | Battery voltage reading | . | ChUtil | Percentage of local airtime in use | . | AirUtil | Percentage of the last hour this node spent transmitting | . | Uptime | Time since last reboot | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/node-metrics.html#device-metrics",
    
    "relUrl": "/iw-rIL/user/node-metrics.html#device-metrics"
  },"3621": {
    "doc": "Node Metrics",
    "title": "Environment Metrics",
    "content": "Environmental sensor data (requires compatible hardware): . | Metric | Sensor Examples | . | Temperature | BME280, BME680, SHT31 | . | Humidity | BME280, BME680, SHT31 | . | Barometric Pressure | BME280, BMP280 | . | Gas Resistance | BME680 | . | IAQ (Air Quality) | BME680 | . Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted: . 💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/node-metrics.html#environment-metrics",
    
    "relUrl": "/iw-rIL/user/node-metrics.html#environment-metrics"
  },"3622": {
    "doc": "Node Metrics",
    "title": "Air Quality Metrics",
    "content": "Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. | Metric | Unit | תיאור | . | PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | . | PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | . | PM10 | µg/m³ | Particulate matter up to 10 microns | . | AQI | EPA index | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated. | . | CO₂ | ppm | Carbon dioxide concentration | . | CO₂ temperature | °C / °F | Temperature reported by the CO₂ sensor itself (e.g. SCD4x) | . | CO₂ humidity | % | Relative humidity reported by the CO₂ sensor | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | Band | CO₂ Range (ppm) | Color | . | Good | < 1000 | Green | . | Stuffy | < 2000 | Amber | . | Poor | < 5000 | Orange | . | Unsafe | < 30000 | Red | . | Evacuate | ≥ 30000 | Dark red | . An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can: . | Select a time frame for the charts. | Filter with metric chips — only metrics that have data are shown. | Refresh / request the latest air-quality telemetry. | Export to CSV for analysis in a spreadsheet. | . 💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/node-metrics.html#air-quality-metrics",
    
    "relUrl": "/iw-rIL/user/node-metrics.html#air-quality-metrics"
  },"3623": {
    "doc": "Node Metrics",
    "title": "Signal Quality",
    "content": "Radio signal quality information: . | Metric | תיאור | . | SNR | Signal-to-Noise Ratio (higher is better) | . | RSSI | Received Signal Strength Indicator (closer to 0 is better) | . | Noise Floor | Local background RF noise in dBm (more negative is quieter) | . | Hop Count | Number of mesh hops for last message | . Signal Quality Reference . Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | Quality | Criteria | . | Good | SNR above the preset’s limit | . | Fair | less than 5.5 dB below the limit | . | Bad | 5.5 dB to 7.5 dB below the limit | . | None | more than 7.5 dB below the limit | . See Understanding the Signal Meter for the full explanation. Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment. | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/node-metrics.html#signal-quality",
    
    "relUrl": "/iw-rIL/user/node-metrics.html#signal-quality"
  },"3624": {
    "doc": "Node Metrics",
    "title": "Power Metrics",
    "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | תיאור | . | Voltage | Per-channel voltage reading | . | Current | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/node-metrics.html#power-metrics",
    
    "relUrl": "/iw-rIL/user/node-metrics.html#power-metrics"
  },"3625": {
    "doc": "Node Metrics",
    "title": "בדיקת מסלול",
    "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | The app sends a traceroute request to the target node. | Results show each hop with its SNR. | . Reading Traceroute Results . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/node-metrics.html#%D7%91%D7%93%D7%99%D7%A7%D7%AA-%D7%9E%D7%A1%D7%9C%D7%95%D7%9C",
    
    "relUrl": "/iw-rIL/user/node-metrics.html#בדיקת-מסלול"
  },"3626": {
    "doc": "Node Metrics",
    "title": "Position Log",
    "content": "Historical position data for nodes that share their location: . | GPS coordinates | Altitude | Speed (if moving) | Timestamp for each position report | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/node-metrics.html#position-log",
    
    "relUrl": "/iw-rIL/user/node-metrics.html#position-log"
  },"3627": {
    "doc": "Node Metrics",
    "title": "Neighbor Info",
    "content": "Shows which nodes a given node can directly hear, useful for understanding mesh topology. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/node-metrics.html#neighbor-info",
    
    "relUrl": "/iw-rIL/user/node-metrics.html#neighbor-info"
  },"3628": {
    "doc": "Node Metrics",
    "title": "Host Metrics",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/node-metrics.html#host-metrics",
    
    "relUrl": "/iw-rIL/user/node-metrics.html#host-metrics"
  },"3629": {
    "doc": "Node Metrics",
    "title": "PAX Metrics",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/node-metrics.html#pax-metrics",
    
    "relUrl": "/iw-rIL/user/node-metrics.html#pax-metrics"
  },"3630": {
    "doc": "Node Metrics",
    "title": "Related Topics",
    "content": ". | Nodes — node list, filtering, and sorting | Telemetry & Sensors — supported sensors and configuration | Signal Meter — how signal quality is calculated from SNR and RSSI | Local Mesh Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/node-metrics.html#related-topics",
    
    "relUrl": "/iw-rIL/user/node-metrics.html#related-topics"
  },"3631": {
    "doc": "Node Metrics",
    "title": "Node Metrics",
    "content": "The node detail screen provides comprehensive telemetry and metrics for each node on your mesh. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/node-metrics.html",
    
    "relUrl": "/pt-rBR/user/node-metrics.html"
  },"3632": {
    "doc": "Node Metrics",
    "title": "Viewing Metrics",
    "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/node-metrics.html#viewing-metrics",
    
    "relUrl": "/pt-rBR/user/node-metrics.html#viewing-metrics"
  },"3633": {
    "doc": "Node Metrics",
    "title": "Device Metrics",
    "content": "Basic operating information reported by each node: . | Metric | Descrição | . | Battery Level | Current battery percentage | . | Voltagem | Battery voltage reading | . | ChUtil | Percentage of local airtime in use | . | AirUtil | Percentage of the last hour this node spent transmitting | . | Uptime | Time since last reboot | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/node-metrics.html#device-metrics",
    
    "relUrl": "/pt-rBR/user/node-metrics.html#device-metrics"
  },"3634": {
    "doc": "Node Metrics",
    "title": "Environment Metrics",
    "content": "Environmental sensor data (requires compatible hardware): . | Metric | Sensor Examples | . | Temperatura | BME280, BME680, SHT31 | . | Umidade | BME280, BME680, SHT31 | . | Pressão Barométrica | BME280, BMP280 | . | Resistência ao gás | BME680 | . | IAQ (Air Quality) | BME680 | . Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted: . 💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/node-metrics.html#environment-metrics",
    
    "relUrl": "/pt-rBR/user/node-metrics.html#environment-metrics"
  },"3635": {
    "doc": "Node Metrics",
    "title": "Air Quality Metrics",
    "content": "Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. | Metric | Unit | Descrição | . | PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | . | PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | . | PM10 | µg/m³ | Particulate matter up to 10 microns | . | AQI | EPA index | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated. | . | CO₂ | ppm | Carbon dioxide concentration | . | CO₂ temperature | °C / °F | Temperature reported by the CO₂ sensor itself (e.g. SCD4x) | . | CO₂ humidity | % | Relative humidity reported by the CO₂ sensor | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | Band | CO₂ Range (ppm) | Color | . | Bom | < 1000 | Verde | . | Stuffy | < 2000 | Amber | . | Poor | < 5000 | Orange | . | Unsafe | < 30000 | Vermelho | . | Evacuate | ≥ 30000 | Dark red | . An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can: . | Select a time frame for the charts. | Filter with metric chips — only metrics that have data are shown. | Refresh / request the latest air-quality telemetry. | Export to CSV for analysis in a spreadsheet. | . 💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/node-metrics.html#air-quality-metrics",
    
    "relUrl": "/pt-rBR/user/node-metrics.html#air-quality-metrics"
  },"3636": {
    "doc": "Node Metrics",
    "title": "Qualidade do sinal",
    "content": "Radio signal quality information: . | Metric | Descrição | . | SNR | Signal-to-Noise Ratio (higher is better) | . | RSSI | Received Signal Strength Indicator (closer to 0 is better) | . | Noise Floor | Local background RF noise in dBm (more negative is quieter) | . | Hop Count | Number of mesh hops for last message | . Signal Quality Reference . Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | Quality | Criteria | . | Bom | SNR above the preset’s limit | . | Média | less than 5.5 dB below the limit | . | Ruim | 5.5 dB to 7.5 dB below the limit | . | Nenhum | more than 7.5 dB below the limit | . See Understanding the Signal Meter for the full explanation. Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment. | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/node-metrics.html#qualidade-do-sinal",
    
    "relUrl": "/pt-rBR/user/node-metrics.html#qualidade-do-sinal"
  },"3637": {
    "doc": "Node Metrics",
    "title": "Power Metrics",
    "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Descrição | . | Voltagem | Per-channel voltage reading | . | Atual | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/node-metrics.html#power-metrics",
    
    "relUrl": "/pt-rBR/user/node-metrics.html#power-metrics"
  },"3638": {
    "doc": "Node Metrics",
    "title": "Traçar rota",
    "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | The app sends a traceroute request to the target node. | Results show each hop with its SNR. | . Reading Traceroute Results . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/node-metrics.html#tra%C3%A7ar-rota",
    
    "relUrl": "/pt-rBR/user/node-metrics.html#traçar-rota"
  },"3639": {
    "doc": "Node Metrics",
    "title": "Log de Posição",
    "content": "Historical position data for nodes that share their location: . | GPS coordinates | Altitude | Speed (if moving) | Timestamp for each position report | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/node-metrics.html#log-de-posi%C3%A7%C3%A3o",
    
    "relUrl": "/pt-rBR/user/node-metrics.html#log-de-posição"
  },"3640": {
    "doc": "Node Metrics",
    "title": "Informações do Vizinho",
    "content": "Shows which nodes a given node can directly hear, useful for understanding mesh topology. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/node-metrics.html#informa%C3%A7%C3%B5es-do-vizinho",
    
    "relUrl": "/pt-rBR/user/node-metrics.html#informações-do-vizinho"
  },"3641": {
    "doc": "Node Metrics",
    "title": "Métricas do Host",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/node-metrics.html#m%C3%A9tricas-do-host",
    
    "relUrl": "/pt-rBR/user/node-metrics.html#métricas-do-host"
  },"3642": {
    "doc": "Node Metrics",
    "title": "PAX Metrics",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/node-metrics.html#pax-metrics",
    
    "relUrl": "/pt-rBR/user/node-metrics.html#pax-metrics"
  },"3643": {
    "doc": "Node Metrics",
    "title": "Related Topics",
    "content": ". | Nodes — node list, filtering, and sorting | Telemetry & Sensors — supported sensors and configuration | Signal Meter — how signal quality is calculated from SNR and RSSI | Local Mesh Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/node-metrics.html#related-topics",
    
    "relUrl": "/pt-rBR/user/node-metrics.html#related-topics"
  },"3644": {
    "doc": "Node Metrics",
    "title": "Node Metrics",
    "content": "The node detail screen provides comprehensive telemetry and metrics for each node on your mesh. ",
    "url": "/Meshtastic-Android/main/en/user/node-metrics.html",
    
    "relUrl": "/en/user/node-metrics.html"
  },"3645": {
    "doc": "Node Metrics",
    "title": "Viewing Metrics",
    "content": ". | Navigate to Nodes. | Tap the node you want to inspect. | Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest. | Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category’s history, and appears once the node has reported that kind of telemetry. | . The Position row expands to show location data for nodes that share GPS: . ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics update at intervals configured on each node’s telemetry settings. ",
    "url": "/Meshtastic-Android/main/en/user/node-metrics.html#viewing-metrics",
    
    "relUrl": "/en/user/node-metrics.html#viewing-metrics"
  },"3646": {
    "doc": "Node Metrics",
    "title": "Device Metrics",
    "content": "Basic operating information reported by each node: . | Metric | Description | . | Battery Level | Current battery percentage | . | Voltage | Battery voltage reading | . | ChUtil | Percentage of local airtime in use | . | AirUtil | Percentage of the last hour this node spent transmitting | . | Uptime | Time since last reboot | . Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV. 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis. ",
    "url": "/Meshtastic-Android/main/en/user/node-metrics.html#device-metrics",
    
    "relUrl": "/en/user/node-metrics.html#device-metrics"
  },"3647": {
    "doc": "Node Metrics",
    "title": "Environment Metrics",
    "content": "Environmental sensor data (requires compatible hardware): . | Metric | Sensor Examples | . | Temperature | BME280, BME680, SHT31 | . | Humidity | BME280, BME680, SHT31 | . | Barometric Pressure | BME280, BMP280 | . | Gas Resistance | BME680 | . | IAQ (Air Quality) | BME680 | . Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis. The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted: . 💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report environmental data. See Telemetry & Sensors for a full list of supported sensors. ",
    "url": "/Meshtastic-Android/main/en/user/node-metrics.html#environment-metrics",
    
    "relUrl": "/en/user/node-metrics.html#environment-metrics"
  },"3648": {
    "doc": "Node Metrics",
    "title": "Air Quality Metrics",
    "content": "Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements. | Metric | Unit | Description | . | PM1.0 | µg/m³ | Particulate matter up to 1.0 micron | . | PM2.5 | µg/m³ | Particulate matter up to 2.5 microns | . | PM10 | µg/m³ | Particulate matter up to 10 microns | . | AQI | EPA index | EPA NowCast AQI computed from the node’s recent PM2.5 history, with a color-coded severity label. Shown next to PM2.5 once enough readings have accumulated. | . | CO₂ | ppm | Carbon dioxide concentration | . | CO₂ temperature | °C / °F | Temperature reported by the CO₂ sensor itself (e.g. SCD4x) | . | CO₂ humidity | % | Relative humidity reported by the CO₂ sensor | . CO₂ readings are color-coded by severity so you can read air quality at a glance: . | Band | CO₂ Range (ppm) | Color | . | Good | < 1000 | Green | . | Stuffy | < 2000 | Amber | . | Poor | < 5000 | Orange | . | Unsafe | < 30000 | Red | . | Evacuate | ≥ 30000 | Dark red | . An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can: . | Select a time frame for the charts. | Filter with metric chips — only metrics that have data are shown. | Refresh / request the latest air-quality telemetry. | Export to CSV for analysis in a spreadsheet. | . 💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See Telemetry & Sensors for supported hardware. ",
    "url": "/Meshtastic-Android/main/en/user/node-metrics.html#air-quality-metrics",
    
    "relUrl": "/en/user/node-metrics.html#air-quality-metrics"
  },"3649": {
    "doc": "Node Metrics",
    "title": "Signal Quality",
    "content": "Radio signal quality information: . | Metric | Description | . | SNR | Signal-to-Noise Ratio (higher is better) | . | RSSI | Received Signal Strength Indicator (closer to 0 is better) | . | Noise Floor | Local background RF noise in dBm (more negative is quieter) | . | Hop Count | Number of mesh hops for last message | . Signal Quality Reference . Signal quality is rated from SNR relative to the active LoRa modem preset’s demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). When RSSI and a noise-floor reading are both available, the app also rates their difference against the preset limit and uses the worse rating. Otherwise, RSSI is display-only. In the table, limit is the preset’s SNR limit. | Quality | Criteria | . | Good | SNR above the preset’s limit | . | Fair | less than 5.5 dB below the limit | . | Bad | 5.5 dB to 7.5 dB below the limit | . | None | more than 7.5 dB below the limit | . See Understanding the Signal Meter for the full explanation. Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment. | Request — ask the connected radio for a fresh Local Stats telemetry report | Clear — remove Local Stats logs for that node | Save — export the visible Local Stats history as CSV | . ",
    "url": "/Meshtastic-Android/main/en/user/node-metrics.html#signal-quality",
    
    "relUrl": "/en/user/node-metrics.html#signal-quality"
  },"3650": {
    "doc": "Node Metrics",
    "title": "Power Metrics",
    "content": "Power management telemetry (requires INA sensor or compatible hardware): . | Metric | Description | . | Voltage | Per-channel voltage reading | . | Current | Per-channel draw, in milliamps | . The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current. ",
    "url": "/Meshtastic-Android/main/en/user/node-metrics.html#power-metrics",
    
    "relUrl": "/en/user/node-metrics.html#power-metrics"
  },"3651": {
    "doc": "Node Metrics",
    "title": "Traceroute",
    "content": "Traceroute shows the path a message takes through the mesh: . | From the node detail screen’s Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds. | The app sends a traceroute request to the target node. | Results show each hop with its SNR. | . Reading Traceroute Results . A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position. A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all. ",
    "url": "/Meshtastic-Android/main/en/user/node-metrics.html#traceroute",
    
    "relUrl": "/en/user/node-metrics.html#traceroute"
  },"3652": {
    "doc": "Node Metrics",
    "title": "Position Log",
    "content": "Historical position data for nodes that share their location: . | GPS coordinates | Altitude | Speed (if moving) | Timestamp for each position report | . ",
    "url": "/Meshtastic-Android/main/en/user/node-metrics.html#position-log",
    
    "relUrl": "/en/user/node-metrics.html#position-log"
  },"3653": {
    "doc": "Node Metrics",
    "title": "Neighbor Info",
    "content": "Shows which nodes a given node can directly hear, useful for understanding mesh topology. ",
    "url": "/Meshtastic-Android/main/en/user/node-metrics.html#neighbor-info",
    
    "relUrl": "/en/user/node-metrics.html#neighbor-info"
  },"3654": {
    "doc": "Node Metrics",
    "title": "Host Metrics",
    "content": "Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host’s own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them. ",
    "url": "/Meshtastic-Android/main/en/user/node-metrics.html#host-metrics",
    
    "relUrl": "/en/user/node-metrics.html#host-metrics"
  },"3655": {
    "doc": "Node Metrics",
    "title": "PAX Metrics",
    "content": "A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people. ",
    "url": "/Meshtastic-Android/main/en/user/node-metrics.html#pax-metrics",
    
    "relUrl": "/en/user/node-metrics.html#pax-metrics"
  },"3656": {
    "doc": "Node Metrics",
    "title": "Related Topics",
    "content": ". | Nodes — node list, filtering, and sorting | Telemetry & Sensors — supported sensors and configuration | Signal Meter — how signal quality is calculated from SNR and RSSI | Local Mesh Discovery — traceroute details and neighbor info | Units & Locale — temperature, distance, and speed display formats | . ",
    "url": "/Meshtastic-Android/main/en/user/node-metrics.html#related-topics",
    
    "relUrl": "/en/user/node-metrics.html#related-topics"
  },"3657": {
    "doc": "Nodes",
    "title": "Nodes",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/nodes.html",
    
    "relUrl": "/sk-rSK/user/nodes.html"
  },"3658": {
    "doc": "Nodes",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Indicator | Meaning | . | Green last-heard time | Node heard within the last 2 hours | . | Plain last-heard time | Node not heard for over 2 hours | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Favorite | Node you marked as a favorite. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Node roles . Nodes can be configured with different roles that affect their mesh behavior: . | Rola | Popis | . | Klient | Standard end-user node | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Stlmený Klient | Receives but doesn’t retransmit | . | Skrytý Klient | Like Client Mute, plus hides from node list | . | Smerovač | Prioritizes message forwarding; stays awake to relay | . | Smerovač s Oneskorením | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Sledovač | Optimized for position reporting at regular intervals | . | Senzor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Sledovač | TAK position reporting only | . | Straty a nálezy | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . 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 nodes. | 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 nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | Icon | Meaning | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Mismatch | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/nodes.html#node-list",
    
    "relUrl": "/sk-rSK/user/nodes.html#node-list"
  },"3659": {
    "doc": "Nodes",
    "title": "Quick Actions",
    "content": "From the node list, you can: . | Tap a node to view its detail page | Touch & hold for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Odstrániť | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/nodes.html#quick-actions",
    
    "relUrl": "/sk-rSK/user/nodes.html#quick-actions"
  },"3660": {
    "doc": "Nodes",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/sk-rSK/user/nodes.html#sharing-a-contact"
  },"3661": {
    "doc": "Nodes",
    "title": "Filtering & sorting",
    "content": "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 . | Filter | Popis | . | Hide offline nodes | Show only nodes heard within the last 2 hours | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Include unknown | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Sort | Popis | . | Last heard | Most recently heard nodes first | . | A-Z | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/nodes.html#filtering--sorting",
    
    "relUrl": "/sk-rSK/user/nodes.html#filtering--sorting"
  },"3662": {
    "doc": "Nodes",
    "title": "Nodes per hop",
    "content": "Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/sk-rSK/user/nodes.html#nodes-per-hop"
  },"3663": {
    "doc": "Nodes",
    "title": "Node detail",
    "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Posledný príjem | | . | Vzdialenosť | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | Meaning | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/nodes.html#node-detail",
    
    "relUrl": "/sk-rSK/user/nodes.html#node-detail"
  },"3664": {
    "doc": "Nodes",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/sk-rSK/user/nodes.html#when-no-nodes-appear"
  },"3665": {
    "doc": "Nodes",
    "title": "Related Topics",
    "content": ". | Node Metrics — detailed telemetry dashboards for each node | Messages & Channels — send a direct message to a node | Map & Waypoints — view node positions geographically | Local Mesh Discovery — traceroute and neighbor info for topology exploration | Signal Meter — understand what the signal bars mean | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/nodes.html#related-topics",
    
    "relUrl": "/sk-rSK/user/nodes.html#related-topics"
  },"3666": {
    "doc": "Nodes",
    "title": "Nodes",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/nodes.html",
    
    "relUrl": "/be-rBY/user/nodes.html"
  },"3667": {
    "doc": "Nodes",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Indicator | Meaning | . | Green last-heard time | Node heard within the last 2 hours | . | Plain last-heard time | Node not heard for over 2 hours | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Favorite | Node you marked as a favorite. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Node roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Апісанне | . | CLIENT | Standard end-user node | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | CLIENT MUTE | Receives but doesn’t retransmit | . | CLIENT HIDDEN | Like Client Mute, plus hides from node list | . | ROUTER | Prioritizes message forwarding; stays awake to relay | . | ROUTER LATE | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | TRACKER | Optimized for position reporting at regular intervals | . | SENSOR | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK TRACKER | TAK position reporting only | . | LOST AND FOUND | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . 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 nodes. | 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 nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | Icon | Meaning | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Mismatch | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/nodes.html#node-list",
    
    "relUrl": "/be-rBY/user/nodes.html#node-list"
  },"3668": {
    "doc": "Nodes",
    "title": "Quick Actions",
    "content": "From the node list, you can: . | Tap a node to view its detail page | Touch & hold for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Прыбраць | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/nodes.html#quick-actions",
    
    "relUrl": "/be-rBY/user/nodes.html#quick-actions"
  },"3669": {
    "doc": "Nodes",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/be-rBY/user/nodes.html#sharing-a-contact"
  },"3670": {
    "doc": "Nodes",
    "title": "Filtering & sorting",
    "content": "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 . | Фільтраваць | Апісанне | . | Hide offline nodes | Show only nodes heard within the last 2 hours | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Include unknown | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Sort | Апісанне | . | Last heard | Most recently heard nodes first | . | A-Z | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/nodes.html#filtering--sorting",
    
    "relUrl": "/be-rBY/user/nodes.html#filtering--sorting"
  },"3671": {
    "doc": "Nodes",
    "title": "Nodes per hop",
    "content": "Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/be-rBY/user/nodes.html#nodes-per-hop"
  },"3672": {
    "doc": "Nodes",
    "title": "Node detail",
    "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Апошні раз пачуты | | . | Адлегласць | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | Meaning | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/nodes.html#node-detail",
    
    "relUrl": "/be-rBY/user/nodes.html#node-detail"
  },"3673": {
    "doc": "Nodes",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/be-rBY/user/nodes.html#when-no-nodes-appear"
  },"3674": {
    "doc": "Nodes",
    "title": "Related Topics",
    "content": ". | Node Metrics — detailed telemetry dashboards for each node | Messages & Channels — send a direct message to a node | Map & Waypoints — view node positions geographically | Local Mesh Discovery — traceroute and neighbor info for topology exploration | Signal Meter — understand what the signal bars mean | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/nodes.html#related-topics",
    
    "relUrl": "/be-rBY/user/nodes.html#related-topics"
  },"3675": {
    "doc": "Nodi",
    "title": "Nodi",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/nodes.html",
    
    "relUrl": "/it-rIT/user/nodes.html"
  },"3676": {
    "doc": "Nodi",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Indicator | Meaning | . | Green last-heard time | Node heard within the last 2 hours | . | Plain last-heard time | Node not heard for over 2 hours | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Favorite | Node you marked as a favorite. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Node roles . Nodes can be configured with different roles that affect their mesh behavior: . | Ruolo | Descrizione | . | Client | Standard end-user node | . | Base Client | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Nascosto | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensore | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Oggetti Smarriti | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . 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 nodes. | 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 nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | Icon | Meaning | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Mismatch | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/nodes.html#node-list",
    
    "relUrl": "/it-rIT/user/nodes.html#node-list"
  },"3677": {
    "doc": "Nodi",
    "title": "Quick Actions",
    "content": "From the node list, you can: . | Tap a node to view its detail page | Touch & hold for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Elimina | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/nodes.html#quick-actions",
    
    "relUrl": "/it-rIT/user/nodes.html#quick-actions"
  },"3678": {
    "doc": "Nodi",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/it-rIT/user/nodes.html#sharing-a-contact"
  },"3679": {
    "doc": "Nodi",
    "title": "Filtering & sorting",
    "content": "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 . | Filtro | Descrizione | . | Hide offline nodes | Show only nodes heard within the last 2 hours | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Include unknown | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Sort | Descrizione | . | Last heard | Most recently heard nodes first | . | A-Z | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/nodes.html#filtering--sorting",
    
    "relUrl": "/it-rIT/user/nodes.html#filtering--sorting"
  },"3680": {
    "doc": "Nodi",
    "title": "Nodes per hop",
    "content": "Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/it-rIT/user/nodes.html#nodes-per-hop"
  },"3681": {
    "doc": "Nodi",
    "title": "Node detail",
    "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Livello batteria | | . | Hop count | | . | Ricevuto più di recente | | . | Distanza | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | Meaning | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/nodes.html#node-detail",
    
    "relUrl": "/it-rIT/user/nodes.html#node-detail"
  },"3682": {
    "doc": "Nodi",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/it-rIT/user/nodes.html#when-no-nodes-appear"
  },"3683": {
    "doc": "Nodi",
    "title": "Related Topics",
    "content": ". | Node Metrics — detailed telemetry dashboards for each node | Messages & Channels — send a direct message to a node | Map & Waypoints — view node positions geographically | Local Mesh Discovery — traceroute and neighbor info for topology exploration | Signal Meter — understand what the signal bars mean | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/nodes.html#related-topics",
    
    "relUrl": "/it-rIT/user/nodes.html#related-topics"
  },"3684": {
    "doc": "Nodos",
    "title": "Nodos",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/es-rES/user/nodes.html",
    
    "relUrl": "/es-rES/user/nodes.html"
  },"3685": {
    "doc": "Nodos",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Indicator | Meaning | . | Green last-heard time | Node heard within the last 2 hours | . | Plain last-heard time | Node not heard for over 2 hours | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Favorite | Node you marked as a favorite. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Node roles . Nodes can be configured with different roles that affect their mesh behavior: . | Rol | Descripción | . | Cliente | Standard end-user node | . | Base cliente | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Cliente silenciado | Receives but doesn’t retransmit | . | Cliente oculto | Like Client Mute, plus hides from node list | . | 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 | . | Rastreador | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | Rastreador TAK | TAK position reporting only | . | Perdido y encontrado | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . 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 nodes. | 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 nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | Icon | Meaning | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Mismatch | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/es-rES/user/nodes.html#node-list",
    
    "relUrl": "/es-rES/user/nodes.html#node-list"
  },"3686": {
    "doc": "Nodos",
    "title": "Quick Actions",
    "content": "From the node list, you can: . | Tap a node to view its detail page | Touch & hold for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Quitar | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/es-rES/user/nodes.html#quick-actions",
    
    "relUrl": "/es-rES/user/nodes.html#quick-actions"
  },"3687": {
    "doc": "Nodos",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/es-rES/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/es-rES/user/nodes.html#sharing-a-contact"
  },"3688": {
    "doc": "Nodos",
    "title": "Filtering & sorting",
    "content": "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 . | Filtro | Descripción | . | Hide offline nodes | Show only nodes heard within the last 2 hours | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Include unknown | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Sort | Descripción | . | Last heard | Most recently heard nodes first | . | A-Z | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/nodes.html#filtering--sorting",
    
    "relUrl": "/es-rES/user/nodes.html#filtering--sorting"
  },"3689": {
    "doc": "Nodos",
    "title": "Nodes per hop",
    "content": "Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ",
    "url": "/Meshtastic-Android/main/es-rES/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/es-rES/user/nodes.html#nodes-per-hop"
  },"3690": {
    "doc": "Nodos",
    "title": "Node detail",
    "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Última escucha | | . | Distancia | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | Meaning | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/es-rES/user/nodes.html#node-detail",
    
    "relUrl": "/es-rES/user/nodes.html#node-detail"
  },"3691": {
    "doc": "Nodos",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/es-rES/user/nodes.html#when-no-nodes-appear"
  },"3692": {
    "doc": "Nodos",
    "title": "Related Topics",
    "content": ". | Node Metrics — detailed telemetry dashboards for each node | Messages & Channels — send a direct message to a node | Map & Waypoints — view node positions geographically | Local Mesh Discovery — traceroute and neighbor info for topology exploration | Signal Meter — understand what the signal bars mean | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/nodes.html#related-topics",
    
    "relUrl": "/es-rES/user/nodes.html#related-topics"
  },"3693": {
    "doc": "Nodes",
    "title": "Nodes",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/nodes.html",
    
    "relUrl": "/sl-rSI/user/nodes.html"
  },"3694": {
    "doc": "Nodes",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Indicator | Meaning | . | Green last-heard time | Node heard within the last 2 hours | . | Plain last-heard time | Node not heard for over 2 hours | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Favorite | Node you marked as a favorite. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Node roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Opis | . | Client | Standard end-user node | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost and Found | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . 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 nodes. | 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 nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | Icon | Meaning | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Mismatch | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/nodes.html#node-list",
    
    "relUrl": "/sl-rSI/user/nodes.html#node-list"
  },"3695": {
    "doc": "Nodes",
    "title": "Quick Actions",
    "content": "From the node list, you can: . | Tap a node to view its detail page | Touch & hold for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Odstrani | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/nodes.html#quick-actions",
    
    "relUrl": "/sl-rSI/user/nodes.html#quick-actions"
  },"3696": {
    "doc": "Nodes",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/sl-rSI/user/nodes.html#sharing-a-contact"
  },"3697": {
    "doc": "Nodes",
    "title": "Filtering & sorting",
    "content": "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 . | Filter | Opis | . | Hide offline nodes | Show only nodes heard within the last 2 hours | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Include unknown | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Sort | Opis | . | Last heard | Most recently heard nodes first | . | A-Z | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/nodes.html#filtering--sorting",
    
    "relUrl": "/sl-rSI/user/nodes.html#filtering--sorting"
  },"3698": {
    "doc": "Nodes",
    "title": "Nodes per hop",
    "content": "Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/sl-rSI/user/nodes.html#nodes-per-hop"
  },"3699": {
    "doc": "Nodes",
    "title": "Node detail",
    "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Nazadnje slišano | | . | Razdalja | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | Meaning | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/nodes.html#node-detail",
    
    "relUrl": "/sl-rSI/user/nodes.html#node-detail"
  },"3700": {
    "doc": "Nodes",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/sl-rSI/user/nodes.html#when-no-nodes-appear"
  },"3701": {
    "doc": "Nodes",
    "title": "Related Topics",
    "content": ". | Node Metrics — detailed telemetry dashboards for each node | Messages & Channels — send a direct message to a node | Map & Waypoints — view node positions geographically | Local Mesh Discovery — traceroute and neighbor info for topology exploration | Signal Meter — understand what the signal bars mean | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/nodes.html#related-topics",
    
    "relUrl": "/sl-rSI/user/nodes.html#related-topics"
  },"3702": {
    "doc": "Nodes",
    "title": "Nodes",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/nodes.html",
    
    "relUrl": "/no-rNO/user/nodes.html"
  },"3703": {
    "doc": "Nodes",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Indicator | Meaning | . | Green last-heard time | Node heard within the last 2 hours | . | Plain last-heard time | Node not heard for over 2 hours | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Favorite | Node you marked as a favorite. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Node roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Beskrivelse | . | Client | Standard end-user node | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost and Found | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . 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 nodes. | 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 nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | Icon | Meaning | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Mismatch | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/nodes.html#node-list",
    
    "relUrl": "/no-rNO/user/nodes.html#node-list"
  },"3704": {
    "doc": "Nodes",
    "title": "Quick Actions",
    "content": "From the node list, you can: . | Tap a node to view its detail page | Touch & hold for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Fjern | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/nodes.html#quick-actions",
    
    "relUrl": "/no-rNO/user/nodes.html#quick-actions"
  },"3705": {
    "doc": "Nodes",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/no-rNO/user/nodes.html#sharing-a-contact"
  },"3706": {
    "doc": "Nodes",
    "title": "Filtering & sorting",
    "content": "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 . | Filter | Beskrivelse | . | Hide offline nodes | Show only nodes heard within the last 2 hours | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Include unknown | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Sort | Beskrivelse | . | Last heard | Most recently heard nodes first | . | A-Z | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/nodes.html#filtering--sorting",
    
    "relUrl": "/no-rNO/user/nodes.html#filtering--sorting"
  },"3707": {
    "doc": "Nodes",
    "title": "Nodes per hop",
    "content": "Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/no-rNO/user/nodes.html#nodes-per-hop"
  },"3708": {
    "doc": "Nodes",
    "title": "Node detail",
    "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Sist hørt | | . | Distanse | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | Meaning | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/nodes.html#node-detail",
    
    "relUrl": "/no-rNO/user/nodes.html#node-detail"
  },"3709": {
    "doc": "Nodes",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/no-rNO/user/nodes.html#when-no-nodes-appear"
  },"3710": {
    "doc": "Nodes",
    "title": "Related Topics",
    "content": ". | Node Metrics — detailed telemetry dashboards for each node | Messages & Channels — send a direct message to a node | Map & Waypoints — view node positions geographically | Local Mesh Discovery — traceroute and neighbor info for topology exploration | Signal Meter — understand what the signal bars mean | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/nodes.html#related-topics",
    
    "relUrl": "/no-rNO/user/nodes.html#related-topics"
  },"3711": {
    "doc": "Csomópontok",
    "title": "Csomópontok",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/nodes.html",
    
    "relUrl": "/hu-rHU/user/nodes.html"
  },"3712": {
    "doc": "Csomópontok",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Indicator | Meaning | . | Green last-heard time | Node heard within the last 2 hours | . | Plain last-heard time | Node not heard for over 2 hours | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Favorite | Node you marked as a favorite. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Node roles . Nodes can be configured with different roles that affect their mesh behavior: . | Szerepkör | Leírás | . | Kliens | Standard end-user node | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Néma Kliens | Receives but doesn’t retransmit | . | Rejtett Kliens | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Késő Router | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Szenzor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Elveszett és Megkerült | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . 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 nodes. | 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 nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | Icon | Meaning | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Mismatch | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/nodes.html#node-list",
    
    "relUrl": "/hu-rHU/user/nodes.html#node-list"
  },"3713": {
    "doc": "Csomópontok",
    "title": "Quick Actions",
    "content": "From the node list, you can: . | Tap a node to view its detail page | Touch & hold for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Törlés | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/nodes.html#quick-actions",
    
    "relUrl": "/hu-rHU/user/nodes.html#quick-actions"
  },"3714": {
    "doc": "Csomópontok",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/hu-rHU/user/nodes.html#sharing-a-contact"
  },"3715": {
    "doc": "Csomópontok",
    "title": "Filtering & sorting",
    "content": "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 . | Filter | Leírás | . | Hide offline nodes | Show only nodes heard within the last 2 hours | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Include unknown | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Sort | Leírás | . | Last heard | Most recently heard nodes first | . | A-Z | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/nodes.html#filtering--sorting",
    
    "relUrl": "/hu-rHU/user/nodes.html#filtering--sorting"
  },"3716": {
    "doc": "Csomópontok",
    "title": "Nodes per hop",
    "content": "Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/hu-rHU/user/nodes.html#nodes-per-hop"
  },"3717": {
    "doc": "Csomópontok",
    "title": "Node detail",
    "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Utoljára hallott | | . | Távolság | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | Meaning | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/nodes.html#node-detail",
    
    "relUrl": "/hu-rHU/user/nodes.html#node-detail"
  },"3718": {
    "doc": "Csomópontok",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/hu-rHU/user/nodes.html#when-no-nodes-appear"
  },"3719": {
    "doc": "Csomópontok",
    "title": "Related Topics",
    "content": ". | Node Metrics — detailed telemetry dashboards for each node | Messages & Channels — send a direct message to a node | Map & Waypoints — view node positions geographically | Local Mesh Discovery — traceroute and neighbor info for topology exploration | Signal Meter — understand what the signal bars mean | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/nodes.html#related-topics",
    
    "relUrl": "/hu-rHU/user/nodes.html#related-topics"
  },"3720": {
    "doc": "Ноды",
    "title": "Ноды",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/nodes.html",
    
    "relUrl": "/ru-rRU/user/nodes.html"
  },"3721": {
    "doc": "Ноды",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Имя ноды — длинное имя, настроенное пользователем | Короткое имя — 4-символьный идентификатор | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Последнее услышанное — время с последнего общения | Расстояние — предполагаемое расстояние (если позиции общие) | Батарея — уровень заряда батареи удалённой ноды (если включена телеметрия) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Индикатор | Значение | . | Green last-heard time | Нода слышна за последние 2 часа | . | Plain last-heard time | Нода не отвечала больше 2 часов | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Избранный | Node you marked as a favorite. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Роли ноды . У нод можно настраивать разные роли, которые влияют на их поведение в сети: . | Роль | Описание | . | Client | Standard end-user node | . | Client Base | Обрабатывает трафик избранных нод как приоритет Router Late; весь остальной трафик как Client | . | Client Mute | Принимает, но не ретранслирует | . | Client Hidden | Как Client Mute, плюс скрыт из списка нод | . | Router | Ставит в приоритет пересылку сообщений; не засыпает чтобы передавать их | . | Router Late | Инфраструктурная нода, которая ретранслирует один раз, но только после всех остальных режимов (обеспечивает дополнительное покрытие) | . | Router Client | ⚠️ Устарело (удалено в прошивке 2.3.15) — больше не выбирается; используй вместо этого Router или Client | . | Repeater | ⚠️ Устарело (удалено в прошивке 2.7.11) — больше не выбирается; используй вместо этого Router | . | Tracker | Оптимизировано для передачи данных о местоположении через регулярные промежутки времени | . | Sensor | Оптимизировано для данных телеметрии | . | Тактический | Взаимодействует с системами TAK (отправляет/принимает CoT) | . | TAK Tracker | Только отчет о позиции TAK | . | Lost and Found | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . Choosing a role . Большинству пользователей стоит оставить роль Client по умолчанию. Рассмотри другую роль, когда: . | Router — У тебя есть узел в фиксированном, высоком месте с надежным источником питания (крыша, вершина холма). Router постоянно бодрствуют, чтобы пересылать сообщения для других, и они необходимы для расширения покрытия сети. Don’t use Router on battery-powered handheld nodes. | Router Late — инфраструктурная нода, которая всегда пересылает пакеты только один раз, но только после того, как все другие режимы маршрутизации выполнили свои ходы. Обеспечивает дополнительное покрытие для локальных кластеров, не конкурируя с основными роутерами. | Client Base — обрабатывает трафик от/к вашим избранным нодам с приоритетом Router Late (обеспечивая этим сообщениям дополнительное ретранслирование), а всё остальное обрабатывает как обычный Client. | Client Mute — хочешь принимать трафик сети, но не участвовать в его ретрансляции. Useful for monitoring-only nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Спит между передачами для экономии батареи. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Похожий профиль мощности на Tracker. | TAK / TAK Tracker — нужно только если работать с системами ATAK/WinTAK. Смотри Интеграция TAK для подробностей. | . 💡 Совет: Сеть работает лучше, когда большинство нод Client или Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. Хорошее практическое правило: один роутер на 5–10 клиентов в вашей зоне. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | Значок | Значение | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Несовпадение | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/nodes.html#node-list",
    
    "relUrl": "/ru-rRU/user/nodes.html#node-list"
  },"3722": {
    "doc": "Ноды",
    "title": "Быстрые действия",
    "content": "Из списка нод ты можешь: . | Нажмите на ноду, чтобы увидеть её страницу с деталями | Touch & hold for quick actions: . | Отметить/убрать из избранного | Отключить/включить уведомления | Отправить личное сообщение | Трассировка | Игнорировать/разблокировать | Удалить | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/nodes.html#%D0%B1%D1%8B%D1%81%D1%82%D1%80%D1%8B%D0%B5-%D0%B4%D0%B5%D0%B9%D1%81%D1%82%D0%B2%D0%B8%D1%8F",
    
    "relUrl": "/ru-rRU/user/nodes.html#быстрые-действия"
  },"3723": {
    "doc": "Ноды",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/ru-rRU/user/nodes.html#sharing-a-contact"
  },"3724": {
    "doc": "Ноды",
    "title": "Filtering & sorting",
    "content": "Text search . Введи в поле поиска, чтобы отфильтровать ноды по имени или короткому имени. Фильтр обновляется в реальном времени по мере набора текста. Filter toggles . | Фильтр | Описание | . | Hide offline nodes | Показывать только ноды, услышанные за последние 2 часа | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Включить неизвестные | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Исключить инфраструктуру | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Исключить MQTT | Скрыть ноды, слышимые только через интернет-мост MQTT | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Сортировка | Описание | . | Last heard | Сначала недавно слышимые ноды | . | A-Z | Сортировать по полному имени ноды | . | Расстояние | Сначала ближайшие ноды (требуется обмен позициями) | . | Меньше хопов | Сначала с наименьшим количеством ретрансляций | . | Канал | Группировать по индексу канала | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/nodes.html#filtering--sorting",
    
    "relUrl": "/ru-rRU/user/nodes.html#filtering--sorting"
  },"3725": {
    "doc": "Ноды",
    "title": "Nodes per hop",
    "content": "Нажми на значок гистограммы хопов в панели приложений списка нод, чтобы открыть столбчатую диаграмму того, сколько нод находится на каждом расстоянии хопа (0 = напрямую, 1 = через один ретранслятор и так далее). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. Это быстрый способ понять, насколько занята и разветвлена твоя местная сеть. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/ru-rRU/user/nodes.html#nodes-per-hop"
  },"3726": {
    "doc": "Ноды",
    "title": "Node detail",
    "content": "Нажатие на ноду открывает подробный вид с полной информацией. Смотри Метрики ноды для полной информации о метриках и телеметрии. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Встроенные индикаторы статуса показывают ключевые показатели с первого взгляда: . | Индикатор | Снимок экрана | . | Качество сигнала | | . | Уровень заряда батареи | | . | Количество хопов | | . | Последний раз слышен | | . | Расстояние | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | Значение | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . Когда оборудование ноды распознано, в детальном просмотре появляется сворачиваемый раздел “Хочу такой”, содержащий ссылки на места, где можно купить или узнать больше об этом устройстве: страницу продукта у производителя, варианты продукта и объявления на региональных торговых площадках (например, AliExpress, Amazon и у поддерживаемых продавцов), отфильтрованные по твоей стране. Каждая ссылка открывается через сервис перенаправления msh.to. Устройства без подходящих ссылок не показывают этот раздел. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/nodes.html#node-detail",
    
    "relUrl": "/ru-rRU/user/nodes.html#node-detail"
  },"3727": {
    "doc": "Ноды",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/ru-rRU/user/nodes.html#when-no-nodes-appear"
  },"3728": {
    "doc": "Ноды",
    "title": "Связанные темы",
    "content": ". | Метрики ноды — подробные телеметрические панели для каждой ноды | Сообщения и каналы — отправь личное сообщение ноде | Карта и путевые точки — просмот позиции нод на карте | Local Mesh Discovery — traceroute and neighbor info for topology exploration | Индикатор сигнала — пойми, что означают полоски сигнала | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/nodes.html#%D1%81%D0%B2%D1%8F%D0%B7%D0%B0%D0%BD%D0%BD%D1%8B%D0%B5-%D1%82%D0%B5%D0%BC%D1%8B",
    
    "relUrl": "/ru-rRU/user/nodes.html#связанные-темы"
  },"3729": {
    "doc": "Uzly",
    "title": "Uzly",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/nodes.html",
    
    "relUrl": "/cs-rCZ/user/nodes.html"
  },"3730": {
    "doc": "Uzly",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Indikátor | Význam | . | Zelený - čas posledního příjmu | Uzel byl slyšet během posledních 2 hodin | . | Běžný - čas posledního příjmu | Uzel nebyl slyšet déle než 2 hodiny | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Oblíbený | Uzel jste označili jako oblíbený. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Role uzlu . Uzlům lze nastavit různé role, které ovlivňují jejich chování v mesh síti: . | Role | Popis | . | Client | Standardní uzel pro koncové uživatele | . | Client Base | Provoz z oblíbených uzlů považuje za prioritu Router Late; veškerý ostatní provoz za Client | . | Client Mute | Přijímá, ale nepřeposílá | . | Client Hidden | Stejně jako Client Mute, navíc skryje uzel ze seznamu uzlů | . | Router | Upřednostňuje přeposílání zpráv a zůstává vzhůru, aby je mohl přeposílat | . | Router Late | Infrastrukturní uzel, který jednou přepošle paket, ale až po všech ostatních režimech (poskytuje doplňkové pokrytí) | . | Router Client | ⚠️ Zastaralé (odstraněno ve firmwaru 2.3.15) – již nelze vybrat; použijte místo něj Router nebo Client | . | Repeater | ⚠️ Zastaralé (odstraněno ve firmwaru 2.7.11) – již nelze vybrat; použijte místo něj Router | . | Tracker | Optimalizováno pro pravidelné odesílání polohy | . | Senzor | Optimalizováno pro hlášení telemetrie | . | TAK | Spolupracuje se systémy TAK (odesílá/přijímá CoT) | . | TAK Tracker | Pouze odesílání polohy TAK | . | Lost and Found | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . Choosing a role . Většina uživatelů by měla ponechat výchozí roli Client. Zvažte jinou roli, pokud: . | **Router **— Máte uzel na pevném, vyvýšeném místě se spolehlivým napájením (střecha, vrchol kopce). Routery zůstávají nepřetržitě aktivní, aby přeposílaly zprávy ostatních, a jsou klíčové pro rozšiřování pokrytí mesh sítě. Don’t use Router on battery-powered handheld nodes. | Router Late — Infrastrukturní uzel, který vždy jednou přepošle paket, ale až poté, co dostaly prostor všechny ostatní směrovací režimy. Poskytuje doplňkové pokrytí místním skupinám uzlů, aniž by konkuroval hlavním routerům. | Client Base — Zachází s provozem z/na vaše oblíbené uzly s prioritou Router Late (zajišťuje těmto zprávám dodatečné přeposílání), zatímco vše ostatní zpracovává jako běžný Client. | Client Mute — Chcete přijímat provoz mesh sítě, ale nechcete se podílet na jeho přeposílání. Useful for monitoring-only nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Podobná spotřeba energie jako Tracker. | TAK / TAK Tracker – Potřebujete pouze pro spolupráci se systémy ATAK/WinTAK. Podrobnosti viz TAK integrace. | . 💡 Tip: Mesh síť funguje nejlépe, když je většina uzlů v roli Client nebo Router. Příliš mnoho uzlů Client Mute snižuje odolnost mesh sítě; příliš mnoho routerů v hustě osídlené oblasti může způsobit zahlcení. Dobrým orientačním pravidlem je jeden Router na 5–10 uzlů Client ve vaší oblasti. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | Icon | Meaning | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Mismatch | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/nodes.html#node-list",
    
    "relUrl": "/cs-rCZ/user/nodes.html#node-list"
  },"3731": {
    "doc": "Uzly",
    "title": "Rychlé akce",
    "content": "From the node list, you can: . | Tap a node to view its detail page | Touch & hold for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Odstranit | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/nodes.html#rychl%C3%A9-akce",
    
    "relUrl": "/cs-rCZ/user/nodes.html#rychlé-akce"
  },"3732": {
    "doc": "Uzly",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/cs-rCZ/user/nodes.html#sharing-a-contact"
  },"3733": {
    "doc": "Uzly",
    "title": "Filtering & sorting",
    "content": "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 . | Filtr | Popis | . | Hide offline nodes | Show only nodes heard within the last 2 hours | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Include unknown | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Sort | Popis | . | Last heard | Most recently heard nodes first | . | A-Z | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/nodes.html#filtering--sorting",
    
    "relUrl": "/cs-rCZ/user/nodes.html#filtering--sorting"
  },"3734": {
    "doc": "Uzly",
    "title": "Nodes per hop",
    "content": "Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/cs-rCZ/user/nodes.html#nodes-per-hop"
  },"3735": {
    "doc": "Uzly",
    "title": "Node detail",
    "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Naposledy slyšen | | . | Vzdálenost | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | Význam | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/nodes.html#node-detail",
    
    "relUrl": "/cs-rCZ/user/nodes.html#node-detail"
  },"3736": {
    "doc": "Uzly",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/cs-rCZ/user/nodes.html#when-no-nodes-appear"
  },"3737": {
    "doc": "Uzly",
    "title": "Související témata",
    "content": ". | Node Metrics — detailed telemetry dashboards for each node | Messages & Channels — send a direct message to a node | Map & Waypoints — view node positions geographically | Local Mesh Discovery — traceroute and neighbor info for topology exploration | Signal Meter — understand what the signal bars mean | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/nodes.html#souvisej%C3%ADc%C3%AD-t%C3%A9mata",
    
    "relUrl": "/cs-rCZ/user/nodes.html#související-témata"
  },"3738": {
    "doc": "Възли",
    "title": "Възли",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/nodes.html",
    
    "relUrl": "/bg-rBG/user/nodes.html"
  },"3739": {
    "doc": "Възли",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Име на възела — зададено от потребителя дълго име | Кратко име — идентификатор от 4 знака | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Последно чут — време от последната комуникация | Разстояние — приблизително разстояние (ако се споделят местоположения) | Батерия — ниво на заряда на батерията на отдалечения възел (ако телеметрията е активирана) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Indicator | Meaning | . | Green last-heard time | Node heard within the last 2 hours | . | Plain last-heard time | Node not heard for over 2 hours | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Favorite | Node you marked as a favorite. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Node roles . Nodes can be configured with different roles that affect their mesh behavior: . | Роля | Описание | . | Клиент | Standard end-user node | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Скрит клиент | 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 | . | Загубено и намерено | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . 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 nodes. | 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 nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | Icon | Meaning | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Mismatch | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/nodes.html#node-list",
    
    "relUrl": "/bg-rBG/user/nodes.html#node-list"
  },"3740": {
    "doc": "Възли",
    "title": "Quick Actions",
    "content": "From the node list, you can: . | Tap a node to view its detail page | Touch & hold for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Изтрий | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/nodes.html#quick-actions",
    
    "relUrl": "/bg-rBG/user/nodes.html#quick-actions"
  },"3741": {
    "doc": "Възли",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/bg-rBG/user/nodes.html#sharing-a-contact"
  },"3742": {
    "doc": "Възли",
    "title": "Filtering & sorting",
    "content": "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 . | Филтър | Описание | . | Hide offline nodes | Show only nodes heard within the last 2 hours | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Include unknown | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Sort | Описание | . | Last heard | Most recently heard nodes first | . | A-Z | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/nodes.html#filtering--sorting",
    
    "relUrl": "/bg-rBG/user/nodes.html#filtering--sorting"
  },"3743": {
    "doc": "Възли",
    "title": "Nodes per hop",
    "content": "Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/bg-rBG/user/nodes.html#nodes-per-hop"
  },"3744": {
    "doc": "Възли",
    "title": "Node detail",
    "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Inline status indicators show key metrics at a glance: . | Indicator | Екранна снимка | . | Signal quality | | . | Ниво на батерията | | . | Hop count | | . | Последно чут | | . | Разстояние | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | Значение | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/nodes.html#node-detail",
    
    "relUrl": "/bg-rBG/user/nodes.html#node-detail"
  },"3745": {
    "doc": "Възли",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/bg-rBG/user/nodes.html#when-no-nodes-appear"
  },"3746": {
    "doc": "Възли",
    "title": "Related Topics",
    "content": ". | Node Metrics — detailed telemetry dashboards for each node | Messages & Channels — send a direct message to a node | Map & Waypoints — view node positions geographically | Local Mesh Discovery — traceroute and neighbor info for topology exploration | Signal Meter — understand what the signal bars mean | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/nodes.html#related-topics",
    
    "relUrl": "/bg-rBG/user/nodes.html#related-topics"
  },"3747": {
    "doc": "Nodes",
    "title": "Nodes",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/nodes.html",
    
    "relUrl": "/ga-rIE/user/nodes.html"
  },"3748": {
    "doc": "Nodes",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Indicator | Meaning | . | Green last-heard time | Node heard within the last 2 hours | . | Plain last-heard time | Node not heard for over 2 hours | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Favorite | Node you marked as a favorite. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Node roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Cur síos | . | Client | Standard end-user node | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost and Found | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . 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 nodes. | 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 nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | Icon | Meaning | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Mismatch | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/nodes.html#node-list",
    
    "relUrl": "/ga-rIE/user/nodes.html#node-list"
  },"3749": {
    "doc": "Nodes",
    "title": "Quick Actions",
    "content": "From the node list, you can: . | Tap a node to view its detail page | Touch & hold for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Bain | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/nodes.html#quick-actions",
    
    "relUrl": "/ga-rIE/user/nodes.html#quick-actions"
  },"3750": {
    "doc": "Nodes",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/ga-rIE/user/nodes.html#sharing-a-contact"
  },"3751": {
    "doc": "Nodes",
    "title": "Filtering & sorting",
    "content": "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 . | Scagaire | Cur síos | . | Hide offline nodes | Show only nodes heard within the last 2 hours | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Include unknown | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Sort | Cur síos | . | Last heard | Most recently heard nodes first | . | A-Z | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/nodes.html#filtering--sorting",
    
    "relUrl": "/ga-rIE/user/nodes.html#filtering--sorting"
  },"3752": {
    "doc": "Nodes",
    "title": "Nodes per hop",
    "content": "Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/ga-rIE/user/nodes.html#nodes-per-hop"
  },"3753": {
    "doc": "Nodes",
    "title": "Node detail",
    "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Deiridh chluinmhu | | . | Sáth | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | Meaning | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/nodes.html#node-detail",
    
    "relUrl": "/ga-rIE/user/nodes.html#node-detail"
  },"3754": {
    "doc": "Nodes",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/ga-rIE/user/nodes.html#when-no-nodes-appear"
  },"3755": {
    "doc": "Nodes",
    "title": "Related Topics",
    "content": ". | Node Metrics — detailed telemetry dashboards for each node | Messages & Channels — send a direct message to a node | Map & Waypoints — view node positions geographically | Local Mesh Discovery — traceroute and neighbor info for topology exploration | Signal Meter — understand what the signal bars mean | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/nodes.html#related-topics",
    
    "relUrl": "/ga-rIE/user/nodes.html#related-topics"
  },"3756": {
    "doc": "Nœuds",
    "title": "Nœuds",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/nodes.html",
    
    "relUrl": "/fr-rCA/user/nodes.html"
  },"3757": {
    "doc": "Nœuds",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Indicator | Meaning | . | Green last-heard time | Node heard within the last 2 hours | . | Plain last-heard time | Node not heard for over 2 hours | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Favorite | Node you marked as a favorite. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Node roles . Nodes can be configured with different roles that affect their mesh behavior: . | Rôle | Description | . | Client | Standard end-user node | . | Base Client | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client muet | Receives but doesn’t retransmit | . | Client masqué | Like Client Mute, plus hides from node list | . | Routeur | Prioritizes message forwarding; stays awake to relay | . | Routeur avec retard | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Traqueur | Optimized for position reporting at regular intervals | . | Capteur | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | Traqueur TAK | TAK position reporting only | . | Objets trouvés | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . 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 nodes. | 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 nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | Icon | Meaning | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Mismatch | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/nodes.html#node-list",
    
    "relUrl": "/fr-rCA/user/nodes.html#node-list"
  },"3758": {
    "doc": "Nœuds",
    "title": "Quick Actions",
    "content": "From the node list, you can: . | Tap a node to view its detail page | Touch & hold for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Supprimer | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/nodes.html#quick-actions",
    
    "relUrl": "/fr-rCA/user/nodes.html#quick-actions"
  },"3759": {
    "doc": "Nœuds",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/fr-rCA/user/nodes.html#sharing-a-contact"
  },"3760": {
    "doc": "Nœuds",
    "title": "Filtering & sorting",
    "content": "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 . | Filtre | Description | . | Hide offline nodes | Show only nodes heard within the last 2 hours | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Include unknown | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Sort | Description | . | Last heard | Most recently heard nodes first | . | A-Z | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/nodes.html#filtering--sorting",
    
    "relUrl": "/fr-rCA/user/nodes.html#filtering--sorting"
  },"3761": {
    "doc": "Nœuds",
    "title": "Nodes per hop",
    "content": "Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/fr-rCA/user/nodes.html#nodes-per-hop"
  },"3762": {
    "doc": "Nœuds",
    "title": "Node detail",
    "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Niveau de batterie | | . | Hop count | | . | Dernière écoute | | . | Distance | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | Meaning | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/nodes.html#node-detail",
    
    "relUrl": "/fr-rCA/user/nodes.html#node-detail"
  },"3763": {
    "doc": "Nœuds",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/fr-rCA/user/nodes.html#when-no-nodes-appear"
  },"3764": {
    "doc": "Nœuds",
    "title": "Related Topics",
    "content": ". | Node Metrics — detailed telemetry dashboards for each node | Messages & Channels — send a direct message to a node | Map & Waypoints — view node positions geographically | Local Mesh Discovery — traceroute and neighbor info for topology exploration | Signal Meter — understand what the signal bars mean | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/nodes.html#related-topics",
    
    "relUrl": "/fr-rCA/user/nodes.html#related-topics"
  },"3765": {
    "doc": "Чворови",
    "title": "Чворови",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/srp/user/nodes.html",
    
    "relUrl": "/srp/user/nodes.html"
  },"3766": {
    "doc": "Чворови",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Indicator | Meaning | . | Green last-heard time | Node heard within the last 2 hours | . | Plain last-heard time | Node not heard for over 2 hours | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Favorite | Node you marked as a favorite. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Node roles . Nodes can be configured with different roles that affect their mesh behavior: . | Улога | Опис | . | Клијент | Standard end-user node | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Клијент мутиран | Receives but doesn’t retransmit | . | Скривени клијент | Like Client Mute, plus hides from node list | . | Рутер | Prioritizes message forwarding; stays awake to relay | . | Рутер са кашњењем | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Трекер | Optimized for position reporting at regular intervals | . | Сензор | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | ТАК Трекер | TAK position reporting only | . | Изгубљено и нађено | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . 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 nodes. | 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 nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | Иконица | Meaning | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Mismatch | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/srp/user/nodes.html#node-list",
    
    "relUrl": "/srp/user/nodes.html#node-list"
  },"3767": {
    "doc": "Чворови",
    "title": "Quick Actions",
    "content": "From the node list, you can: . | Tap a node to view its detail page | Touch & hold for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Уклони | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/srp/user/nodes.html#quick-actions",
    
    "relUrl": "/srp/user/nodes.html#quick-actions"
  },"3768": {
    "doc": "Чворови",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/srp/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/srp/user/nodes.html#sharing-a-contact"
  },"3769": {
    "doc": "Чворови",
    "title": "Filtering & sorting",
    "content": "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 . | Филтер | Опис | . | Hide offline nodes | Show only nodes heard within the last 2 hours | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Include unknown | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Sort | Опис | . | Last heard | Most recently heard nodes first | . | A-Z | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/srp/user/nodes.html#filtering--sorting",
    
    "relUrl": "/srp/user/nodes.html#filtering--sorting"
  },"3770": {
    "doc": "Чворови",
    "title": "Nodes per hop",
    "content": "Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ",
    "url": "/Meshtastic-Android/main/srp/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/srp/user/nodes.html#nodes-per-hop"
  },"3771": {
    "doc": "Чворови",
    "title": "Node detail",
    "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Последње откривање | | . | Раздаљина | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | Meaning | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/srp/user/nodes.html#node-detail",
    
    "relUrl": "/srp/user/nodes.html#node-detail"
  },"3772": {
    "doc": "Чворови",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/srp/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/srp/user/nodes.html#when-no-nodes-appear"
  },"3773": {
    "doc": "Чворови",
    "title": "Related Topics",
    "content": ". | Node Metrics — detailed telemetry dashboards for each node | Messages & Channels — send a direct message to a node | Map & Waypoints — view node positions geographically | Local Mesh Discovery — traceroute and neighbor info for topology exploration | Signal Meter — understand what the signal bars mean | . ",
    "url": "/Meshtastic-Android/main/srp/user/nodes.html#related-topics",
    
    "relUrl": "/srp/user/nodes.html#related-topics"
  },"3774": {
    "doc": "Nodes",
    "title": "Nodes",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/nodes.html",
    
    "relUrl": "/ca-rES/user/nodes.html"
  },"3775": {
    "doc": "Nodes",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Indicator | Meaning | . | Green last-heard time | Node heard within the last 2 hours | . | Plain last-heard time | Node not heard for over 2 hours | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Favorite | Node you marked as a favorite. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Node roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Descripció | . | Client | Standard end-user node | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost and Found | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . 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 nodes. | 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 nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | Icon | Meaning | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Mismatch | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/nodes.html#node-list",
    
    "relUrl": "/ca-rES/user/nodes.html#node-list"
  },"3776": {
    "doc": "Nodes",
    "title": "Quick Actions",
    "content": "From the node list, you can: . | Tap a node to view its detail page | Touch & hold for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Eliminar | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/nodes.html#quick-actions",
    
    "relUrl": "/ca-rES/user/nodes.html#quick-actions"
  },"3777": {
    "doc": "Nodes",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/ca-rES/user/nodes.html#sharing-a-contact"
  },"3778": {
    "doc": "Nodes",
    "title": "Filtering & sorting",
    "content": "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 . | Filtre | Descripció | . | Hide offline nodes | Show only nodes heard within the last 2 hours | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Include unknown | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Sort | Descripció | . | Last heard | Most recently heard nodes first | . | A-Z | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/nodes.html#filtering--sorting",
    
    "relUrl": "/ca-rES/user/nodes.html#filtering--sorting"
  },"3779": {
    "doc": "Nodes",
    "title": "Nodes per hop",
    "content": "Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/ca-rES/user/nodes.html#nodes-per-hop"
  },"3780": {
    "doc": "Nodes",
    "title": "Node detail",
    "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Última notícia | | . | Distància | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | Meaning | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/nodes.html#node-detail",
    
    "relUrl": "/ca-rES/user/nodes.html#node-detail"
  },"3781": {
    "doc": "Nodes",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/ca-rES/user/nodes.html#when-no-nodes-appear"
  },"3782": {
    "doc": "Nodes",
    "title": "Related Topics",
    "content": ". | Node Metrics — detailed telemetry dashboards for each node | Messages & Channels — send a direct message to a node | Map & Waypoints — view node positions geographically | Local Mesh Discovery — traceroute and neighbor info for topology exploration | Signal Meter — understand what the signal bars mean | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/nodes.html#related-topics",
    
    "relUrl": "/ca-rES/user/nodes.html#related-topics"
  },"3783": {
    "doc": "노드",
    "title": "노드",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/nodes.html",
    
    "relUrl": "/ko-rKR/user/nodes.html"
  },"3784": {
    "doc": "노드",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Indicator | Meaning | . | Green last-heard time | Node heard within the last 2 hours | . | Plain last-heard time | Node not heard for over 2 hours | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Favorite | Node you marked as a favorite. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Node roles . Nodes can be configured with different roles that affect their mesh behavior: . | 역할 | 설명 | . | Client | Standard end-user node | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost and Found | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . 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 nodes. | 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 nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | Icon | Meaning | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Mismatch | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/nodes.html#node-list",
    
    "relUrl": "/ko-rKR/user/nodes.html#node-list"
  },"3785": {
    "doc": "노드",
    "title": "Quick Actions",
    "content": "From the node list, you can: . | Tap a node to view its detail page | Touch & hold for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | 지우기 | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/nodes.html#quick-actions",
    
    "relUrl": "/ko-rKR/user/nodes.html#quick-actions"
  },"3786": {
    "doc": "노드",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/ko-rKR/user/nodes.html#sharing-a-contact"
  },"3787": {
    "doc": "노드",
    "title": "Filtering & sorting",
    "content": "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 . | 필터 | 설명 | . | Hide offline nodes | Show only nodes heard within the last 2 hours | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Include unknown | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Sort | 설명 | . | Last heard | Most recently heard nodes first | . | A-Z | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/nodes.html#filtering--sorting",
    
    "relUrl": "/ko-rKR/user/nodes.html#filtering--sorting"
  },"3788": {
    "doc": "노드",
    "title": "Nodes per hop",
    "content": "Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/ko-rKR/user/nodes.html#nodes-per-hop"
  },"3789": {
    "doc": "노드",
    "title": "Node detail",
    "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | 최근 수신 | | . | 거리 | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | Meaning | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/nodes.html#node-detail",
    
    "relUrl": "/ko-rKR/user/nodes.html#node-detail"
  },"3790": {
    "doc": "노드",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/ko-rKR/user/nodes.html#when-no-nodes-appear"
  },"3791": {
    "doc": "노드",
    "title": "Related Topics",
    "content": ". | Node Metrics — detailed telemetry dashboards for each node | Messages & Channels — send a direct message to a node | Map & Waypoints — view node positions geographically | Local Mesh Discovery — traceroute and neighbor info for topology exploration | Signal Meter — understand what the signal bars mean | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/nodes.html#related-topics",
    
    "relUrl": "/ko-rKR/user/nodes.html#related-topics"
  },"3792": {
    "doc": "Noder",
    "title": "Noder",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/nodes.html",
    
    "relUrl": "/sv-rSE/user/nodes.html"
  },"3793": {
    "doc": "Noder",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Indicator | Meaning | . | Green last-heard time | Node heard within the last 2 hours | . | Plain last-heard time | Node not heard for over 2 hours | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Favorite | Node you marked as a favorite. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Node roles . Nodes can be configured with different roles that affect their mesh behavior: . | Roll | Beskrivning | . | Client | Standard end-user node | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Hittegods | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . 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 nodes. | 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 nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | Icon | Meaning | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Mismatch | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/nodes.html#node-list",
    
    "relUrl": "/sv-rSE/user/nodes.html#node-list"
  },"3794": {
    "doc": "Noder",
    "title": "Quick Actions",
    "content": "From the node list, you can: . | Tap a node to view its detail page | Touch & hold for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Ta bort | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/nodes.html#quick-actions",
    
    "relUrl": "/sv-rSE/user/nodes.html#quick-actions"
  },"3795": {
    "doc": "Noder",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/sv-rSE/user/nodes.html#sharing-a-contact"
  },"3796": {
    "doc": "Noder",
    "title": "Filtering & sorting",
    "content": "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 . | Filter | Beskrivning | . | Hide offline nodes | Show only nodes heard within the last 2 hours | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Include unknown | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Sort | Beskrivning | . | Last heard | Most recently heard nodes first | . | A-Z | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/nodes.html#filtering--sorting",
    
    "relUrl": "/sv-rSE/user/nodes.html#filtering--sorting"
  },"3797": {
    "doc": "Noder",
    "title": "Nodes per hop",
    "content": "Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/sv-rSE/user/nodes.html#nodes-per-hop"
  },"3798": {
    "doc": "Noder",
    "title": "Node detail",
    "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Batterinivå | | . | Hop count | | . | Senast hörd | | . | Avstånd | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | Meaning | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/nodes.html#node-detail",
    
    "relUrl": "/sv-rSE/user/nodes.html#node-detail"
  },"3799": {
    "doc": "Noder",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/sv-rSE/user/nodes.html#when-no-nodes-appear"
  },"3800": {
    "doc": "Noder",
    "title": "Related Topics",
    "content": ". | Node Metrics — detailed telemetry dashboards for each node | Messages & Channels — send a direct message to a node | Map & Waypoints — view node positions geographically | Local Mesh Discovery — traceroute and neighbor info for topology exploration | Signal Meter — understand what the signal bars mean | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/nodes.html#related-topics",
    
    "relUrl": "/sv-rSE/user/nodes.html#related-topics"
  },"3801": {
    "doc": "Nodes",
    "title": "Nodes",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/nodes.html",
    
    "relUrl": "/ht-rHT/user/nodes.html"
  },"3802": {
    "doc": "Nodes",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Indicator | Meaning | . | Green last-heard time | Node heard within the last 2 hours | . | Plain last-heard time | Node not heard for over 2 hours | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Favorite | Node you marked as a favorite. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Node roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Deskripsyon | . | Client | Standard end-user node | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost and Found | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . 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 nodes. | 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 nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | Icon | Meaning | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Mismatch | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/nodes.html#node-list",
    
    "relUrl": "/ht-rHT/user/nodes.html#node-list"
  },"3803": {
    "doc": "Nodes",
    "title": "Quick Actions",
    "content": "From the node list, you can: . | Tap a node to view its detail page | Touch & hold for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Retire | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/nodes.html#quick-actions",
    
    "relUrl": "/ht-rHT/user/nodes.html#quick-actions"
  },"3804": {
    "doc": "Nodes",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/ht-rHT/user/nodes.html#sharing-a-contact"
  },"3805": {
    "doc": "Nodes",
    "title": "Filtering & sorting",
    "content": "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 . | Filtre | Deskripsyon | . | Hide offline nodes | Show only nodes heard within the last 2 hours | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Include unknown | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Sort | Deskripsyon | . | Last heard | Most recently heard nodes first | . | A-Z | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/nodes.html#filtering--sorting",
    
    "relUrl": "/ht-rHT/user/nodes.html#filtering--sorting"
  },"3806": {
    "doc": "Nodes",
    "title": "Nodes per hop",
    "content": "Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/ht-rHT/user/nodes.html#nodes-per-hop"
  },"3807": {
    "doc": "Nodes",
    "title": "Node detail",
    "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Dènye fwa li tande | | . | Distans | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | Meaning | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/nodes.html#node-detail",
    
    "relUrl": "/ht-rHT/user/nodes.html#node-detail"
  },"3808": {
    "doc": "Nodes",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/ht-rHT/user/nodes.html#when-no-nodes-appear"
  },"3809": {
    "doc": "Nodes",
    "title": "Related Topics",
    "content": ". | Node Metrics — detailed telemetry dashboards for each node | Messages & Channels — send a direct message to a node | Map & Waypoints — view node positions geographically | Local Mesh Discovery — traceroute and neighbor info for topology exploration | Signal Meter — understand what the signal bars mean | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/nodes.html#related-topics",
    
    "relUrl": "/ht-rHT/user/nodes.html#related-topics"
  },"3810": {
    "doc": "Чворови",
    "title": "Чворови",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/nodes.html",
    
    "relUrl": "/sr-rLatn/user/nodes.html"
  },"3811": {
    "doc": "Чворови",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Indicator | Meaning | . | Green last-heard time | Node heard within the last 2 hours | . | Plain last-heard time | Node not heard for over 2 hours | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Favorite | Node you marked as a favorite. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Node roles . Nodes can be configured with different roles that affect their mesh behavior: . | Улога | Опис | . | Клијент | Standard end-user node | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Клијент мутиран | Receives but doesn’t retransmit | . | Скривени клијент | Like Client Mute, plus hides from node list | . | Рутер | Prioritizes message forwarding; stays awake to relay | . | Рутер са кашњењем | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Трекер | Optimized for position reporting at regular intervals | . | Сензор | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | ТАК Трекер | TAK position reporting only | . | Изгубљено и нађено | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . 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 nodes. | 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 nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | Иконица | Meaning | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Mismatch | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/nodes.html#node-list",
    
    "relUrl": "/sr-rLatn/user/nodes.html#node-list"
  },"3812": {
    "doc": "Чворови",
    "title": "Quick Actions",
    "content": "From the node list, you can: . | Tap a node to view its detail page | Touch & hold for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Уклони | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/nodes.html#quick-actions",
    
    "relUrl": "/sr-rLatn/user/nodes.html#quick-actions"
  },"3813": {
    "doc": "Чворови",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/sr-rLatn/user/nodes.html#sharing-a-contact"
  },"3814": {
    "doc": "Чворови",
    "title": "Filtering & sorting",
    "content": "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 . | Filter | Опис | . | Hide offline nodes | Show only nodes heard within the last 2 hours | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Include unknown | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Sort | Опис | . | Last heard | Most recently heard nodes first | . | A-Z | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/nodes.html#filtering--sorting",
    
    "relUrl": "/sr-rLatn/user/nodes.html#filtering--sorting"
  },"3815": {
    "doc": "Чворови",
    "title": "Nodes per hop",
    "content": "Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/sr-rLatn/user/nodes.html#nodes-per-hop"
  },"3816": {
    "doc": "Чворови",
    "title": "Node detail",
    "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Poslednji put viđeno | | . | Udaljenost | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | Meaning | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/nodes.html#node-detail",
    
    "relUrl": "/sr-rLatn/user/nodes.html#node-detail"
  },"3817": {
    "doc": "Чворови",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/sr-rLatn/user/nodes.html#when-no-nodes-appear"
  },"3818": {
    "doc": "Чворови",
    "title": "Related Topics",
    "content": ". | Node Metrics — detailed telemetry dashboards for each node | Messages & Channels — send a direct message to a node | Map & Waypoints — view node positions geographically | Local Mesh Discovery — traceroute and neighbor info for topology exploration | Signal Meter — understand what the signal bars mean | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/nodes.html#related-topics",
    
    "relUrl": "/sr-rLatn/user/nodes.html#related-topics"
  },"3819": {
    "doc": "Nodes",
    "title": "Nodes",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/nodes.html",
    
    "relUrl": "/nl-rNL/user/nodes.html"
  },"3820": {
    "doc": "Nodes",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Indicator | Meaning | . | Green last-heard time | Node heard within the last 2 hours | . | Plain last-heard time | Node not heard for over 2 hours | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Favorite | Node you marked as a favorite. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Node roles . Nodes can be configured with different roles that affect their mesh behavior: . | Functie | Beschrijving | . | Client | Standard end-user node | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost and Found | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . 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 nodes. | 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 nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | Icon | Meaning | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Mismatch | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/nodes.html#node-list",
    
    "relUrl": "/nl-rNL/user/nodes.html#node-list"
  },"3821": {
    "doc": "Nodes",
    "title": "Quick Actions",
    "content": "From the node list, you can: . | Tap a node to view its detail page | Touch & hold for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Verwijder | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/nodes.html#quick-actions",
    
    "relUrl": "/nl-rNL/user/nodes.html#quick-actions"
  },"3822": {
    "doc": "Nodes",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/nl-rNL/user/nodes.html#sharing-a-contact"
  },"3823": {
    "doc": "Nodes",
    "title": "Filtering & sorting",
    "content": "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 . | Filter | Beschrijving | . | Hide offline nodes | Show only nodes heard within the last 2 hours | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Include unknown | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Sort | Beschrijving | . | Last heard | Most recently heard nodes first | . | A-Z | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/nodes.html#filtering--sorting",
    
    "relUrl": "/nl-rNL/user/nodes.html#filtering--sorting"
  },"3824": {
    "doc": "Nodes",
    "title": "Nodes per hop",
    "content": "Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/nl-rNL/user/nodes.html#nodes-per-hop"
  },"3825": {
    "doc": "Nodes",
    "title": "Node detail",
    "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Laatst gehoord | | . | Afstand | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | Meaning | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/nodes.html#node-detail",
    
    "relUrl": "/nl-rNL/user/nodes.html#node-detail"
  },"3826": {
    "doc": "Nodes",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/nl-rNL/user/nodes.html#when-no-nodes-appear"
  },"3827": {
    "doc": "Nodes",
    "title": "Related Topics",
    "content": ". | Node Metrics — detailed telemetry dashboards for each node | Messages & Channels — send a direct message to a node | Map & Waypoints — view node positions geographically | Local Mesh Discovery — traceroute and neighbor info for topology exploration | Signal Meter — understand what the signal bars mean | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/nodes.html#related-topics",
    
    "relUrl": "/nl-rNL/user/nodes.html#related-topics"
  },"3828": {
    "doc": "Вузли",
    "title": "Вузли",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/nodes.html",
    
    "relUrl": "/uk-rUA/user/nodes.html"
  },"3829": {
    "doc": "Вузли",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Indicator | Meaning | . | Green last-heard time | Node heard within the last 2 hours | . | Plain last-heard time | Node not heard for over 2 hours | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Favorite | Node you marked as a favorite. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Node roles . Nodes can be configured with different roles that affect their mesh behavior: . | Роль | Опис | . | Клієнт | Standard end-user node | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Трекер | Optimized for position reporting at regular intervals | . | Датчик | Optimized for telemetry reporting | . | ТАК | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Loast and Found | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . 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 nodes. | 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 nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | Icon | Meaning | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Mismatch | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/nodes.html#node-list",
    
    "relUrl": "/uk-rUA/user/nodes.html#node-list"
  },"3830": {
    "doc": "Вузли",
    "title": "Quick Actions",
    "content": "From the node list, you can: . | Tap a node to view its detail page | Touch & hold for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Видалити | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/nodes.html#quick-actions",
    
    "relUrl": "/uk-rUA/user/nodes.html#quick-actions"
  },"3831": {
    "doc": "Вузли",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/uk-rUA/user/nodes.html#sharing-a-contact"
  },"3832": {
    "doc": "Вузли",
    "title": "Filtering & sorting",
    "content": "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 . | Фільтри | Опис | . | Hide offline nodes | Show only nodes heard within the last 2 hours | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Include unknown | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Sort | Опис | . | Last heard | Most recently heard nodes first | . | A-Z | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Стрибків | Fewest relay hops first | . | Channel | Grouped by channel index | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/nodes.html#filtering--sorting",
    
    "relUrl": "/uk-rUA/user/nodes.html#filtering--sorting"
  },"3833": {
    "doc": "Вузли",
    "title": "Nodes per hop",
    "content": "Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/uk-rUA/user/nodes.html#nodes-per-hop"
  },"3834": {
    "doc": "Вузли",
    "title": "Node detail",
    "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Рівень заряду батареї | | . | Hop count | | . | Востаннє в мережі | | . | Відстань | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | Meaning | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/nodes.html#node-detail",
    
    "relUrl": "/uk-rUA/user/nodes.html#node-detail"
  },"3835": {
    "doc": "Вузли",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/uk-rUA/user/nodes.html#when-no-nodes-appear"
  },"3836": {
    "doc": "Вузли",
    "title": "Related Topics",
    "content": ". | Node Metrics — detailed telemetry dashboards for each node | Messages & Channels — send a direct message to a node | Map & Waypoints — view node positions geographically | Local Mesh Discovery — traceroute and neighbor info for topology exploration | Signal Meter — understand what the signal bars mean | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/nodes.html#related-topics",
    
    "relUrl": "/uk-rUA/user/nodes.html#related-topics"
  },"3837": {
    "doc": "Laitteet",
    "title": "Laitteet",
    "content": "Radionäkymässä luetellaan kaikki mesh-verkossasi näkyvät radiot. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/nodes.html",
    
    "relUrl": "/fi-rFI/user/nodes.html"
  },"3838": {
    "doc": "Laitteet",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Radion nimi — käyttäjän määrittämä pitkä nimi | Lyhyt nimi — 4-merkkinen tunniste | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Viimeksi kuultu — aika viimeisimmästä yhteydestä | Etäisyys — arvioitu etäisyys (jos sijaintitiedot jaetaan) | Akku — etäradion akun varaustaso (jos telemetria on käytössä) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Ilmaisin | Tarkoitus | . | Green last-heard time | Radio kuultu viimeisen 2 tunnin aikana | . | Plain last-heard time | Radiosta ei ole kuultu yli 2 tuntiin | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Suosikki | Radio, jonka olet merkinnyt suosikiksi. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Radioiden roolit . Radioille voidaan määrittää erilaisia rooleja, jotka vaikuttavat niiden toimintaan verkossa: . | Rooli | Kuvaus | . | Client | Tavallinen käyttäjäradio | . | Client Base | Käsittelee suosikkiradioiden liikenteen Router Late -prioriteetilla, kaiken muun liikenteen Client -prioriteetilla | . | Client Mute | Vastaanottaa viestejä, mutta ei lähetä niitä edelleen | . | Client Hidden | Kuten Client Mute, mutta piilotetaan myös radioluettelosta | . | Router | Priorisoi viestien välittämistä; pysyy hereillä välittääkseen viestejä | . | Router Late | Infrastruktuuriradio, joka lähettää viestin uudelleen kerran, mutta vasta kaikkien muiden tilojen jälkeen (tarjoaa lisäpeittoa) | . | Router Client | ⚠️ Vanhentunut (poistettu laiteohjelmistossa 2.3.15) — ei enää valittavissa; käytä sen sijaan Router- tai Client-roolia | . | Repeater | ⚠️ Vanhentunut (poistettu laiteohjelmistossa 2.7.11) — ei enää valittavissa; käytä sen sijaan Router-roolia | . | Tracker | Optimoitu sijainnin raportointiin säännöllisin väliajoin | . | Sensor | Optimoitu telemetrian raportointiin | . | TAK | Yhteensopiva TAK-järjestelmien kanssa (lähettää ja vastaanottaa CoT-viestejä) | . | TAK Tracker | Vain TAK-sijainnin raportointi | . | Lost and Found | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . Choosing a role . Useimpien käyttäjien kannattaa käyttää oletusarvoista Client-roolia. Harkitse muuta roolia seuraavissa tilanteissa: . | Router — Sinulla on radio kiinteässä, korkealla sijaitsevassa paikassa, jossa on luotettava virransyöttö (katto, mäki). Routerit pysyvät jatkuvasti hereillä välittääkseen muiden viestejä ja ovat tärkeitä verkon peittoalueen laajentamisessa. Don’t use Router on battery-powered handheld nodes. | Router Late — Infrastruktuuriradio, joka lähettää paketit uudelleen kerran, mutta vasta kaikkien muiden reititystilojen jälkeen. Tarjoaa lisäpeittoa paikallisille ryhmille kilpailematta ensisijaisten Routerien kanssa. | Client Base — Käsittelee suosikkiradioihisi menevän tai niistä tulevan liikenteen Router Late -prioriteetilla (varmistaen näille viesteille ylimääräisen välityspeiton), samalla kun kaikki muu käsitellään tavallisen Client-roolin tavoin. | Client Mute — Voit vastaanottaa verkkoliikennettä, mutta et osallistu viestien välittämiseen. Useful for monitoring-only nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Nukkuu lähetysten välillä akun säästämiseksi. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Samanlainen virrankulutusprofiili kuin Tracker-roolissa. | TAK / TAK Tracker — Tarvitaan vain yhteensopivuuteen ATAK-/WinTAK-järjestelmien kanssa. Katso TAK-integraatio lisätietoja varten. | . 💡 Vinkki: Verkko toimii parhaiten, kun suurin osa radioista käyttää Client- tai Router-roolia. Liian suuri määrä Client Mute (mykistetty) -radioita heikentää mesh-verkon vikasietoisuutta. Liian useat Router -roolin radiot tiheällä alueella voivat aiheuttaa ruuhkaa. Hyvä nyrkkisääntö on yksi Router jokaista 5–10 Client-roolia kohden alueellasi. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | Kuvake | Merkitys | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Ei täsmää | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/nodes.html#node-list",
    
    "relUrl": "/fi-rFI/user/nodes.html#node-list"
  },"3839": {
    "doc": "Laitteet",
    "title": "Pikatoiminnot",
    "content": "Radioluettelosta voit: . | Napauttaa radiota avataksesi sen tietosivun | Kosketa ja pidä painettuna nähdäksesi pikatoiminnot: . | Merkitse tai poista suosikki | Mykistä tai poista mykistys ilmoituksista | Lähetä yksityisviesti | Reitinselvitys | Ohita tai poista ohitus | Poista | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/nodes.html#pikatoiminnot",
    
    "relUrl": "/fi-rFI/user/nodes.html#pikatoiminnot"
  },"3840": {
    "doc": "Laitteet",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/fi-rFI/user/nodes.html#sharing-a-contact"
  },"3841": {
    "doc": "Laitteet",
    "title": "Filtering & sorting",
    "content": "Text search . Kirjoita hakukenttään suodattaaksesi radioita nimen tai lyhyen nimen perusteella. Suodatus päivittyy reaaliajassa kirjoittaessasi. Filter toggles . | Suodatus | Kuvaus | . | Hide offline nodes | Näytä vain radiot, joista on kuultu viimeisten 2 tunnin aikana | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Näytä tuntemattomat | Näytä radiot, jotka eivät ole vielä lähettäneet käyttäjätietoja. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Ohita infrastruktuurilaitteet | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Rajaa MQTT pois | Piilottaa radiot, joista on kuultu vain MQTT-internetsillan kautta | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Lajittelu | Kuvaus | . | Last heard | Näytä viimeksi kuullut radiot ensin | . | A-Z | Lajiteltu radion pitkän nimen mukaan | . | Etäisyys | Lähimpänä olevat radiot ensin (edellyttää sijainnin jakamista) | . | Hyppyjä | Vähiten välityshyppyjä vaativat radiot ensin | . | Kanava | Ryhmitelty kanavaindeksin mukaan | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/nodes.html#filtering--sorting",
    
    "relUrl": "/fi-rFI/user/nodes.html#filtering--sorting"
  },"3842": {
    "doc": "Laitteet",
    "title": "Nodes per hop",
    "content": "Avaa pylväskaavio, joka näyttää radioiden määrän kullakin hyppyetäisyydellä, napauttamalla radioluettelon sovelluspalkissa olevaa hyppyhistogrammikuvaketta (0 = suora yhteys, 1 = yksi välityshyppy ja niin edelleen). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. Tämä on nopea tapa arvioida, kuinka laaja ja kuormittunut paikallinen mesh-verkkosi on. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/fi-rFI/user/nodes.html#nodes-per-hop"
  },"3843": {
    "doc": "Laitteet",
    "title": "Node detail",
    "content": "Radion napauttaminen avaa tietonäkymän, jossa on kattavat tiedot. Katso Radion mittarit saadaksesi täydelliset tiedot mittareista ja telemetriasta. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Rivinsisäiset tilailmaisimet näyttävät tärkeimmät tiedot yhdellä silmäyksellä: . | Ilmaisin | Kuvakaappaus | . | Signaalin laatu | | . | Akun varaus | | . | Hyppymäärä | | . | Viimeksi kuultu | | . | Etäisyys | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | Merkitys | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . Kun radion laitteisto tunnistetaan, tietonäkymä näyttää avattavan “Haluan sellaisen” -osion, jossa on linkkejä laitteen ostamiseen tai lisätietojen hankkimiseen: valmistajan tuotesivu, tuoteversiot sekä alueelliset kauppapaikkalistaukset (esim. AliExpress, Amazon ja tuetut jälleenmyyjät), suodatettuna maasi mukaan. Jokainen linkki avautuu mesh.to -uudelleenohjauspalvelun kautta. Laitteet, joille ei löydy vastaavia linkkejä, eivät näytä tätä osiota. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/nodes.html#node-detail",
    
    "relUrl": "/fi-rFI/user/nodes.html#node-detail"
  },"3844": {
    "doc": "Laitteet",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/fi-rFI/user/nodes.html#when-no-nodes-appear"
  },"3845": {
    "doc": "Laitteet",
    "title": "Aiheeseen liittyvät aiheet",
    "content": ". | Radion mittarit — yksityiskohtaiset telemetriakoontinäytöt jokaiselle radiolle | Viestit ja kanavat — lähetä yksityisviesti radiolle | Kartta ja reittipisteet — tarkastele radioiden sijainteja kartalla | Paikallinen mesh-verkon etsintä — reitiselvitys ja naapuritiedot verkon rakenteen hahmottamiseen | Signaalimittari — ymmärrä, mitä signaalipalkit tarkoittavat | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/nodes.html#aiheeseen-liittyv%C3%A4t-aiheet",
    
    "relUrl": "/fi-rFI/user/nodes.html#aiheeseen-liittyvät-aiheet"
  },"3846": {
    "doc": "Nodes",
    "title": "Nodes",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/nodes.html",
    
    "relUrl": "/is-rIS/user/nodes.html"
  },"3847": {
    "doc": "Nodes",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Indicator | Meaning | . | Green last-heard time | Node heard within the last 2 hours | . | Plain last-heard time | Node not heard for over 2 hours | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Favorite | Node you marked as a favorite. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Node roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Lýsing | . | Client | Standard end-user node | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost and Found | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . 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 nodes. | 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 nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | Icon | Meaning | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Mismatch | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/nodes.html#node-list",
    
    "relUrl": "/is-rIS/user/nodes.html#node-list"
  },"3848": {
    "doc": "Nodes",
    "title": "Quick Actions",
    "content": "From the node list, you can: . | Tap a node to view its detail page | Touch & hold for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/nodes.html#quick-actions",
    
    "relUrl": "/is-rIS/user/nodes.html#quick-actions"
  },"3849": {
    "doc": "Nodes",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/is-rIS/user/nodes.html#sharing-a-contact"
  },"3850": {
    "doc": "Nodes",
    "title": "Filtering & sorting",
    "content": "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 . | Filter | Lýsing | . | Hide offline nodes | Show only nodes heard within the last 2 hours | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Include unknown | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Sort | Lýsing | . | Last heard | Most recently heard nodes first | . | A-Z | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/nodes.html#filtering--sorting",
    
    "relUrl": "/is-rIS/user/nodes.html#filtering--sorting"
  },"3851": {
    "doc": "Nodes",
    "title": "Nodes per hop",
    "content": "Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/is-rIS/user/nodes.html#nodes-per-hop"
  },"3852": {
    "doc": "Nodes",
    "title": "Node detail",
    "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Last heard | | . | Distance | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | Meaning | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/nodes.html#node-detail",
    
    "relUrl": "/is-rIS/user/nodes.html#node-detail"
  },"3853": {
    "doc": "Nodes",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/is-rIS/user/nodes.html#when-no-nodes-appear"
  },"3854": {
    "doc": "Nodes",
    "title": "Related Topics",
    "content": ". | Node Metrics — detailed telemetry dashboards for each node | Messages & Channels — send a direct message to a node | Map & Waypoints — view node positions geographically | Local Mesh Discovery — traceroute and neighbor info for topology exploration | Signal Meter — understand what the signal bars mean | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/nodes.html#related-topics",
    
    "relUrl": "/is-rIS/user/nodes.html#related-topics"
  },"3855": {
    "doc": "Nodes",
    "title": "Nodes",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/nodes.html",
    
    "relUrl": "/lt-rLT/user/nodes.html"
  },"3856": {
    "doc": "Nodes",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Indicator | Meaning | . | Green last-heard time | Node heard within the last 2 hours | . | Plain last-heard time | Node not heard for over 2 hours | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Favorite | Node you marked as a favorite. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Node roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Aprašymas | . | Client | Standard end-user node | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost and Found | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . 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 nodes. | 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 nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | Icon | Meaning | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Mismatch | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/nodes.html#node-list",
    
    "relUrl": "/lt-rLT/user/nodes.html#node-list"
  },"3857": {
    "doc": "Nodes",
    "title": "Quick Actions",
    "content": "From the node list, you can: . | Tap a node to view its detail page | Touch & hold for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Pašalinti | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/nodes.html#quick-actions",
    
    "relUrl": "/lt-rLT/user/nodes.html#quick-actions"
  },"3858": {
    "doc": "Nodes",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/lt-rLT/user/nodes.html#sharing-a-contact"
  },"3859": {
    "doc": "Nodes",
    "title": "Filtering & sorting",
    "content": "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 . | Filtras | Aprašymas | . | Hide offline nodes | Show only nodes heard within the last 2 hours | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Include unknown | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Sort | Aprašymas | . | Last heard | Most recently heard nodes first | . | A-Z | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/nodes.html#filtering--sorting",
    
    "relUrl": "/lt-rLT/user/nodes.html#filtering--sorting"
  },"3860": {
    "doc": "Nodes",
    "title": "Nodes per hop",
    "content": "Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/lt-rLT/user/nodes.html#nodes-per-hop"
  },"3861": {
    "doc": "Nodes",
    "title": "Node detail",
    "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Seniausiai girdėtas | | . | Atstumas | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | Meaning | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/nodes.html#node-detail",
    
    "relUrl": "/lt-rLT/user/nodes.html#node-detail"
  },"3862": {
    "doc": "Nodes",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/lt-rLT/user/nodes.html#when-no-nodes-appear"
  },"3863": {
    "doc": "Nodes",
    "title": "Related Topics",
    "content": ". | Node Metrics — detailed telemetry dashboards for each node | Messages & Channels — send a direct message to a node | Map & Waypoints — view node positions geographically | Local Mesh Discovery — traceroute and neighbor info for topology exploration | Signal Meter — understand what the signal bars mean | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/nodes.html#related-topics",
    
    "relUrl": "/lt-rLT/user/nodes.html#related-topics"
  },"3864": {
    "doc": "Nodes",
    "title": "Nodes",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/nodes.html",
    
    "relUrl": "/gl-rES/user/nodes.html"
  },"3865": {
    "doc": "Nodes",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Indicator | Meaning | . | Green last-heard time | Node heard within the last 2 hours | . | Plain last-heard time | Node not heard for over 2 hours | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Favorite | Node you marked as a favorite. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Node roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Descrición | . | Cliente | Standard end-user node | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost and Found | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . 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 nodes. | 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 nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | Icon | Meaning | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Mismatch | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/nodes.html#node-list",
    
    "relUrl": "/gl-rES/user/nodes.html#node-list"
  },"3866": {
    "doc": "Nodes",
    "title": "Quick Actions",
    "content": "From the node list, you can: . | Tap a node to view its detail page | Touch & hold for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Eliminar | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/nodes.html#quick-actions",
    
    "relUrl": "/gl-rES/user/nodes.html#quick-actions"
  },"3867": {
    "doc": "Nodes",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/gl-rES/user/nodes.html#sharing-a-contact"
  },"3868": {
    "doc": "Nodes",
    "title": "Filtering & sorting",
    "content": "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 . | Filtro | Descrición | . | Hide offline nodes | Show only nodes heard within the last 2 hours | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Include unknown | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Sort | Descrición | . | Last heard | Most recently heard nodes first | . | A-Z | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/nodes.html#filtering--sorting",
    
    "relUrl": "/gl-rES/user/nodes.html#filtering--sorting"
  },"3869": {
    "doc": "Nodes",
    "title": "Nodes per hop",
    "content": "Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/gl-rES/user/nodes.html#nodes-per-hop"
  },"3870": {
    "doc": "Nodes",
    "title": "Node detail",
    "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Última escoita | | . | Distancia | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | Meaning | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/nodes.html#node-detail",
    
    "relUrl": "/gl-rES/user/nodes.html#node-detail"
  },"3871": {
    "doc": "Nodes",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/gl-rES/user/nodes.html#when-no-nodes-appear"
  },"3872": {
    "doc": "Nodes",
    "title": "Related Topics",
    "content": ". | Node Metrics — detailed telemetry dashboards for each node | Messages & Channels — send a direct message to a node | Map & Waypoints — view node positions geographically | Local Mesh Discovery — traceroute and neighbor info for topology exploration | Signal Meter — understand what the signal bars mean | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/nodes.html#related-topics",
    
    "relUrl": "/gl-rES/user/nodes.html#related-topics"
  },"3873": {
    "doc": "ノード",
    "title": "ノード",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/nodes.html",
    
    "relUrl": "/ja-rJP/user/nodes.html"
  },"3874": {
    "doc": "ノード",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | ノード名： ユーザーが設定した正式名称 | 短縮名： 4 文字の識別子 | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | 最後の通信： 最後に通信してからの経過時間 | 距離： 推定距離（位置情報が共有されている場合） | バッテリー： リモートノードのバッテリー残量（テレメトリが有効な場合） | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | 指標 | 意味 | . | Green last-heard time | 過去 2 時間以内に受信したノード | . | Plain last-heard time | 2 時間を超えて受信していないノード | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ お気に入り | Node you marked as a favorite. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Node roles . ノードには、メッシュ上での動作に影響するさまざまな役割を設定できます： . | 役割 | 説明 | . | クライアント | Standard end-user node | . | クライアント・ベース | お気に入りノードの通信をルーター・レイトの優先度で扱い、それ以外の通信はクライアントとして扱います | . | クライアント・ミュート | 受信しますが、再送信はしません | . | クライアント・非表示 | クライアント・ミュートと同様で、さらにノードリストから隠れます | . | ルーター | メッセージの転送を優先し、中継のために起動し続けます | . | ルーター・レイト | 1 回だけ再送信するインフラノードですが、他のすべてのモードの後にのみ行います（補助的なカバレッジを提供します） | . | ルーター・クライアント | ⚠️ 非推奨（ファームウェア 2.3.15 で削除）。選択できなくなりました。代わりにルーターまたはクライアントを使用してください | . | リピーター | ⚠️ 非推奨（ファームウェア 2.7.11 で削除）。選択できなくなりました。代わりにルーターを使用してください | . | トラッカー | 一定間隔での位置報告に最適化されています | . | センサー | テレメトリ報告に最適化されています | . | TAK | TAK システムと相互運用します（CoT を送受信） | . | TAK Tracker | TAK の位置報告のみ | . | 紛失モード | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . Choosing a role . ほとんどのユーザーは、デフォルトのクライアント役割のままにしてください。次のような場合は、別の役割を検討してください： . | ルーター： 電源が安定した、固定された高所（屋上、丘の上など）にノードを設置している場合。ルーターは他のノードのメッセージを中継するために常に起動し続け、メッシュのカバレッジ拡大に不可欠です。 Don’t use Router on battery-powered handheld nodes. | ルーター・レイト： パケットを常に 1 回だけ再送信するインフラノードですが、他のすべてのルーティングモードの番が終わった後にのみ行います。主要なルーターと競合することなく、ローカルのクラスターに補助的なカバレッジを提供します。 | クライアント・ベース： お気に入りノードとの間の通信をルーター・レイトの優先度で扱い（それらのメッセージが追加の中継カバレッジを得られるようにします）、それ以外はすべて通常のクライアントとして処理します。 | クライアント・ミュート： メッシュの通信を受信したいが、中継には貢献したくない場合。 Useful for monitoring-only nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). 発信の合間はスリープしてバッテリーを節約します。 | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). 電力プロファイルはトラッカーと同様です。 | TAK／TAK Tracker： ATAK／WinTAK システムと相互運用する場合にのみ必要です。詳しくは TAK 連携 を参照してください。 | . 💡 ヒント： メッシュは、ほとんどのノードがクライアントまたはルーターのときに最も良く機能します。 Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. 目安としては、地域内のクライアント 5〜10 台につきルーター 1 台です。 . Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | アイコン | 意味 | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ 不一致 | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/nodes.html#node-list",
    
    "relUrl": "/ja-rJP/user/nodes.html#node-list"
  },"3875": {
    "doc": "ノード",
    "title": "クイック操作",
    "content": "ノードリストから、次のことができます： . | ノードをタップすると詳細ページを表示します | Touch & hold for quick actions: . | お気に入りに追加／解除 | 通知のミュート／解除 | ダイレクトメッセージを送信 | 経路をトレース | 無視／無視の解除 | 削除 | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/nodes.html#%E3%82%AF%E3%82%A4%E3%83%83%E3%82%AF%E6%93%8D%E4%BD%9C",
    
    "relUrl": "/ja-rJP/user/nodes.html#クイック操作"
  },"3876": {
    "doc": "ノード",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/ja-rJP/user/nodes.html#sharing-a-contact"
  },"3877": {
    "doc": "ノード",
    "title": "Filtering & sorting",
    "content": "Text search . 検索欄に入力すると、名前または短縮名でノードを絞り込めます。絞り込みは、入力に応じてリアルタイムで更新されます。 . Filter toggles . | 絞り込み | 説明 | . | Hide offline nodes | 過去 2 時間以内に受信したノードのみを表示します | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | 不明なノードを含む | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | インフラを除外 | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | MQTT を除外 | MQTT のインターネットブリッジ経由でのみ受信したノードを非表示にします | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | 並べ替え | 説明 | . | Last heard | 最近受信したノードを先頭に表示します | . | A-Z | ノードの正式名称で並べ替えます | . | 距離 | 近いノードを先頭に表示します（位置情報の共有が必要） | . | ホップ数 | 中継ホップ数が少ないノードを先頭に表示します | . | チャンネル | チャンネルインデックスごとにグループ化します | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/nodes.html#filtering--sorting",
    
    "relUrl": "/ja-rJP/user/nodes.html#filtering--sorting"
  },"3878": {
    "doc": "ノード",
    "title": "Nodes per hop",
    "content": "ノードリストのアプリバーにあるホップヒストグラムのアイコンをタップすると、各ホップ距離にいくつのノードがあるかを示す棒グラフが開きます（0 = 直接、1 = 中継 1 回、以下同様）。 Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. ローカルメッシュがどれだけ混雑し、どれだけ広がっているかを手早く把握できます。 . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/ja-rJP/user/nodes.html#nodes-per-hop"
  },"3879": {
    "doc": "ノード",
    "title": "Node detail",
    "content": "ノードをタップすると、詳しい情報を含む詳細ビューが開きます。メトリクスとテレメトリの詳細については、ノードメトリクス を参照してください。 . Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . インラインのステータス表示で、主要なメトリクスをひと目で確認できます： . | 指標 | スクリーンショット | . | 信号品質 | | . | バッテリー残量 | | . | ホップ数 | | . | 最後の通信 | | . | 距離 | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | 意味 | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . ノードのハードウェアが認識されると、詳細ビューに折りたたみ式の**「購入はこちら」**セクションが表示され、そのデバイスを購入したり詳しく知ったりできる場所（ベンダーの製品ページ、製品バリエーション、AliExpress・Amazon・対応小売店などの地域のマーケットプレイスの掲載）が、あなたの国に合わせて絞り込まれて表示されます。各リンクは msh.to のリダイレクトサービスを通じて開きます。一致するリンクがないデバイスでは、このセクションは表示されません。 . A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/nodes.html#node-detail",
    
    "relUrl": "/ja-rJP/user/nodes.html#node-detail"
  },"3880": {
    "doc": "ノード",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/ja-rJP/user/nodes.html#when-no-nodes-appear"
  },"3881": {
    "doc": "ノード",
    "title": "関連トピック",
    "content": ". | ノードメトリクス：各ノードの詳細なテレメトリダッシュボード | メッセージとチャンネル：ノードにダイレクトメッセージを送信 | マップとウェイポイント：ノードの位置を地図上で確認 | Local Mesh Discovery — traceroute and neighbor info for topology exploration | 信号メーター：信号バーの意味を理解する | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/nodes.html#%E9%96%A2%E9%80%A3%E3%83%88%E3%83%94%E3%83%83%E3%82%AF",
    
    "relUrl": "/ja-rJP/user/nodes.html#関連トピック"
  },"3882": {
    "doc": "Knoten",
    "title": "Knoten",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/nodes.html",
    
    "relUrl": "/de-rDE/user/nodes.html"
  },"3883": {
    "doc": "Knoten",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Indicator | Meaning | . | Green last-heard time | Node heard within the last 2 hours | . | Plain last-heard time | Node not heard for over 2 hours | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Favorite | Node you marked as a favorite. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Node roles . Nodes can be configured with different roles that affect their mesh behavior: . | Rolle | Beschreibung | . | Client | Standard end-user node | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client - Versteckt | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router mit Verzögerung | 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 | . | Tracker | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . 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 nodes. | 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 — Behandelt Datenverkehr von/zu Ihren bevorzugten Knoten mit der Priorität „Router Late“ (wodurch sichergestellt wird, dass diese Nachrichten eine zusätzliche Relaisabdeckung erhalten), während der übrige Verkehr wie bei einem normalen Client gehandhabt wird. | Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | Symbol | Meaning | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Mismatch | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/nodes.html#node-list",
    
    "relUrl": "/de-rDE/user/nodes.html#node-list"
  },"3884": {
    "doc": "Knoten",
    "title": "Quick Actions",
    "content": "From the node list, you can: . | Tap a node to view its detail page | Touch & hold for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Entfernen | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/nodes.html#quick-actions",
    
    "relUrl": "/de-rDE/user/nodes.html#quick-actions"
  },"3885": {
    "doc": "Knoten",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/de-rDE/user/nodes.html#sharing-a-contact"
  },"3886": {
    "doc": "Knoten",
    "title": "Filtering & sorting",
    "content": "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 . | Filter | Beschreibung | . | Hide offline nodes | Show only nodes heard within the last 2 hours | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Include unknown | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Sortieren | Beschreibung | . | Last heard | Most recently heard nodes first | . | A-Z | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/nodes.html#filtering--sorting",
    
    "relUrl": "/de-rDE/user/nodes.html#filtering--sorting"
  },"3887": {
    "doc": "Knoten",
    "title": "Nodes per hop",
    "content": "Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/de-rDE/user/nodes.html#nodes-per-hop"
  },"3888": {
    "doc": "Knoten",
    "title": "Node detail",
    "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Inline status indicators show key metrics at a glance: . | Indicator | Bildschirmfoto | . | Signal quality | | . | Akkustand | | . | Hop count | | . | Zuletzt gehört | | . | Distanz | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | Bedeutung | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . Sobald die Hardware eines Knotens erkannt wird, zeigt die Detailansicht einen ausklappbaren Bereich mit der Bezeichnung „Ich möchte eins“ an. Dieser enthält Links zu Bezugsquellen oder weiterführenden Informationen zu dem jeweiligen Gerät – etwa zur Produktseite des Herstellers, zu Produktvarianten sowie zu Angeboten auf regionalen Marktplätzen (wie AliExpress, Amazon und unterstützten Händlern), gefiltert nach Ihrem Land. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/nodes.html#node-detail",
    
    "relUrl": "/de-rDE/user/nodes.html#node-detail"
  },"3889": {
    "doc": "Knoten",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/de-rDE/user/nodes.html#when-no-nodes-appear"
  },"3890": {
    "doc": "Knoten",
    "title": "Related Topics",
    "content": ". | Node Metrics — detailed telemetry dashboards for each node | Messages & Channels — send a direct message to a node | Map & Waypoints — view node positions geographically | Local Mesh Discovery — traceroute and neighbor info for topology exploration | Signal Meter — understand what the signal bars mean | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/nodes.html#related-topics",
    
    "relUrl": "/de-rDE/user/nodes.html#related-topics"
  },"3891": {
    "doc": "Nodes",
    "title": "Nodes",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/nodes.html",
    
    "relUrl": "/ar-rSA/user/nodes.html"
  },"3892": {
    "doc": "Nodes",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Indicator | Meaning | . | Green last-heard time | Node heard within the last 2 hours | . | Plain last-heard time | Node not heard for over 2 hours | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Favorite | Node you marked as a favorite. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Node roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | الوصف | . | Client | Standard end-user node | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost and Found | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . 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 nodes. | 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 nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | Icon | Meaning | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Mismatch | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/nodes.html#node-list",
    
    "relUrl": "/ar-rSA/user/nodes.html#node-list"
  },"3893": {
    "doc": "Nodes",
    "title": "Quick Actions",
    "content": "From the node list, you can: . | Tap a node to view its detail page | Touch & hold for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/nodes.html#quick-actions",
    
    "relUrl": "/ar-rSA/user/nodes.html#quick-actions"
  },"3894": {
    "doc": "Nodes",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/ar-rSA/user/nodes.html#sharing-a-contact"
  },"3895": {
    "doc": "Nodes",
    "title": "Filtering & sorting",
    "content": "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 . | عربي | الوصف | . | Hide offline nodes | Show only nodes heard within the last 2 hours | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Include unknown | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Sort | الوصف | . | Last heard | Most recently heard nodes first | . | A-Z | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/nodes.html#filtering--sorting",
    
    "relUrl": "/ar-rSA/user/nodes.html#filtering--sorting"
  },"3896": {
    "doc": "Nodes",
    "title": "Nodes per hop",
    "content": "Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/ar-rSA/user/nodes.html#nodes-per-hop"
  },"3897": {
    "doc": "Nodes",
    "title": "Node detail",
    "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | آخر ظهور | | . | المسافة | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | Meaning | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/nodes.html#node-detail",
    
    "relUrl": "/ar-rSA/user/nodes.html#node-detail"
  },"3898": {
    "doc": "Nodes",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/ar-rSA/user/nodes.html#when-no-nodes-appear"
  },"3899": {
    "doc": "Nodes",
    "title": "Related Topics",
    "content": ". | Node Metrics — detailed telemetry dashboards for each node | Messages & Channels — send a direct message to a node | Map & Waypoints — view node positions geographically | Local Mesh Discovery — traceroute and neighbor info for topology exploration | Signal Meter — understand what the signal bars mean | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/nodes.html#related-topics",
    
    "relUrl": "/ar-rSA/user/nodes.html#related-topics"
  },"3900": {
    "doc": "Nodes",
    "title": "Nodes",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/nodes.html",
    
    "relUrl": "/hr-rHR/user/nodes.html"
  },"3901": {
    "doc": "Nodes",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Indicator | Meaning | . | Green last-heard time | Node heard within the last 2 hours | . | Plain last-heard time | Node not heard for over 2 hours | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Favorite | Node you marked as a favorite. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Node roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Opis | . | Client | Standard end-user node | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost and Found | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . 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 nodes. | 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 nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | Icon | Meaning | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Mismatch | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/nodes.html#node-list",
    
    "relUrl": "/hr-rHR/user/nodes.html#node-list"
  },"3902": {
    "doc": "Nodes",
    "title": "Quick Actions",
    "content": "From the node list, you can: . | Tap a node to view its detail page | Touch & hold for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Ukloni | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/nodes.html#quick-actions",
    
    "relUrl": "/hr-rHR/user/nodes.html#quick-actions"
  },"3903": {
    "doc": "Nodes",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/hr-rHR/user/nodes.html#sharing-a-contact"
  },"3904": {
    "doc": "Nodes",
    "title": "Filtering & sorting",
    "content": "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 . | Filtriraj | Opis | . | Hide offline nodes | Show only nodes heard within the last 2 hours | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Include unknown | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Sort | Opis | . | Last heard | Most recently heard nodes first | . | A-Z | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/nodes.html#filtering--sorting",
    
    "relUrl": "/hr-rHR/user/nodes.html#filtering--sorting"
  },"3905": {
    "doc": "Nodes",
    "title": "Nodes per hop",
    "content": "Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/hr-rHR/user/nodes.html#nodes-per-hop"
  },"3906": {
    "doc": "Nodes",
    "title": "Node detail",
    "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Posljednje čuo | | . | Udaljenost | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | Meaning | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/nodes.html#node-detail",
    
    "relUrl": "/hr-rHR/user/nodes.html#node-detail"
  },"3907": {
    "doc": "Nodes",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/hr-rHR/user/nodes.html#when-no-nodes-appear"
  },"3908": {
    "doc": "Nodes",
    "title": "Related Topics",
    "content": ". | Node Metrics — detailed telemetry dashboards for each node | Messages & Channels — send a direct message to a node | Map & Waypoints — view node positions geographically | Local Mesh Discovery — traceroute and neighbor info for topology exploration | Signal Meter — understand what the signal bars mean | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/nodes.html#related-topics",
    
    "relUrl": "/hr-rHR/user/nodes.html#related-topics"
  },"3909": {
    "doc": "Nodes",
    "title": "Nodes",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/nodes.html",
    
    "relUrl": "/pt-rPT/user/nodes.html"
  },"3910": {
    "doc": "Nodes",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Indicator | Meaning | . | Green last-heard time | Node heard within the last 2 hours | . | Plain last-heard time | Node not heard for over 2 hours | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Favorite | Node you marked as a favorite. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Node roles . Nodes can be configured with different roles that affect their mesh behavior: . | Papel | Descrição | . | Cliente | Standard end-user node | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Cliente silenciado | Receives but doesn’t retransmit | . | Cliente oculto | Like Client Mute, plus hides from node list | . | Roteador | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Monitor | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK — ‘Kit’ de Consciencialização da Equipa | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Perdidos e Achados | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . 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 nodes. | 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 nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | Icon | Meaning | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Mismatch | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/nodes.html#node-list",
    
    "relUrl": "/pt-rPT/user/nodes.html#node-list"
  },"3911": {
    "doc": "Nodes",
    "title": "Quick Actions",
    "content": "From the node list, you can: . | Tap a node to view its detail page | Touch & hold for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remover | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/nodes.html#quick-actions",
    
    "relUrl": "/pt-rPT/user/nodes.html#quick-actions"
  },"3912": {
    "doc": "Nodes",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/pt-rPT/user/nodes.html#sharing-a-contact"
  },"3913": {
    "doc": "Nodes",
    "title": "Filtering & sorting",
    "content": "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 . | Filtrar | Descrição | . | Hide offline nodes | Show only nodes heard within the last 2 hours | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Include unknown | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Sort | Descrição | . | Last heard | Most recently heard nodes first | . | A-Z | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/nodes.html#filtering--sorting",
    
    "relUrl": "/pt-rPT/user/nodes.html#filtering--sorting"
  },"3914": {
    "doc": "Nodes",
    "title": "Nodes per hop",
    "content": "Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/pt-rPT/user/nodes.html#nodes-per-hop"
  },"3915": {
    "doc": "Nodes",
    "title": "Node detail",
    "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Último recebido | | . | Distância | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | Meaning | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/nodes.html#node-detail",
    
    "relUrl": "/pt-rPT/user/nodes.html#node-detail"
  },"3916": {
    "doc": "Nodes",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/pt-rPT/user/nodes.html#when-no-nodes-appear"
  },"3917": {
    "doc": "Nodes",
    "title": "Related Topics",
    "content": ". | Node Metrics — detailed telemetry dashboards for each node | Messages & Channels — send a direct message to a node | Map & Waypoints — view node positions geographically | Local Mesh Discovery — traceroute and neighbor info for topology exploration | Signal Meter — understand what the signal bars mean | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/nodes.html#related-topics",
    
    "relUrl": "/pt-rPT/user/nodes.html#related-topics"
  },"3918": {
    "doc": "Węzły",
    "title": "Węzły",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/nodes.html",
    
    "relUrl": "/pl-rPL/user/nodes.html"
  },"3919": {
    "doc": "Węzły",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Indicator | Meaning | . | Green last-heard time | Node heard within the last 2 hours | . | Plain last-heard time | Node not heard for over 2 hours | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Favorite | Node you marked as a favorite. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Node roles . Nodes can be configured with different roles that affect their mesh behavior: . | Rola | Opis | . | Klient | Standard end-user node | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Klient pasywny | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Czujnik | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost and Found | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . 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 nodes. | 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 nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | Icon | Meaning | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Mismatch | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/nodes.html#node-list",
    
    "relUrl": "/pl-rPL/user/nodes.html#node-list"
  },"3920": {
    "doc": "Węzły",
    "title": "Quick Actions",
    "content": "From the node list, you can: . | Tap a node to view its detail page | Touch & hold for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Usuń | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/nodes.html#quick-actions",
    
    "relUrl": "/pl-rPL/user/nodes.html#quick-actions"
  },"3921": {
    "doc": "Węzły",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/pl-rPL/user/nodes.html#sharing-a-contact"
  },"3922": {
    "doc": "Węzły",
    "title": "Filtering & sorting",
    "content": "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 . | Filtr | Opis | . | Hide offline nodes | Show only nodes heard within the last 2 hours | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Include unknown | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Sort | Opis | . | Last heard | Most recently heard nodes first | . | A-Z | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/nodes.html#filtering--sorting",
    
    "relUrl": "/pl-rPL/user/nodes.html#filtering--sorting"
  },"3923": {
    "doc": "Węzły",
    "title": "Nodes per hop",
    "content": "Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/pl-rPL/user/nodes.html#nodes-per-hop"
  },"3924": {
    "doc": "Węzły",
    "title": "Node detail",
    "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Poziom naładowania baterii | | . | Hop count | | . | Aktywność | | . | Odległość | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | Meaning | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/nodes.html#node-detail",
    
    "relUrl": "/pl-rPL/user/nodes.html#node-detail"
  },"3925": {
    "doc": "Węzły",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/pl-rPL/user/nodes.html#when-no-nodes-appear"
  },"3926": {
    "doc": "Węzły",
    "title": "Related Topics",
    "content": ". | Node Metrics — detailed telemetry dashboards for each node | Messages & Channels — send a direct message to a node | Map & Waypoints — view node positions geographically | Local Mesh Discovery — traceroute and neighbor info for topology exploration | Signal Meter — understand what the signal bars mean | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/nodes.html#related-topics",
    
    "relUrl": "/pl-rPL/user/nodes.html#related-topics"
  },"3927": {
    "doc": "节点",
    "title": "节点",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/nodes.html",
    
    "relUrl": "/zh-rCN/user/nodes.html"
  },"3928": {
    "doc": "节点",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Indicator | Meaning | . | Green last-heard time | Node heard within the last 2 hours | . | Plain last-heard time | Node not heard for over 2 hours | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Favorite | Node you marked as a favorite. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Node roles . Nodes can be configured with different roles that affect their mesh behavior: . | 角色 | 说明 | . | 客户端 | Standard end-user node | . | 客户群 | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | 客户端静默 | Receives but doesn’t retransmit | . | 客户端隐藏 | Like Client Mute, plus hides from node list | . | 路由 | Prioritizes message forwarding; stays awake to relay | . | 延迟时间 | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | 追踪器 | Optimized for position reporting at regular intervals | . | 传感器 | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK 追踪器 | TAK position reporting only | . | 失物招领 | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . 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 nodes. | 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 nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | 图标 | Meaning | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Mismatch | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/nodes.html#node-list",
    
    "relUrl": "/zh-rCN/user/nodes.html#node-list"
  },"3929": {
    "doc": "节点",
    "title": "Quick Actions",
    "content": "From the node list, you can: . | Tap a node to view its detail page | Touch & hold for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | 移除 | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/nodes.html#quick-actions",
    
    "relUrl": "/zh-rCN/user/nodes.html#quick-actions"
  },"3930": {
    "doc": "节点",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/zh-rCN/user/nodes.html#sharing-a-contact"
  },"3931": {
    "doc": "节点",
    "title": "Filtering & sorting",
    "content": "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 . | 搜索节点 | 说明 | . | Hide offline nodes | Show only nodes heard within the last 2 hours | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Include unknown | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Sort | 说明 | . | Last heard | Most recently heard nodes first | . | A-Z | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/nodes.html#filtering--sorting",
    
    "relUrl": "/zh-rCN/user/nodes.html#filtering--sorting"
  },"3932": {
    "doc": "节点",
    "title": "Nodes per hop",
    "content": "Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/zh-rCN/user/nodes.html#nodes-per-hop"
  },"3933": {
    "doc": "节点",
    "title": "Node detail",
    "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | 电池电量 | | . | Hop count | | . | 最后听到 | | . | 距离 | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | Meaning | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/nodes.html#node-detail",
    
    "relUrl": "/zh-rCN/user/nodes.html#node-detail"
  },"3934": {
    "doc": "节点",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/zh-rCN/user/nodes.html#when-no-nodes-appear"
  },"3935": {
    "doc": "节点",
    "title": "Related Topics",
    "content": ". | Node Metrics — detailed telemetry dashboards for each node | Messages & Channels — send a direct message to a node | Map & Waypoints — view node positions geographically | Local Mesh Discovery — traceroute and neighbor info for topology exploration | Signal Meter — understand what the signal bars mean | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/nodes.html#related-topics",
    
    "relUrl": "/zh-rCN/user/nodes.html#related-topics"
  },"3936": {
    "doc": "Nodes",
    "title": "Nodes",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/nodes.html",
    
    "relUrl": "/sq-rAL/user/nodes.html"
  },"3937": {
    "doc": "Nodes",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Indicator | Meaning | . | Green last-heard time | Node heard within the last 2 hours | . | Plain last-heard time | Node not heard for over 2 hours | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Favorite | Node you marked as a favorite. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Node roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Përshkrimi | . | Client | Standard end-user node | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost and Found | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . 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 nodes. | 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 nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | Icon | Meaning | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Mismatch | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/nodes.html#node-list",
    
    "relUrl": "/sq-rAL/user/nodes.html#node-list"
  },"3938": {
    "doc": "Nodes",
    "title": "Quick Actions",
    "content": "From the node list, you can: . | Tap a node to view its detail page | Touch & hold for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Hiq | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/nodes.html#quick-actions",
    
    "relUrl": "/sq-rAL/user/nodes.html#quick-actions"
  },"3939": {
    "doc": "Nodes",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/sq-rAL/user/nodes.html#sharing-a-contact"
  },"3940": {
    "doc": "Nodes",
    "title": "Filtering & sorting",
    "content": "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 . | Filtrimi | Përshkrimi | . | Hide offline nodes | Show only nodes heard within the last 2 hours | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Include unknown | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Sort | Përshkrimi | . | Last heard | Most recently heard nodes first | . | A-Z | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/nodes.html#filtering--sorting",
    
    "relUrl": "/sq-rAL/user/nodes.html#filtering--sorting"
  },"3941": {
    "doc": "Nodes",
    "title": "Nodes per hop",
    "content": "Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/sq-rAL/user/nodes.html#nodes-per-hop"
  },"3942": {
    "doc": "Nodes",
    "title": "Node detail",
    "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | I fundit që u dëgjua | | . | Distanca | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | Meaning | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/nodes.html#node-detail",
    
    "relUrl": "/sq-rAL/user/nodes.html#node-detail"
  },"3943": {
    "doc": "Nodes",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/sq-rAL/user/nodes.html#when-no-nodes-appear"
  },"3944": {
    "doc": "Nodes",
    "title": "Related Topics",
    "content": ". | Node Metrics — detailed telemetry dashboards for each node | Messages & Channels — send a direct message to a node | Map & Waypoints — view node positions geographically | Local Mesh Discovery — traceroute and neighbor info for topology exploration | Signal Meter — understand what the signal bars mean | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/nodes.html#related-topics",
    
    "relUrl": "/sq-rAL/user/nodes.html#related-topics"
  },"3945": {
    "doc": "節點",
    "title": "節點",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/nodes.html",
    
    "relUrl": "/zh-rTW/user/nodes.html"
  },"3946": {
    "doc": "節點",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Indicator | Meaning | . | Green last-heard time | Node heard within the last 2 hours | . | Plain last-heard time | Node not heard for over 2 hours | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Favorite | Node you marked as a favorite. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Node roles . Nodes can be configured with different roles that affect their mesh behavior: . | 角色 | 描述說明 | . | 用戶端 | Standard end-user node | . | 客戶端基礎模式 | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Repeater | Optimized for position reporting at regular intervals | . | 感測器 | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost and Found | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . 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 nodes. | 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 nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | Icon | Meaning | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Mismatch | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/nodes.html#node-list",
    
    "relUrl": "/zh-rTW/user/nodes.html#node-list"
  },"3947": {
    "doc": "節點",
    "title": "Quick Actions",
    "content": "From the node list, you can: . | Tap a node to view its detail page | Touch & hold for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | 移除 | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/nodes.html#quick-actions",
    
    "relUrl": "/zh-rTW/user/nodes.html#quick-actions"
  },"3948": {
    "doc": "節點",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/zh-rTW/user/nodes.html#sharing-a-contact"
  },"3949": {
    "doc": "節點",
    "title": "Filtering & sorting",
    "content": "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 . | 過濾器 | 描述說明 | . | Hide offline nodes | Show only nodes heard within the last 2 hours | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Include unknown | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Sort | 描述說明 | . | Last heard | Most recently heard nodes first | . | A-Z | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/nodes.html#filtering--sorting",
    
    "relUrl": "/zh-rTW/user/nodes.html#filtering--sorting"
  },"3950": {
    "doc": "節點",
    "title": "Nodes per hop",
    "content": "Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/zh-rTW/user/nodes.html#nodes-per-hop"
  },"3951": {
    "doc": "節點",
    "title": "Node detail",
    "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Inline status indicators show key metrics at a glance: . | Indicator | 螢幕截圖 | . | Signal quality | | . | 電池電量 | | . | Hop count | | . | 最近一次收到排序 | | . | 距離 | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | 含義 | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/nodes.html#node-detail",
    
    "relUrl": "/zh-rTW/user/nodes.html#node-detail"
  },"3952": {
    "doc": "節點",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/zh-rTW/user/nodes.html#when-no-nodes-appear"
  },"3953": {
    "doc": "節點",
    "title": "Related Topics",
    "content": ". | Node Metrics — detailed telemetry dashboards for each node | Messages & Channels — send a direct message to a node | Map & Waypoints — view node positions geographically | Local Mesh Discovery — traceroute and neighbor info for topology exploration | Signal Meter — understand what the signal bars mean | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/nodes.html#related-topics",
    
    "relUrl": "/zh-rTW/user/nodes.html#related-topics"
  },"3954": {
    "doc": "Sõlmed",
    "title": "Sõlmed",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/nodes.html",
    
    "relUrl": "/et-rEE/user/nodes.html"
  },"3955": {
    "doc": "Sõlmed",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Sõlme nimi — kasutaja pandud pikk nimi | Lühinimi — 4-tähemärgiline identifikaator | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Last heard — time since last communication | Vahemaa — hinnanguline vahemaa (kui asukohta jagatakse) | Aku — kaugsõlme aku tase (kui telemeetria on lubatud) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Indicator | Tähendus | . | Green last-heard time | Viimase 2 tunni jooksul kuuldud sõlm | . | Plain last-heard time | Viimase 2 tunni jooksul kuuldud sõlm | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Lemmik | Node you marked as a favorite. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Node roles . Sõlmedele saab määrata erinevaid rolle, mis mõjutavad nende kärgvõrgus käitumist: . | Roll | Kirjeldus | . | Klient | Standard end-user node | . | Klient-baas | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Vaikne klient | Receives but doesn’t retransmit | . | Peidetud klient | Like Client Mute, plus hides from node list | . | Ruuter | Prioriseerib sõnumi edastamist; jääb edastamiseks ärkvele | . | Hiline ruuter | Infrastruktuurisõlm, mis levitab signaali ühe korra, kuid alles pärast kõiki teisi režiime (pakub täiendavat leviala) | . | Ruuteri klient | ⚠️ Vananenud (eemaldatud püsivara versioonis 2.3.15) — enam mitte valitav; kasuta hoopis ruuterint või kliendina | . | Repiiter | ⚠️ Vananenud (eemaldatud püsivara versioonis 2.7.11) — enam mitte valitav; kasuta hoopis ruuterina | . | Jälgitav | Optimized for position reporting at regular intervals | . | Andur | Optimized for telemetry reporting | . | TAK | Ühildub TAK süsteemidega (saadab/võtab vastu CoT) | . | Jälgitav TAK | Ainult TAK asukoha aruandlus | . | Kaotud ja leitud | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . Choosing a role . Most users should keep the default Client role. Consider a different role when: . | Ruuter — Teil on sõlm fikseeritud, kõrgemal asuvas asukohas, millel on usaldusväärne toide (katusel, mäetipul). Ruuterid püsivad pidevalt ärkvel, et vahendada teistele sõnumeid ja on võrguühenduse laiendamiseks hädavajalikud. Don’t use Router on battery-powered handheld nodes. | Ruuter hiline – infrastruktuurisõlm, mis levitab pakette alati üks kord uuesti, aga alles pärast seda, kui kõik teised marsruutimisrežiimid on oma käigu teinud. Provides supplemental coverage for local clusters without competing with primary routers. | Baas klient – käsitleb lemmiksõlmedesse suunduvat ja sealt tulevaid liiklusi ruuteri hilinemise prioriteediga (tagades, et need sõnumid saavad täiendava edastuskatte), samal ajal kui kõike muud käsitletakse tavalise kliendina. | Kliendi vaigistatud — Soovid vastu võtta võrguliiklust, aga mitte edastamisse panustada. Useful for monitoring-only nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Aku säästmiseks magab saadete vahel. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Sarnane võimsusprofiil jälgimisseadmele. | TAK / TAK jälgimisseade — Vajalik ainult ATAK/WinTAK süsteemidega koostööl. Üksikasjade saamiseks vaata TAK integratsioon. | . 💡 Vihje: Kärgvõrk töötab kõige paremini, kui enamik sõlmi on klient või ruuter. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | Ikoon | Tähendus | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Ebakõla | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/nodes.html#node-list",
    
    "relUrl": "/et-rEE/user/nodes.html#node-list"
  },"3956": {
    "doc": "Sõlmed",
    "title": "Quick Actions",
    "content": "From the node list, you can: . | Puuduta sõlmel, et vaadata üksikasjade lehte | Touch & hold for quick actions: . | Mark/remove favorite | Teavituste vaigistamine/vaigistuse tühistamine | Saada otsesõnum | Trace route | Ignore/unignore | Eemalda | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/nodes.html#quick-actions",
    
    "relUrl": "/et-rEE/user/nodes.html#quick-actions"
  },"3957": {
    "doc": "Sõlmed",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/et-rEE/user/nodes.html#sharing-a-contact"
  },"3958": {
    "doc": "Sõlmed",
    "title": "Filtering & sorting",
    "content": "Text search . Sõlmede filtreerimiseks nime või lühinime järgi tipi otsinguväljal. Filter uueneb reaalajas kirjutamise ajal. Filter toggles . | Filtreeri | Kirjeldus | . | Hide offline nodes | Näita ainult viimase 2 tunni jooksul kuuldud sõlmi | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Include unknown | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Välista MQTT | Peida ainult MQTT internetisilla kaudu kuuldavad sõlmed | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Sorteeri | Kirjeldus | . | Last heard | Viimati kuuldud sõlmed esimesena | . | A-Z | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hüppe kaugusel | Vähim vahendatud hüppeid esimesena | . | Kanal | Rühmitatud kanali loendi alusel | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/nodes.html#filtering--sorting",
    
    "relUrl": "/et-rEE/user/nodes.html#filtering--sorting"
  },"3959": {
    "doc": "Sõlmed",
    "title": "Nodes per hop",
    "content": "Puuduta sõlmede loendi rakenduse ribal hüppehistogrammi ikooni, et avada tulpdiagramm, mis näitab, mitu sõlme asub igal hüppekaugusel (0 = otse, 1 = ühe relee kaugusel jne). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/et-rEE/user/nodes.html#nodes-per-hop"
  },"3960": {
    "doc": "Sõlmed",
    "title": "Node detail",
    "content": "Sõlmel klõpsamine avab detailvaate koos põhjaliku teabega. See Node Metrics for full details on metrics and telemetry. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Tekstisisesed olekuindikaatorid näitavad peamisi mõõdikuid lühidalt: . | Indikaator | Screenshot | . | Signal quality | | . | Aku tase | | . | Hüppete loendur | | . | Viimati kuuldud | | . | Kaugus | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | Tähendus | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . Kui sõlme riistvara tuvastatakse, kuvatakse detailvaates kokkupandav jaotis „Soovin ühte”, mis lingib kohtadele, kust seadet osta või selle kohta lisateavet saada: müüja tooteleht, tootevariandid ja piirkondlike marketplace loendid (nt AliExpress, Amazon ja toetatud jaemüüjad), mis on filtreeritud sinu riigi järgi. Iga link avaneb ümbersuunamisteenuse msh.to kaudu. Seadmed, millel pole vastavaid linke, seda jaotist ei kuva. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/nodes.html#node-detail",
    
    "relUrl": "/et-rEE/user/nodes.html#node-detail"
  },"3961": {
    "doc": "Sõlmed",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/et-rEE/user/nodes.html#when-no-nodes-appear"
  },"3962": {
    "doc": "Sõlmed",
    "title": "Seotud teemad",
    "content": ". | Node Metrics — detailed telemetry dashboards for each node | Sõnumid ja kanalid — saada otsesõnum sõlmele | Kaart ja teekonnapunktid — vaata sõlmede geograafilisi asukohti | Local Mesh Discovery — traceroute and neighbor info for topology exploration | Signal Meter — understand what the signal bars mean | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/nodes.html#seotud-teemad",
    
    "relUrl": "/et-rEE/user/nodes.html#seotud-teemad"
  },"3963": {
    "doc": "Nœuds",
    "title": "Nœuds",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/nodes.html",
    
    "relUrl": "/fr-rFR/user/nodes.html"
  },"3964": {
    "doc": "Nœuds",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Indicator | Meaning | . | Green last-heard time | Node heard within the last 2 hours | . | Plain last-heard time | Node not heard for over 2 hours | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Favorite | Node you marked as a favorite. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Node roles . Nodes can be configured with different roles that affect their mesh behavior: . | Rôle | Description | . | Client | Standard end-user node | . | Base Client | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client muet | Receives but doesn’t retransmit | . | Client masqué | Like Client Mute, plus hides from node list | . | Routeur | Prioritizes message forwarding; stays awake to relay | . | Routeur avec retard | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Traqueur | Optimized for position reporting at regular intervals | . | Capteur | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | Traqueur TAK | TAK position reporting only | . | Objets trouvés | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . 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 nodes. | 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 nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | Icon | Meaning | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Mismatch | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/nodes.html#node-list",
    
    "relUrl": "/fr-rFR/user/nodes.html#node-list"
  },"3965": {
    "doc": "Nœuds",
    "title": "Quick Actions",
    "content": "From the node list, you can: . | Tap a node to view its detail page | Touch & hold for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Supprimer | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/nodes.html#quick-actions",
    
    "relUrl": "/fr-rFR/user/nodes.html#quick-actions"
  },"3966": {
    "doc": "Nœuds",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/fr-rFR/user/nodes.html#sharing-a-contact"
  },"3967": {
    "doc": "Nœuds",
    "title": "Filtering & sorting",
    "content": "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 . | Filtre | Description | . | Hide offline nodes | Show only nodes heard within the last 2 hours | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Include unknown | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Sort | Description | . | Last heard | Most recently heard nodes first | . | A-Z | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/nodes.html#filtering--sorting",
    
    "relUrl": "/fr-rFR/user/nodes.html#filtering--sorting"
  },"3968": {
    "doc": "Nœuds",
    "title": "Nodes per hop",
    "content": "Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/fr-rFR/user/nodes.html#nodes-per-hop"
  },"3969": {
    "doc": "Nœuds",
    "title": "Node detail",
    "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Niveau de batterie | | . | Hop count | | . | Dernière écoute | | . | Distance | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | Meaning | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/nodes.html#node-detail",
    
    "relUrl": "/fr-rFR/user/nodes.html#node-detail"
  },"3970": {
    "doc": "Nœuds",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/fr-rFR/user/nodes.html#when-no-nodes-appear"
  },"3971": {
    "doc": "Nœuds",
    "title": "Related Topics",
    "content": ". | Node Metrics — detailed telemetry dashboards for each node | Messages & Channels — send a direct message to a node | Map & Waypoints — view node positions geographically | Local Mesh Discovery — traceroute and neighbor info for topology exploration | Signal Meter — understand what the signal bars mean | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/nodes.html#related-topics",
    
    "relUrl": "/fr-rFR/user/nodes.html#related-topics"
  },"3972": {
    "doc": "Nodelar",
    "title": "Nodelar",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/nodes.html",
    
    "relUrl": "/tr-rTR/user/nodes.html"
  },"3973": {
    "doc": "Nodelar",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Indicator | Meaning | . | Green last-heard time | Node heard within the last 2 hours | . | Plain last-heard time | Node not heard for over 2 hours | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Favorite | Node you marked as a favorite. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Node roles . Nodes can be configured with different roles that affect their mesh behavior: . | Rol | Açıklaması | . | Client | Standard end-user node | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost and Found | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . 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 nodes. | 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 nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | Icon | Meaning | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Mismatch | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/nodes.html#node-list",
    
    "relUrl": "/tr-rTR/user/nodes.html#node-list"
  },"3974": {
    "doc": "Nodelar",
    "title": "Quick Actions",
    "content": "From the node list, you can: . | Tap a node to view its detail page | Touch & hold for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Kaldır | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/nodes.html#quick-actions",
    
    "relUrl": "/tr-rTR/user/nodes.html#quick-actions"
  },"3975": {
    "doc": "Nodelar",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/tr-rTR/user/nodes.html#sharing-a-contact"
  },"3976": {
    "doc": "Nodelar",
    "title": "Filtering & sorting",
    "content": "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 . | Filtre | Açıklaması | . | Hide offline nodes | Show only nodes heard within the last 2 hours | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Include unknown | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Sort | Açıklaması | . | Last heard | Most recently heard nodes first | . | A-Z | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/nodes.html#filtering--sorting",
    
    "relUrl": "/tr-rTR/user/nodes.html#filtering--sorting"
  },"3977": {
    "doc": "Nodelar",
    "title": "Nodes per hop",
    "content": "Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/tr-rTR/user/nodes.html#nodes-per-hop"
  },"3978": {
    "doc": "Nodelar",
    "title": "Node detail",
    "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Son duyulma | | . | Mesafe | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | Meaning | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/nodes.html#node-detail",
    
    "relUrl": "/tr-rTR/user/nodes.html#node-detail"
  },"3979": {
    "doc": "Nodelar",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/tr-rTR/user/nodes.html#when-no-nodes-appear"
  },"3980": {
    "doc": "Nodelar",
    "title": "Related Topics",
    "content": ". | Node Metrics — detailed telemetry dashboards for each node | Messages & Channels — send a direct message to a node | Map & Waypoints — view node positions geographically | Local Mesh Discovery — traceroute and neighbor info for topology exploration | Signal Meter — understand what the signal bars mean | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/nodes.html#related-topics",
    
    "relUrl": "/tr-rTR/user/nodes.html#related-topics"
  },"3981": {
    "doc": "Nodes",
    "title": "Nodes",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/nodes.html",
    
    "relUrl": "/el-rGR/user/nodes.html"
  },"3982": {
    "doc": "Nodes",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Indicator | Meaning | . | Green last-heard time | Node heard within the last 2 hours | . | Plain last-heard time | Node not heard for over 2 hours | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Favorite | Node you marked as a favorite. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Node roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Περιγραφή | . | Client | Standard end-user node | . | Πελάτης Βάση | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost and Found | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . 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 nodes. | 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 nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | Icon | Meaning | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Mismatch | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/nodes.html#node-list",
    
    "relUrl": "/el-rGR/user/nodes.html#node-list"
  },"3983": {
    "doc": "Nodes",
    "title": "Quick Actions",
    "content": "From the node list, you can: . | Tap a node to view its detail page | Touch & hold for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Διαγραφή | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/nodes.html#quick-actions",
    
    "relUrl": "/el-rGR/user/nodes.html#quick-actions"
  },"3984": {
    "doc": "Nodes",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/el-rGR/user/nodes.html#sharing-a-contact"
  },"3985": {
    "doc": "Nodes",
    "title": "Filtering & sorting",
    "content": "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 . | Φίλτρο | Περιγραφή | . | Hide offline nodes | Show only nodes heard within the last 2 hours | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Include unknown | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Sort | Περιγραφή | . | Last heard | Most recently heard nodes first | . | A-Z | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/nodes.html#filtering--sorting",
    
    "relUrl": "/el-rGR/user/nodes.html#filtering--sorting"
  },"3986": {
    "doc": "Nodes",
    "title": "Nodes per hop",
    "content": "Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/el-rGR/user/nodes.html#nodes-per-hop"
  },"3987": {
    "doc": "Nodes",
    "title": "Node detail",
    "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Last heard | | . | Απόσταση | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | Meaning | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/nodes.html#node-detail",
    
    "relUrl": "/el-rGR/user/nodes.html#node-detail"
  },"3988": {
    "doc": "Nodes",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/el-rGR/user/nodes.html#when-no-nodes-appear"
  },"3989": {
    "doc": "Nodes",
    "title": "Related Topics",
    "content": ". | Node Metrics — detailed telemetry dashboards for each node | Messages & Channels — send a direct message to a node | Map & Waypoints — view node positions geographically | Local Mesh Discovery — traceroute and neighbor info for topology exploration | Signal Meter — understand what the signal bars mean | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/nodes.html#related-topics",
    
    "relUrl": "/el-rGR/user/nodes.html#related-topics"
  },"3990": {
    "doc": "Noduri",
    "title": "Noduri",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/nodes.html",
    
    "relUrl": "/ro-rRO/user/nodes.html"
  },"3991": {
    "doc": "Noduri",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Indicator | Meaning | . | Green last-heard time | Node heard within the last 2 hours | . | Plain last-heard time | Node not heard for over 2 hours | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Favorite | Node you marked as a favorite. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Node roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Descriere | . | Client | Standard end-user node | . | Client bază | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client mut | Receives but doesn’t retransmit | . | Client ascuns | Like Client Mute, plus hides from node list | . | Ruter | Prioritizes message forwarding; stays awake to relay | . | Ruter cu întârziere | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Senzor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | Tracker TAK | TAK position reporting only | . | Pierdut și găsit | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . 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 nodes. | 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 nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | Icon | Meaning | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Mismatch | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/nodes.html#node-list",
    
    "relUrl": "/ro-rRO/user/nodes.html#node-list"
  },"3992": {
    "doc": "Noduri",
    "title": "Quick Actions",
    "content": "From the node list, you can: . | Tap a node to view its detail page | Touch & hold for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Eliminare | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/nodes.html#quick-actions",
    
    "relUrl": "/ro-rRO/user/nodes.html#quick-actions"
  },"3993": {
    "doc": "Noduri",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/ro-rRO/user/nodes.html#sharing-a-contact"
  },"3994": {
    "doc": "Noduri",
    "title": "Filtering & sorting",
    "content": "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 . | Filtru | Descriere | . | Hide offline nodes | Show only nodes heard within the last 2 hours | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Include unknown | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Sort | Descriere | . | Last heard | Most recently heard nodes first | . | A-Z | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/nodes.html#filtering--sorting",
    
    "relUrl": "/ro-rRO/user/nodes.html#filtering--sorting"
  },"3995": {
    "doc": "Noduri",
    "title": "Nodes per hop",
    "content": "Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/ro-rRO/user/nodes.html#nodes-per-hop"
  },"3996": {
    "doc": "Noduri",
    "title": "Node detail",
    "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Ultima recepție | | . | Distanță | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | Meaning | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/nodes.html#node-detail",
    
    "relUrl": "/ro-rRO/user/nodes.html#node-detail"
  },"3997": {
    "doc": "Noduri",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/ro-rRO/user/nodes.html#when-no-nodes-appear"
  },"3998": {
    "doc": "Noduri",
    "title": "Related Topics",
    "content": ". | Node Metrics — detailed telemetry dashboards for each node | Messages & Channels — send a direct message to a node | Map & Waypoints — view node positions geographically | Local Mesh Discovery — traceroute and neighbor info for topology exploration | Signal Meter — understand what the signal bars mean | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/nodes.html#related-topics",
    
    "relUrl": "/ro-rRO/user/nodes.html#related-topics"
  },"3999": {
    "doc": "Nodes",
    "title": "Nodes",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/nodes.html",
    
    "relUrl": "/iw-rIL/user/nodes.html"
  },"4000": {
    "doc": "Nodes",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Indicator | Meaning | . | Green last-heard time | Node heard within the last 2 hours | . | Plain last-heard time | Node not heard for over 2 hours | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Favorite | Node you marked as a favorite. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Node roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | תיאור | . | Client | Standard end-user node | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost and Found | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . 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 nodes. | 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 nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | Icon | Meaning | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Mismatch | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/nodes.html#node-list",
    
    "relUrl": "/iw-rIL/user/nodes.html#node-list"
  },"4001": {
    "doc": "Nodes",
    "title": "Quick Actions",
    "content": "From the node list, you can: . | Tap a node to view its detail page | Touch & hold for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/nodes.html#quick-actions",
    
    "relUrl": "/iw-rIL/user/nodes.html#quick-actions"
  },"4002": {
    "doc": "Nodes",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/iw-rIL/user/nodes.html#sharing-a-contact"
  },"4003": {
    "doc": "Nodes",
    "title": "Filtering & sorting",
    "content": "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 . | פילטר | תיאור | . | Hide offline nodes | Show only nodes heard within the last 2 hours | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Include unknown | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Sort | תיאור | . | Last heard | Most recently heard nodes first | . | A-Z | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/nodes.html#filtering--sorting",
    
    "relUrl": "/iw-rIL/user/nodes.html#filtering--sorting"
  },"4004": {
    "doc": "Nodes",
    "title": "Nodes per hop",
    "content": "Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/iw-rIL/user/nodes.html#nodes-per-hop"
  },"4005": {
    "doc": "Nodes",
    "title": "Node detail",
    "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Last heard | | . | מרחק | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | Meaning | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/nodes.html#node-detail",
    
    "relUrl": "/iw-rIL/user/nodes.html#node-detail"
  },"4006": {
    "doc": "Nodes",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/iw-rIL/user/nodes.html#when-no-nodes-appear"
  },"4007": {
    "doc": "Nodes",
    "title": "Related Topics",
    "content": ". | Node Metrics — detailed telemetry dashboards for each node | Messages & Channels — send a direct message to a node | Map & Waypoints — view node positions geographically | Local Mesh Discovery — traceroute and neighbor info for topology exploration | Signal Meter — understand what the signal bars mean | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/nodes.html#related-topics",
    
    "relUrl": "/iw-rIL/user/nodes.html#related-topics"
  },"4008": {
    "doc": "Nós",
    "title": "Nós",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/nodes.html",
    
    "relUrl": "/pt-rBR/user/nodes.html"
  },"4009": {
    "doc": "Nós",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Indicator | Meaning | . | Green last-heard time | Node heard within the last 2 hours | . | Plain last-heard time | Node not heard for over 2 hours | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Favorite | Node you marked as a favorite. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Node roles . Nodes can be configured with different roles that affect their mesh behavior: . | Função | Descrição | . | Client | Standard end-user node | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost and Found | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . 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 nodes. | 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 nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | Icon | Meaning | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Mismatch | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/nodes.html#node-list",
    
    "relUrl": "/pt-rBR/user/nodes.html#node-list"
  },"4010": {
    "doc": "Nós",
    "title": "Quick Actions",
    "content": "From the node list, you can: . | Tap a node to view its detail page | Touch & hold for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Excluir | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/nodes.html#quick-actions",
    
    "relUrl": "/pt-rBR/user/nodes.html#quick-actions"
  },"4011": {
    "doc": "Nós",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/pt-rBR/user/nodes.html#sharing-a-contact"
  },"4012": {
    "doc": "Nós",
    "title": "Filtering & sorting",
    "content": "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 . | Filtro | Descrição | . | Hide offline nodes | Show only nodes heard within the last 2 hours | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Include unknown | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Sort | Descrição | . | Last heard | Most recently heard nodes first | . | A-Z | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/nodes.html#filtering--sorting",
    
    "relUrl": "/pt-rBR/user/nodes.html#filtering--sorting"
  },"4013": {
    "doc": "Nós",
    "title": "Nodes per hop",
    "content": "Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/pt-rBR/user/nodes.html#nodes-per-hop"
  },"4014": {
    "doc": "Nós",
    "title": "Node detail",
    "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Visto pela última vez | | . | Distância | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | Meaning | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/nodes.html#node-detail",
    
    "relUrl": "/pt-rBR/user/nodes.html#node-detail"
  },"4015": {
    "doc": "Nós",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/pt-rBR/user/nodes.html#when-no-nodes-appear"
  },"4016": {
    "doc": "Nós",
    "title": "Related Topics",
    "content": ". | Node Metrics — detailed telemetry dashboards for each node | Messages & Channels — send a direct message to a node | Map & Waypoints — view node positions geographically | Local Mesh Discovery — traceroute and neighbor info for topology exploration | Signal Meter — understand what the signal bars mean | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/nodes.html#related-topics",
    
    "relUrl": "/pt-rBR/user/nodes.html#related-topics"
  },"4017": {
    "doc": "Nodes",
    "title": "Nodes",
    "content": "The Nodes screen lists every node visible on your mesh. ",
    "url": "/Meshtastic-Android/main/en/user/nodes.html",
    
    "relUrl": "/en/user/nodes.html"
  },"4018": {
    "doc": "Nodes",
    "title": "Node list",
    "content": "The node list shows every node your node has heard, including: . | Node name — user-configured long name | Short name — 4-character identifier | Signal quality — SNR, RSSI, and a quality word, shown only for nodes your node heard directly. In the Complete layout a node reached through a relay shows its hop count here instead; a node heard only over MQTT shows neither | Last heard — time since last communication | Distance — estimated distance (if positions are shared) | Battery — remote node battery level (if telemetry is enabled) | . Choosing what the list shows . The list has two densities, set at Settings → Node Layout. Complete shows every field a node has reported and hides the ones it hasn’t. Compact fits more nodes on screen and lets you pick the fields yourself — Power, Last Heard Time, Relative Last Heard Time, Distance and Bearing, Hops Away, Signal (Direct Only), Channel, and Device & Role. The Environment Metrics toggle applies to both densities. A preview above the toggles shows the effect before you leave the screen. Node Status indicators . | Indicator | Meaning | . | Green last-heard time | Node heard within the last 2 hours | . | Plain last-heard time | Node not heard for over 2 hours | . | Orange last-heard time with a crossed-out signal icon | Not heard since your node’s LoRa settings changed, so it can’t be reached from here | . | Struck-through name | Node you have ignored | . | ⭐ Favorite | Node you marked as a favorite. | . There is no separate “away” tier, but the orange unreachable state takes precedence over the green one: a node can be online and still be unreachable on your current settings. Nodes known only over MQTT are never shown as unreachable. Node roles . Nodes can be configured with different roles that affect their mesh behavior: . | Role | Description | . | Client | Standard end-user node | . | Client Base | Treats favorited-node traffic as Router Late priority; all other traffic as Client | . | Client Mute | Receives but doesn’t retransmit | . | Client Hidden | Like Client Mute, plus hides from node list | . | Router | Prioritizes message forwarding; stays awake to relay | . | Router Late | Infrastructure node that rebroadcasts once, but only after all other modes (provides supplemental coverage) | . | Router Client | ⚠️ Deprecated (removed in firmware 2.3.15) — no longer selectable; use Router or Client instead | . | Repeater | ⚠️ Deprecated (removed in firmware 2.7.11) — no longer selectable; use Router instead | . | Tracker | Optimized for position reporting at regular intervals | . | Sensor | Optimized for telemetry reporting | . | TAK | Interoperates with TAK systems (sends/receives CoT) | . | TAK Tracker | TAK position reporting only | . | Lost and Found | Sends its position to the default channel as a text message at regular intervals, to help recover a lost node | . 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 nodes. | 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 nodes or to reduce congestion in dense areas. | Tracker — An unattended node whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery. | Sensor — An unattended node reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker. | TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details. | . 💡 Tip: The mesh works best when most nodes are Client or Router. Too many Client Mute nodes reduce mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area. Security indicators . Each node carries one security icon beside its name in the node list. Tap it to read what it means, and choose Show All Meanings in that dialog for the full legend. The detail screen shows the same state in words, as a Security row that opens the same dialog. | Icon | Meaning | Shown for | . | Person with a shield check (green) | Verified contact — you verified this node’s key in person by exchanging contact QR codes, so its identity is confirmed. The strongest trust the list shows. Your own connected node carries it too | Any firmware version | . | Nodes icon with a shield check (green) | Signed node — this node signs its broadcasts with its identity key, so its identity is consistent over time, but you haven’t verified it in person. On firmware 2.8 the icon appears from the version alone, before any signed broadcast has been heard | Firmware 2.8 or newer, and any node whose signed broadcast your node has verified | . | 🔒 Closed lock | A public key is on file and matches, so direct messages to this node are encrypted | Firmware before 2.8, or no reported version | . | 🔓 Open lock | No public key has been received for this node, so it can’t be direct messaged — use Request User Info on the node detail page to ask for one | Firmware before 2.8, or no reported version | . | ⚠️ Mismatch | Public key mismatch — a different key arrived for this node after one was stored. Investigate before trusting | Any firmware version | . Every node on firmware 2.8 or newer signs its broadcasts, so on that firmware the signed state is the baseline and the locks aren’t shown. Direct messages always use public-key encryption, so your node needs the other node’s public key before it can send one. It refuses the send rather than falling back to channel encryption. Keys arrive inside node info, which is why an open lock usually clears itself once that node is heard from properly. A mismatch never replaces the key you already hold. The app keeps the first key it recorded and refuses the new one, as the firmware does, so a stray or hostile node info can’t silently break encrypted messaging to a contact. To clear a mismatch, first confirm through another trusted channel that the key change was intentional — a factory reset causes one. Then touch & hold the node, choose Remove, and let the two nodes exchange keys again the next time yours hears it. ",
    "url": "/Meshtastic-Android/main/en/user/nodes.html#node-list",
    
    "relUrl": "/en/user/nodes.html#node-list"
  },"4019": {
    "doc": "Nodes",
    "title": "Quick Actions",
    "content": "From the node list, you can: . | Tap a node to view its detail page | Touch & hold for quick actions: . | Mark/remove favorite | Mute/unmute notifications | Send a direct message | Trace route | Ignore/unignore | Remove | . | . Touch & hold your own node instead and you get one action, Update status, which opens the User settings screen with the cursor already in the Status Message field. It only appears while the node is connected and running firmware 2.8 or newer — see Settings — Radio & User for the field itself. ",
    "url": "/Meshtastic-Android/main/en/user/nodes.html#quick-actions",
    
    "relUrl": "/en/user/nodes.html#quick-actions"
  },"4020": {
    "doc": "Nodes",
    "title": "Sharing a contact",
    "content": "On a node’s detail screen, tap Share Contact to produce a link and a QR code for that node. From the same dialog, Share link opens the Android share sheet (on desktop it copies the link instead), Write to NFC tag saves it to a writable NFC tag, and Copy puts it on the clipboard. While that dialog is open and in front of you, the phone also offers the same link to any NFC reader, so someone can take the contact by tapping their phone against yours with no tag involved. Sharing your own contact this way marks it as verified in person, so whoever imports it sees the Verified contact icon rather than the signed one. Relaying someone else’s contact passes on only what your app had already recorded about them. To add someone else’s contact, use the import button on the node list and choose Scan Shared Contact QR Code, Scan Shared Contact NFC, or Input Shared Contact URL. The app asks you to confirm with Import Shared Contact?, and warns you when the contact is one you already have. ",
    "url": "/Meshtastic-Android/main/en/user/nodes.html#sharing-a-contact",
    
    "relUrl": "/en/user/nodes.html#sharing-a-contact"
  },"4021": {
    "doc": "Nodes",
    "title": "Filtering & sorting",
    "content": "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 . | Filter | Description | . | Hide offline nodes | Show only nodes heard within the last 2 hours | . | Only show direct nodes | Show only nodes your node heard directly, with no relay in between | . | Include unknown | Show nodes that haven’t sent user info yet. On by default, so a node heard before its info arrives stays visible; these carry a badge marking them incomplete, and can’t be direct messaged until their user info brings a public key | . | Exclude infrastructure | Hide infrastructure-role nodes (Router, Router Late, Client Base, and legacy Repeater nodes) and any node that can’t be messaged, whatever its role | . | Exclude MQTT | Hide nodes heard only via MQTT internet bridge | . | Hide unheard nodes | Hide nodes your own node hasn’t heard since its LoRa settings changed. Off by default, and it does nothing on firmware that doesn’t report whether a node was heard on the current settings | . | Signed only | Show only nodes whose signed broadcasts your node has actually heard and verified. Stricter than the icon: a node on 2.8 shows as signed by its firmware version before any signed broadcast arrives, and a contact verified in person on older firmware isn’t signed at all | . | Encrypted only | Show nodes with a matching public key on file, the key an encrypted direct message needs. A node with a key mismatch is excluded | . | Only show ignored Nodes | Replace the list with the nodes you have ignored. Every other node is hidden while this is on, and a banner appears at the top of the list to take you back | . Nodes not heard on your current Settings . When your node’s LoRa settings change — a different preset, region or frequency slot — nodes heard under the old settings are still in the list but can no longer be reached. The app marks them with an orange last-heard time and a crossed-out signal icon, and shows a banner at the top of the list: N nodes not heard on your current LoRa settings. The banner offers two actions: . | Keep dismisses the banner and leaves every node in place. | Remove deletes those nodes from the list. Your favorites and your own node are never removed. | . Remove is a bulk delete and there is no undo, so use Keep if you expect to switch back to the old settings. Removed nodes reappear if your node hears them again. The Hide unheard nodes filter does the same hiding without deleting anything. Sort options . | Sort | Description | . | Last heard | Most recently heard nodes first | . | A-Z | Sorted by node long name | . | Distance | Nearest nodes first (requires position sharing) | . | Hops away | Fewest relay hops first | . | Channel | Grouped by channel index | . | via MQTT | Grouped by MQTT vs. node-heard | . | via Favorite (default) | Favorited nodes first, then the rest | . ",
    "url": "/Meshtastic-Android/main/en/user/nodes.html#filtering--sorting",
    
    "relUrl": "/en/user/nodes.html#filtering--sorting"
  },"4022": {
    "doc": "Nodes",
    "title": "Nodes per hop",
    "content": "Tap the hop-histogram icon in the node list’s app bar to open a bar chart of how many nodes sit at each hop distance (0 = direct, 1 = one relay away, and so on). Filter the chart to a last heard window — All, 1 Hour, 8 Hours or 24H — to see how the mesh looks right now versus over a longer period. It’s a quick way to gauge how busy and spread out your local mesh is. ",
    "url": "/Meshtastic-Android/main/en/user/nodes.html#nodes-per-hop",
    
    "relUrl": "/en/user/nodes.html#nodes-per-hop"
  },"4023": {
    "doc": "Nodes",
    "title": "Node detail",
    "content": "Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry. Signal quality is rated against your modem preset. The same SNR can be good on a long-range preset and poor on a faster one. Traceroute and neighbor-info SNR colors use that preset too. RSSI text has its own strength colors; it affects the quality rating only when a noise-floor reading is also available. The Details card carries the node’s short name, role, IDs, last heard time, hops away, uptime, and its SNR and RSSI: . Inline status indicators show key metrics at a glance: . | Indicator | Screenshot | . | Signal quality | | . | Battery level | | . | Hop count | | . | Last heard | | . | Distance | | . Hardware support status . When a node’s hardware is recognized, the detail view names the device and marks its support status, taken from the Meshtastic device registry rather than the app: . | Mark | Meaning | . | Rosette (green) | Supported — hardware the Meshtastic project actively supports | . | Wrench (sky blue) | Independent maker hardware — built and tested by an independent maker, shown as its own rung whether or not the project has promoted it yet | . | Unverified (red) | Supported by Meshtastic Community — hardware the project does not actively support, including legacy boards | . The label always accompanies the mark, so the status is never conveyed by colour alone. Device links (“I want one”) . When a node’s hardware is recognized, the detail view shows a collapsible “I want one” section linking to places to buy or learn more about that device: the vendor’s product page, product variants, and regional marketplace listings (such as AliExpress, Amazon, and supported retailers), filtered to your country. Each link opens through the msh.to redirect service. Devices with no matching links don’t show the section. A full, browsable directory of every link is also available at Settings → Device Links. The item is hidden while you have Settings open for a remote node. Some of these are affiliate links. Both places say so above the links: product links may be affiliate links, and purchases may earn Meshtastic a commission. ",
    "url": "/Meshtastic-Android/main/en/user/nodes.html#node-detail",
    
    "relUrl": "/en/user/nodes.html#node-detail"
  },"4024": {
    "doc": "Nodes",
    "title": "When no nodes appear",
    "content": "The list stays empty until your node hears another node. | No device connected — the app isn’t connected to a node. See Connections. | Searching for nodes — the node is connected and listening, but nothing has arrived yet. Check that its region and modem preset match the mesh around you, and leave Include unknown on so a node that hasn’t yet sent its name still appears. See Settings — Radio & User. | A node you expect is missing — check the filter toggles. Only show direct nodes, Exclude MQTT, and Exclude infrastructure each hide a whole category of node. | . ",
    "url": "/Meshtastic-Android/main/en/user/nodes.html#when-no-nodes-appear",
    
    "relUrl": "/en/user/nodes.html#when-no-nodes-appear"
  },"4025": {
    "doc": "Nodes",
    "title": "Related Topics",
    "content": ". | Node Metrics — detailed telemetry dashboards for each node | Messages & Channels — send a direct message to a node | Map & Waypoints — view node positions geographically | Local Mesh Discovery — traceroute and neighbor info for topology exploration | Signal Meter — understand what the signal bars mean | . ",
    "url": "/Meshtastic-Android/main/en/user/nodes.html#related-topics",
    
    "relUrl": "/en/user/nodes.html#related-topics"
  },"4026": {
    "doc": "Getting Started",
    "title": "Getting Started",
    "content": "This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/onboarding.html",
    
    "relUrl": "/sk-rSK/user/onboarding.html"
  },"4027": {
    "doc": "Getting Started",
    "title": "First Launch",
    "content": "When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. Welcome Screen . The welcome screen introduces Meshtastic with three feature rows: . |   |   | . | Stay Connected Anywhere | Communicate off-the-grid with your friends and community without cell service. | . | Create Your Own Networks | Easily set up private mesh networks for secure and reliable communication in remote areas. | . | Track and Share Locations | Share your location in real-time and keep your group coordinated with integrated GPS features. | . Tap Get started to proceed through the setup flow. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/onboarding.html#first-launch",
    
    "relUrl": "/sk-rSK/user/onboarding.html#first-launch"
  },"4028": {
    "doc": "Getting Started",
    "title": "Permissions",
    "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/onboarding.html#permissions",
    
    "relUrl": "/sk-rSK/user/onboarding.html#permissions"
  },"4029": {
    "doc": "Getting Started",
    "title": "After Setup",
    "content": "After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions. 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own. Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/onboarding.html#after-setup",
    
    "relUrl": "/sk-rSK/user/onboarding.html#after-setup"
  },"4030": {
    "doc": "Getting Started",
    "title": "Related Topics",
    "content": ". | Connections — pair your first radio | Messages & Channels — send your first message | Nodes — see who else is on your mesh | Map & Waypoints — view node positions | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/onboarding.html#related-topics",
    
    "relUrl": "/sk-rSK/user/onboarding.html#related-topics"
  },"4031": {
    "doc": "Начало работы",
    "title": "Начало работы",
    "content": "This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/onboarding.html",
    
    "relUrl": "/be-rBY/user/onboarding.html"
  },"4032": {
    "doc": "Начало работы",
    "title": "First Launch",
    "content": "When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. Welcome Screen . The welcome screen introduces Meshtastic with three feature rows: . |   |   | . | Stay Connected Anywhere | Communicate off-the-grid with your friends and community without cell service. | . | Create Your Own Networks | Easily set up private mesh networks for secure and reliable communication in remote areas. | . | Track and Share Locations | Share your location in real-time and keep your group coordinated with integrated GPS features. | . Tap Get started to proceed through the setup flow. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/onboarding.html#first-launch",
    
    "relUrl": "/be-rBY/user/onboarding.html#first-launch"
  },"4033": {
    "doc": "Начало работы",
    "title": "Permissions",
    "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/onboarding.html#permissions",
    
    "relUrl": "/be-rBY/user/onboarding.html#permissions"
  },"4034": {
    "doc": "Начало работы",
    "title": "After Setup",
    "content": "After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions. 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own. Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/onboarding.html#after-setup",
    
    "relUrl": "/be-rBY/user/onboarding.html#after-setup"
  },"4035": {
    "doc": "Начало работы",
    "title": "Related Topics",
    "content": ". | Connections — pair your first radio | Messages & Channels — send your first message | Nodes — see who else is on your mesh | Map & Waypoints — view node positions | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/onboarding.html#related-topics",
    
    "relUrl": "/be-rBY/user/onboarding.html#related-topics"
  },"4036": {
    "doc": "Come iniziare",
    "title": "Come iniziare",
    "content": "This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/onboarding.html",
    
    "relUrl": "/it-rIT/user/onboarding.html"
  },"4037": {
    "doc": "Come iniziare",
    "title": "First Launch",
    "content": "When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. Welcome Screen . The welcome screen introduces Meshtastic with three feature rows: . |   |   | . | Stay Connected Anywhere | Comunica off-grid con i tuoi amici e la tua comunità senza la connessione cellulare. | . | Create Your Own Networks | Crea reti mesh private in modo semplice per connessioni sicure e affidabili in zone remote. | . | Track and Share Locations | Condividi la tua posizione in tempo reale e mantieni il tuo gruppo coordinato con le funzionalità GPS integrate. | . Tap Get started to proceed through the setup flow. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/onboarding.html#first-launch",
    
    "relUrl": "/it-rIT/user/onboarding.html#first-launch"
  },"4038": {
    "doc": "Come iniziare",
    "title": "Permissions",
    "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/onboarding.html#permissions",
    
    "relUrl": "/it-rIT/user/onboarding.html#permissions"
  },"4039": {
    "doc": "Come iniziare",
    "title": "After Setup",
    "content": "After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions. 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own. Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/onboarding.html#after-setup",
    
    "relUrl": "/it-rIT/user/onboarding.html#after-setup"
  },"4040": {
    "doc": "Come iniziare",
    "title": "Related Topics",
    "content": ". | Connections — pair your first radio | Messages & Channels — send your first message | Nodes — see who else is on your mesh | Map & Waypoints — view node positions | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/onboarding.html#related-topics",
    
    "relUrl": "/it-rIT/user/onboarding.html#related-topics"
  },"4041": {
    "doc": "Primeros Pasos",
    "title": "Primeros Pasos",
    "content": "This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later. ",
    "url": "/Meshtastic-Android/main/es-rES/user/onboarding.html",
    
    "relUrl": "/es-rES/user/onboarding.html"
  },"4042": {
    "doc": "Primeros Pasos",
    "title": "First Launch",
    "content": "When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. Welcome Screen . The welcome screen introduces Meshtastic with three feature rows: . |   |   | . | Stay Connected Anywhere | Communicate off-the-grid with your friends and community without cell service. | . | Create Your Own Networks | Easily set up private mesh networks for secure and reliable communication in remote areas. | . | Track and Share Locations | Comparte tu ubicación en tiempo real y mantén tu grupo coordinado con las características integradas del GPS. | . Tap Get started to proceed through the setup flow. ",
    "url": "/Meshtastic-Android/main/es-rES/user/onboarding.html#first-launch",
    
    "relUrl": "/es-rES/user/onboarding.html#first-launch"
  },"4043": {
    "doc": "Primeros Pasos",
    "title": "Permissions",
    "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
    "url": "/Meshtastic-Android/main/es-rES/user/onboarding.html#permissions",
    
    "relUrl": "/es-rES/user/onboarding.html#permissions"
  },"4044": {
    "doc": "Primeros Pasos",
    "title": "After Setup",
    "content": "After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions. 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own. Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup. ",
    "url": "/Meshtastic-Android/main/es-rES/user/onboarding.html#after-setup",
    
    "relUrl": "/es-rES/user/onboarding.html#after-setup"
  },"4045": {
    "doc": "Primeros Pasos",
    "title": "Related Topics",
    "content": ". | Connections — pair your first radio | Messages & Channels — send your first message | Nodes — see who else is on your mesh | Map & Waypoints — view node positions | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/onboarding.html#related-topics",
    
    "relUrl": "/es-rES/user/onboarding.html#related-topics"
  },"4046": {
    "doc": "Getting Started",
    "title": "Getting Started",
    "content": "This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/onboarding.html",
    
    "relUrl": "/sl-rSI/user/onboarding.html"
  },"4047": {
    "doc": "Getting Started",
    "title": "First Launch",
    "content": "When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. Welcome Screen . The welcome screen introduces Meshtastic with three feature rows: . |   |   | . | Stay Connected Anywhere | Communicate off-the-grid with your friends and community without cell service. | . | Create Your Own Networks | Easily set up private mesh networks for secure and reliable communication in remote areas. | . | Track and Share Locations | Share your location in real-time and keep your group coordinated with integrated GPS features. | . Tap Get started to proceed through the setup flow. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/onboarding.html#first-launch",
    
    "relUrl": "/sl-rSI/user/onboarding.html#first-launch"
  },"4048": {
    "doc": "Getting Started",
    "title": "Permissions",
    "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/onboarding.html#permissions",
    
    "relUrl": "/sl-rSI/user/onboarding.html#permissions"
  },"4049": {
    "doc": "Getting Started",
    "title": "After Setup",
    "content": "After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions. 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own. Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/onboarding.html#after-setup",
    
    "relUrl": "/sl-rSI/user/onboarding.html#after-setup"
  },"4050": {
    "doc": "Getting Started",
    "title": "Related Topics",
    "content": ". | Connections — pair your first radio | Messages & Channels — send your first message | Nodes — see who else is on your mesh | Map & Waypoints — view node positions | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/onboarding.html#related-topics",
    
    "relUrl": "/sl-rSI/user/onboarding.html#related-topics"
  },"4051": {
    "doc": "Getting Started",
    "title": "Getting Started",
    "content": "This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/onboarding.html",
    
    "relUrl": "/no-rNO/user/onboarding.html"
  },"4052": {
    "doc": "Getting Started",
    "title": "First Launch",
    "content": "When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. Welcome Screen . The welcome screen introduces Meshtastic with three feature rows: . |   |   | . | Stay Connected Anywhere | Communicate off-the-grid with your friends and community without cell service. | . | Create Your Own Networks | Easily set up private mesh networks for secure and reliable communication in remote areas. | . | Track and Share Locations | Share your location in real-time and keep your group coordinated with integrated GPS features. | . Tap Get started to proceed through the setup flow. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/onboarding.html#first-launch",
    
    "relUrl": "/no-rNO/user/onboarding.html#first-launch"
  },"4053": {
    "doc": "Getting Started",
    "title": "Permissions",
    "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/onboarding.html#permissions",
    
    "relUrl": "/no-rNO/user/onboarding.html#permissions"
  },"4054": {
    "doc": "Getting Started",
    "title": "After Setup",
    "content": "After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions. 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own. Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/onboarding.html#after-setup",
    
    "relUrl": "/no-rNO/user/onboarding.html#after-setup"
  },"4055": {
    "doc": "Getting Started",
    "title": "Related Topics",
    "content": ". | Connections — pair your first radio | Messages & Channels — send your first message | Nodes — see who else is on your mesh | Map & Waypoints — view node positions | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/onboarding.html#related-topics",
    
    "relUrl": "/no-rNO/user/onboarding.html#related-topics"
  },"4056": {
    "doc": "Getting Started",
    "title": "Getting Started",
    "content": "This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/onboarding.html",
    
    "relUrl": "/hu-rHU/user/onboarding.html"
  },"4057": {
    "doc": "Getting Started",
    "title": "First Launch",
    "content": "When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. Welcome Screen . The welcome screen introduces Meshtastic with three feature rows: . |   |   | . | Stay Connected Anywhere | Kommunikálj a barátaiddal és a közösségeddel mobilhálózat nélkül, a hálózaton kívül is. | . | Create Your Own Networks | Egyszerűen állíts be privát mesh hálózatokat a biztonságos és megbízható kommunikáció érdekében távoli területeken. | . | Track and Share Locations | Oszd meg a helyzeted valós időben, és tartsd összehangoltan a csoportot a beépített GPS-funkciókkal. | . Tap Get started to proceed through the setup flow. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/onboarding.html#first-launch",
    
    "relUrl": "/hu-rHU/user/onboarding.html#first-launch"
  },"4058": {
    "doc": "Getting Started",
    "title": "Permissions",
    "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/onboarding.html#permissions",
    
    "relUrl": "/hu-rHU/user/onboarding.html#permissions"
  },"4059": {
    "doc": "Getting Started",
    "title": "After Setup",
    "content": "After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions. 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own. Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/onboarding.html#after-setup",
    
    "relUrl": "/hu-rHU/user/onboarding.html#after-setup"
  },"4060": {
    "doc": "Getting Started",
    "title": "Related Topics",
    "content": ". | Connections — pair your first radio | Messages & Channels — send your first message | Nodes — see who else is on your mesh | Map & Waypoints — view node positions | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/onboarding.html#related-topics",
    
    "relUrl": "/hu-rHU/user/onboarding.html#related-topics"
  },"4061": {
    "doc": "Начало работы",
    "title": "Начало работы",
    "content": "На этой странице рассказывается о процессе первого запуска приложения Meshtastic для Android, для чего нужно каждое разрешение и как вернуться к нему позже. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/onboarding.html",
    
    "relUrl": "/ru-rRU/user/onboarding.html"
  },"4062": {
    "doc": "Начало работы",
    "title": "Первый запуск",
    "content": "Когда ты открываешь приложение впервые, оно проводит тебя через вводный процесс, который настраивает необходимые разрешения и параметры. Выполни каждый шаг по порядку или пропусти — здесь ничто не является одноразовым предложением. Каждое разрешение можно просмотреть и выдать позже в разделе Разрешения в Настройках внутри приложения. Экран приветствия . Экран приветствия знакомит с Meshtastic с тремя рядами функций: . |   |   | . | Будь на связи везде | Общайтесь вне сети со своими друзьями и сообществом без использования сотовой связи. | . | Создавай свои собственные сети | Легко создать частные сети для защищённой и надежной связи в удаленных районах. | . | Отслеживай и делись местоположением | Делитесь своим местоположением в режиме реального времени и поддерживайте работу группы с функциями GPS. | . Нажми Начать, чтобы пройти процесс настройки. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/onboarding.html#%D0%BF%D0%B5%D1%80%D0%B2%D1%8B%D0%B9-%D0%B7%D0%B0%D0%BF%D1%83%D1%81%D0%BA",
    
    "relUrl": "/ru-rRU/user/onboarding.html#первый-запуск"
  },"4063": {
    "doc": "Начало работы",
    "title": "Разрешения",
    "content": "Приложение запрашивает несколько разрешений во время настройки. Каждое из них служит определенной цели, и некоторые необходимы для основной функциональности. Разрешения Bluetooth . Bluetooth — это основной способ подключения твоего телефона к радиостанции Meshtastic. Экран Bluetooth показывает, что даёт тебе это разрешение: . | Обнаружение — найди и определи устройства Meshtastic рядом с тобой. | Настройки — управляйте параметрами устройства и каналами по беспроводной сети. | . На Android 12 и новее система спрашивает один раз про ближайшие устройства, и это разрешение покрывает и сканирование, и подключение. Без него придётся использовать USB или TCP-соединения. Разрешение на доступ к местоположению . ℹ️ Примечание: Для Bluetooth на Android 12 и выше местоположение не требуется. Android 11 и старше показывают один шаг для местоположения на экране Bluetooth, а не два — эти версии рассматривают сканирование Bluetooth как функцию определения местоположения, поэтому приложение запрашивает доступ к Местоположению вместо “Ближайшие устройства”. Если спросить дважды, это приведёт к тому, что Android вообще перестанет показывать диалог (второй отказ на Android 11; галочка “Больше не спрашивать” на Android 10 и старее). На Android 12 и новее это два разных момента: “Ближайшие устройства” объявлены как neverForLocation, и отказ от доступа к местоположению не мешает находить или подключаться к радио. Meshtastic также использует местоположение для: . | Показ вашего положения на карте | Вычисление расстояний до других нод | Обмен GPS-координатами с другими участниками сети (если включено) | . Предоставьте “При использовании приложения”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Разрешение на уведомления . Уведомления оповещают тебя о: . | Входящие сообщения из каналов и личных сообщений | Новые ноды, присоединившиеся к сети | Низкий заряд на удаленной ноде | . 💡 Совет: Ты можешь тонко настроить уведомления позже в настройках системы — приложение создает отдельный канал уведомлений по категориям (плюс несколько внутренних, как фоновая служба), поэтому ты можешь включить или заглушить их по отдельности. Разрешение на критические уведомления . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | Состояние | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Ничего — разрешения на твоём устройстве нет | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. Подсказка уведомлений есть только на Android 13 и новее — на более старых версиях уведомления включены по умолчанию и ими управляют через настройки самого Android. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/onboarding.html#%D1%80%D0%B0%D0%B7%D1%80%D0%B5%D1%88%D0%B5%D0%BD%D0%B8%D1%8F",
    
    "relUrl": "/ru-rRU/user/onboarding.html#разрешения"
  },"4064": {
    "doc": "Начало работы",
    "title": "После настройки",
    "content": "После предоставления разрешений, приложение открывает основной интерфейс. Ваше первое действие должно заключаться в подключении к радиостанции Meshtastic — см. Подключения для подробных инструкций. 💡 Совет: Если ты пропустил какие-либо разрешения при настройке, открой раздел Разрешения в Настройках приложения. Там перечислены все разрешения во время работы с их текущим состоянием и возможностью вернуться к ним — включая уведомления, на которые система сама больше не будет выдавать запрос второй раз. Возможности также спрашивают в контексте. На вкладке Подключение карточка над списком устройств объясняет, для чего нужен доступ к Bluetooth, и предлагает Предоставить доступ; как только Android перестанет показывать подсказки, эта кнопка станет Открыть настройки. Новичок в Meshtastic? Руководство по началу работы на meshtastic.org охватывает выбор оборудования, начальную настройку радиостанции и первую установку сети. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/onboarding.html#%D0%BF%D0%BE%D1%81%D0%BB%D0%B5-%D0%BD%D0%B0%D1%81%D1%82%D1%80%D0%BE%D0%B9%D0%BA%D0%B8",
    
    "relUrl": "/ru-rRU/user/onboarding.html#после-настройки"
  },"4065": {
    "doc": "Начало работы",
    "title": "Связанные темы",
    "content": ". | Подключения — подключи своё первое радиоустройство | Сообщения и каналы — отправь своё первое сообщение | Ноды — посмотри, кто ещё в твоей сети | Карта и контрольные точки — просмотр позиций нод | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/onboarding.html#%D1%81%D0%B2%D1%8F%D0%B7%D0%B0%D0%BD%D0%BD%D1%8B%D0%B5-%D1%82%D0%B5%D0%BC%D1%8B",
    
    "relUrl": "/ru-rRU/user/onboarding.html#связанные-темы"
  },"4066": {
    "doc": "Getting Started",
    "title": "Getting Started",
    "content": "This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/onboarding.html",
    
    "relUrl": "/cs-rCZ/user/onboarding.html"
  },"4067": {
    "doc": "Getting Started",
    "title": "First Launch",
    "content": "When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. Welcome Screen . The welcome screen introduces Meshtastic with three feature rows: . |   |   | . | Stay Connected Anywhere | Komunikujte off-the-grid s přáteli a komunitou bez mobilních služeb. | . | Create Your Own Networks | Jednoduché nastavení soukromých mesh sítí pro bezpečnou a spolehlivou komunikaci i v odlehlých místech. | . | Track and Share Locations | Sdílejte svou polohu v reálném čase a udržujte svou skupinu koordinovanou díky integrovaným funkcím GPS. | . Tap Get started to proceed through the setup flow. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/onboarding.html#first-launch",
    
    "relUrl": "/cs-rCZ/user/onboarding.html#first-launch"
  },"4068": {
    "doc": "Getting Started",
    "title": "Permissions",
    "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/onboarding.html#permissions",
    
    "relUrl": "/cs-rCZ/user/onboarding.html#permissions"
  },"4069": {
    "doc": "Getting Started",
    "title": "After Setup",
    "content": "After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions. 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own. Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/onboarding.html#after-setup",
    
    "relUrl": "/cs-rCZ/user/onboarding.html#after-setup"
  },"4070": {
    "doc": "Getting Started",
    "title": "Related Topics",
    "content": ". | Connections — pair your first radio | Messages & Channels — send your first message | Nodes — see who else is on your mesh | Map & Waypoints — view node positions | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/onboarding.html#related-topics",
    
    "relUrl": "/cs-rCZ/user/onboarding.html#related-topics"
  },"4071": {
    "doc": "Първи стъпки",
    "title": "Първи стъпки",
    "content": "This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/onboarding.html",
    
    "relUrl": "/bg-rBG/user/onboarding.html"
  },"4072": {
    "doc": "Първи стъпки",
    "title": "First Launch",
    "content": "When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. Welcome Screen . The welcome screen introduces Meshtastic with three feature rows: . |   |   | . | Stay Connected Anywhere | Комуникирайте извън мрежата с вашите приятели и общността без клетъчна услуга. | . | Create Your Own Networks | Настройте лесно частни mesh мрежи за сигурна и надеждна комуникация в отдалечени райони. | . | Track and Share Locations | Споделяйте местоположението си в реално време и координирайте групата си с вградени GPS функции. | . Tap Get started to proceed through the setup flow. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/onboarding.html#first-launch",
    
    "relUrl": "/bg-rBG/user/onboarding.html#first-launch"
  },"4073": {
    "doc": "Първи стъпки",
    "title": "Permissions",
    "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | Състояние | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/onboarding.html#permissions",
    
    "relUrl": "/bg-rBG/user/onboarding.html#permissions"
  },"4074": {
    "doc": "Първи стъпки",
    "title": "After Setup",
    "content": "After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions. 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own. Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/onboarding.html#after-setup",
    
    "relUrl": "/bg-rBG/user/onboarding.html#after-setup"
  },"4075": {
    "doc": "Първи стъпки",
    "title": "Свързани теми",
    "content": ". | Connections — pair your first radio | Messages & Channels — send your first message | Nodes — see who else is on your mesh | Map & Waypoints — view node positions | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/onboarding.html#%D1%81%D0%B2%D1%8A%D1%80%D0%B7%D0%B0%D0%BD%D0%B8-%D1%82%D0%B5%D0%BC%D0%B8",
    
    "relUrl": "/bg-rBG/user/onboarding.html#свързани-теми"
  },"4076": {
    "doc": "Getting Started",
    "title": "Getting Started",
    "content": "This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/onboarding.html",
    
    "relUrl": "/ga-rIE/user/onboarding.html"
  },"4077": {
    "doc": "Getting Started",
    "title": "First Launch",
    "content": "When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. Welcome Screen . The welcome screen introduces Meshtastic with three feature rows: . |   |   | . | Stay Connected Anywhere | Communicate off-the-grid with your friends and community without cell service. | . | Create Your Own Networks | Easily set up private mesh networks for secure and reliable communication in remote areas. | . | Track and Share Locations | Share your location in real-time and keep your group coordinated with integrated GPS features. | . Tap Get started to proceed through the setup flow. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/onboarding.html#first-launch",
    
    "relUrl": "/ga-rIE/user/onboarding.html#first-launch"
  },"4078": {
    "doc": "Getting Started",
    "title": "Permissions",
    "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/onboarding.html#permissions",
    
    "relUrl": "/ga-rIE/user/onboarding.html#permissions"
  },"4079": {
    "doc": "Getting Started",
    "title": "After Setup",
    "content": "After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions. 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own. Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/onboarding.html#after-setup",
    
    "relUrl": "/ga-rIE/user/onboarding.html#after-setup"
  },"4080": {
    "doc": "Getting Started",
    "title": "Related Topics",
    "content": ". | Connections — pair your first radio | Messages & Channels — send your first message | Nodes — see who else is on your mesh | Map & Waypoints — view node positions | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/onboarding.html#related-topics",
    
    "relUrl": "/ga-rIE/user/onboarding.html#related-topics"
  },"4081": {
    "doc": "Getting Started",
    "title": "Getting Started",
    "content": "This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/onboarding.html",
    
    "relUrl": "/fr-rCA/user/onboarding.html"
  },"4082": {
    "doc": "Getting Started",
    "title": "First Launch",
    "content": "When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. Welcome Screen . The welcome screen introduces Meshtastic with three feature rows: . |   |   | . | Stay Connected Anywhere | Communiquez en dehors du réseau avec vos amis et votre communauté sans service cellulaire. | . | Create Your Own Networks | Installez facilement des réseaux de maillage privé pour une communication sûre et fiable dans les régions éloignées. | . | Track and Share Locations | Partagez votre position en temps réel et gardez votre groupe coordonné avec les fonctionnalités GPS intégrées. | . Tap Get started to proceed through the setup flow. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/onboarding.html#first-launch",
    
    "relUrl": "/fr-rCA/user/onboarding.html#first-launch"
  },"4083": {
    "doc": "Getting Started",
    "title": "Permissions",
    "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/onboarding.html#permissions",
    
    "relUrl": "/fr-rCA/user/onboarding.html#permissions"
  },"4084": {
    "doc": "Getting Started",
    "title": "After Setup",
    "content": "After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions. 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own. Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/onboarding.html#after-setup",
    
    "relUrl": "/fr-rCA/user/onboarding.html#after-setup"
  },"4085": {
    "doc": "Getting Started",
    "title": "Related Topics",
    "content": ". | Connections — pair your first radio | Messages & Channels — send your first message | Nodes — see who else is on your mesh | Map & Waypoints — view node positions | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/onboarding.html#related-topics",
    
    "relUrl": "/fr-rCA/user/onboarding.html#related-topics"
  },"4086": {
    "doc": "Getting Started",
    "title": "Getting Started",
    "content": "This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later. ",
    "url": "/Meshtastic-Android/main/srp/user/onboarding.html",
    
    "relUrl": "/srp/user/onboarding.html"
  },"4087": {
    "doc": "Getting Started",
    "title": "First Launch",
    "content": "When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. Welcome Screen . The welcome screen introduces Meshtastic with three feature rows: . |   |   | . | Stay Connected Anywhere | Communicate off-the-grid with your friends and community without cell service. | . | Create Your Own Networks | Easily set up private mesh networks for secure and reliable communication in remote areas. | . | Track and Share Locations | Share your location in real-time and keep your group coordinated with integrated GPS features. | . Tap Get started to proceed through the setup flow. ",
    "url": "/Meshtastic-Android/main/srp/user/onboarding.html#first-launch",
    
    "relUrl": "/srp/user/onboarding.html#first-launch"
  },"4088": {
    "doc": "Getting Started",
    "title": "Permissions",
    "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
    "url": "/Meshtastic-Android/main/srp/user/onboarding.html#permissions",
    
    "relUrl": "/srp/user/onboarding.html#permissions"
  },"4089": {
    "doc": "Getting Started",
    "title": "After Setup",
    "content": "After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions. 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own. Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup. ",
    "url": "/Meshtastic-Android/main/srp/user/onboarding.html#after-setup",
    
    "relUrl": "/srp/user/onboarding.html#after-setup"
  },"4090": {
    "doc": "Getting Started",
    "title": "Related Topics",
    "content": ". | Connections — pair your first radio | Messages & Channels — send your first message | Nodes — see who else is on your mesh | Map & Waypoints — view node positions | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/srp/user/onboarding.html#related-topics",
    
    "relUrl": "/srp/user/onboarding.html#related-topics"
  },"4091": {
    "doc": "Getting Started",
    "title": "Getting Started",
    "content": "This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/onboarding.html",
    
    "relUrl": "/ca-rES/user/onboarding.html"
  },"4092": {
    "doc": "Getting Started",
    "title": "First Launch",
    "content": "When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. Welcome Screen . The welcome screen introduces Meshtastic with three feature rows: . |   |   | . | Stay Connected Anywhere | Communicate off-the-grid with your friends and community without cell service. | . | Create Your Own Networks | Easily set up private mesh networks for secure and reliable communication in remote areas. | . | Track and Share Locations | Share your location in real-time and keep your group coordinated with integrated GPS features. | . Tap Get started to proceed through the setup flow. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/onboarding.html#first-launch",
    
    "relUrl": "/ca-rES/user/onboarding.html#first-launch"
  },"4093": {
    "doc": "Getting Started",
    "title": "Permissions",
    "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/onboarding.html#permissions",
    
    "relUrl": "/ca-rES/user/onboarding.html#permissions"
  },"4094": {
    "doc": "Getting Started",
    "title": "After Setup",
    "content": "After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions. 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own. Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/onboarding.html#after-setup",
    
    "relUrl": "/ca-rES/user/onboarding.html#after-setup"
  },"4095": {
    "doc": "Getting Started",
    "title": "Related Topics",
    "content": ". | Connections — pair your first radio | Messages & Channels — send your first message | Nodes — see who else is on your mesh | Map & Waypoints — view node positions | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/onboarding.html#related-topics",
    
    "relUrl": "/ca-rES/user/onboarding.html#related-topics"
  },"4096": {
    "doc": "Getting Started",
    "title": "Getting Started",
    "content": "This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/onboarding.html",
    
    "relUrl": "/ko-rKR/user/onboarding.html"
  },"4097": {
    "doc": "Getting Started",
    "title": "First Launch",
    "content": "When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. Welcome Screen . The welcome screen introduces Meshtastic with three feature rows: . |   |   | . | Stay Connected Anywhere | Communicate off-the-grid with your friends and community without cell service. | . | Create Your Own Networks | Easily set up private mesh networks for secure and reliable communication in remote areas. | . | Track and Share Locations | Share your location in real-time and keep your group coordinated with integrated GPS features. | . Tap Get started to proceed through the setup flow. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/onboarding.html#first-launch",
    
    "relUrl": "/ko-rKR/user/onboarding.html#first-launch"
  },"4098": {
    "doc": "Getting Started",
    "title": "Permissions",
    "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/onboarding.html#permissions",
    
    "relUrl": "/ko-rKR/user/onboarding.html#permissions"
  },"4099": {
    "doc": "Getting Started",
    "title": "After Setup",
    "content": "After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions. 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own. Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/onboarding.html#after-setup",
    
    "relUrl": "/ko-rKR/user/onboarding.html#after-setup"
  },"4100": {
    "doc": "Getting Started",
    "title": "Related Topics",
    "content": ". | Connections — pair your first radio | Messages & Channels — send your first message | Nodes — see who else is on your mesh | Map & Waypoints — view node positions | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/onboarding.html#related-topics",
    
    "relUrl": "/ko-rKR/user/onboarding.html#related-topics"
  },"4101": {
    "doc": "Kom igång",
    "title": "Kom igång",
    "content": "This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/onboarding.html",
    
    "relUrl": "/sv-rSE/user/onboarding.html"
  },"4102": {
    "doc": "Kom igång",
    "title": "First Launch",
    "content": "When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. Welcome Screen . The welcome screen introduces Meshtastic with three feature rows: . |   |   | . | Stay Connected Anywhere | Kommunicera med din släkt och dina vänner utan online- och mobiltjänster. | . | Create Your Own Networks | Konfigurera enkelt privata nätverk för säker och tillförlitlig kommunikation i avlägsna områden. | . | Track and Share Locations | Dela din plats i realtid och håll din grupp samordnad med integrerade GPS-funktioner. | . Tap Get started to proceed through the setup flow. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/onboarding.html#first-launch",
    
    "relUrl": "/sv-rSE/user/onboarding.html#first-launch"
  },"4103": {
    "doc": "Kom igång",
    "title": "Permissions",
    "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/onboarding.html#permissions",
    
    "relUrl": "/sv-rSE/user/onboarding.html#permissions"
  },"4104": {
    "doc": "Kom igång",
    "title": "After Setup",
    "content": "After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions. 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own. Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/onboarding.html#after-setup",
    
    "relUrl": "/sv-rSE/user/onboarding.html#after-setup"
  },"4105": {
    "doc": "Kom igång",
    "title": "Related Topics",
    "content": ". | Connections — pair your first radio | Messages & Channels — send your first message | Nodes — see who else is on your mesh | Map & Waypoints — view node positions | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/onboarding.html#related-topics",
    
    "relUrl": "/sv-rSE/user/onboarding.html#related-topics"
  },"4106": {
    "doc": "Getting Started",
    "title": "Getting Started",
    "content": "This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/onboarding.html",
    
    "relUrl": "/ht-rHT/user/onboarding.html"
  },"4107": {
    "doc": "Getting Started",
    "title": "First Launch",
    "content": "When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. Welcome Screen . The welcome screen introduces Meshtastic with three feature rows: . |   |   | . | Stay Connected Anywhere | Communicate off-the-grid with your friends and community without cell service. | . | Create Your Own Networks | Easily set up private mesh networks for secure and reliable communication in remote areas. | . | Track and Share Locations | Share your location in real-time and keep your group coordinated with integrated GPS features. | . Tap Get started to proceed through the setup flow. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/onboarding.html#first-launch",
    
    "relUrl": "/ht-rHT/user/onboarding.html#first-launch"
  },"4108": {
    "doc": "Getting Started",
    "title": "Permissions",
    "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/onboarding.html#permissions",
    
    "relUrl": "/ht-rHT/user/onboarding.html#permissions"
  },"4109": {
    "doc": "Getting Started",
    "title": "After Setup",
    "content": "After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions. 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own. Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/onboarding.html#after-setup",
    
    "relUrl": "/ht-rHT/user/onboarding.html#after-setup"
  },"4110": {
    "doc": "Getting Started",
    "title": "Related Topics",
    "content": ". | Connections — pair your first radio | Messages & Channels — send your first message | Nodes — see who else is on your mesh | Map & Waypoints — view node positions | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/onboarding.html#related-topics",
    
    "relUrl": "/ht-rHT/user/onboarding.html#related-topics"
  },"4111": {
    "doc": "Getting Started",
    "title": "Getting Started",
    "content": "This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/onboarding.html",
    
    "relUrl": "/sr-rLatn/user/onboarding.html"
  },"4112": {
    "doc": "Getting Started",
    "title": "First Launch",
    "content": "When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. Welcome Screen . The welcome screen introduces Meshtastic with three feature rows: . |   |   | . | Stay Connected Anywhere | Communicate off-the-grid with your friends and community without cell service. | . | Create Your Own Networks | Easily set up private mesh networks for secure and reliable communication in remote areas. | . | Track and Share Locations | Share your location in real-time and keep your group coordinated with integrated GPS features. | . Tap Get started to proceed through the setup flow. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/onboarding.html#first-launch",
    
    "relUrl": "/sr-rLatn/user/onboarding.html#first-launch"
  },"4113": {
    "doc": "Getting Started",
    "title": "Permissions",
    "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/onboarding.html#permissions",
    
    "relUrl": "/sr-rLatn/user/onboarding.html#permissions"
  },"4114": {
    "doc": "Getting Started",
    "title": "After Setup",
    "content": "After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions. 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own. Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/onboarding.html#after-setup",
    
    "relUrl": "/sr-rLatn/user/onboarding.html#after-setup"
  },"4115": {
    "doc": "Getting Started",
    "title": "Related Topics",
    "content": ". | Connections — pair your first radio | Messages & Channels — send your first message | Nodes — see who else is on your mesh | Map & Waypoints — view node positions | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/onboarding.html#related-topics",
    
    "relUrl": "/sr-rLatn/user/onboarding.html#related-topics"
  },"4116": {
    "doc": "Getting Started",
    "title": "Getting Started",
    "content": "This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/onboarding.html",
    
    "relUrl": "/nl-rNL/user/onboarding.html"
  },"4117": {
    "doc": "Getting Started",
    "title": "First Launch",
    "content": "When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. Welcome Screen . The welcome screen introduces Meshtastic with three feature rows: . |   |   | . | Stay Connected Anywhere | Communicate off-the-grid with your friends and community without cell service. | . | Create Your Own Networks | Easily set up private mesh networks for secure and reliable communication in remote areas. | . | Track and Share Locations | Share your location in real-time and keep your group coordinated with integrated GPS features. | . Tap Get started to proceed through the setup flow. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/onboarding.html#first-launch",
    
    "relUrl": "/nl-rNL/user/onboarding.html#first-launch"
  },"4118": {
    "doc": "Getting Started",
    "title": "Permissions",
    "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/onboarding.html#permissions",
    
    "relUrl": "/nl-rNL/user/onboarding.html#permissions"
  },"4119": {
    "doc": "Getting Started",
    "title": "After Setup",
    "content": "After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions. 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own. Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/onboarding.html#after-setup",
    
    "relUrl": "/nl-rNL/user/onboarding.html#after-setup"
  },"4120": {
    "doc": "Getting Started",
    "title": "Related Topics",
    "content": ". | Connections — pair your first radio | Messages & Channels — send your first message | Nodes — see who else is on your mesh | Map & Waypoints — view node positions | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/onboarding.html#related-topics",
    
    "relUrl": "/nl-rNL/user/onboarding.html#related-topics"
  },"4121": {
    "doc": "Getting Started",
    "title": "Getting Started",
    "content": "This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/onboarding.html",
    
    "relUrl": "/uk-rUA/user/onboarding.html"
  },"4122": {
    "doc": "Getting Started",
    "title": "First Launch",
    "content": "When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. Welcome Screen . The welcome screen introduces Meshtastic with three feature rows: . |   |   | . | Stay Connected Anywhere | Спілкуйтеся з друзями та спільнотою поза мережею, навіть без мобільного зв’язку. | . | Create Your Own Networks | Легко налаштовуйте приватні mesh-мережі для безпечного та надійного зв’язку у віддалених районах. | . | Track and Share Locations | Діліться своїм місцезнаходженням у реальному часі та координуйте групу завдяки вбудованим функціям GPS. | . Tap Get started to proceed through the setup flow. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/onboarding.html#first-launch",
    
    "relUrl": "/uk-rUA/user/onboarding.html#first-launch"
  },"4123": {
    "doc": "Getting Started",
    "title": "Permissions",
    "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/onboarding.html#permissions",
    
    "relUrl": "/uk-rUA/user/onboarding.html#permissions"
  },"4124": {
    "doc": "Getting Started",
    "title": "After Setup",
    "content": "After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions. 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own. Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/onboarding.html#after-setup",
    
    "relUrl": "/uk-rUA/user/onboarding.html#after-setup"
  },"4125": {
    "doc": "Getting Started",
    "title": "Related Topics",
    "content": ". | Connections — pair your first radio | Messages & Channels — send your first message | Nodes — see who else is on your mesh | Map & Waypoints — view node positions | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/onboarding.html#related-topics",
    
    "relUrl": "/uk-rUA/user/onboarding.html#related-topics"
  },"4126": {
    "doc": "Aloittaminen",
    "title": "Aloittaminen",
    "content": "Tällä sivulla kerrotaan Meshtastic Android -sovelluksen ensimmäisen käynnistyksen käyttöönotosta, mitä kukin käyttöoikeus tarkoittaa ja miten niihin voi palata myöhemmin. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/onboarding.html",
    
    "relUrl": "/fi-rFI/user/onboarding.html"
  },"4127": {
    "doc": "Aloittaminen",
    "title": "Ensimmäinen käynnistys",
    "content": "Kun avaat sovelluksen ensimmäisen kerran, se ohjaa sinut käyttöönottoon, jossa määritetään tarvittavat käyttöoikeudet ja asetukset. Suorita vaiheet järjestyksessä tai ohita ne — mikään täällä ei ole kertaluonteinen mahdollisuus. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. Aloitusnäkymä . Tervetulonäkymä esittelee Meshtasticin kolmella ominaisuusrivillä: . |   |   | . | Pysy yhteydessä kaikkialla | Viestitä ilman verkkoyhteyttä ystäviesi ja yhteisösi kanssa ilman matkapuhelinverkkoa. | . | Luo omat verkkosi | Luo vaivattomasti yksityisiä meshtastic verkkoja turvalliseen ja luotettavaan viestintään kaukana asutuista paikoista. | . | Seuraa ja jaa sijainteja | Jaa sijaintisi reaaliaikaisesti ja varmista ryhmäsi yhteistoiminta GPS-toimintojen avulla. | . Napauta Aloita siirtyäksesi käyttöönottoon. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/onboarding.html#ensimm%C3%A4inen-k%C3%A4ynnistys",
    
    "relUrl": "/fi-rFI/user/onboarding.html#ensimmäinen-käynnistys"
  },"4128": {
    "doc": "Aloittaminen",
    "title": "Käyttöoikeudet",
    "content": "Sovellus pyytää määrityksen aikana useita käyttöoikeuksia. Jokaisella niistä on oma tarkoituksensa, ja osa niistä on välttämättömiä perustoimintojen kannalta. Bluetooth-käyttöoikeus . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Sijaintikäyttöoikeus . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Käyttöoikeuden pyytäminen kahdesti voisi johtaa tilanteeseen, jossa Android lakkaa näyttämästä valintaikkunaa kokonaan (toinen hylkäys Android 11:ssä, Älä kysy uudelleen -valintaruutu Android 10:ssä ja sitä vanhemmissa versioissa). Android 12:ssa ja uudemmissa versioissa nämä ovat erillisiä: “Lähistön laitteet” on määritelty asetuksella neverForLocation, eikä sijaintikäyttöoikeuden hylkääminen estä radion löytämistä tai siihen yhdistämistä. Meshtastic käyttää sijaintiasi myös seuraaviin tarkoituksiin: . | Sijaintisi näyttäminen mesh-kartalla | Etäisyyksien laskeminen muihin radioihin | GPS-koordinaattiesi jakaminen muiden verkon jäsenten kanssa (jos käytössä) | . Myönnä Sovelluksen käytön aikana. Sovellus ei pyydä taustasijaintia — sen manifestissa ei ole ACCESS_BACKGROUND_LOCATION-oikeutta — joten Android ei tarjoa Aina-vaihtoehtoa, ja sijaintipäivitykset tapahtuvat sovelluksen ollessa etualalla tai sen suorittaessa taustapalvelua. Sijaintikäyttöoikeuden hylkääminen ei estä sovelluksen muuta toimintaa. Android 12:ssa ja uudemmissa versioissa Bluetooth toimii edelleen, ja vain kartta, sijainnin näyttäminen ja sijainnin jakaminen poistuvat käytöstä. Android 11:ssä ja uudemmissa versioissa myös Bluetooth-skannaus estyy, koska Android liittää sen tähän käyttöoikeuteen — lisäksi järjestelmän Sijaintipalvelut on oltava käytössä, jotta skannaus palauttaa tuloksia. Ilmoituskäyttöoikeus . Ilmoitukset kertovat sinulle: . | Saapuvista viesteistä kanavilta ja yksityisviesteistä | Uusista mesh-verkkoon liittyvistä radioista | Etäradion akun vähäisestä virrasta | . 💡 Vinkki: Voit myöhemmin säätää ilmoitusasetuksia Androidin järjestelmäasetuksissa. Sovellus luo jokaiselle ilmoitusluokalle oman ilmoituskanavan (sekä muutamia sisäisiä kanavia, kuten taustapalvelulle), joten voit ottaa ne käyttöön tai mykistää ne yksitellen. Kriittisten hälytysten käyttöoikeus . Kriittiset hälytykset ovat korkean prioriteetin ilmoituksia, jotka ohittavat Älä häiritse -tilan — niitä käytetään mesh-verkon hätähälytyksiin ja kiireellisiin viesteihin. Tämä vaihe ei ole käyttöoikeuspyyntö. Hyväksy/hylkää-valintaikkunaa ei ole: painike avaa Androidin järjestelmäasetusten sivun sovelluksen Hälytykset-ilmoituskanavalle, jossa voit itse ottaa käyttöön Älä häiritse -tilan ohituksen. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Käyttöoikeuksien tarkistaminen myöhemmin . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | Tila | Mitä rivin napauttaminen tekee | . | Sallittu | Avaa järjestelmän sivun, jossa voit tarkistaa tai peruuttaa käyttöoikeuden | . | Ei kysytty vielä | Pyytää sitä | . | Estetty - napauta salliaksesi | Selittää, mihin käyttöoikeutta tarvitaan, ja pyytää sitä uudelleen, jos hyväksyt | . | Estetty - napauta avataksesi järjestelmäasetukset | Android ei enää näytä käyttöoikeusikkunaa, joten tämä avaa sivun, jossa voit ottaa käyttöoikeuden uudelleen käyttöön | . | Ei tarvita tässä Android-versiossa | Ei mitään – tätä käyttöoikeutta ei ole laitteessasi | . Tämä koskee erityisesti ilmoituksia. Jos hylkäät ne käyttöönoton aikana, tämä rivi toimii paluutienä: Android lakkaa näyttämästä valintaikkunaa, kun olet hylännyt pyynnön lopullisesti (toinen hylkäys), jolloin tämän rivin tilaksi vaihtuu Estetty ja se avaa sen sijaan järjestelmäasetukset. Ilmoituskäyttöoikeutta pyydetään vain Android 13:ssa ja uudemmissa versioissa — vanhemmissa versioissa ilmoitukset ovat oletusarvoisesti käytössä ja niitä hallitaan Androidin omista asetuksista. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/onboarding.html#k%C3%A4ytt%C3%B6oikeudet",
    
    "relUrl": "/fi-rFI/user/onboarding.html#käyttöoikeudet"
  },"4129": {
    "doc": "Aloittaminen",
    "title": "Määrityksen jälkeen",
    "content": "Kun olet myöntänyt käyttöoikeudet, sovellus avaa pääkäyttöliittymän. Ensimmäinen toimenpiteesi pitäisi olla yhteyden muodostaminen Meshtastic-radioon — katso Yhteydet yksityiskohtaisia ohjeita varten. 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Kaikki käyttöaikaiset käyttöoikeudet näkyvät siellä nykyisessä tilassaan sekä linkkinä niiden hallintaan, mukaan lukien ilmoitukset, joita järjestelmä ei pyydä toista kertaa automaattisesti. Sovelluksen toiminnot pyytävät käyttöoikeuksia myös tarpeen mukaan. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. Uusi Meshtasticissa? Aloitusopas meshtastic.org-sivustolla käsittelee laitteiston valintaa, radion alkuasetuksia ja ensimmäisen verkon käyttöönottoa. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/onboarding.html#m%C3%A4%C3%A4rityksen-j%C3%A4lkeen",
    
    "relUrl": "/fi-rFI/user/onboarding.html#määrityksen-jälkeen"
  },"4130": {
    "doc": "Aloittaminen",
    "title": "Aiheeseen liittyvät aiheet",
    "content": ". | Yhteydet — yhdistä ensimmäinen radiosi | Viestit ja kanavat — lähetä ensimmäinen viestisi | Radiot — katso, ketkä muut ovat mesh-verkossasi | Kartta ja reittipisteet — tarkastele radioiden sijainteja | Asetukset — Radio ja käyttäjä — määritä radio ja käyttäjäprofiili | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/onboarding.html#aiheeseen-liittyv%C3%A4t-aiheet",
    
    "relUrl": "/fi-rFI/user/onboarding.html#aiheeseen-liittyvät-aiheet"
  },"4131": {
    "doc": "Getting Started",
    "title": "Getting Started",
    "content": "This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/onboarding.html",
    
    "relUrl": "/is-rIS/user/onboarding.html"
  },"4132": {
    "doc": "Getting Started",
    "title": "First Launch",
    "content": "When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. Welcome Screen . The welcome screen introduces Meshtastic with three feature rows: . |   |   | . | Stay Connected Anywhere | Communicate off-the-grid with your friends and community without cell service. | . | Create Your Own Networks | Easily set up private mesh networks for secure and reliable communication in remote areas. | . | Track and Share Locations | Share your location in real-time and keep your group coordinated with integrated GPS features. | . Tap Get started to proceed through the setup flow. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/onboarding.html#first-launch",
    
    "relUrl": "/is-rIS/user/onboarding.html#first-launch"
  },"4133": {
    "doc": "Getting Started",
    "title": "Permissions",
    "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/onboarding.html#permissions",
    
    "relUrl": "/is-rIS/user/onboarding.html#permissions"
  },"4134": {
    "doc": "Getting Started",
    "title": "After Setup",
    "content": "After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions. 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own. Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/onboarding.html#after-setup",
    
    "relUrl": "/is-rIS/user/onboarding.html#after-setup"
  },"4135": {
    "doc": "Getting Started",
    "title": "Related Topics",
    "content": ". | Connections — pair your first radio | Messages & Channels — send your first message | Nodes — see who else is on your mesh | Map & Waypoints — view node positions | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/onboarding.html#related-topics",
    
    "relUrl": "/is-rIS/user/onboarding.html#related-topics"
  },"4136": {
    "doc": "Getting Started",
    "title": "Getting Started",
    "content": "This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/onboarding.html",
    
    "relUrl": "/lt-rLT/user/onboarding.html"
  },"4137": {
    "doc": "Getting Started",
    "title": "First Launch",
    "content": "When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. Welcome Screen . The welcome screen introduces Meshtastic with three feature rows: . |   |   | . | Stay Connected Anywhere | Communicate off-the-grid with your friends and community without cell service. | . | Create Your Own Networks | Easily set up private mesh networks for secure and reliable communication in remote areas. | . | Track and Share Locations | Share your location in real-time and keep your group coordinated with integrated GPS features. | . Tap Get started to proceed through the setup flow. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/onboarding.html#first-launch",
    
    "relUrl": "/lt-rLT/user/onboarding.html#first-launch"
  },"4138": {
    "doc": "Getting Started",
    "title": "Permissions",
    "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/onboarding.html#permissions",
    
    "relUrl": "/lt-rLT/user/onboarding.html#permissions"
  },"4139": {
    "doc": "Getting Started",
    "title": "After Setup",
    "content": "After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions. 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own. Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/onboarding.html#after-setup",
    
    "relUrl": "/lt-rLT/user/onboarding.html#after-setup"
  },"4140": {
    "doc": "Getting Started",
    "title": "Related Topics",
    "content": ". | Connections — pair your first radio | Messages & Channels — send your first message | Nodes — see who else is on your mesh | Map & Waypoints — view node positions | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/onboarding.html#related-topics",
    
    "relUrl": "/lt-rLT/user/onboarding.html#related-topics"
  },"4141": {
    "doc": "Getting Started",
    "title": "Getting Started",
    "content": "This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/onboarding.html",
    
    "relUrl": "/gl-rES/user/onboarding.html"
  },"4142": {
    "doc": "Getting Started",
    "title": "First Launch",
    "content": "When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. Welcome Screen . The welcome screen introduces Meshtastic with three feature rows: . |   |   | . | Stay Connected Anywhere | Communicate off-the-grid with your friends and community without cell service. | . | Create Your Own Networks | Easily set up private mesh networks for secure and reliable communication in remote areas. | . | Track and Share Locations | Share your location in real-time and keep your group coordinated with integrated GPS features. | . Tap Get started to proceed through the setup flow. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/onboarding.html#first-launch",
    
    "relUrl": "/gl-rES/user/onboarding.html#first-launch"
  },"4143": {
    "doc": "Getting Started",
    "title": "Permissions",
    "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/onboarding.html#permissions",
    
    "relUrl": "/gl-rES/user/onboarding.html#permissions"
  },"4144": {
    "doc": "Getting Started",
    "title": "After Setup",
    "content": "After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions. 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own. Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/onboarding.html#after-setup",
    
    "relUrl": "/gl-rES/user/onboarding.html#after-setup"
  },"4145": {
    "doc": "Getting Started",
    "title": "Related Topics",
    "content": ". | Connections — pair your first radio | Messages & Channels — send your first message | Nodes — see who else is on your mesh | Map & Waypoints — view node positions | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/onboarding.html#related-topics",
    
    "relUrl": "/gl-rES/user/onboarding.html#related-topics"
  },"4146": {
    "doc": "はじめに",
    "title": "はじめに",
    "content": "This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/onboarding.html",
    
    "relUrl": "/ja-rJP/user/onboarding.html"
  },"4147": {
    "doc": "はじめに",
    "title": "初回起動",
    "content": "When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. ようこそ画面 . The welcome screen introduces Meshtastic with three feature rows: . |   |   | . | Stay Connected Anywhere | 携帯電話の電波がなくても、友人やコミュニティとオフグリッドで通信できます。 | . | Create Your Own Networks | 遠隔地での安全で信頼性の高い通信のために、プライベートメッシュネットワークを簡単にセットアップできます。 | . | Track and Share Locations | 統合された GPS 機能で位置情報をリアルタイムに共有し、グループの連携を保ちます。 | . Tap Get started to proceed through the setup flow. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/onboarding.html#%E5%88%9D%E5%9B%9E%E8%B5%B7%E5%8B%95",
    
    "relUrl": "/ja-rJP/user/onboarding.html#初回起動"
  },"4148": {
    "doc": "はじめに",
    "title": "権限",
    "content": "アプリはセットアップ中にいくつかの権限を要求します。それぞれに特定の目的があり、一部は主要な機能に必要です。 . Bluetooth の権限 . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. 位置情報の権限 . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic は、次の目的でも位置情報を使用します： . | メッシュマップ上に自分の位置を表示する | 他のノードまでの距離を計算する | 他のメッシュメンバーと GPS 座標を共有する（有効な場合） | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. 通知の権限 . 通知は、次のことをお知らせします： . | チャンネルおよびダイレクトメッセージの受信 | メッシュに参加する新しいノード | リモートノードのバッテリー低下 | . 💡 ヒント： 通知の設定は、後で Android のシステム設定で細かく調整できます。アプリはカテゴリごとに個別の通知チャンネルを作成する（さらに、バックグラウンドサービスなどの内部用のものもいくつか作成する）ため、個別に有効化したり消音したりできます。 . 重要なアラートの権限 . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | 状態 | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/onboarding.html#%E6%A8%A9%E9%99%90",
    
    "relUrl": "/ja-rJP/user/onboarding.html#権限"
  },"4149": {
    "doc": "はじめに",
    "title": "セットアップ後",
    "content": "After you grant permissions, the app opens the main interface. 最初に行うべきことは、Meshtastic 無線機への接続です。詳しい手順は接続を参照してください。 . 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own. Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. Meshtastic は初めてですか？ meshtastic.org の入門ガイドでは、ハードウェアの選択、無線機の初期設定、最初のメッシュのセットアップについて説明しています。 . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/onboarding.html#%E3%82%BB%E3%83%83%E3%83%88%E3%82%A2%E3%83%83%E3%83%97%E5%BE%8C",
    
    "relUrl": "/ja-rJP/user/onboarding.html#セットアップ後"
  },"4150": {
    "doc": "はじめに",
    "title": "関連トピック",
    "content": ". | Connections — pair your first radio | メッセージとチャンネル：最初のメッセージを送信する | Nodes — see who else is on your mesh | マップとウェイポイント：ノードの位置を表示する | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/onboarding.html#%E9%96%A2%E9%80%A3%E3%83%88%E3%83%94%E3%83%83%E3%82%AF",
    
    "relUrl": "/ja-rJP/user/onboarding.html#関連トピック"
  },"4151": {
    "doc": "Erste Schritte",
    "title": "Erste Schritte",
    "content": "This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/onboarding.html",
    
    "relUrl": "/de-rDE/user/onboarding.html"
  },"4152": {
    "doc": "Erste Schritte",
    "title": "First Launch",
    "content": "When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. Welcome Screen . The welcome screen introduces Meshtastic with three feature rows: . |   |   | . | Stay Connected Anywhere | Kommunizieren Sie außerhalb des Netzwerks mit Ihren Freunden und der Gemeinschaft ohne Mobilfunkdienst. | . | Create Your Own Networks | Leicht einzurichtende, private Netznetze für sichere und zuverlässige Kommunikation in entlegenen Gebieten. | . | Track and Share Locations | Teilen Sie Ihren Standort in Echtzeit und koordinieren Sie Ihre Gruppe mit integrierten GPS Funktionen. | . Tap Get started to proceed through the setup flow. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/onboarding.html#first-launch",
    
    "relUrl": "/de-rDE/user/onboarding.html#first-launch"
  },"4153": {
    "doc": "Erste Schritte",
    "title": "Permissions",
    "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | Status | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/onboarding.html#permissions",
    
    "relUrl": "/de-rDE/user/onboarding.html#permissions"
  },"4154": {
    "doc": "Erste Schritte",
    "title": "After Setup",
    "content": "After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions. 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own. Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. New to Meshtastic? Die Anleitung für den Einstieg auf meshtastic.org behandelt die Hardware-Auswahl, die anfängliche Funkkonfiguration und die Einrichtung deines ersten Mesh-Netzwerks. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/onboarding.html#after-setup",
    
    "relUrl": "/de-rDE/user/onboarding.html#after-setup"
  },"4155": {
    "doc": "Erste Schritte",
    "title": "Verwandte Themen",
    "content": ". | Connections — pair your first radio | Messages & Channels — send your first message | Nodes — see who else is on your mesh | Map & Waypoints — view node positions | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/onboarding.html#verwandte-themen",
    
    "relUrl": "/de-rDE/user/onboarding.html#verwandte-themen"
  },"4156": {
    "doc": "Getting Started",
    "title": "Getting Started",
    "content": "This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/onboarding.html",
    
    "relUrl": "/ar-rSA/user/onboarding.html"
  },"4157": {
    "doc": "Getting Started",
    "title": "First Launch",
    "content": "When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. Welcome Screen . The welcome screen introduces Meshtastic with three feature rows: . |   |   | . | Stay Connected Anywhere | Communicate off-the-grid with your friends and community without cell service. | . | Create Your Own Networks | Easily set up private mesh networks for secure and reliable communication in remote areas. | . | Track and Share Locations | Share your location in real-time and keep your group coordinated with integrated GPS features. | . Tap Get started to proceed through the setup flow. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/onboarding.html#first-launch",
    
    "relUrl": "/ar-rSA/user/onboarding.html#first-launch"
  },"4158": {
    "doc": "Getting Started",
    "title": "Permissions",
    "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/onboarding.html#permissions",
    
    "relUrl": "/ar-rSA/user/onboarding.html#permissions"
  },"4159": {
    "doc": "Getting Started",
    "title": "After Setup",
    "content": "After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions. 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own. Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/onboarding.html#after-setup",
    
    "relUrl": "/ar-rSA/user/onboarding.html#after-setup"
  },"4160": {
    "doc": "Getting Started",
    "title": "Related Topics",
    "content": ". | Connections — pair your first radio | Messages & Channels — send your first message | Nodes — see who else is on your mesh | Map & Waypoints — view node positions | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/onboarding.html#related-topics",
    
    "relUrl": "/ar-rSA/user/onboarding.html#related-topics"
  },"4161": {
    "doc": "Getting Started",
    "title": "Getting Started",
    "content": "This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/onboarding.html",
    
    "relUrl": "/hr-rHR/user/onboarding.html"
  },"4162": {
    "doc": "Getting Started",
    "title": "First Launch",
    "content": "When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. Welcome Screen . The welcome screen introduces Meshtastic with three feature rows: . |   |   | . | Stay Connected Anywhere | Communicate off-the-grid with your friends and community without cell service. | . | Create Your Own Networks | Easily set up private mesh networks for secure and reliable communication in remote areas. | . | Track and Share Locations | Share your location in real-time and keep your group coordinated with integrated GPS features. | . Tap Get started to proceed through the setup flow. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/onboarding.html#first-launch",
    
    "relUrl": "/hr-rHR/user/onboarding.html#first-launch"
  },"4163": {
    "doc": "Getting Started",
    "title": "Permissions",
    "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/onboarding.html#permissions",
    
    "relUrl": "/hr-rHR/user/onboarding.html#permissions"
  },"4164": {
    "doc": "Getting Started",
    "title": "After Setup",
    "content": "After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions. 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own. Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/onboarding.html#after-setup",
    
    "relUrl": "/hr-rHR/user/onboarding.html#after-setup"
  },"4165": {
    "doc": "Getting Started",
    "title": "Related Topics",
    "content": ". | Connections — pair your first radio | Messages & Channels — send your first message | Nodes — see who else is on your mesh | Map & Waypoints — view node positions | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/onboarding.html#related-topics",
    
    "relUrl": "/hr-rHR/user/onboarding.html#related-topics"
  },"4166": {
    "doc": "Getting Started",
    "title": "Getting Started",
    "content": "This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/onboarding.html",
    
    "relUrl": "/pt-rPT/user/onboarding.html"
  },"4167": {
    "doc": "Getting Started",
    "title": "First Launch",
    "content": "When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. Welcome Screen . The welcome screen introduces Meshtastic with three feature rows: . |   |   | . | Stay Connected Anywhere | Communicate off-the-grid with your friends and community without cell service. | . | Create Your Own Networks | Easily set up private mesh networks for secure and reliable communication in remote areas. | . | Track and Share Locations | Share your location in real-time and keep your group coordinated with integrated GPS features. | . Tap Get started to proceed through the setup flow. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/onboarding.html#first-launch",
    
    "relUrl": "/pt-rPT/user/onboarding.html#first-launch"
  },"4168": {
    "doc": "Getting Started",
    "title": "Permissions",
    "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/onboarding.html#permissions",
    
    "relUrl": "/pt-rPT/user/onboarding.html#permissions"
  },"4169": {
    "doc": "Getting Started",
    "title": "After Setup",
    "content": "After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions. 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own. Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/onboarding.html#after-setup",
    
    "relUrl": "/pt-rPT/user/onboarding.html#after-setup"
  },"4170": {
    "doc": "Getting Started",
    "title": "Related Topics",
    "content": ". | Connections — pair your first radio | Messages & Channels — send your first message | Nodes — see who else is on your mesh | Map & Waypoints — view node positions | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/onboarding.html#related-topics",
    
    "relUrl": "/pt-rPT/user/onboarding.html#related-topics"
  },"4171": {
    "doc": "Getting Started",
    "title": "Getting Started",
    "content": "This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/onboarding.html",
    
    "relUrl": "/pl-rPL/user/onboarding.html"
  },"4172": {
    "doc": "Getting Started",
    "title": "First Launch",
    "content": "When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. Welcome Screen . The welcome screen introduces Meshtastic with three feature rows: . |   |   | . | Stay Connected Anywhere | Communicate off-the-grid with your friends and community without cell service. | . | Create Your Own Networks | Easily set up private mesh networks for secure and reliable communication in remote areas. | . | Track and Share Locations | Udostępniaj swoją lokalizację w czasie rzeczywistym i koordynuj działania swojej grupy dzięki zintegrowanym funkcjom GPS. | . Tap Get started to proceed through the setup flow. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/onboarding.html#first-launch",
    
    "relUrl": "/pl-rPL/user/onboarding.html#first-launch"
  },"4173": {
    "doc": "Getting Started",
    "title": "Permissions",
    "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/onboarding.html#permissions",
    
    "relUrl": "/pl-rPL/user/onboarding.html#permissions"
  },"4174": {
    "doc": "Getting Started",
    "title": "After Setup",
    "content": "After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions. 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own. Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/onboarding.html#after-setup",
    
    "relUrl": "/pl-rPL/user/onboarding.html#after-setup"
  },"4175": {
    "doc": "Getting Started",
    "title": "Related Topics",
    "content": ". | Connections — pair your first radio | Messages & Channels — send your first message | Nodes — see who else is on your mesh | Map & Waypoints — view node positions | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/onboarding.html#related-topics",
    
    "relUrl": "/pl-rPL/user/onboarding.html#related-topics"
  },"4176": {
    "doc": "Getting Started",
    "title": "Getting Started",
    "content": "This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/onboarding.html",
    
    "relUrl": "/zh-rCN/user/onboarding.html"
  },"4177": {
    "doc": "Getting Started",
    "title": "First Launch",
    "content": "When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. Welcome Screen . The welcome screen introduces Meshtastic with three feature rows: . |   |   | . | Stay Connected Anywhere | 在没有手机服务的情况下与您的朋友和社区进行网外通信。 | . | Create Your Own Networks | 轻松建立私人网格网络，以便在偏远地区进行安全和可靠的通信。 | . | Track and Share Locations | 实时分享您的位置，并通过集成的GPS功能保持团队的协调一致。 | . Tap Get started to proceed through the setup flow. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/onboarding.html#first-launch",
    
    "relUrl": "/zh-rCN/user/onboarding.html#first-launch"
  },"4178": {
    "doc": "Getting Started",
    "title": "Permissions",
    "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/onboarding.html#permissions",
    
    "relUrl": "/zh-rCN/user/onboarding.html#permissions"
  },"4179": {
    "doc": "Getting Started",
    "title": "After Setup",
    "content": "After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions. 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own. Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/onboarding.html#after-setup",
    
    "relUrl": "/zh-rCN/user/onboarding.html#after-setup"
  },"4180": {
    "doc": "Getting Started",
    "title": "Related Topics",
    "content": ". | Connections — pair your first radio | Messages & Channels — send your first message | Nodes — see who else is on your mesh | Map & Waypoints — view node positions | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/onboarding.html#related-topics",
    
    "relUrl": "/zh-rCN/user/onboarding.html#related-topics"
  },"4181": {
    "doc": "Getting Started",
    "title": "Getting Started",
    "content": "This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/onboarding.html",
    
    "relUrl": "/sq-rAL/user/onboarding.html"
  },"4182": {
    "doc": "Getting Started",
    "title": "First Launch",
    "content": "When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. Welcome Screen . The welcome screen introduces Meshtastic with three feature rows: . |   |   | . | Stay Connected Anywhere | Communicate off-the-grid with your friends and community without cell service. | . | Create Your Own Networks | Easily set up private mesh networks for secure and reliable communication in remote areas. | . | Track and Share Locations | Share your location in real-time and keep your group coordinated with integrated GPS features. | . Tap Get started to proceed through the setup flow. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/onboarding.html#first-launch",
    
    "relUrl": "/sq-rAL/user/onboarding.html#first-launch"
  },"4183": {
    "doc": "Getting Started",
    "title": "Permissions",
    "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/onboarding.html#permissions",
    
    "relUrl": "/sq-rAL/user/onboarding.html#permissions"
  },"4184": {
    "doc": "Getting Started",
    "title": "After Setup",
    "content": "After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions. 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own. Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/onboarding.html#after-setup",
    
    "relUrl": "/sq-rAL/user/onboarding.html#after-setup"
  },"4185": {
    "doc": "Getting Started",
    "title": "Related Topics",
    "content": ". | Connections — pair your first radio | Messages & Channels — send your first message | Nodes — see who else is on your mesh | Map & Waypoints — view node positions | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/onboarding.html#related-topics",
    
    "relUrl": "/sq-rAL/user/onboarding.html#related-topics"
  },"4186": {
    "doc": "新手入門",
    "title": "# 入門指南",
    "content": "This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/onboarding.html#-%E5%85%A5%E9%96%80%E6%8C%87%E5%8D%97",
    
    "relUrl": "/zh-rTW/user/onboarding.html#-入門指南"
  },"4187": {
    "doc": "新手入門",
    "title": "First Launch",
    "content": "When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. Welcome Screen . The welcome screen introduces Meshtastic with three feature rows: . |   |   | . | Stay Connected Anywhere | 無需手機訊號，也能與您的朋友和社群離線通訊。 | . | Create Your Own Networks | 輕鬆設定私有網狀網絡，以實現偏遠地區安全可靠的通訊。 | . | Track and Share Locations | 透過整合的 GPS 功能，即時分享你的位置，並保持團隊協調一致。 | . Tap Get started to proceed through the setup flow. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/onboarding.html#first-launch",
    
    "relUrl": "/zh-rTW/user/onboarding.html#first-launch"
  },"4188": {
    "doc": "新手入門",
    "title": "Permissions",
    "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | 狀態 | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/onboarding.html#permissions",
    
    "relUrl": "/zh-rTW/user/onboarding.html#permissions"
  },"4189": {
    "doc": "新手入門",
    "title": "After Setup",
    "content": "After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions. 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own. Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/onboarding.html#after-setup",
    
    "relUrl": "/zh-rTW/user/onboarding.html#after-setup"
  },"4190": {
    "doc": "新手入門",
    "title": "相關主題",
    "content": ". | Connections — pair your first radio | Messages & Channels — send your first message | Nodes — see who else is on your mesh | Map & Waypoints — view node positions | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/onboarding.html#%E7%9B%B8%E9%97%9C%E4%B8%BB%E9%A1%8C",
    
    "relUrl": "/zh-rTW/user/onboarding.html#相關主題"
  },"4191": {
    "doc": "新手入門",
    "title": "新手入門",
    "content": " ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/onboarding.html",
    
    "relUrl": "/zh-rTW/user/onboarding.html"
  },"4192": {
    "doc": "Getting Started",
    "title": "Getting Started",
    "content": "This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/onboarding.html",
    
    "relUrl": "/et-rEE/user/onboarding.html"
  },"4193": {
    "doc": "Getting Started",
    "title": "First Launch",
    "content": "When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. Tervituskuva . The welcome screen introduces Meshtastic with three feature rows: . |   |   | . | Stay Connected Anywhere | Saada sõnumeid sõpradele ja kommuunile ilma võrguühenduse või mobiilivõrguta. | . | Create Your Own Networks | Loo hõlpsalt privaatseid kärgvõrke turvaliseks ja usaldusväärseks suhtluseks asustamata piirkondades. | . | Track and Share Locations | Jaga reaalajas oma asukohta ja hoia oma grupp ühtsena integreeritud GPS funktsioonide abil. | . Tap Get started to proceed through the setup flow. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/onboarding.html#first-launch",
    
    "relUrl": "/et-rEE/user/onboarding.html#first-launch"
  },"4194": {
    "doc": "Getting Started",
    "title": "Permissions",
    "content": "Rakendus küsib seadistamise ajal mitmeid lube. Igal neist on kindel eesmärk ja mõned on vajalikud põhifunktsioonide täitmiseks. Sinihamba load . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Asukoha luba . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic kasutab sinu asukohta ka järgmiseks: . | Kuvatakse asukoht kärgvõrgu kaardil | Calculating distances to other nodes | GPS koordinaatide jagamine teiste kärgvõrgu liikmetega (kui lubatud) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Märguannete load . Märguanded teavitavad teid järgmisest: . | Sissetulevad sõnumid kanalitelt ja otsesõnumid | New nodes joining the mesh | Kaugsõlmel on aku tühjenenud | . 💡 Vihje: Teavituste eelistusi saab hiljem Androidi süsteemiseadetes täpsustada – rakendus loob iga kategooria kohta eraldi teavituskanali (lisaks mõned sisemised, näiteks taustateenus), nii et saad need eraldi lubada või vaigistada. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | Olek | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/onboarding.html#permissions",
    
    "relUrl": "/et-rEE/user/onboarding.html#permissions"
  },"4195": {
    "doc": "Getting Started",
    "title": "Peale seadistamist",
    "content": "After you grant permissions, the app opens the main interface. Esimene samm peaks olema ühenduse loomine Meshtastic raadioga – üksikasjalike juhiste saamiseks vaata [Ühendused] (connections). 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own. Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. Kas oled Meshtasticus algaja? Meshtastic.org lehel olev alustusjuhend käsitleb riistvara valimist, raadio esialgset seadistamist ja esimest võrgu seadistamist. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/onboarding.html#peale-seadistamist",
    
    "relUrl": "/et-rEE/user/onboarding.html#peale-seadistamist"
  },"4196": {
    "doc": "Getting Started",
    "title": "Seotud teemad",
    "content": ". | Connections — pair your first radio | Sõnumid ja kanalid — saada oma esimene sõnum | Nodes — see who else is on your mesh | Kaart ja teekonnapunktid — vaata sõlmede asukohti | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/onboarding.html#seotud-teemad",
    
    "relUrl": "/et-rEE/user/onboarding.html#seotud-teemad"
  },"4197": {
    "doc": "Getting Started",
    "title": "Getting Started",
    "content": "This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/onboarding.html",
    
    "relUrl": "/fr-rFR/user/onboarding.html"
  },"4198": {
    "doc": "Getting Started",
    "title": "First Launch",
    "content": "When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. Welcome Screen . The welcome screen introduces Meshtastic with three feature rows: . |   |   | . | Stay Connected Anywhere | Communiquez en dehors du réseau avec vos amis et votre communauté sans service cellulaire. | . | Create Your Own Networks | Installez facilement des réseaux de maillage privé pour une communication sûre et fiable dans les régions éloignées. | . | Track and Share Locations | Partagez votre position en temps réel et gardez votre groupe coordonné avec les fonctionnalités GPS intégrées. | . Tap Get started to proceed through the setup flow. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/onboarding.html#first-launch",
    
    "relUrl": "/fr-rFR/user/onboarding.html#first-launch"
  },"4199": {
    "doc": "Getting Started",
    "title": "Permissions",
    "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/onboarding.html#permissions",
    
    "relUrl": "/fr-rFR/user/onboarding.html#permissions"
  },"4200": {
    "doc": "Getting Started",
    "title": "After Setup",
    "content": "After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions. 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own. Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/onboarding.html#after-setup",
    
    "relUrl": "/fr-rFR/user/onboarding.html#after-setup"
  },"4201": {
    "doc": "Getting Started",
    "title": "Related Topics",
    "content": ". | Connections — pair your first radio | Messages & Channels — send your first message | Nodes — see who else is on your mesh | Map & Waypoints — view node positions | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/onboarding.html#related-topics",
    
    "relUrl": "/fr-rFR/user/onboarding.html#related-topics"
  },"4202": {
    "doc": "Getting Started",
    "title": "Getting Started",
    "content": "This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/onboarding.html",
    
    "relUrl": "/tr-rTR/user/onboarding.html"
  },"4203": {
    "doc": "Getting Started",
    "title": "First Launch",
    "content": "When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. Welcome Screen . The welcome screen introduces Meshtastic with three feature rows: . |   |   | . | Stay Connected Anywhere | Communicate off-the-grid with your friends and community without cell service. | . | Create Your Own Networks | Easily set up private mesh networks for secure and reliable communication in remote areas. | . | Track and Share Locations | Share your location in real-time and keep your group coordinated with integrated GPS features. | . Tap Get started to proceed through the setup flow. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/onboarding.html#first-launch",
    
    "relUrl": "/tr-rTR/user/onboarding.html#first-launch"
  },"4204": {
    "doc": "Getting Started",
    "title": "Permissions",
    "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/onboarding.html#permissions",
    
    "relUrl": "/tr-rTR/user/onboarding.html#permissions"
  },"4205": {
    "doc": "Getting Started",
    "title": "After Setup",
    "content": "After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions. 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own. Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/onboarding.html#after-setup",
    
    "relUrl": "/tr-rTR/user/onboarding.html#after-setup"
  },"4206": {
    "doc": "Getting Started",
    "title": "Related Topics",
    "content": ". | Connections — pair your first radio | Messages & Channels — send your first message | Nodes — see who else is on your mesh | Map & Waypoints — view node positions | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/onboarding.html#related-topics",
    
    "relUrl": "/tr-rTR/user/onboarding.html#related-topics"
  },"4207": {
    "doc": "Getting Started",
    "title": "Getting Started",
    "content": "This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/onboarding.html",
    
    "relUrl": "/el-rGR/user/onboarding.html"
  },"4208": {
    "doc": "Getting Started",
    "title": "First Launch",
    "content": "When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. Welcome Screen . The welcome screen introduces Meshtastic with three feature rows: . |   |   | . | Stay Connected Anywhere | Communicate off-the-grid with your friends and community without cell service. | . | Create Your Own Networks | Easily set up private mesh networks for secure and reliable communication in remote areas. | . | Track and Share Locations | Share your location in real-time and keep your group coordinated with integrated GPS features. | . Tap Get started to proceed through the setup flow. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/onboarding.html#first-launch",
    
    "relUrl": "/el-rGR/user/onboarding.html#first-launch"
  },"4209": {
    "doc": "Getting Started",
    "title": "Permissions",
    "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/onboarding.html#permissions",
    
    "relUrl": "/el-rGR/user/onboarding.html#permissions"
  },"4210": {
    "doc": "Getting Started",
    "title": "After Setup",
    "content": "After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions. 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own. Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/onboarding.html#after-setup",
    
    "relUrl": "/el-rGR/user/onboarding.html#after-setup"
  },"4211": {
    "doc": "Getting Started",
    "title": "Related Topics",
    "content": ". | Connections — pair your first radio | Messages & Channels — send your first message | Nodes — see who else is on your mesh | Map & Waypoints — view node positions | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/onboarding.html#related-topics",
    
    "relUrl": "/el-rGR/user/onboarding.html#related-topics"
  },"4212": {
    "doc": "Getting Started",
    "title": "Getting Started",
    "content": "This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/onboarding.html",
    
    "relUrl": "/ro-rRO/user/onboarding.html"
  },"4213": {
    "doc": "Getting Started",
    "title": "First Launch",
    "content": "When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. Welcome Screen . The welcome screen introduces Meshtastic with three feature rows: . |   |   | . | Stay Connected Anywhere | Comunicați în afara grilei cu prietenii și comunitatea dvs. fără serviciu celular. | . | Create Your Own Networks | Înființarea cu ușurință a rețelelor private de plasare pentru comunicații sigure și fiabile în zonele îndepărtate; | . | Track and Share Locations | Partajați-vă locația în timp real și păstrați grupul coordonat cu funcții GPS integrate. | . Tap Get started to proceed through the setup flow. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/onboarding.html#first-launch",
    
    "relUrl": "/ro-rRO/user/onboarding.html#first-launch"
  },"4214": {
    "doc": "Getting Started",
    "title": "Permissions",
    "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/onboarding.html#permissions",
    
    "relUrl": "/ro-rRO/user/onboarding.html#permissions"
  },"4215": {
    "doc": "Getting Started",
    "title": "After Setup",
    "content": "After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions. 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own. Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/onboarding.html#after-setup",
    
    "relUrl": "/ro-rRO/user/onboarding.html#after-setup"
  },"4216": {
    "doc": "Getting Started",
    "title": "Related Topics",
    "content": ". | Connections — pair your first radio | Messages & Channels — send your first message | Nodes — see who else is on your mesh | Map & Waypoints — view node positions | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/onboarding.html#related-topics",
    
    "relUrl": "/ro-rRO/user/onboarding.html#related-topics"
  },"4217": {
    "doc": "Getting Started",
    "title": "Getting Started",
    "content": "This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/onboarding.html",
    
    "relUrl": "/iw-rIL/user/onboarding.html"
  },"4218": {
    "doc": "Getting Started",
    "title": "First Launch",
    "content": "When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. Welcome Screen . The welcome screen introduces Meshtastic with three feature rows: . |   |   | . | Stay Connected Anywhere | Communicate off-the-grid with your friends and community without cell service. | . | Create Your Own Networks | Easily set up private mesh networks for secure and reliable communication in remote areas. | . | Track and Share Locations | Share your location in real-time and keep your group coordinated with integrated GPS features. | . Tap Get started to proceed through the setup flow. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/onboarding.html#first-launch",
    
    "relUrl": "/iw-rIL/user/onboarding.html#first-launch"
  },"4219": {
    "doc": "Getting Started",
    "title": "Permissions",
    "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/onboarding.html#permissions",
    
    "relUrl": "/iw-rIL/user/onboarding.html#permissions"
  },"4220": {
    "doc": "Getting Started",
    "title": "After Setup",
    "content": "After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions. 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own. Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/onboarding.html#after-setup",
    
    "relUrl": "/iw-rIL/user/onboarding.html#after-setup"
  },"4221": {
    "doc": "Getting Started",
    "title": "Related Topics",
    "content": ". | Connections — pair your first radio | Messages & Channels — send your first message | Nodes — see who else is on your mesh | Map & Waypoints — view node positions | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/onboarding.html#related-topics",
    
    "relUrl": "/iw-rIL/user/onboarding.html#related-topics"
  },"4222": {
    "doc": "Getting Started",
    "title": "Getting Started",
    "content": "This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/onboarding.html",
    
    "relUrl": "/pt-rBR/user/onboarding.html"
  },"4223": {
    "doc": "Getting Started",
    "title": "First Launch",
    "content": "When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. Welcome Screen . The welcome screen introduces Meshtastic with three feature rows: . |   |   | . | Stay Connected Anywhere | Comunique-se off-grid com seus amigos e comunidades sem serviço de celular. | . | Create Your Own Networks | Configure facilmente redes de malha privada para uma comunicação segura e confiável em áreas remotas. | . | Track and Share Locations | Compartilhe sua localização em tempo real e mantenha seu grupo coordenado com recursos integrados de GPS. | . Tap Get started to proceed through the setup flow. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/onboarding.html#first-launch",
    
    "relUrl": "/pt-rBR/user/onboarding.html#first-launch"
  },"4224": {
    "doc": "Getting Started",
    "title": "Permissions",
    "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/onboarding.html#permissions",
    
    "relUrl": "/pt-rBR/user/onboarding.html#permissions"
  },"4225": {
    "doc": "Getting Started",
    "title": "After Setup",
    "content": "After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions. 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own. Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/onboarding.html#after-setup",
    
    "relUrl": "/pt-rBR/user/onboarding.html#after-setup"
  },"4226": {
    "doc": "Getting Started",
    "title": "Related Topics",
    "content": ". | Connections — pair your first radio | Messages & Channels — send your first message | Nodes — see who else is on your mesh | Map & Waypoints — view node positions | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/onboarding.html#related-topics",
    
    "relUrl": "/pt-rBR/user/onboarding.html#related-topics"
  },"4227": {
    "doc": "Getting Started",
    "title": "Getting Started",
    "content": "This page covers the first-launch flow of the Meshtastic Android app, what each permission is for, and how to revisit them later. ",
    "url": "/Meshtastic-Android/main/en/user/onboarding.html",
    
    "relUrl": "/en/user/onboarding.html"
  },"4228": {
    "doc": "Getting Started",
    "title": "First Launch",
    "content": "When you open the app for the first time, the app guides you through an introductory flow that configures essential permissions and settings. Complete each step in order or skip it — nothing here is a one-time offer. Every permission can be reviewed and granted later from the Permissions section of Settings inside the app. Welcome Screen . The welcome screen introduces Meshtastic with three feature rows: . |   |   | . | Stay Connected Anywhere | Communicate off-the-grid with your friends and community without cell service. | . | Create Your Own Networks | Easily set up private mesh networks for secure and reliable communication in remote areas. | . | Track and Share Locations | Share your location in real-time and keep your group coordinated with integrated GPS features. | . Tap Get started to proceed through the setup flow. ",
    "url": "/Meshtastic-Android/main/en/user/onboarding.html#first-launch",
    
    "relUrl": "/en/user/onboarding.html#first-launch"
  },"4229": {
    "doc": "Getting Started",
    "title": "Permissions",
    "content": "The app requests several permissions during setup. Each one serves a specific purpose, and some are required for core functionality. Bluetooth Permission . Bluetooth is the primary connection method between your phone and Meshtastic radio. The Bluetooth screen shows what the permission buys you: . | Discovery — find and identify Meshtastic devices near you. | Configuration — wirelessly manage your device settings and channels. | . On Android 12 and newer, Android asks once, for Nearby devices, and that one grant covers both scanning and connecting. Without it, you’ll need to use USB or TCP connections instead. Location Permission . ℹ️ Note: Location is not required for Bluetooth on Android 12 and newer. Android 11 and older show one location step, on the Bluetooth screen, rather than two — those releases treat a Bluetooth scan as a location capability, so the app asks for Location instead of “Nearby devices”. Asking twice would push you toward the point where Android stops offering the dialog at all (a second denial on Android 11; the “Don’t ask again” checkbox on Android 10 and older). On Android 12 and newer the two are separate: “Nearby devices” is declared neverForLocation, and declining Location does not stop you finding or connecting to a radio. Meshtastic also uses your location for: . | Showing your position on the mesh map | Calculating distances to other nodes | Sharing your GPS coordinates with other mesh members (if enabled) | . Grant “While using the app”. The app does not request background location — ACCESS_BACKGROUND_LOCATION is not in its manifest — so Android will not offer an “Always” option, and position updates happen while the app is in the foreground or running its foreground service. Declining leaves the rest of the app working: on Android 12 and newer, Bluetooth is unaffected and only the map position and position sharing are disabled. On Android 11 and older, Bluetooth scanning also stops, because that is the permission Android gates it behind — and system Location Services must also be switched on for a scan to return anything. Notifications Permission . Notifications alert you to: . | Incoming messages from channels and direct messages | New nodes joining the mesh | Low battery on a remote node | . 💡 Tip: You can fine-tune notification preferences later in Android system settings — the app creates a separate notification channel per category (plus a few internal ones, like the background service), so you can enable or silence them individually. Critical Alerts Permission . Critical alerts are high-priority notifications that break through Do Not Disturb — for emergency mesh alerts and urgent messages. This step is not a runtime permission prompt. There is no grant/deny dialog: the button opens the Android system settings page for the app’s Alerts notification channel, where you turn the breakthrough behavior on yourself. Tap Configure Critical Alerts to open that page, or Skip to move on — you can reach the same page later from Android’s notification settings for Meshtastic. This step appears only if you granted notifications on the previous screen — skip or decline them and setup ends there. Reviewing permissions later . The Permissions section of Settings summarizes where every runtime permission stands. On Android 12 and newer it lists five: Nearby devices permission (Bluetooth), Location permission, App Notifications, Camera permission (scanning channel and contact QR codes) and Local network permission (finding radios over Wi-Fi by mDNS). On Android 11 and older a single Location permission row covers both Bluetooth and location, so there are four. The last two are never asked for during setup, only when a feature first needs them. The section reads All allowed when every permission is granted, Nothing needs your attention when some have simply never been asked for, and names a count when one is denied — in which case it expands itself. Tap the row to expand or collapse it at any time: . | State | What tapping the row does | . | Allowed | Opens the system page, so you can review or revoke it | . | Not asked yet | Requests it | . | Denied — tap to allow | Explains what the permission is for, then asks again if you agree | . | Blocked — tap to open system settings | Android will no longer show its dialog, so this opens the page where you can turn it back on | . | Not required on this version of Android | Nothing — the permission does not exist on your device | . This matters most for notifications. If you decline them during setup, this row is the way back: Android stops showing the dialog once you have declined firmly (a second denial), at which point this row switches to Blocked and sends you to the system settings page instead. The notification prompt exists only on Android 13 and newer — on older versions notifications are on by default and managed from Android’s own settings. ",
    "url": "/Meshtastic-Android/main/en/user/onboarding.html#permissions",
    
    "relUrl": "/en/user/onboarding.html#permissions"
  },"4230": {
    "doc": "Getting Started",
    "title": "After Setup",
    "content": "After you grant permissions, the app opens the main interface. Your first action should be connecting to a Meshtastic radio — see Connections for detailed instructions. 💡 Tip: If you skipped any permissions during setup, open the Permissions section of Settings in the app. Every runtime permission is listed there with its current state and a way back to it — including notifications, which the system will not prompt for a second time on its own. Features also ask in context. On the Connect tab, a card above the device list explains what the Bluetooth permission is for and offers Grant permission; once Android stops prompting, that button becomes Open settings. New to Meshtastic? The getting started guide on meshtastic.org covers hardware selection, initial radio configuration, and your first mesh setup. ",
    "url": "/Meshtastic-Android/main/en/user/onboarding.html#after-setup",
    
    "relUrl": "/en/user/onboarding.html#after-setup"
  },"4231": {
    "doc": "Getting Started",
    "title": "Related Topics",
    "content": ". | Connections — pair your first radio | Messages & Channels — send your first message | Nodes — see who else is on your mesh | Map & Waypoints — view node positions | Settings — Radio & User — configure your radio and user profile | . ",
    "url": "/Meshtastic-Android/main/en/user/onboarding.html#related-topics",
    
    "relUrl": "/en/user/onboarding.html#related-topics"
  },"4232": {
    "doc": "Persistence",
    "title": "Persistence",
    "content": "The app’s three persistence layers — Room, DataStore, and core:prefs — and when a contributor should use each. ",
    "url": "/Meshtastic-Android/main/en/developer/persistence.html",
    
    "relUrl": "/en/developer/persistence.html"
  },"4233": {
    "doc": "Persistence",
    "title": "Room KMP Database",
    "content": "Module: core:database . The primary structured data store: . | Node information and history | Message history | Waypoints | Telemetry data | Channel set configuration (channel names and LoRa config) | . Key Points . | Uses Room KMP for cross-platform compatibility | Migrations managed through Room’s built-in migration system | DAO interfaces live in core:database | Repository layer in core:repository provides the public API | Full-text message search is backed by an FTS5 content table (PacketFts) over Packet, kept in sync by Room-managed triggers | . What’s Stored in Room . | Entity | Description | . | NodeEntity | All known mesh nodes and their metadata | . | MyNodeEntity | The local node’s own info | . | Packet | Message history (channel and direct), waypoints, and telemetry data | . | PacketFts | FTS5 virtual table mirroring Packet.messageText for full-text message search (Room-managed INSERT/UPDATE/DELETE triggers keep it in sync) | . | ContactSettings | Per-contact mute and read-state | . | ReactionEntity | Emoji reactions on messages | . | MeshLog | Raw mesh protocol logs | . | MetadataEntity | Device metadata (firmware version, hardware model) | . | ChannelSetEntity | The connected radio’s channel set — channel names and LoRa config — one row per device | . | QuickChatAction | User-configured quick-chat messages | . | DeviceHardwareEntity | Cached device hardware catalog | . | FirmwareReleaseEntity | Cached firmware release info | . | TracerouteNodePositionEntity | Traceroute hop position data | . | DiscoverySessionEntity | A Local Mesh Discovery scan session (timestamp, presets scanned, home preset) | . | DiscoveryPresetResultEntity | Per-preset result within a discovery session | . | DiscoveredNodeEntity | Nodes found during a discovery preset scan | . | DeviceLinkEntity | Cached msh.to device links from the Meshtastic API | . ℹ️ Note: Waypoints and telemetry are stored within the Packet entity (the port_num field distinguishes packet types), alongside a channel index recording which channel each packet used. Channel configuration — names and LoRa settings — lives separately, in ChannelSetEntity. ",
    "url": "/Meshtastic-Android/main/en/developer/persistence.html#room-kmp-database",
    
    "relUrl": "/en/developer/persistence.html#room-kmp-database"
  },"4234": {
    "doc": "Persistence",
    "title": "DataStore Preferences",
    "content": "Module: core:datastore . For lightweight key-value preferences: . | Local radio configuration (LocalConfig) | Module configuration (ModuleConfig) | Local statistics | Recently connected radio addresses | . ",
    "url": "/Meshtastic-Android/main/en/developer/persistence.html#datastore-preferences",
    
    "relUrl": "/en/developer/persistence.html#datastore-preferences"
  },"4235": {
    "doc": "Persistence",
    "title": "Core Prefs",
    "content": "Module: core:prefs . Higher-level preferences abstraction: . | User-facing settings | App behavior configuration | Feature toggles | . ",
    "url": "/Meshtastic-Android/main/en/developer/persistence.html#core-prefs",
    
    "relUrl": "/en/developer/persistence.html#core-prefs"
  },"4236": {
    "doc": "Persistence",
    "title": "What Docs Intentionally Skip",
    "content": "The feature:docs module uses no Room or persistent database. Documentation ships as build-time assets versioned with the app binary, so it stays fully offline, is replaced on each update, and needs no migration story. Optional UX state (e.g. last viewed page) could live in core:prefs but isn’t part of the docs data model. ",
    "url": "/Meshtastic-Android/main/en/developer/persistence.html#what-docs-intentionally-skip",
    
    "relUrl": "/en/developer/persistence.html#what-docs-intentionally-skip"
  },"4237": {
    "doc": "Persistence",
    "title": "Best Practices",
    "content": ". | Use Room for structured, queryable data that changes at runtime | Use DataStore for simple preferences and state | Use bundled resources/assets for static content | Never store sensitive data (keys, passwords) in plain Room tables | Always provide migrations for schema changes | . ",
    "url": "/Meshtastic-Android/main/en/developer/persistence.html#best-practices",
    
    "relUrl": "/en/developer/persistence.html#best-practices"
  },"4238": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": "Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled. 💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders: . . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/settings-module-admin.html#settings--modules--admin",
    
    "relUrl": "/sk-rSK/user/settings-module-admin.html#settings--modules--admin"
  },"4239": {
    "doc": "Settings — Modules & Admin",
    "title": "Konfigurácia modulu",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Popis | . | MQTT enabled | Toggle MQTT bridge | . | Adresa | MQTT broker address | . | Používateľské meno | Authentication username | . | Heslo | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Popis | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Popis | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Časový limit | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Popis | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Output duration (milliseconds) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Zvonenie | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Popis | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Popis | . | Range test enabled | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Popis | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Popis | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Správy | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Enkóder #1 aktivovaný | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Popis | . | CODEC 2 zapnutý | Activate audio module | . | CODEC2 vzorkovacia frekvencia | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2C výber slova | GPIO pin for I2S WS | . | I2S vstup dát | GPIO pin for I2S DIN | . | I2S výstup dát | GPIO pin for I2S DOUT | . | I2S čas | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Popis | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Popis | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update interval (seconds) | How often to broadcast neighbor list | . | Vysielať cez sieť LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Popis | . | Stav LED | Turn the LED on or off | . | Prúd | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Popis | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum broadcast (seconds) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Popis | . | Paxcounter enabled | Activate people counting | . | Update interval (seconds) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/settings-module-admin.html#konfigur%C3%A1cia-modulu",
    
    "relUrl": "/sk-rSK/user/settings-module-admin.html#konfigurácia-modulu"
  },"4240": {
    "doc": "Settings — Modules & Admin",
    "title": "Administrácia",
    "content": "Administrácia na diaľku . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Reštartovať | Restarts the node | . | Vypnúť | Powers the node down | . | Obnova do výrobných nastavení | Returns every setting to its factory default | . | Reset databázy uzlov | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Zálohovanie a Obnovenie . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Debug okno . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. O aplikácii . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/settings-module-admin.html#administr%C3%A1cia",
    
    "relUrl": "/sk-rSK/user/settings-module-admin.html#administrácia"
  },"4241": {
    "doc": "Settings — Modules & Admin",
    "title": "Related Topics",
    "content": ". | Settings — Radio & User — core node and user profile settings | Module configuration reference — detailed module docs on meshtastic.org | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/settings-module-admin.html#related-topics",
    
    "relUrl": "/sk-rSK/user/settings-module-admin.html#related-topics"
  },"4242": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": " ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/settings-module-admin.html",
    
    "relUrl": "/sk-rSK/user/settings-module-admin.html"
  },"4243": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": "Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled. 💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders: . . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/settings-module-admin.html#settings--modules--admin",
    
    "relUrl": "/be-rBY/user/settings-module-admin.html#settings--modules--admin"
  },"4244": {
    "doc": "Settings — Modules & Admin",
    "title": "Module configuration",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Апісанне | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Імя карыстальніка | Authentication username | . | Пароль | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Апісанне | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Апісанне | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Скончыўся час чакання | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Апісанне | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Output duration (milliseconds) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Апісанне | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Сервер | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Апісанне | . | Range test enabled | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Апісанне | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Апісанне | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Паведамленні | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Апісанне | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Апісанне | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Апісанне | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update interval (seconds) | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Апісанне | . | LED state | Turn the LED on or off | . | 3 | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Апісанне | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum broadcast (seconds) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Апісанне | . | Paxcounter enabled | Activate people counting | . | Update interval (seconds) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/settings-module-admin.html#module-configuration",
    
    "relUrl": "/be-rBY/user/settings-module-admin.html#module-configuration"
  },"4245": {
    "doc": "Settings — Modules & Admin",
    "title": "Administration",
    "content": "Remote Administration . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Перазагрузіць | Restarts the node | . | Shutdown | Powers the node down | . | Factory reset | Returns every setting to its factory default | . | NodeDB reset | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Панэль адладкі . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. О нас . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/settings-module-admin.html#administration",
    
    "relUrl": "/be-rBY/user/settings-module-admin.html#administration"
  },"4246": {
    "doc": "Settings — Modules & Admin",
    "title": "Related Topics",
    "content": ". | Settings — Radio & User — core node and user profile settings | Module configuration reference — detailed module docs on meshtastic.org | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/settings-module-admin.html#related-topics",
    
    "relUrl": "/be-rBY/user/settings-module-admin.html#related-topics"
  },"4247": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": " ",
    "url": "/Meshtastic-Android/main/be-rBY/user/settings-module-admin.html",
    
    "relUrl": "/be-rBY/user/settings-module-admin.html"
  },"4248": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": "Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled. 💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders: . . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/settings-module-admin.html#settings--modules--admin",
    
    "relUrl": "/it-rIT/user/settings-module-admin.html#settings--modules--admin"
  },"4249": {
    "doc": "Settings — Modules & Admin",
    "title": "Impostazioni moduli",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Impostazione | Descrizione | . | MQTT abilitato | Toggle MQTT bridge | . | Indirizzo | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Crittografia abilitata | Encrypt MQTT payloads | . | Output JSON abilitato | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS abilitato | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client attivato | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | Proxy MQTT su questo telefono | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Segnalazione su mappa | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Impostazione | Descrizione | . | Sono d’accordo. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Intervallo di segnalazione su mappa (secondi) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Impostazione | Descrizione | . | Seriale abilitata | Activate serial communication | . | Echo abilitato | Echo received serial data back | . | Modalità seriale | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Velocità della seriale | Port speed | . | Timeout | How long to wait before considering an incoming message complete | . | Sovrascrivi porta seriale della console | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Impostazione | Descrizione | . | Notifica esterna attivata | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | LED Output (GPIO) | Pin the LED is wired to | . | Output per LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibrazione (GPIO) | Pin the vibration motor is wired to | . | Usa buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Usa I2S come buzzer | Send the alert through an I2S audio output instead | . | Durata output (millisecondi) | How long a single alert lasts | . | Timeout chiusura popup (secondi) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Suoneria | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Impostazione | Descrizione | . | Store & Forward abilitato | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Numero di record | Maximum stored messages | . | Cronologia ritorno max | Max messages to replay | . | Finestra di ritorno cronologia | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Impostazione | Descrizione | . | Test distanza massima abilitato | Activate range testing | . | Intervallo messaggio mittente (secondi) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Salva .CSV nella memoria (solo ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Impostazione | Descrizione | . | Invia Telemetria Dispositivo | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Intervallo aggiornamento metriche dispositivo | How often to report battery, uptime and channel utilization | . | Modulo metriche ambientali abilitato | Report the attached environment sensors | . | Intervallo aggiornamento metriche ambientali | How often to report them | . | Metriche ambientali visualizzate su schermo | Also show these readings on the device’s own display | . | Usa i gradi Fahrenheit nelle metriche ambientali | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Modulo metriche della qualità dell’aria abilitato | Report particulate and CO₂ sensor data | . | Intervallo aggiornamento metriche qualità aria | How often to report them | . | Modulo metriche di alimentazione abilitato | Report the per-channel voltage and current readings | . | Intervallo aggiornamento metriche alimentazione | How often to report them | . | Metriche di alimentazione visualizzate su schermo | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Impostazione | Descrizione | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Messaggi | Newline-separated list of messages | . | Invia campanella | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Encoder rotativo #1 abilitato | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Input Su/Giu/Selezione abilitato | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Impostazione | Descrizione | . | CODEC 2 attivato | Activate audio module | . | Frequenza di campionamento CODEC2 | Audio quality/bandwidth tradeoff | . | Pin PTT | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Impostazione | Descrizione | . | Hardware Remoto abilitato | Activate remote GPIO access | . | Consenti accesso a pin non definiti | Allow access to any GPIO pin (security risk) | . | Pin disponibili | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Impostazione | Descrizione | . | Info Nodi Vicini abilitato | Activate neighbor broadcasting | . | Intervallo di aggiornamento (secondi) | How often to broadcast neighbor list | . | Trasmettere su LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Impostazione | Descrizione | . | LED di stato | Turn the LED on or off | . | Attuale | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Impostazione | Descrizione | . | Sensore Rilevamento attivo | Activate detection sensor | . | Pin GPIO da monitorare | GPIO pin connected to sensor | . | Tipo di trigger di rilevamento | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Usa modalità INPUT_PULLUP | Enable the pin’s internal pull-up resistor | . | Trasmissione minima (secondi) | Minimum time between alert broadcasts | . | Trasmissione stato (secondi) | Periodic state broadcast interval | . | Invia campanella con messaggio di avviso | Include bell character in alerts | . | Nome semplificato | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Impostazione | Descrizione | . | Paxcounter abilitato | Activate people counting | . | Intervallo di aggiornamento (secondi) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/settings-module-admin.html#impostazioni-moduli",
    
    "relUrl": "/it-rIT/user/settings-module-admin.html#impostazioni-moduli"
  },"4250": {
    "doc": "Settings — Modules & Admin",
    "title": "Amministrazione",
    "content": "Amministrazione Remota . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Imposta l’ora | Sends your phone’s clock to the node | . | Riavvia | Restarts the node | . | Spegni | Powers the node down | . | Ripristina impostazioni di fabbrica | Returns every setting to its factory default | . | NodeDB reset | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Ripristino . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Avanzate . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Azzera il database dei nodi . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Pannello Di Debug . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Informazioni . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Ringraziamenti . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/settings-module-admin.html#amministrazione",
    
    "relUrl": "/it-rIT/user/settings-module-admin.html#amministrazione"
  },"4251": {
    "doc": "Settings — Modules & Admin",
    "title": "Related Topics",
    "content": ". | Settings — Radio & User — core node and user profile settings | Module configuration reference — detailed module docs on meshtastic.org | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/settings-module-admin.html#related-topics",
    
    "relUrl": "/it-rIT/user/settings-module-admin.html#related-topics"
  },"4252": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": " ",
    "url": "/Meshtastic-Android/main/it-rIT/user/settings-module-admin.html",
    
    "relUrl": "/it-rIT/user/settings-module-admin.html"
  },"4253": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": "Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled. 💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders: . . ",
    "url": "/Meshtastic-Android/main/es-rES/user/settings-module-admin.html#settings--modules--admin",
    
    "relUrl": "/es-rES/user/settings-module-admin.html#settings--modules--admin"
  },"4254": {
    "doc": "Settings — Modules & Admin",
    "title": "Configuración de módulo",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Descripción | . | Activar el MQTT | Toggle MQTT bridge | . | Dirección del Servidor MQTT | MQTT broker address | . | Usuario | Authentication username | . | Contraseña | Authentication password | . | Permitir Encripción | Encrypt MQTT payloads | . | Salida JSON activada | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS activado | Use secure connection | . | Tema raíz | Base MQTT topic path | . | Compartir Internet a la Radio | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Reportar Posición | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Descripción | . | Estoy de acuerdo. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Tiempo entre Reportes de Posición (en Segundos) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Descripción | . | Comunicación serial activada | Activate serial communication | . | Eco activado | Echo received serial data back | . | Modo serial | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Tasa de baudios por segundo | Port speed | . | Tiempo agotado | How long to wait before considering an incoming message complete | . | Sobreescribir el puerto serie de la consola | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Descripción | . | Notificaciones externas activadas | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Salida LED (pin GPIO) | Pin the LED is wired to | . | LED de salida activo en alto | Whether the LED pin is active high or low | . | Salida buzzer (pin GPIO) | Pin the buzzer is wired to | . | Salida vibratoria (pin GPIO) | Pin the vibration motor is wired to | . | Utilizar buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Utilizar el Buzzer como uno I2S | Send the alert through an I2S audio output instead | . | Duración en las salidas (milisegundos) | How long a single alert lasts | . |   | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Tono de notificación | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Descripción | . | Descargar y reenviar activado | Activate store and forward | . | Pulso de vida | Periodically announce this node’s store-and-forward capability | . | Número de registros | Maximum stored messages | . | Historial máximo devuelto | Max messages to replay | . | History return window | Time window for replay | . | Servidor | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Descripción | . | Test de alcance activado | Activate range testing | . | Periodo entre los mensajes del transmisor (segundos) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Guardar el .CSV en el almacenamiento (Esp32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Descripción | . | Enviar telemetría del dispositivo | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Intervalo actualización de métricas del dispositivo | How often to report battery, uptime and channel utilization | . | Módulo para las medidas del entorno activado | Report the attached environment sensors | . | Intervalo actualización de métricas del entorno | How often to report them | . | Mostrar las medidas del entorno en la | Also show these readings on the device’s own display | . | Grados Fahrenheit para la temperatura ambiente | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Módulo para la medición de la calidad del aire activado | Report particulate and CO₂ sensor data | . | Intervalo actualización de métricas calidad del aire | How often to report them | . | Módulo de medidas eléctricas activado | Report the per-channel voltage and current readings | . | Intervalo de actualización de métricas de energía | How often to report them | . | Medidas eléctricas en pantalla | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Descripción | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Mensajes | Newline-separated list of messages | . | Mandar campana 🔔 | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Encoder Número 1 Activado | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Arriba/Abajo/Seleccionar Activado | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Descripción | . | CODEC 2 activado | Activate audio module | . | Frecuencia de Muestreo CODEC2 | Audio quality/bandwidth tradeoff | . | Pin PTT | GPIO pin for the push-to-talk button | . | Selecionar palabras I2S | GPIO pin for I2S WS | . | Entrada de datos I2S | GPIO pin for I2S DIN | . | Salida de datos I2S | GPIO pin for I2S DOUT | . | Reloj del I2S | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Descripción | . | Hardware remoto activado | Activate remote GPIO access | . | Permitir el acceso sin un pin definido | Allow access to any GPIO pin (security risk) | . | Pines disponibles | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Descripción | . | Información de Vecinos | Activate neighbor broadcasting | . | Intervalo de refresco (segundos) | How often to broadcast neighbor list | . | Transmitir en LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Descripción | . | Estado de led | Turn the LED on or off | . | Intensidad | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Descripción | . | Sensor detector activado | Activate detection sensor | . | Pin GPIO para monitorizar | GPIO pin connected to sensor | . | Tipo de detección para activar | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Utilizar el modo de entrada PULL_UP | Enable the pin’s internal pull-up resistor | . | Tiempo mínimo de transmisión (segundos) | Minimum time between alert broadcasts | . | Periodo entre transmisión de estado (segundos) | Periodic state broadcast interval | . | Mandar la campana con el mensaje de alerta | Include bell character in alerts | . | Mote | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Descripción | . | Activar el Contador de Paquetes | Activate people counting | . | Intervalo de refresco (segundos) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ",
    "url": "/Meshtastic-Android/main/es-rES/user/settings-module-admin.html#configuraci%C3%B3n-de-m%C3%B3dulo",
    
    "relUrl": "/es-rES/user/settings-module-admin.html#configuración-de-módulo"
  },"4255": {
    "doc": "Settings — Modules & Admin",
    "title": "Administración",
    "content": "Administración remota . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Reiniciar | Restarts the node | . | Apagar | Powers the node down | . | Restablecer los valores de fábrica | Returns every setting to its factory default | . | Reinicio de NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Hacer copia de seguridad y restaurar . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Avanzado . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Limpiar nodos de la base de datos . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Panel de depuración . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Acerca de . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Agradecimientos . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/settings-module-admin.html#administraci%C3%B3n",
    
    "relUrl": "/es-rES/user/settings-module-admin.html#administración"
  },"4256": {
    "doc": "Settings — Modules & Admin",
    "title": "Related Topics",
    "content": ". | Settings — Radio & User — core node and user profile settings | Module configuration reference — detailed module docs on meshtastic.org | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/settings-module-admin.html#related-topics",
    
    "relUrl": "/es-rES/user/settings-module-admin.html#related-topics"
  },"4257": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": " ",
    "url": "/Meshtastic-Android/main/es-rES/user/settings-module-admin.html",
    
    "relUrl": "/es-rES/user/settings-module-admin.html"
  },"4258": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": "Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled. 💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders: . . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/settings-module-admin.html#settings--modules--admin",
    
    "relUrl": "/sl-rSI/user/settings-module-admin.html#settings--modules--admin"
  },"4259": {
    "doc": "Settings — Modules & Admin",
    "title": "Nastavitev modula",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Opis | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Opis | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Opis | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Časovna omejitev | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Opis | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Output duration (milliseconds) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Opis | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Opis | . | Range test enabled | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Opis | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Opis | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Messages | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Opis | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Opis | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Opis | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update interval (seconds) | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Opis | . | LED state | Turn the LED on or off | . | Current | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Opis | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum broadcast (seconds) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Opis | . | Paxcounter enabled | Activate people counting | . | Update interval (seconds) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/settings-module-admin.html#nastavitev-modula",
    
    "relUrl": "/sl-rSI/user/settings-module-admin.html#nastavitev-modula"
  },"4260": {
    "doc": "Settings — Modules & Admin",
    "title": "Administracija",
    "content": "Administracija na daljavo . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Ponovni zagon | Restarts the node | . | Ugasni | Powers the node down | . | Povrnitev tovarniških nastavitev | Returns every setting to its factory default | . | Ponastavi NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Plošča za odpravljanje napak . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. O programu . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/settings-module-admin.html#administracija",
    
    "relUrl": "/sl-rSI/user/settings-module-admin.html#administracija"
  },"4261": {
    "doc": "Settings — Modules & Admin",
    "title": "Related Topics",
    "content": ". | Settings — Radio & User — core node and user profile settings | Module configuration reference — detailed module docs on meshtastic.org | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/settings-module-admin.html#related-topics",
    
    "relUrl": "/sl-rSI/user/settings-module-admin.html#related-topics"
  },"4262": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": " ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/settings-module-admin.html",
    
    "relUrl": "/sl-rSI/user/settings-module-admin.html"
  },"4263": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": "Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled. 💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders: . . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/settings-module-admin.html#settings--modules--admin",
    
    "relUrl": "/no-rNO/user/settings-module-admin.html#settings--modules--admin"
  },"4264": {
    "doc": "Settings — Modules & Admin",
    "title": "Modul konfigurasjon",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Beskrivelse | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Beskrivelse | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Beskrivelse | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Tidsavbrudd | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Beskrivelse | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Output duration (milliseconds) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Beskrivelse | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Beskrivelse | . | Range test enabled | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Beskrivelse | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Beskrivelse | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Messages | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Beskrivelse | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Beskrivelse | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Beskrivelse | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update interval (seconds) | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Beskrivelse | . | LED state | Turn the LED on or off | . | Current | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Beskrivelse | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum broadcast (seconds) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Beskrivelse | . | Paxcounter enabled | Activate people counting | . | Update interval (seconds) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/settings-module-admin.html#modul-konfigurasjon",
    
    "relUrl": "/no-rNO/user/settings-module-admin.html#modul-konfigurasjon"
  },"4265": {
    "doc": "Settings — Modules & Admin",
    "title": "Administrasjon",
    "content": "Fjernadministrasjon . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Omstart | Restarts the node | . | Avslutt | Powers the node down | . | Tilbakestill til fabrikkstandard | Returns every setting to its factory default | . | NodeDB reset | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Feilsøkningspanel . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Om . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/settings-module-admin.html#administrasjon",
    
    "relUrl": "/no-rNO/user/settings-module-admin.html#administrasjon"
  },"4266": {
    "doc": "Settings — Modules & Admin",
    "title": "Related Topics",
    "content": ". | Settings — Radio & User — core node and user profile settings | Module configuration reference — detailed module docs on meshtastic.org | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/settings-module-admin.html#related-topics",
    
    "relUrl": "/no-rNO/user/settings-module-admin.html#related-topics"
  },"4267": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": " ",
    "url": "/Meshtastic-Android/main/no-rNO/user/settings-module-admin.html",
    
    "relUrl": "/no-rNO/user/settings-module-admin.html"
  },"4268": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": "Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled. 💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders: . . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/settings-module-admin.html#settings--modules--admin",
    
    "relUrl": "/hu-rHU/user/settings-module-admin.html#settings--modules--admin"
  },"4269": {
    "doc": "Settings — Modules & Admin",
    "title": "Modul beállítások",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Leírás | . | MQTT engedélyezve | Toggle MQTT bridge | . | Cím | MQTT broker address | . | Felhasználónév | Authentication username | . | Jelszó | Authentication password | . | Titkosítás engedélyezve | Encrypt MQTT payloads | . | JSON kimenet engedélyezve | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS engedélyezve | Use secure connection | . | Gyökér téma | Base MQTT topic path | . | Proxy kliens felé engedélyezve | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Térképadat-jelentés | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Leírás | . | Elfogadom. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Térképadat-jelentés intervalluma (másodperc) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Leírás | . | Soros engedélyezve | Activate serial communication | . | Echo engedélyezve | Echo received serial data back | . | Soros mód | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Soros baud ráta | Port speed | . | Időtúllépés | How long to wait before considering an incoming message complete | . | Konzol soros port felülbírálása | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Leírás | . | Külső értesítés engedélyezve | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Kimeneti LED (GPIO) | Pin the LED is wired to | . | Kimeneti LED aktív magas szint | Whether the LED pin is active high or low | . | Kimeneti csipogó (GPIO) | Pin the buzzer is wired to | . | Kimeneti rezgő (GPIO) | Pin the vibration motor is wired to | . | PWM csipogó használata | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | I2S használata csipogóként | Send the alert through an I2S audio output instead | . | Kimeneti időtartam (ezredmásodperc) | How long a single alert lasts | . | Ismétlő riasztás időkorlát (másodperc) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Csengőhang | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Leírás | . | Tárolás és továbbítás engedélyezve | Activate store and forward | . | Heartbeat jel | Periodically announce this node’s store-and-forward capability | . | Rekordok száma | Maximum stored messages | . | Előzmény-visszaadás maximum | Max messages to replay | . | Előzmény-visszaadás időablak | Time window for replay | . | Szerver | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Leírás | . | Hatótáv-teszt engedélyezve | Activate range testing | . | Küldési üzenetintervallum (másodperc) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | .CSV mentése a tárhelyre (csak ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Leírás | . | Eszköztelemetria küldése | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Eszközmetrikák frissítési időköze | How often to report battery, uptime and channel utilization | . | Környezeti metrika modul engedélyezve | Report the attached environment sensors | . | Környezeti metrikák frissítési időköze | How often to report them | . | Környezeti metrikák megjelenítése képernyőn | Also show these readings on the device’s own display | . | Környezeti metrikák Fahrenheit-ben | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Levegőminőség-metrika modul engedélyezve | Report particulate and CO₂ sensor data | . | Levegőminőségi metrikák frissítési időköze | How often to report them | . | Energia-metrika modul engedélyezve | Report the per-channel voltage and current readings | . | Tápellátási metrikák frissítési időköze | How often to report them | . | Energia-metrikák megjelenítése képernyőn engedélyezve | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Leírás | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Üzenetek | Newline-separated list of messages | . | Harangjel küldése | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | 1. forgóenkóder engedélyezve | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Fel/Le/Kiválaszt gomb engedélyezve | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Leírás | . | CODEC 2 engedélyezve | Activate audio module | . | CODEC2 mintavételi ráta | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S szóválasztás | GPIO pin for I2S WS | . | I2S adat be | GPIO pin for I2S DIN | . | I2S adat ki | GPIO pin for I2S DOUT | . | I2S órajel | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Leírás | . | Távoli hardver engedélyezve | Activate remote GPIO access | . | Nem definiált pinek elérésének engedélyezése | Allow access to any GPIO pin (security risk) | . | Elérhető pinek | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Leírás | . | Szomszéd-információ engedélyezve | Activate neighbor broadcasting | . | Frissítési intervallum (másodperc) | How often to broadcast neighbor list | . | Továbbítás LoRa-n keresztül | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Leírás | . | LED állapot | Turn the LED on or off | . | Áramerősség | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Leírás | . | Érzékelő szenzor engedélyezve | Activate detection sensor | . | Figyelt GPIO láb | GPIO pin connected to sensor | . | Érzékelési ravasztípus | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | INPUT_PULLUP mód használata | Enable the pin’s internal pull-up resistor | . | Minimális sugárzási idő (másodperc) | Minimum time between alert broadcasts | . | Állapot-sugárzás (másodperc) | Periodic state broadcast interval | . | Harangjel küldése riasztási üzenettel | Include bell character in alerts | . | Barátságos név | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Leírás | . | Paxcounter engedélyezve | Activate people counting | . | Frissítési intervallum (másodperc) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/settings-module-admin.html#modul-be%C3%A1ll%C3%ADt%C3%A1sok",
    
    "relUrl": "/hu-rHU/user/settings-module-admin.html#modul-beállítások"
  },"4270": {
    "doc": "Settings — Modules & Admin",
    "title": "Adminisztráció",
    "content": "Távoli Adminisztráció . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Újraindítás | Restarts the node | . | Leállítás | Powers the node down | . | Gyári beállítások visszaállítása | Returns every setting to its factory default | . | NodeDB törlése | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Biztonsági mentés és visszaállítás . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Haladó . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Csomópont-adatbázis tisztítása . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Hibakereső panel . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. A programról . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Visszaigazolások (ACK-ek) . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/settings-module-admin.html#adminisztr%C3%A1ci%C3%B3",
    
    "relUrl": "/hu-rHU/user/settings-module-admin.html#adminisztráció"
  },"4271": {
    "doc": "Settings — Modules & Admin",
    "title": "Related Topics",
    "content": ". | Settings — Radio & User — core node and user profile settings | Module configuration reference — detailed module docs on meshtastic.org | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/settings-module-admin.html#related-topics",
    
    "relUrl": "/hu-rHU/user/settings-module-admin.html#related-topics"
  },"4272": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": " ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/settings-module-admin.html",
    
    "relUrl": "/hu-rHU/user/settings-module-admin.html"
  },"4273": {
    "doc": "Настройки — Модули и администрирование",
    "title": "Настройки — Модули и администрирование",
    "content": "Настрой дополнительные функциональные модули и выполняй управление устройством. Модули расширяют Meshtastic с помощью специализированных возможностей — каждый из них можно включать или отключать отдельно. 💡 Совет: Тебе нужно включать только те модули, которые действительно используешь. Отключение неиспользуемых модулей снижает время передачи, экономит батарею и упрощает конфигурацию. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Настройки модулей используют макет на основе карточек с переключателями, выпадающими списками, текстовыми полями и ползунками: . . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/settings-module-admin.html",
    
    "relUrl": "/ru-rRU/user/settings-module-admin.html"
  },"4274": {
    "doc": "Настройки — Модули и администрирование",
    "title": "Настройки модуля",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Мосты передают сообщения туда и обратно от брокера MQTT для подключения к интернету. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Настройка | Описание | . | MQTT включен | Переключить MQTT мост | . | Адрес | Адрес MQTT брокера | . | Имя пользователя | Имя пользователя для аутентификации | . | Пароль | Пароль аутентификации | . | Шифрование включено | Зашифровать MQTT-пейлоады | . | Вывод JSON включен | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS включен | Использовать защищённое соединение | . | Корневая тема | Базовый путь темы MQTT | . | Прокси клиенту включен | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT-прокси на этом телефоне | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Отчёты по карте | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Настройка | Описание | . | Я согласен. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Интервал отчета карты (в секундах) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . См. MQTT для подробного руководства по использованию, включая шифрование, конфиденциальность и настройку брокера. Serial module . Позволяет общаться через последовательный порт с внешними устройствами (GPS-модулями, датчиками или собственной техникой). Когда включено, последовательный порт ноды может отправлять и получать данные в формате protobuf или текст, что позволяет внешним микроконтроллерам или компьютерам взаимодействовать с сетью. | Настройка | Описание | . | COM-порт включен | Включить последовательное соединение | . | Echo включен | Echo получил обратно последовательные данные | . | Режим COM-порта | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Скорость COM-порта | Port speed | . | Время ожидания истекло | How long to wait before considering an incoming message complete | . | Переопределить COM-порт консоли | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Полезно для устройств, которым нужно физически сигнализировать о приходе сообщения — особенно удобно для неоснащенных персоналом или уличных установок. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Настройка | Описание | . | Внешние уведомления включены | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Выход LED (GPIO) | Pin the LED is wired to | . | Вывод светодиода активный высокий | Whether the LED pin is active high or low | . | Выход Буззера (GPIO) | Pin the buzzer is wired to | . | Вибросигнал (GPIO) | Pin the vibration motor is wired to | . | Использовать PWM-звукоизлучатель | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Использовать I2S как буззер | Send the alert through an I2S audio output instead | . | Продолжительность вывода (миллисекунды) | How long a single alert lasts | . | Таймаут Nag (в секундах) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Рингтон | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Буферизирует сообщения для узлов, которые временно были недоступны, а затем ретранслирует их, когда эти узлы переподключаются. Важное значение для сеток, где узлы входят и выходят вне диапазона регулярно - обеспечивает отсутствие потери сообщений при коротких разъединениях. | Настройка | Описание | . | Store & Forward включен | Активировать режим хранения и пересылки | . | Heartbeat | Периодически объявлять о наличии функции хранения и пересылки у этого узла | . | Количество записей | Максимальное количество сохраненных сообщений | . | Макс возврат истории | Максимум сообщений для повтора | . | Окно возврата истории | Окно времени для повтора | . | Сервер | Действовать как сервер хранения и пересылки для mesh-сети (требуется большой объем памяти, например, ESP32 с PSRAM) | . 💡 Совет: Хранение и пересылка лучше всего работает на узлах с достаточной памятью (ESP32 с PSRAM). Узлы маршрутизатора являются идеальными кандидатами, так как они обычно всегда включены. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Автоматизированный инструмент для проверки дальности и оценки качества связи между нодами. Когда включено, нода периодически отправляет сообщения с увеличивающимся счетчиком. Приёмная нода записывает эти сообщения, что позволяет тебе уйти пешком или уехать на машине, а потом проанализировать, на каком расстоянии сообщения перестали приходить. | Настройка | Описание | . | Проверка дальности включена | Активировать проверку дальности | . | Интервал сообщений отправителя (в секундах) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Сохранить .CSV в хранилище (только ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Контролирует какими телеметрическими данными ваш узел делится с сеткой. Телеметрия включает данные о состоянии устройства (заряд батареи, время работы) и данные с датчиков окружающей среды (температура, влажность, давление). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Настройка | Описание | . | Отправлять телеметрию устройства | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Интервал обновления метрик устройства | How often to report battery, uptime and channel utilization | . | Модуль метрик окружения включен | Report the attached environment sensors | . | Интервал обновления метрик среды | How often to report them | . | Показатели окружения на экране включены | Also show these readings on the device’s own display | . | Использовать метрику окружения в Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Модуль измерения качества воздуха включен | Report particulate and CO₂ sensor data | . | Интервал обновления данных качества воздуха | How often to report them | . | Модуль метрик питания включен | Report the per-channel voltage and current readings | . | Интервал обновления метрик электропитания | How often to report them | . | Включить метрики питания на экране | Also show power readings on the device’s display | . Посмотрите Телеметрия и датчики — для получения информации о поддерживаемых датчиках и рекомендациях по настройке. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Определите список быстрых сообщений, которые могут быть переданы без подключённого телефона — идеально подходит для использования в поле. | Настройка | Описание | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Сообщения | Список сообщений, разделённых новой строкой | . | Отправить колокольчик | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Поворотный энкодер #1 включен | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Вверх/Вниз/Выбирать включён | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Поддержка аудио Codec2 для низкополосной голосовой связи через сетку. Это экспериментальная функция, которая кодирует голос в очень маленькие пакеты данных с помощью кодека Codec2. | Настройка | Описание | . | CODEC 2 включен | Активировать модуль аудио | . | Частота дискретизации CODEC2 | Компромисс между качеством звука и полосой пропускания | . | Контакт PTT | GPIO pin for the push-to-talk button | . | I2S Word Select | GPIO контакт для I2S WS | . | I2S Data In | Пин GPIO для I2S DIN | . | I2S Data Out | Пин GPIO для I2S DOUT | . | I2S Clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Качество голоса очень низкополосное — представьте себе «разборчивую радиосвязь», а не качество телефонного звонка. Remote Hardware module . Управление GPIO через mesh-сеть. Позволяет удалённому узлу читать и записывать состояния выводов GPIO на другом узле — полезно для активации реле, опроса переключателей или удалённого управления внешним оборудованием. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Настройка | Описание | . | Удаленное оборудование включено | Активировать удаленный GPIO доступ | . | Разрешить неопределённый контакт | Разрешить доступ к любому GPIO-пину (риск для безопасности) | . | Доступные контакты | До 4 пинов GPIO, которые этот узел предоставляет для удалённого чтения и записи | . Neighbor Info module . Транслирует информацию о доступных услышанных соседей, включив ячейку сеточной топологии. Каждый включенный узел периодически делится списком других узлов которые он может слышать и их качество сигнала. | Настройка | Описание | . | Информация о соседях включена | Включить трансляцию соседей | . | Интервал обновления (в секундах) | Как часто транслировать список соседей | . | Передать через LoRa | Также транслировать информацию соседей по LoRa, а не только MQTT/телефон. Недоступно на канале используя ключ по умолчанию и имя | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Управляет встроенными светодиодами NeoPixel или другими адресуемыми RGB-светодиодами на поддерживаемом оборудовании. Может использоваться для визуальных статусовых индикаторов, световых уведомлений, или декоративных эффектов. | Настройка | Описание | . | Состояние LED | Включить или выключить светодиод | . | Ток | Текущий лимит светодиодов (0–31) | . | Красный / Зеленый / Синий | Индивидуальные значения цветов канала (0–255) | . Detection Sensor module . Превращает ваш узел в систему сигнализации на основе датчика движения или открытия двери. При обнаружении изменения состояния на выводе GPIO (например, сработал датчик движения или открылась дверь) узел отправляет по меш-сети оповещение. | Настройка | Описание | . | Датчик определения включен | Активировать датчик обнаружения | . | GPIO контакт для мониторинга | Пин GPIO, подключенный к датчику | . | Тип триггера обнаружения | Как состояние пина интерпретируется как событие обнаружения (например, активный высокий/низкий уровень, срабатывание по фронту) | . | Использовать режим INPUT_PULLUP | Включить внутренний подтягивающий резистор пина | . | Минимальная трансляция (в секундах) | Минимальный интервал между оповещениями | . | Трансляция состояния (в секундах) | Интервал периодической отправки состояния | . | Отправить колокол с уведомлением | Включать символ колокола в оповещения | . | Понятное имя | Пользовательское имя для этого датчика | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Засчитывает ближайшие устройства, пассивно прослушивая зондирующие запросы, чтобы телефоны и ноутбуки излучали при сканировании сетей. Доступно только на устройствах ESP32. | Настройка | Описание | . | Paxcounter включен | Активировать подсчет людей | . | Интервал обновления (в секундах) | Как часто сообщать подсчитывания | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Совет: Paxcounter полезен для приблизительной оценки пешеходного потока в местах начала маршрутов, на мероприятийных площадках или в других локациях. Счетчики приблизительны — один человек может иметь несколько устройств. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Интеграция Team Awareness Kit для совместимости с ATAK и WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. См. TAK Integration для детальной настройки и использования. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/settings-module-admin.html#%D0%BD%D0%B0%D1%81%D1%82%D1%80%D0%BE%D0%B9%D0%BA%D0%B8-%D0%BC%D0%BE%D0%B4%D1%83%D0%BB%D1%8F",
    
    "relUrl": "/ru-rRU/user/settings-module-admin.html#настройки-модуля"
  },"4275": {
    "doc": "Настройки — Модули и администрирование",
    "title": "Администрирование",
    "content": "Удаленное администрирование . Удалённо настраивай ноды, которые используют твой ключ администрирования: . | Выбери целевую ноду в списке нод. | Перейди в Настройки этой ноды. | Измени конфигурацию. | Нажми Сохранить — изменения отправляются через сеть. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Действие | Что она делает | . | Установить время | Sends your phone’s clock to the node | . | Перезагрузка | Restarts the node | . | Выключение | Powers the node down | . | Сброс до заводских настроек | Returns every setting to its factory default | . | Очистка списка нод сети | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Бэкап & Восстановление . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Расширенные . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Очистить базу данных нод . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Панель отладки . Открывает вкладки Пакет и Журналы приложений для просмотра, фильтрации и экспорта диагностических выходов. См. Отладочные журналы для полного прохождения. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. О приложении . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Благодарности . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “Нет ответа от целевого узла” — цель может находиться вне диапазона, в автономном режиме или иметь несоответствующий ключ администратора. Проверьте соответствие ключа администратора на обоих узлах. | Изменения не применены — чтобы некоторые настройки вступили в силу, нужно перезагрузить устройство. Попробуй перезагрузить после сохранения. | Не видны настройки удалённой ноды — убедись, что твоя нода имеет админ-ключ для целевой ноды. Админ-канал настраивается автоматически, когда задан ключ администратора. | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/settings-module-admin.html#%D0%B0%D0%B4%D0%BC%D0%B8%D0%BD%D0%B8%D1%81%D1%82%D1%80%D0%B8%D1%80%D0%BE%D0%B2%D0%B0%D0%BD%D0%B8%D0%B5",
    
    "relUrl": "/ru-rRU/user/settings-module-admin.html#администрирование"
  },"4276": {
    "doc": "Настройки — Модули и администрирование",
    "title": "Связанные темы",
    "content": ". | Settings — Radio & User — core node and user profile settings | Ссылка на конфигурацию модуля — подробная документация по модулям на meshtastic.org | FAQ — общие вопросы на meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/settings-module-admin.html#%D1%81%D0%B2%D1%8F%D0%B7%D0%B0%D0%BD%D0%BD%D1%8B%D0%B5-%D1%82%D0%B5%D0%BC%D1%8B",
    
    "relUrl": "/ru-rRU/user/settings-module-admin.html#связанные-темы"
  },"4277": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": "Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled. 💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders: . . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/settings-module-admin.html#settings--modules--admin",
    
    "relUrl": "/cs-rCZ/user/settings-module-admin.html#settings--modules--admin"
  },"4278": {
    "doc": "Settings — Modules & Admin",
    "title": "Nastavení modulů",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Nastavení | Popis | . | MQTT povoleno | Toggle MQTT bridge | . | Adresa | MQTT broker address | . | Uživatelské jméno | Authentication username | . | Heslo | Authentication password | . | Šifrování povoleno | Encrypt MQTT payloads | . | JSON výstup povolen | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS povoleno | Use secure connection | . | Kořenové téma | Base MQTT topic path | . | Proxy na klienta povoleno | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy na tomto telefonu | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Hlášení mapy | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Nastavení | Popis | . | Souhlasím. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Interval hlášení mapy | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Nastavení | Popis | . | Sériová komunikace povolena | Activate serial communication | . | Povolit echo | Echo received serial data back | . | Sériový režim | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Rychlost sériového přenosu | Port speed | . | Vypršel čas spojení | How long to wait before considering an incoming message complete | . | Přepsat sériový port komunikace | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Nastavení | Popis | . | Externí oznámení povoleno | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Výstupní LED (GPIO) | Pin the LED is wired to | . | Výstupní LED aktivní při HIGH | Whether the LED pin is active high or low | . | Výstupní pin bzučáku (GPIO) | Pin the buzzer is wired to | . | Výstupní pin vybračního motorku (GPIO) | Pin the vibration motor is wired to | . | Použít PWM bzučák | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Použít I2S jako bzučák | Send the alert through an I2S audio output instead | . | Doba trvání výstupu (v milisekundách) | How long a single alert lasts | . | Interval opakovaného zvonění | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Vyzváněcí tón | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Nastavení | Popis | . | Uložit a přeposlat povoleno | Activate store and forward | . | Pulzující LED | Periodically announce this node’s store-and-forward capability | . | Počet záznamů | Maximum stored messages | . | Max. počet záznamů historie | Max messages to replay | . | Časové okno historie | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Nastavení | Popis | . | Test pokrytí povolen | Activate range testing | . | Interval odesílání zpráv | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Uložit .CSV do úložiště (pouze ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Nastavení | Popis | . | Odesílat telemetrii zařízení | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Interval aktualizace metrik zařízení | How often to report battery, uptime and channel utilization | . | Modul měření životního prostředí povolen | Report the attached environment sensors | . | Interval aktualizace měření životního prostředí | How often to report them | . | Zobrazení měření životního prostředí povoleno | Also show these readings on the device’s own display | . | Měření životního prostředí používá Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Modul měření kvality ovzduší povolen | Report particulate and CO₂ sensor data | . | Interval aktualizace měření kvality ovzduší | How often to report them | . | Modul měření spotřeby povolen | Report the per-channel voltage and current readings | . | Interval aktualizace měření napájení | How often to report them | . | Měření spotřeby na obrazovce povoleno | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Nastavení | Popis | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Zprávy | Newline-separated list of messages | . | Odeslat zvonek | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotační enkodér #1 povolen | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Vstup Nahoru/Dolů/Výběr povolen | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Nastavení | Popis | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S výběr slov | GPIO pin for I2S WS | . | I2S vstupní data | GPIO pin for I2S DIN | . | I2S výstupní data | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Nastavení | Popis | . | Vzdálený modul povolen | Activate remote GPIO access | . | Povolit přiřazení nedefinovaného pinu | Allow access to any GPIO pin (security risk) | . | Dostupné piny | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Nastavení | Popis | . | Informace o sousedech povoleny | Activate neighbor broadcasting | . | Interval aktualizace (v sekundách) | How often to broadcast neighbor list | . | Přenos přes LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Nastavení | Popis | . | Stav LED | Turn the LED on or off | . | Proud | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Nastavení | Popis | . | Detekční senzor povolen | Activate detection sensor | . | GPIO pin ke sledování | GPIO pin connected to sensor | . | Typ spouštění detekce | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Použít INPUT_PULLUP režim | Enable the pin’s internal pull-up resistor | . | Minimální vysílání (sekundy) | Minimum time between alert broadcasts | . | Vysílání stavu (v sekundách) | Periodic state broadcast interval | . | Poslat zvonek s výstražnou zprávou | Include bell character in alerts | . | Přezdívka | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Nastavení | Popis | . | Paxcounter povolen | Activate people counting | . | Interval aktualizace (v sekundách) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/settings-module-admin.html#nastaven%C3%AD-modul%C5%AF",
    
    "relUrl": "/cs-rCZ/user/settings-module-admin.html#nastavení-modulů"
  },"4279": {
    "doc": "Settings — Modules & Admin",
    "title": "Administrace",
    "content": "Vzdálená administrace . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Nastavení času | Sends your phone’s clock to the node | . | Restartovat | Restarts the node | . | Vypnout | Powers the node down | . | Obnovení továrního nastavení | Returns every setting to its factory default | . | Reset NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Zálohování a obnovení . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Rozšířené . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Vyčistit databázi uzlů . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Panel pro ladění . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. O aplikaci . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Poděkování . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/settings-module-admin.html#administrace",
    
    "relUrl": "/cs-rCZ/user/settings-module-admin.html#administrace"
  },"4280": {
    "doc": "Settings — Modules & Admin",
    "title": "Related Topics",
    "content": ". | Settings — Radio & User — core node and user profile settings | Module configuration reference — detailed module docs on meshtastic.org | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/settings-module-admin.html#related-topics",
    
    "relUrl": "/cs-rCZ/user/settings-module-admin.html#related-topics"
  },"4281": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": " ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/settings-module-admin.html",
    
    "relUrl": "/cs-rCZ/user/settings-module-admin.html"
  },"4282": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": "Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled. 💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders: . . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/settings-module-admin.html#settings--modules--admin",
    
    "relUrl": "/bg-rBG/user/settings-module-admin.html#settings--modules--admin"
  },"4283": {
    "doc": "Settings — Modules & Admin",
    "title": "Конфигуриране на модулите",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Настройка | Описание | . | MQTT е активиран | Toggle MQTT bridge | . | Адрес | MQTT broker address | . | Потребителско име | Authentication username | . | Парола | Authentication password | . | Криптирането е активирано | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS е активиран | Use secure connection | . | Root topic | Base MQTT topic path | . | Прокси към клиент е активиран | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT прокси на този телефон | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Настройка | Описание | . | Съгласен съм. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Настройка | Описание | . | Серийната връзка е активирана | Activate serial communication | . | Echo е активирано | Echo received serial data back | . | Сериен режим | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Серийна скорост на предаване | Port speed | . | Timeout | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Настройка | Описание | . | Външните известия са активирани | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Използване на PWM зумер | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Output duration (milliseconds) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Тон на звънене | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Настройка | Описание | . | Съхраняване & препращане е активиран | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Брой записи | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Сървър | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Настройка | Описание | . | Тест на обхвата е активиран | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Запазване на .CSV в хранилище (само за ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Настройка | Описание | . | Изпращане на телеметрия на устройството | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Интервал на актуализиране на показателите на устройството | How often to report battery, uptime and channel utilization | . | Модулът за измерване на околната среда е активиран | Report the attached environment sensors | . | Интервал на актуализиране на показателите за средата | How often to report them | . | Показателите на околната среда на екрана са активирани | Also show these readings on the device’s own display | . | Показателите на околната среда използват Фаренхайт | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Модулът за показатели за качеството на въздуха е активиран | Report particulate and CO₂ sensor data | . | Интервал на актуализиране на показателите за качеството на въздуха | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Настройка | Описание | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Съобщения | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Ротационен енкодер #1 е активиран | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Настройка | Описание | . | CODEC 2 е активиран | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | Пин за РТТ | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Настройка | Описание | . | Отдалечен хардуер е активиран | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Налични пинове | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Настройка | Описание | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Интервал на актуализиране (секунди) | How often to broadcast neighbor list | . | Предаване през LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Настройка | Описание | . | LED за състояние | Turn the LED on or off | . | Текущ | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Настройка | Описание | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Използване на режим INPUT_PULLUP | Enable the pin’s internal pull-up resistor | . | Minimum broadcast (seconds) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Приятелско име | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Настройка | Описание | . | Paxcounter е активиран | Activate people counting | . | Интервал на актуализиране (секунди) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/settings-module-admin.html#%D0%BA%D0%BE%D0%BD%D1%84%D0%B8%D0%B3%D1%83%D1%80%D0%B8%D1%80%D0%B0%D0%BD%D0%B5-%D0%BD%D0%B0-%D0%BC%D0%BE%D0%B4%D1%83%D0%BB%D0%B8%D1%82%D0%B5",
    
    "relUrl": "/bg-rBG/user/settings-module-admin.html#конфигуриране-на-модулите"
  },"4284": {
    "doc": "Settings — Modules & Admin",
    "title": "Администриране",
    "content": "Отдалечено администриране . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Действие | Какво прави | . | Set time | Sends your phone’s clock to the node | . | Рестартиране | Restarts the node | . | Изключване | Powers the node down | . | Фабрично нулиране | Returns every setting to its factory default | . | Нулиране на базата данни с възли | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Архивиране & Възстановяване . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Разширени . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Почистване на базата данни с възлите . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Панел за отстраняване на грешки . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Относно . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Благодарности . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/settings-module-admin.html#%D0%B0%D0%B4%D0%BC%D0%B8%D0%BD%D0%B8%D1%81%D1%82%D1%80%D0%B8%D1%80%D0%B0%D0%BD%D0%B5",
    
    "relUrl": "/bg-rBG/user/settings-module-admin.html#администриране"
  },"4285": {
    "doc": "Settings — Modules & Admin",
    "title": "Related Topics",
    "content": ". | Settings — Radio & User — core node and user profile settings | Module configuration reference — detailed module docs on meshtastic.org | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/settings-module-admin.html#related-topics",
    
    "relUrl": "/bg-rBG/user/settings-module-admin.html#related-topics"
  },"4286": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": " ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/settings-module-admin.html",
    
    "relUrl": "/bg-rBG/user/settings-module-admin.html"
  },"4287": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": "Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled. 💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders: . . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/settings-module-admin.html#settings--modules--admin",
    
    "relUrl": "/ga-rIE/user/settings-module-admin.html#settings--modules--admin"
  },"4288": {
    "doc": "Settings — Modules & Admin",
    "title": "Cumraíocht an mhódule",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Cur síos | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Cur síos | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Cur síos | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Am tráth | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Cur síos | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Output duration (milliseconds) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Cur síos | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Cur síos | . | Range test enabled | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Cur síos | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Cur síos | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Messages | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Cur síos | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Cur síos | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Cur síos | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update interval (seconds) | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Cur síos | . | LED state | Turn the LED on or off | . | Current | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Cur síos | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum broadcast (seconds) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Cur síos | . | Paxcounter enabled | Activate people counting | . | Update interval (seconds) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/settings-module-admin.html#cumra%C3%ADocht-an-mh%C3%B3dule",
    
    "relUrl": "/ga-rIE/user/settings-module-admin.html#cumraíocht-an-mhódule"
  },"4289": {
    "doc": "Settings — Modules & Admin",
    "title": "Rialachas",
    "content": "Rialú iargúlta . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Athmhaoinigh | Restarts the node | . | Dún | Powers the node down | . | Athshocraigh an fhactaraí | Returns every setting to its factory default | . | Athshocraigh NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Painéal Laige . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Maidir le . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/settings-module-admin.html#rialachas",
    
    "relUrl": "/ga-rIE/user/settings-module-admin.html#rialachas"
  },"4290": {
    "doc": "Settings — Modules & Admin",
    "title": "Related Topics",
    "content": ". | Settings — Radio & User — core node and user profile settings | Module configuration reference — detailed module docs on meshtastic.org | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/settings-module-admin.html#related-topics",
    
    "relUrl": "/ga-rIE/user/settings-module-admin.html#related-topics"
  },"4291": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": " ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/settings-module-admin.html",
    
    "relUrl": "/ga-rIE/user/settings-module-admin.html"
  },"4292": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": "Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled. 💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders: . . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/settings-module-admin.html#settings--modules--admin",
    
    "relUrl": "/fr-rCA/user/settings-module-admin.html#settings--modules--admin"
  },"4293": {
    "doc": "Settings — Modules & Admin",
    "title": "Réglages du module",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Description | . | MQTT activé | Toggle MQTT bridge | . | Adresse | MQTT broker address | . | Nom d’utilisateur | Authentication username | . | Mot de passe | Authentication password | . | Chiffrement activé | Encrypt MQTT payloads | . | Sortie JSON activée | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS activé | Use secure connection | . | Sujet principal | Base MQTT topic path | . | Proxy pour le client activé | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Rapport cartographique | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Description | . | J’accepte. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Intervalle de rapport cartographique (secondes) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Description | . | Série activée | Activate serial communication | . | Écho activé | Echo received serial data back | . | Mode série | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Vitesse de transmission série | Port speed | . | Délai d’expiration | How long to wait before considering an incoming message complete | . | Outrepasser le port série de la console | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Description | . | Notifications externes activées | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | LED extérieure (GPIO) | Pin the LED is wired to | . | Sortie LED active à l’état haut | Whether the LED pin is active high or low | . | Buzzer extérieur (GPIO) | Pin the buzzer is wired to | . | Sortie vibreur (GPIO) | Pin the vibration motor is wired to | . | Utiliser le buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Utiliser l’I2S comme buzzer | Send the alert through an I2S audio output instead | . | Durée de sortie (en millisecondes) | How long a single alert lasts | . | Durée de répétition de la sortie (secondes) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Sonnerie | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Description | . | Stocker & Transférer activé | Activate store and forward | . | Battement de cœur (heartbeat) | Periodically announce this node’s store-and-forward capability | . | Nombre d’enregistrements | Maximum stored messages | . | Limite d’historique renvoyé | Max messages to replay | . | Fenêtre de retour d’historique | Time window for replay | . | Serveur | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Description | . | Test de portée activé | Activate range testing | . | Intervalle de message de l’expéditeur (secondes) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Enregistrer .CSV dans le stockage (ESP32 seulement) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Description | . | Envoyer la télémétrie de l’appareil | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Intervalle de mise à jour des mesures | How often to report battery, uptime and channel utilization | . | Module de métriques de l’environnement activé | Report the attached environment sensors | . | Intervalle de mise à jour des mesures d’environnement | How often to report them | . | Mesures d’environnement à l’écran activées | Also show these readings on the device’s own display | . | Les mesures environnementales utilisent Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Module de mesure de la qualité de l’air activé | Report particulate and CO₂ sensor data | . | Intervalle de mise à jour des mesures de qualité d’air | How often to report them | . | Module de mesure de puissance activé | Report the per-channel voltage and current readings | . | Intervalle de mise à jour des mesures d’alimentation | How often to report them | . | Indicateurs d’alimentation à l’écran activés | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Description | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Messages | Newline-separated list of messages | . | Envoyer une sonnerie | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Encodeur rotatif #1 activé | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Entrée Haut/Bas/Select activée | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Description | . | CODEC 2 activé | Activate audio module | . | Taux d’échantillonnage CODEC2 | Audio quality/bandwidth tradeoff | . | Broche PTT | GPIO pin for the push-to-talk button | . | Selection de mot I2S | GPIO pin for I2S WS | . | Données d’entrée I2S | GPIO pin for I2S DIN | . | Données de sortie I2S | GPIO pin for I2S DOUT | . | Horloge I2C | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Description | . | Matériel distant activé | Activate remote GPIO access | . | Autoriser l’accès non défini aux broches | Allow access to any GPIO pin (security risk) | . | Broches disponibles | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Description | . | Infos de voisinage activées | Activate neighbor broadcasting | . | Intervalle de mise à jour (secondes) | How often to broadcast neighbor list | . | Transmettre par LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Description | . | État de la LED | Turn the LED on or off | . | Actif | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Description | . | Capteur de détection activé | Activate detection sensor | . | Broche GPIO à surveiller | GPIO pin connected to sensor | . | Type du déclencheur de détection | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Utiliser le mode INPUT_PULLUP | Enable the pin’s internal pull-up resistor | . | Diffusion minimale (secondes) | Minimum time between alert broadcasts | . | Diffusion de l’État (secondes) | Periodic state broadcast interval | . | Envoyer une sonnerie avec un message d’alerte | Include bell character in alerts | . | Nom convivial | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Paramètre | Description | . | Paxcounter activé | Activate people counting | . | Intervalle de mise à jour (secondes) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/settings-module-admin.html#r%C3%A9glages-du-module",
    
    "relUrl": "/fr-rCA/user/settings-module-admin.html#réglages-du-module"
  },"4294": {
    "doc": "Settings — Modules & Admin",
    "title": "Administration",
    "content": "Administration à distance . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Redémarrer | Restarts the node | . | Éteindre | Powers the node down | . | Réinitialisation d’usine | Returns every setting to its factory default | . | Reconfiguration de NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Sauvegarder & Restaurer . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Avancé . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Nettoyer la base de données des nœuds . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Panneau de débogage . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. A propros . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Remerciements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/settings-module-admin.html#administration",
    
    "relUrl": "/fr-rCA/user/settings-module-admin.html#administration"
  },"4295": {
    "doc": "Settings — Modules & Admin",
    "title": "Related Topics",
    "content": ". | Settings — Radio & User — core node and user profile settings | Module configuration reference — detailed module docs on meshtastic.org | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/settings-module-admin.html#related-topics",
    
    "relUrl": "/fr-rCA/user/settings-module-admin.html#related-topics"
  },"4296": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": " ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/settings-module-admin.html",
    
    "relUrl": "/fr-rCA/user/settings-module-admin.html"
  },"4297": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": "Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled. 💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders: . . ",
    "url": "/Meshtastic-Android/main/srp/user/settings-module-admin.html#settings--modules--admin",
    
    "relUrl": "/srp/user/settings-module-admin.html#settings--modules--admin"
  },"4298": {
    "doc": "Settings — Modules & Admin",
    "title": "Конфигурација модула",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Опис | . | MQTT enabled | Toggle MQTT bridge | . | Адреса | MQTT broker address | . | Корисничко име | Authentication username | . | Лозинка | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Опис | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Опис | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Временско ограничење | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Опис | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Output duration (milliseconds) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Мелодија звона | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Опис | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Број записа | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Сервер | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Опис | . | Range test enabled | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Опис | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Опис | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Поруке | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Опис | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Опис | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Опис | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update interval (seconds) | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Опис | . | LED state | Turn the LED on or off | . | Струја | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Опис | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum broadcast (seconds) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Пријатељски назив | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Опис | . | Paxcounter enabled | Activate people counting | . | Update interval (seconds) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ",
    "url": "/Meshtastic-Android/main/srp/user/settings-module-admin.html#%D0%BA%D0%BE%D0%BD%D1%84%D0%B8%D0%B3%D1%83%D1%80%D0%B0%D1%86%D0%B8%D1%98%D0%B0-%D0%BC%D0%BE%D0%B4%D1%83%D0%BB%D0%B0",
    
    "relUrl": "/srp/user/settings-module-admin.html#конфигурација-модула"
  },"4299": {
    "doc": "Settings — Modules & Admin",
    "title": "Администрација",
    "content": "Удаљена администрација . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Поновно покретање | Restarts the node | . | Искључи | Powers the node down | . | Рестартовање на фабричка подешавања | Returns every setting to its factory default | . | Ресетовање базе чворова | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Напредно . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Панел за отклањање грешака . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. Подешавања апликације . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. О . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
    "url": "/Meshtastic-Android/main/srp/user/settings-module-admin.html#%D0%B0%D0%B4%D0%BC%D0%B8%D0%BD%D0%B8%D1%81%D1%82%D1%80%D0%B0%D1%86%D0%B8%D1%98%D0%B0",
    
    "relUrl": "/srp/user/settings-module-admin.html#администрација"
  },"4300": {
    "doc": "Settings — Modules & Admin",
    "title": "Related Topics",
    "content": ". | Settings — Radio & User — core node and user profile settings | Module configuration reference — detailed module docs on meshtastic.org | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/srp/user/settings-module-admin.html#related-topics",
    
    "relUrl": "/srp/user/settings-module-admin.html#related-topics"
  },"4301": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": " ",
    "url": "/Meshtastic-Android/main/srp/user/settings-module-admin.html",
    
    "relUrl": "/srp/user/settings-module-admin.html"
  },"4302": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": "Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled. 💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders: . . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/settings-module-admin.html#settings--modules--admin",
    
    "relUrl": "/ca-rES/user/settings-module-admin.html#settings--modules--admin"
  },"4303": {
    "doc": "Settings — Modules & Admin",
    "title": "Configuració de mòdul",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Descripció | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Descripció | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Descripció | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Temps esgotat | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Descripció | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Output duration (milliseconds) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Descripció | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Descripció | . | Range test enabled | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Descripció | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Descripció | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Messages | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Descripció | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Descripció | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Descripció | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update interval (seconds) | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Descripció | . | LED state | Turn the LED on or off | . | Current | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Descripció | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum broadcast (seconds) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Descripció | . | Paxcounter enabled | Activate people counting | . | Update interval (seconds) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/settings-module-admin.html#configuraci%C3%B3-de-m%C3%B2dul",
    
    "relUrl": "/ca-rES/user/settings-module-admin.html#configuració-de-mòdul"
  },"4304": {
    "doc": "Settings — Modules & Admin",
    "title": "Administration",
    "content": "Remote Administration . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Reiniciar | Restarts the node | . | Apagar | Powers the node down | . | Restauració dels paràmetres de fàbrica | Returns every setting to its factory default | . | Restablir NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Panell de depuració . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Sobre . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/settings-module-admin.html#administration",
    
    "relUrl": "/ca-rES/user/settings-module-admin.html#administration"
  },"4305": {
    "doc": "Settings — Modules & Admin",
    "title": "Related Topics",
    "content": ". | Settings — Radio & User — core node and user profile settings | Module configuration reference — detailed module docs on meshtastic.org | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/settings-module-admin.html#related-topics",
    
    "relUrl": "/ca-rES/user/settings-module-admin.html#related-topics"
  },"4306": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": " ",
    "url": "/Meshtastic-Android/main/ca-rES/user/settings-module-admin.html",
    
    "relUrl": "/ca-rES/user/settings-module-admin.html"
  },"4307": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": "Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled. 💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders: . . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/settings-module-admin.html#settings--modules--admin",
    
    "relUrl": "/ko-rKR/user/settings-module-admin.html#settings--modules--admin"
  },"4308": {
    "doc": "Settings — Modules & Admin",
    "title": "모듈 설정",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | 설명 | . | MQTT 활성화 | Toggle MQTT bridge | . | 서버 주소 | MQTT broker address | . | 사용자명 | Authentication username | . | 비밀번호 | Authentication password | . | 암호화 사용 | Encrypt MQTT payloads | . | JSON 사용 | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS 사용 | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client 사용 | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | 맵 보고 | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | 설명 | . | 동의합니다. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | 맵 보고 간격 (초) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | 설명 | . | 시리얼 활성화 | Activate serial communication | . | 에코 활성화 | Echo received serial data back | . | 시리얼 모드 | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | 시리얼 baud rate | Port speed | . | 시간 초과 | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | 설명 | . | 외부 알림 활성화 | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | LED 출력 (GPIO) | Pin the LED is wired to | . | LED 출력 active high | Whether the LED pin is active high or low | . | 부저 출력 (GPIO) | Pin the buzzer is wired to | . | 진동 출력 (GPIO) | Pin the vibration motor is wired to | . | PWM 부저 사용 | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | I2S 부저 사용 | Send the alert through an I2S audio output instead | . | 출력 지속시간 (밀리초) | How long a single alert lasts | . | 반복 종료 시간 (초) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | 벨소리 | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | 설명 | . | 저장 및 전달 활성화 | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | 서버 | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | 설명 | . | 거리 테스트 활성화 | Activate range testing | . | 송신 장치 메시지 간격 (초) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | .CSV 파일 저장 (EPS32만 동작) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | 설명 | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | 환경 메트릭 모듈 사용 | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | 환경 메트릭 화면 사용 | Also show these readings on the device’s own display | . | 환경 메트릭에서 화씨 사용 | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | 대기질 메트릭 모듈 사용 | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | 전력 메트릭 모듈 사용 | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | 전력 메트릭 화면 사용 | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | 설명 | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | 메시지기기 | Newline-separated list of messages | . | 벨 전송 | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | 로터리 엔코더 #1 활성화 | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | 업/다운/선택 입력 활성화 | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | 설명 | . | CODEC2 활성화 | Activate audio module | . | CODEC2 샘플 레이트 | Audio quality/bandwidth tradeoff | . | PTT 핀 | GPIO pin for the push-to-talk button | . | I2S 단어 선택 | GPIO pin for I2S WS | . | I2S 데이터 in | GPIO pin for I2S DIN | . | I2S 데이터 out | GPIO pin for I2S DOUT | . | I2S 시간 | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | 설명 | . | 원격 하드웨어 활성화 | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | 설명 | . | 이웃 정보 활성화 | Activate neighbor broadcasting | . | 업데이트 간격 (초) | How often to broadcast neighbor list | . | LoRa로 전송 | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | 설명 | . | LED 상태 | Turn the LED on or off | . | 전류 | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | 설명 | . | 감지 센서 활성화 | Activate detection sensor | . | 상태 모니터링 GPIO 핀 | GPIO pin connected to sensor | . | 디텍션 트리거 타입 | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | INPUT_PULLUP 모드 사용 | Enable the pin’s internal pull-up resistor | . | 최소 전송 간격 (초) | Minimum time between alert broadcasts | . | 상태 전송 간격 (초) | Periodic state broadcast interval | . | 알람 메시지와 벨 전송 | Include bell character in alerts | . | 식별 이름 | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | 설명 | . | 팍스카운터 활성화 | Activate people counting | . | 업데이트 간격 (초) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/settings-module-admin.html#%EB%AA%A8%EB%93%88-%EC%84%A4%EC%A0%95",
    
    "relUrl": "/ko-rKR/user/settings-module-admin.html#모듈-설정"
  },"4309": {
    "doc": "Settings — Modules & Admin",
    "title": "관리",
    "content": "원격 설정 . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | 재부팅 | Restarts the node | . | 종료 | Powers the node down | . | 공장초기화 | Returns every setting to its factory default | . | 노드 목록 리셋 | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. 백업 & 복구 . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. 고급 . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. 디버그 패널 . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. 앱에 대하여 . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/settings-module-admin.html#%EA%B4%80%EB%A6%AC",
    
    "relUrl": "/ko-rKR/user/settings-module-admin.html#관리"
  },"4310": {
    "doc": "Settings — Modules & Admin",
    "title": "Related Topics",
    "content": ". | Settings — Radio & User — core node and user profile settings | Module configuration reference — detailed module docs on meshtastic.org | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/settings-module-admin.html#related-topics",
    
    "relUrl": "/ko-rKR/user/settings-module-admin.html#related-topics"
  },"4311": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": " ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/settings-module-admin.html",
    
    "relUrl": "/ko-rKR/user/settings-module-admin.html"
  },"4312": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": "Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled. 💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders: . . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/settings-module-admin.html#settings--modules--admin",
    
    "relUrl": "/sv-rSE/user/settings-module-admin.html#settings--modules--admin"
  },"4313": {
    "doc": "Settings — Modules & Admin",
    "title": "Modul konfiguration",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Beskrivning | . | MQTT är aktiverat | Toggle MQTT bridge | . | Adress | MQTT broker address | . | Användarnamn | Authentication username | . | Lösenord | Authentication password | . | Kryptering aktiverad | Encrypt MQTT payloads | . | JSON-utdata aktiverad | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS är aktiverat | Use secure connection | . | Rotämne (root topic) | Base MQTT topic path | . | Proxy till klient aktiverad | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Beskrivning | . | Jag godkänner. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Beskrivning | . | Seriell aktiverad | Activate serial communication | . | Eko aktiverad | Echo received serial data back | . | Seriellt läge | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Den seriella kommunikationens hastighet | Port speed | . | Timeout | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Beskrivning | . | Externa aviseringar aktiverad | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Utmatning LED (GPIO) | Pin the LED is wired to | . | Utmatnings-LED aktiv hög | Whether the LED pin is active high or low | . | Utmatning summer (GPIO) | Pin the buzzer is wired to | . | Utmatning vibration (GPIO) | Pin the vibration motor is wired to | . | Använd PWM-summern | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Använd I2S som summer | Send the alert through an I2S audio output instead | . | Utmatningstid (millisekunder) | How long a single alert lasts | . | Sluta tjata efter (sekunder) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringsignal | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Beskrivning | . | Lagra & vidarebefordra är aktiverad | Activate store and forward | . | Pulsera | Periodically announce this node’s store-and-forward capability | . | Antal poster | Maximum stored messages | . | Maxstorlek för historik | Max messages to replay | . | Returfönstrets storlek för historik | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Beskrivning | . | Räckvidstest aktiverat | Activate range testing | . | Avsändarens meddelandeintervall (sekunder) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Spara .CSV i enheten (endast ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Beskrivning | . | Skicka enhetstelemetri | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Uppdateringsintervall för enhetsdata | How often to report battery, uptime and channel utilization | . | Mätmodul för miljö aktiverad | Report the attached environment sensors | . | Uppdateringsintervall för miljödata | How often to report them | . | Visning av miljödata på skärm är aktiverad | Also show these readings on the device’s own display | . | Miljömätvärden använder Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Luftkvalitetsmätarmodul aktiverad | Report particulate and CO₂ sensor data | . | Uppdateringsintervall för luftkvalitet | How often to report them | . | Strömmätarmodul aktiverad | Report the per-channel voltage and current readings | . | Uppdateringsintervall för strömmätare | How often to report them | . | Visning av strömvärden på skärm är aktiverad | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Beskrivning | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Meddelanden | Newline-separated list of messages | . | Skicka ljudavisering | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Beskrivning | . | CODEC 2 aktiverat | Activate audio module | . | CODEC2 samplingshastighet | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S ordval | GPIO pin for I2S WS | . | I2S-data in | GPIO pin for I2S DIN | . | I2S-data ut | GPIO pin for I2S DOUT | . | I2S-klocka | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Beskrivning | . | Fjärrhårdvara aktiverad | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Tillgängliga pin | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Beskrivning | . | Grannskapsinformation aktiverat | Activate neighbor broadcasting | . | Uppdateringsintervall (sekunder) | How often to broadcast neighbor list | . | Skicka över LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Beskrivning | . | LED-läge | Turn the LED on or off | . | Ström | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Beskrivning | . | Detektionssensor aktiverad | Activate detection sensor | . | GPIO-pin att övervaka | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Använd INPUT_PULLUP-läge | Enable the pin’s internal pull-up resistor | . | Minsta sändningsintervall (sekunder) | Minimum time between alert broadcasts | . | Statussändningsintervall (sekunder) | Periodic state broadcast interval | . | Skicka ljudavisering med larmmeddelande | Include bell character in alerts | . | Visningsnamn | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Beskrivning | . | PAX-räknare aktiverad | Activate people counting | . | Uppdateringsintervall (sekunder) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/settings-module-admin.html#modul-konfiguration",
    
    "relUrl": "/sv-rSE/user/settings-module-admin.html#modul-konfiguration"
  },"4314": {
    "doc": "Settings — Modules & Admin",
    "title": "Administration",
    "content": "Fjärradministration . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Ställ in tid | Sends your phone’s clock to the node | . | Starta om | Restarts the node | . | Stäng av | Powers the node down | . | Återställ till standardinställningar | Returns every setting to its factory default | . | Nollställ NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Säkerhetskopiering och återställning . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advancerat . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Rensa noddatabas . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Felsökningspanel . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Om . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Bekräftelser . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/settings-module-admin.html#administration",
    
    "relUrl": "/sv-rSE/user/settings-module-admin.html#administration"
  },"4315": {
    "doc": "Settings — Modules & Admin",
    "title": "Related Topics",
    "content": ". | Settings — Radio & User — core node and user profile settings | Module configuration reference — detailed module docs on meshtastic.org | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/settings-module-admin.html#related-topics",
    
    "relUrl": "/sv-rSE/user/settings-module-admin.html#related-topics"
  },"4316": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": " ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/settings-module-admin.html",
    
    "relUrl": "/sv-rSE/user/settings-module-admin.html"
  },"4317": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": "Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled. 💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders: . . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/settings-module-admin.html#settings--modules--admin",
    
    "relUrl": "/ht-rHT/user/settings-module-admin.html#settings--modules--admin"
  },"4318": {
    "doc": "Settings — Modules & Admin",
    "title": "Konfigirasyon modil",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Deskripsyon | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Deskripsyon | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Deskripsyon | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Tan pase | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Deskripsyon | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Output duration (milliseconds) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Deskripsyon | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Deskripsyon | . | Range test enabled | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Deskripsyon | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Deskripsyon | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Messages | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Deskripsyon | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Deskripsyon | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Deskripsyon | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update interval (seconds) | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Deskripsyon | . | LED state | Turn the LED on or off | . | Current | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Deskripsyon | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum broadcast (seconds) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Deskripsyon | . | Paxcounter enabled | Activate people counting | . | Update interval (seconds) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/settings-module-admin.html#konfigirasyon-modil",
    
    "relUrl": "/ht-rHT/user/settings-module-admin.html#konfigirasyon-modil"
  },"4319": {
    "doc": "Settings — Modules & Admin",
    "title": "Administrasyon",
    "content": "Administrasyon Remote . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Rekòmanse | Restarts the node | . | Fèmen | Powers the node down | . | Reyajiste nan faktori | Returns every setting to its factory default | . | Reyajiste NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Panno Debug . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Sou . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/settings-module-admin.html#administrasyon",
    
    "relUrl": "/ht-rHT/user/settings-module-admin.html#administrasyon"
  },"4320": {
    "doc": "Settings — Modules & Admin",
    "title": "Related Topics",
    "content": ". | Settings — Radio & User — core node and user profile settings | Module configuration reference — detailed module docs on meshtastic.org | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/settings-module-admin.html#related-topics",
    
    "relUrl": "/ht-rHT/user/settings-module-admin.html#related-topics"
  },"4321": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": " ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/settings-module-admin.html",
    
    "relUrl": "/ht-rHT/user/settings-module-admin.html"
  },"4322": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": "Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled. 💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders: . . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/settings-module-admin.html#settings--modules--admin",
    
    "relUrl": "/sr-rLatn/user/settings-module-admin.html#settings--modules--admin"
  },"4323": {
    "doc": "Settings — Modules & Admin",
    "title": "Конфигурација модула",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Опис | . | MQTT enabled | Toggle MQTT bridge | . | Адреса | MQTT broker address | . | Корисничко име | Authentication username | . | Лозинка | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Опис | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Опис | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Isteklo vreme | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Опис | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Output duration (milliseconds) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Мелодија звона | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Опис | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Број записа | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Сервер | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Опис | . | Range test enabled | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Опис | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Опис | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Поруке | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Опис | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Опис | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Опис | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update interval (seconds) | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Опис | . | LED state | Turn the LED on or off | . | Струја | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Опис | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum broadcast (seconds) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Пријатељски назив | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Опис | . | Paxcounter enabled | Activate people counting | . | Update interval (seconds) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/settings-module-admin.html#%D0%BA%D0%BE%D0%BD%D1%84%D0%B8%D0%B3%D1%83%D1%80%D0%B0%D1%86%D0%B8%D1%98%D0%B0-%D0%BC%D0%BE%D0%B4%D1%83%D0%BB%D0%B0",
    
    "relUrl": "/sr-rLatn/user/settings-module-admin.html#конфигурација-модула"
  },"4324": {
    "doc": "Settings — Modules & Admin",
    "title": "Administracija",
    "content": "Udaljena administracija . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Поново покрени | Restarts the node | . | Искључи | Powers the node down | . | Рестартовање на фабричка подешавања | Returns every setting to its factory default | . | Ресетовање базе чворова | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Напредно . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Panel za otklanjanje grešaka . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. Подешавања апликације . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. O nama . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/settings-module-admin.html#administracija",
    
    "relUrl": "/sr-rLatn/user/settings-module-admin.html#administracija"
  },"4325": {
    "doc": "Settings — Modules & Admin",
    "title": "Related Topics",
    "content": ". | Settings — Radio & User — core node and user profile settings | Module configuration reference — detailed module docs on meshtastic.org | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/settings-module-admin.html#related-topics",
    
    "relUrl": "/sr-rLatn/user/settings-module-admin.html#related-topics"
  },"4326": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": " ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/settings-module-admin.html",
    
    "relUrl": "/sr-rLatn/user/settings-module-admin.html"
  },"4327": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": "Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled. 💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders: . . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/settings-module-admin.html#settings--modules--admin",
    
    "relUrl": "/nl-rNL/user/settings-module-admin.html#settings--modules--admin"
  },"4328": {
    "doc": "Settings — Modules & Admin",
    "title": "Module-configuratie",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Beschrijving | . | MQTT ingeschakeld | Toggle MQTT bridge | . | Adres | MQTT broker address | . | Gebruikersnaam | Authentication username | . | Wachtwoord | Authentication password | . | Encryptie ingeschakeld | Encrypt MQTT payloads | . | JSON uitvoer ingeschakeld | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS ingeschakeld | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client ingeschakeld | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Kaartrapportage | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Beschrijving | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Beschrijving | . | Serieel ingeschakeld | Activate serial communication | . | Echo ingeschakeld | Echo received serial data back | . | Seriële modus | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Time-Out | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Beschrijving | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Gebruik PWM zoemer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Output duur (milliseconden) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Beltoon | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Beschrijving | . | Store & Forward enabled | Activate store and forward | . | Hartslag | Periodically announce this node’s store-and-forward capability | . | Aantal records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Beschrijving | . | Range test enabled | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Beschrijving | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Beschrijving | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Berichten | Newline-separated list of messages | . | Verstuur bel | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Beschrijving | . | CODEC 2 ingeschakeld | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S klok | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Beschrijving | . | Externe hardware ingeschakeld | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Beschikbare pinnen | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Beschrijving | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update-interval (seconden) | How often to broadcast neighbor list | . | Zend over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Beschrijving | . | LED status | Turn the LED on or off | . | Huidige | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Beschrijving | . | Bewegingssensor Ingeschakeld | Activate detection sensor | . | GPIO pin om te monitoren | GPIO pin connected to sensor | . | Detectie trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimale broadcast (seconden) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Weergavenaam | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Beschrijving | . | Paxcounter ingeschakeld | Activate people counting | . | Update-interval (seconden) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/settings-module-admin.html#module-configuratie",
    
    "relUrl": "/nl-rNL/user/settings-module-admin.html#module-configuratie"
  },"4329": {
    "doc": "Settings — Modules & Admin",
    "title": "Beheer",
    "content": "Extern beheer . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Herstart | Restarts the node | . | Zet uit | Powers the node down | . | Reset naar fabrieksinstellingen | Returns every setting to its factory default | . | NodeDB reset | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Back-up & Herstellen . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Debug-paneel . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Over . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/settings-module-admin.html#beheer",
    
    "relUrl": "/nl-rNL/user/settings-module-admin.html#beheer"
  },"4330": {
    "doc": "Settings — Modules & Admin",
    "title": "Related Topics",
    "content": ". | Settings — Radio & User — core node and user profile settings | Module configuration reference — detailed module docs on meshtastic.org | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/settings-module-admin.html#related-topics",
    
    "relUrl": "/nl-rNL/user/settings-module-admin.html#related-topics"
  },"4331": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": " ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/settings-module-admin.html",
    
    "relUrl": "/nl-rNL/user/settings-module-admin.html"
  },"4332": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": "Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled. 💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders: . . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/settings-module-admin.html#settings--modules--admin",
    
    "relUrl": "/uk-rUA/user/settings-module-admin.html#settings--modules--admin"
  },"4333": {
    "doc": "Settings — Modules & Admin",
    "title": "Налаштування модуля",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Опис | . | MQTT увімкнений | Toggle MQTT bridge | . | Адреса | MQTT broker address | . | Ім’я користувача | Authentication username | . | Пароль | Authentication password | . | Шифрування увімкнено | Encrypt MQTT payloads | . | Вивід JSON увімкнено | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS увімкнений | Use secure connection | . | Кореневий чат | Base MQTT topic path | . | Проксі для клієнта увімкнуто | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT проксі на цьому телефоні | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Відображення на мапі | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Опис | . | Погоджуюся. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Інтервал звітування на мапі (секунди) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Опис | . | Послідовний порт увімкнено | Activate serial communication | . | Відлуння активоване | Echo received serial data back | . | Послідовний режим | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Швидкість послідовного порту | Port speed | . | Таймаут | How long to wait before considering an incoming message complete | . | Перевизначити послідовний порт | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Опис | . | Зовнішні сповіщення увімкнено | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Вихідний LED (GPIO) | Pin the LED is wired to | . | Активний високий рівень світлодіода | Whether the LED pin is active high or low | . | Вихідний гудок (GPIO) | Pin the buzzer is wired to | . | Вихід вібросигналу (GPIO) | Pin the vibration motor is wired to | . | Використовувати зумер із ШІМ-керуванням | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Використовувати I2S як гудок | Send the alert through an I2S audio output instead | . | Тривалість виводу (мілісекунд) | How long a single alert lasts | . | Інтервал нагадувань (секунди) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Мелодія | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Опис | . | Збереження та перенаправлення увімкнено | Activate store and forward | . | Пульсація | Periodically announce this node’s store-and-forward capability | . | Кількість записів | Maximum stored messages | . | Максимальний обсяг історії | Max messages to replay | . | Максимальне вікно історії | Time window for replay | . | Сервер | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Опис | . | Тест на відстань увімкнений | Activate range testing | . | Інтервал надсилання повідомлень (секунди) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Зберегти .CSV у сховищі (лише ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Опис | . | Надсилати телеметрію пристрою | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Інтервал оновлення показників пристрою | How often to report battery, uptime and channel utilization | . | Модуль екологічних показників увімкнено | Report the attached environment sensors | . | Інтервал оновлення екологічних показників | How often to report them | . | Екологічні показники на екрані увімкнено | Also show these readings on the device’s own display | . | Екологічні показники використовують шкалу Фаренгейта | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Модуль показників якості повітря увімкнено | Report particulate and CO₂ sensor data | . | Інтервал оновлення показників якості повітря | How often to report them | . | Модуль показників потужності ввімкнено | Report the per-channel voltage and current readings | . | Інтервал оновлення показників потужності | How often to report them | . | Показники потужності на екрані ввімкнено | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Опис | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Повідомлення | Newline-separated list of messages | . | Надіслати дзвіночок | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Енкодер #1 активований | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Увімкнути керування Вгору/Вниз/Вибір | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Опис | . | CODEC 2 увімкнено | Activate audio module | . | Частота дискретизації CODEC2 | Audio quality/bandwidth tradeoff | . | PTT контакт | GPIO pin for the push-to-talk button | . | Вибір слова I2S | GPIO pin for I2S WS | . | Вибір входу I2S | GPIO pin for I2S DIN | . | Вибір виходу I2S | GPIO pin for I2S DOUT | . | I2S тактування | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Опис | . | Конфігурація віддаленого пристрою активована | Activate remote GPIO access | . | Дозволити доступ до невизначених пінів | Allow access to any GPIO pin (security risk) | . | Доступні піни | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Опис | . | Інформацію про сусідів увімкнено | Activate neighbor broadcasting | . | Інтервал оновлення (секунд) | How often to broadcast neighbor list | . | Передавати через LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Опис | . | Стан світлодіоду | Turn the LED on or off | . | Поточний | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Опис | . | Датчик виявлення увімкнено | Activate detection sensor | . | GPIO контакт для моніторингу | GPIO pin connected to sensor | . | Тип тригера виявлення | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Використовувати режим INPUT_PULLUP | Enable the pin’s internal pull-up resistor | . | Мінімальний період розсилки (секунди) | Minimum time between alert broadcasts | . | Інтервал трансляції стану (секунди) | Periodic state broadcast interval | . | Надсилати дзвіночок з тривожним повідомленням | Include bell character in alerts | . | Дружня назва | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Опис | . | Лічильник пристроїв активований | Activate people counting | . | Інтервал оновлення (секунд) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/settings-module-admin.html#%D0%BD%D0%B0%D0%BB%D0%B0%D1%88%D1%82%D1%83%D0%B2%D0%B0%D0%BD%D0%BD%D1%8F-%D0%BC%D0%BE%D0%B4%D1%83%D0%BB%D1%8F",
    
    "relUrl": "/uk-rUA/user/settings-module-admin.html#налаштування-модуля"
  },"4334": {
    "doc": "Settings — Modules & Admin",
    "title": "Адміністрування",
    "content": "Віддалене керування . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Встановити час | Sends your phone’s clock to the node | . | Перевантажити | Restarts the node | . | Вимкнути | Powers the node down | . | Скинути до заводських налаштувань | Returns every setting to its factory default | . | Очищення бази вузлів | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Резервна копія & Відновлення . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Розширені . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Очистити базу даних вузлів . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Панель налагодження . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Про . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Подяки . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/settings-module-admin.html#%D0%B0%D0%B4%D0%BC%D1%96%D0%BD%D1%96%D1%81%D1%82%D1%80%D1%83%D0%B2%D0%B0%D0%BD%D0%BD%D1%8F",
    
    "relUrl": "/uk-rUA/user/settings-module-admin.html#адміністрування"
  },"4335": {
    "doc": "Settings — Modules & Admin",
    "title": "Related Topics",
    "content": ". | Settings — Radio & User — core node and user profile settings | Module configuration reference — detailed module docs on meshtastic.org | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/settings-module-admin.html#related-topics",
    
    "relUrl": "/uk-rUA/user/settings-module-admin.html#related-topics"
  },"4336": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": " ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/settings-module-admin.html",
    
    "relUrl": "/uk-rUA/user/settings-module-admin.html"
  },"4337": {
    "doc": "Asetukset — Moduulit ja ylläpito",
    "title": "Asetukset — Moduulit ja ylläpito",
    "content": "Määritä valinnaiset ominaisuusmoduulit ja suorita laitteen ylläpitotoimia. Moduulit laajentavat Meshtasticia erikoisominaisuuksilla — jokainen voidaan ottaa käyttöön tai poistaa käytöstä erikseen. 💡 Vinkki: Ota käyttöön vain ne moduulit, joita todella käytät. Käyttämättömien moduulien poistaminen käytöstä vähentää lähetyksen käyttöastetta, säästää akkua ja yksinkertaistaa määrityksiä. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Moduuliasetukset käyttävät korttipohjaista asettelua, jossa on kytkimiä, pudotusvalikoita, tekstikenttiä ja liukusäätimiä: . . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/settings-module-admin.html",
    
    "relUrl": "/fi-rFI/user/settings-module-admin.html"
  },"4338": {
    "doc": "Asetukset — Moduulit ja ylläpito",
    "title": "Moduulin asetukset",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Yhdistää verkon viestejä MQTT-välityspalvelimeen ja sieltä takaisin internet-yhteyksiä varten. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Asetus | Kuvaus | . | MQTT käytössä | Ota MQTT-välityspalvelin käyttöön | . | Osoite | MQTT-välityspalvelimen osoite | . | Käyttäjänimi | Todennuksen käyttäjätunnus | . | Salasana | Todennuksen salasana | . | Salaus käytössä | Salaa MQTT-viestisisällöt | . | JSON ulostulo käytössä | Julkaise ja vastaanota MQTT-viestejä JSON-muodossa. Merkitty protobuf-rakenteessa vanhentuneeksi, mutta tämä on edelleen ainoa asetus tähän toimintaan, ja laiteohjelmisto käyttää sitä yhä | . | TLS käytössä | Käytä suojattua yhteyttä | . | Palvelimen osoite (root topic) | MQTT:n perusaihepolku | . | Välityspalvelin käytössä | Anna yhdistetyn puhelimen välittää radion MQTT-liikenne sen sijaan, että radio muodostaisi itse yhteyden välityspalvelimeen | . | MQTT-välityspalvelin tällä puhelimella | Yllä olevan Välitys asiakkaalle käytössä -asetuksen puhelinpään osuus: käyttääkö tämä puhelin kyseistä välitystä. Katso MQTT | . | Karttaraportointi | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Asetus | Kuvaus | . | Hyväksyn. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Karttaraportoinnin aikaväli (sekuntia) | Kuinka usein sijainti julkaistaan. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . Katso MQTT saadaksesi yksityiskohtaisen käyttöoppaan, joka sisältää salauksen, tietosuojan ja välityspalvelimen määrityksen. Serial module . Mahdollistaa sarjaporttiviestinnän ulkoisten laiteintegraatioiden kanssa (GPS-moduulit, anturit tai mukautettu laitteisto). Kun tämä on käytössä, radion sarjaportti voi lähettää ja vastaanottaa protobuf- tai tekstimuotoista dataa, jolloin ulkoiset mikrokontrollerit tai tietokoneet voivat olla vuorovaikutuksessa verkon kanssa. | Asetus | Kuvaus | . | Sarjaportti käytössä | Ota sarjaporttiviestintä käyttöön | . | Palautus päällä | Toista vastaanotettu sarjaporttidata takaisin | . | Sarjaportin tila | Portin käyttämä protokolla – Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, YE.Direct, MeshSolar config, Log tai Log (vain teksti) | . | Vastaanotto / lähetys | Sarjayhteyden GPIO-nastat | . | Sarjaportin nopeus | Portin nopeus | . | Aikakatkaisu | Kuinka kauan odotetaan ennen kuin saapuva viesti katsotaan kokonaiseksi | . | Korvaa konsolin sarjaportti | Ota käyttöön portti, jota virheenkorjauskonsoli normaalisti käyttää | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Hyödyllinen laitteille, joiden täytyy ilmoittaa fyysisesti viestin saapumisesta — erityisen hyödyllinen valvomattomissa tai ulkokäyttöön asennetuissa laitteissa. Käynnistimiä on kaksi – saapuva viesti ja vastaanotettu BEL-ohjausmerkki – ja kumpikin voi ohjata LED-valoa, summeria ja värinämoottoria erikseen, joten käytettävissä on kuusi kytkintä. | Asetus | Kuvaus | . | Ulkoiset ilmoitukset käytössä | Moduulin pääkytkin | . | Hälytysviesti: LED / summeri / värinä | Mitkä lähdöt aktivoituvat saapuvasta viestistä | . | Hälytysmerkki: LED / summeri / värinä | Mitkä lähdöt aktivoituvat vastaanotetusta BEL-ohjausmerkistä | . | Ulostulon LED (GPIO) | LED on kytketty nastaan | . | Ulostulon LED aktiivinen | Onko LED-nasta aktiivinen korkealla vai matalalla tasolla | . | Ulostulon äänimerkki (GPIO) | Summeri on kytketty nastaan | . | Ulostulon värinä (GPIO) | Värinämoottori on kytketty nastaan | . | Käytä PWM-äänimerkkiä | Ohjaa summeria PWM:llä, jolloin voidaan toistaa ääniä yhden kiinteän taajuuden sijaan | . | Käytä I2S protokollaa äänimerkille | Lähetä hälytys sen sijaan I2S-äänilähdön kautta | . | Ulostulon kesto (millisekuntia) | Kuinka kauan yksittäinen hälytys kestää | . | Hälytysaikakatkaisu (sekuntia) | Toista hälytystä tämän ajan, kunnes se kuitataan. 0 poistaa toistuvan muistutuksen käytöstä | . | Soittoääni | PWM-summerilla toistettava RTTTL-soittoääni. Voidaan tuoda tiedostosta | . Store & Forward module . Puskuroi viestejä radioille, jotka ovat tilapäisesti poissa verkosta, ja toimittaa ne, kun nämä radiot yhdistyvät uudelleen. Välttämätön verkoissa, joissa radiot siirtyvät säännöllisesti kuuluvuusalueelle ja sen ulkopuolelle — varmistaa, etteivät viestit katoa lyhyiden yhteyskatkosten aikana. | Asetus | Kuvaus | . | Tallenna ja lähetä edelleen | Ota Varastoi & välitä käyttöön | . | Valvontasignaali | Ilmoita tämän radion varastoi & välitä -ominaisuudesta säännöllisesti | . | Kirjausten määrä | Tallennettujen viestien enimmäismäärä | . | Historian maksimimäärä | Toistettavien viestien enimmäismäärä | . | Historian aikamäärä | Aikaikkuna viestien toistolle | . | Palvelin | Toimi mesh-verkon varastoi & välitä -palvelimena (edellyttää riittävästi muistia, esimerkiksi ESP32 PSRAM:lla) | . 💡 Vinkki: Varastoi & välitä toimii parhaiten radioissa, joissa on runsaasti muistia (ESP32 ja PSRAM). Router-roolin radiot ovat ihanteellisia ehdokkaita, koska ne ovat yleensä jatkuvasti käynnissä. Range Test module . ⚠️ Varoitus: Kuuluvuustesti toimii vain suojatulla ensisijaisella kanavalla. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automaattinen kuuluvuustestityökalu radioiden välisen yhteyden laadun arviointiin. Kun toiminto on käytössä, radio lähettää säännöllisesti testiviestejä kasvavilla laskuriarvoilla. Vastaanottava radio kirjaa nämä viestit, jolloin voit myöhemmin kävellä tai ajaa pois ja analysoida, millä etäisyydellä viestien saapuminen loppui. | Asetus | Kuvaus | . | Kuuluvuustesti käytössä | Ota kuuluvuustesti käyttöön | . | Viestien lähetyksen aikaväli (sekuntia) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Tallenna .CSV (ESP32 ainoastaan) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Määrittää, mitä telemetriatietoja radiosi jakaa verkkoon. Telemetria sisältää laitteen kuntoon liittyviä tietoja (akun varaustaso, käyttöaika) sekä ympäristöanturien tietoja (lämpötila, kosteus, ilmanpaine). Jokaisella neljällä mittausryhmällä on oma käyttöönottokytkin ja oma mittausväli, joten esimerkiksi akun tila voidaan raportoida usein ja anturitiedot harvemmin. | Asetus | Kuvaus | . | Lähetä laitteen telemetriatiedot | Laitemittausten pääkytkin. Näkyy vain laiteohjelmistoversiossa 2.7.12 ja uudemmissa | . | Laitemittareiden päivitysväli | How often to report battery, uptime and channel utilization | . | Ympäristötietojen moduuli käytössä | Raportoi liitettyjen ympäristöanturien tiedot | . | Ympäristömittareiden päivitysväli | Kuinka usein tiedot raportoidaan | . | Näytä ympäristötiedot näytöllä | Näytä nämä tiedot myös radion omalla näytöllä | . | Käytä Fahrenheit yksikköä | Käytä radion näytössä Fahrenheit-asteita. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Ilmanlaadun tietojen moduuli käytössä | Raportoi hiukkas- ja CO₂-anturin tiedot | . | Ilmanlaatumittareiden päivitysväli | Kuinka usein tiedot raportoidaan | . | Virrankulutuksen moduuli käytössä | Raportoi kanavakohtaiset jännite- ja virtamittaukset | . | Virtamittareiden päivitysväli | Kuinka usein tiedot raportoidaan | . | Virrankulutuksen näyttö käytössä | Näytä virtamittaukset myös radion omalla näytöllä | . Katso Telemetria ja anturit saadaksesi tietoa tuetuista antureista ja määrityssuosituksista. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Määritä luettelo pikaviesteistä, jotka voidaan lähettää ilman yhdistettyä puhelinta — ihanteellinen kenttäkäyttöön. | Asetus | Kuvaus | . | Valmisviesti käytössä | ⚠️ Vanhentunut protobuf-rakenteessa | . | Viestit | Rivinvaihdoilla eroteltu viestiluettelo | . | Lähetä äänimerkki | Lähetä viestin mukana BEL-ohjausmerkki, jotta vastaanottavan radion Ulkoiset ilmoitukset -moduuli voi antaa hälytyksen | . | Kiertovalitsin #1 käytössä | Käytä kiertokoodainta syöttölaitteena | . | GPIO pin for rotary encoder A / B / Press port | Kolme nastaa, joihin kiertokoodain on kytketty | . | Generate input event on Press / CW / CCW | Minkä näppäintapahtuman kukin kiertokoodaimen toiminto tuottaa | . | Ylös/Alas/Valitse syöte käytössä | Erillinen, yksinkertaisempi syöttötapa, jossa käytetään ylös-/alas-/valitse-painikkeita kiertokoodaimen sijaan | . | Salli syöttölähde | ⚠️ Vanhentunut protobuf-rakenteessa | . Audio module . Codec2-äänituki matalan kaistanleveyden puheviestintään verkossa. Tämä on kokeellinen ominaisuus, joka koodaa puheen erittäin pieniksi datapaketeiksi käyttäen Codec2-koodekkia. | Asetus | Kuvaus | . | CODEC 2 käytössä | Ota äänimoduuli käyttöön | . | CODEC2 näytteenottotaajuus | Äänenlaadun ja kaistanleveyden välinen kompromissi | . | PTT-pinni | PTT-painikkeen GPIO-nasta | . | I2S-sanan valinta | GPIO-pinni I2S WS:lle | . | I2S-datatulo | GPIO-nasta I2S DIN:lle | . | I2S-datalähtö | GPIO-pinni I2S DOUT:lle | . | I2S-kello | I2S-bittikellon GPIO-nasta | . ℹ️ Huomautus: Ääniominaisuus edellyttää yhteensopivaa laitteistoa (I2S-mikrofoni ja -kaiutin). Äänenlaatu on hyvin matalakaistainen — ajattele “ymmärrettävää radiopuhetta”, ei puhelinlaatua. Remote Hardware module . GPIO-ohjaus mesh-verkon kautta. Mahdollistaa etäradion lukea tai kirjoittaa GPIO-nastoja toisessa radiossa — hyödyllinen releiden aktivointiin, kytkimien lukemiseen tai ulkoisen laitteiston ohjaamiseen etäältä. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Asetus | Kuvaus | . | Etälaitteen ohjaus käytössä | Ota etä-GPIO-käyttö käyttöön | . | Salli määrittämättömän pinnin käyttö | Salli pääsy mihin tahansa GPIO-nastaan (tietoturvariski) | . | Käytettävissä olevat pinnit | Enintään 4 tämän radion etälukuun tai kirjoitukseen tarjoamaa GPIO-pinniä | . Neighbor Info module . Lähettää tietoa suoraan kuulluista naapureista mahdollistaen verkon topologian kartoituksen. Jokainen käyttöön otettu radio jakaa säännöllisesti luettelon muista radioista, jotka se kuulee, sekä niiden signaalin laadun. | Asetus | Kuvaus | . | Naapuritiedot käytössä | Ota naapuritiedon lähetys käyttöön | . | Päivityksen aikaväli (sekuntia) | Kuinka usein naapuriluettelo lähetetään | . | Lähetä LoRa:n kautta | Lähetä myös naapuritiedot LoRa:n kautta, ei pelkästään MQTT:n tai puhelimen kautta. Ei käytettävissä kanavalla, joka käyttää oletusavainta ja nimeä | . Katso Paikallinen mesh-haku, miten naapuritietoja käytetään mesh-verkon rakenteen tutkimiseen. Ambient Lighting module . Ohjaa tuetuissa laitteissa olevaa NeoPixeliä tai muita osoitteellisia RGB-LEDejä. Voidaan käyttää visuaalisina tilailmaisimina, ilmoitusvaloina tai koriste-efekteinä. | Asetus | Kuvaus | . | LED-tila | Kytke LED päälle tai pois päältä | . | Virta | LED-virran rajoitus (0–31) | . | Punainen / vihreä / sininen | Yksittäisten värikanavien arvot (0–255) | . Detection Sensor module . Muuttaa radiosi liike- tai ovitunnistimeen perustuvaksi hälytysjärjestelmäksi. Kun GPIO-pinni havaitsee tilamuutoksen (liike havaittu, ovi avattu), radio lähettää hälytysviestin verkkoon. | Asetus | Kuvaus | . | Tunnistinsensori käytössä | Ota tunnistusanturi käyttöön | . | GPIO-pinni valvontaa varten | Anturiin kytketty GPIO-pinni | . | Tunnistuksen tyyppi | Miten pinnin tila vastaa havaitsemistapahtumaa (esim. aktiivinen korkea/matala taso tai reunalaukaisu) | . | Käytä INPUT_PULLUP tilaa | Ota pinnin sisäinen ylösvetovastus käyttöön | . | Minimilähetys (sekuntia) | Hälytyslähetysten vähimmäisaika | . | Tilatiedon lähetys (sekuntia) | Tilatiedon lähetysväli | . | Lähetä äänimerkki hälytyssanoman kanssa | Sisällytä soittomerkkimerkki hälytyksiin | . | Käyttäjäystävällinen nimi | Tälle anturille määritetty nimi | . Paxcounter module . Henkilöt, jotka lasketaan WiFi- ja BLE-hakukyselyiden perusteella. Laskee lähellä olevia laitteita kuuntelemalla passiivisesti koepyyntöjä, joita puhelimet ja kannettavat tietokoneet lähettävät etsiessään verkkoja. Saatavilla vain ESP32-laitteissa. | Asetus | Kuvaus | . | PAX-laskuri käytössä | Ota henkilölaskenta käyttöön | . | Päivityksen aikaväli (sekuntia) | Kuinka usein laskentatiedot raportoidaan | . | WiFi-signaalin RSSI-kynnys | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE-signaalin RSSI-kynnys | Sama raja-arvo BLE-mainospaketeille (oletus: -80 dBm) | . 💡 Vinkki: PAX-laskuri on hyödyllinen jalankulkijamäärien arviointiin retkeilyreittien lähtöpisteissä, tapahtumapaikoilla tai muissa kohteissa. Laskentatulokset ovat arvioita — yhdellä henkilöllä voi olla useita laitteita mukana. Status Message module . Tilaviestillä ei ole omaa moduulinäkymää. Sitä muokataan yhdessä muiden radion tunnistetietojen kanssa kohdassa Asetukset → Radio ja käyttäjä. Mesh Beacon module . Lähettää kutsun mesh-verkkoosi ja vastaanottaa muiden lähettämiä kutsuja. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit -integraatio yhteensopivuutta varten ATAK- ja WinTAK-järjestelmien kanssa. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. Katso TAK-integraatio saadaksesi tarkemmat määritys- ja käyttöohjeet. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/settings-module-admin.html#moduulin-asetukset",
    
    "relUrl": "/fi-rFI/user/settings-module-admin.html#moduulin-asetukset"
  },"4339": {
    "doc": "Asetukset — Moduulit ja ylläpito",
    "title": "Ylläpito",
    "content": "Etähallinta . Määritä etänä radiot, jotka jakavat saman ylläpitoavaimen: . | Valitse kohderadio radioluettelosta. | Siirry kyseisen radion Asetukset-kohtaan. | Muokkaa määrityksiä. | Napauta Tallenna — muutokset lähetetään verkon kautta. | . ⚠️ Tärkeää: Edellyttää, että järjestelmänvalvojan avain on määritetty sekä omassa radiossasi että kohderadiossa. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Toiminto | Mitä se tekee | . | Aseta aika | Sends your phone’s clock to the node | . | Käynnistä uudelleen | Restarts the node | . | Sammuta | Powers the node down | . | Palauta tehdasasetukset | Returns every setting to its factory default | . | Tyhjennä NodeDB-tietokanta | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Varmuuskopiointi ja palautus . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Lisäasetukset . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Tyhjennä NodeDB-tietokanta . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Vianetsintäpaneeli . Avaa Paketit- ja Sovelluslokit-välilehdet diagnostiikkatietojen tarkastelua, suodatusta ja vientiä varten. Katso Virheenjäljityslokit, jossa on täydellinen käyttöohje. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Tietoja . Settings → About carries the app’s own identity rather than the node’s: . Kolme osiota: . | Mikä on Meshtastic? – lyhyt kuvaus projektista. | Sovellukset — avaa Tarvitsetko laitteiston? -näkymän, jossa on suosittujen laitteiden karuselli ja linkit niiden ostopaikkoihin. Siellä näytetään myös GitHub-tietovarasto, käytössä oleva sovellusversio ja Tekijätiedot (katso seuraava osio). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Kiitokset . Tietoja-kohdasta avattava näkymä, jossa luetellaan kaikki sovelluksen käyttämät avoimen lähdekoodin kirjastot lisensseineen. Luettelo luodaan käännöshetkellä AboutLibraries-kirjastolla. Tätä kutsuttiin aiemmin lisenssinäkymäksi. Troubleshooting remote admin . | Ei vastausta kohderadiolta — kohderadio voi olla kuuluvuusalueen ulkopuolella, poissa verkosta tai siinä voi olla eri ylläpitoavain. Varmista, että ylläpitoavain on sama molemmissa radioissa. | Muutokset eivät tule voimaan — jotkin asetukset edellyttävät uudelleenkäynnistystä ennen kuin ne astuvat voimaan. Kokeile Uudelleenkäynnistystä tallennuksen jälkeen. | Et näe etäasetuksia — varmista, että radiossasi on kohderadion ylläpitoavain. Ylläpitokanava määritetään automaattisesti, kun ylläpitoavain on asetettu. | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/settings-module-admin.html#yll%C3%A4pito",
    
    "relUrl": "/fi-rFI/user/settings-module-admin.html#ylläpito"
  },"4340": {
    "doc": "Asetukset — Moduulit ja ylläpito",
    "title": "Aiheeseen liittyvät aiheet",
    "content": ". | Settings — Radio & User — core node and user profile settings | Moduulien määritysviite — yksityiskohtainen moduulidokumentaatio meshtastic.org-sivustolla | UKK – usein kysytyt kysymykset meshtastic.org -sivustolla | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/settings-module-admin.html#aiheeseen-liittyv%C3%A4t-aiheet",
    
    "relUrl": "/fi-rFI/user/settings-module-admin.html#aiheeseen-liittyvät-aiheet"
  },"4341": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": "Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled. 💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders: . . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/settings-module-admin.html#settings--modules--admin",
    
    "relUrl": "/is-rIS/user/settings-module-admin.html#settings--modules--admin"
  },"4342": {
    "doc": "Settings — Modules & Admin",
    "title": "Stillingar aukaeininga",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Lýsing | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Lýsing | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Lýsing | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Timeout | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Lýsing | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Output duration (milliseconds) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Lýsing | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Lýsing | . | Range test enabled | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Lýsing | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Lýsing | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Messages | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Lýsing | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Lýsing | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Lýsing | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update interval (seconds) | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Lýsing | . | LED state | Turn the LED on or off | . | Current | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Lýsing | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum broadcast (seconds) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Lýsing | . | Paxcounter enabled | Activate people counting | . | Update interval (seconds) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/settings-module-admin.html#stillingar-aukaeininga",
    
    "relUrl": "/is-rIS/user/settings-module-admin.html#stillingar-aukaeininga"
  },"4343": {
    "doc": "Settings — Modules & Admin",
    "title": "Administration",
    "content": "Remote Administration . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Endurræsa | Restarts the node | . | Slökkva | Powers the node down | . | Grunnstilla | Returns every setting to its factory default | . | Endurræsa NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Villuleitarborð . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Um smáforrit . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/settings-module-admin.html#administration",
    
    "relUrl": "/is-rIS/user/settings-module-admin.html#administration"
  },"4344": {
    "doc": "Settings — Modules & Admin",
    "title": "Related Topics",
    "content": ". | Settings — Radio & User — core node and user profile settings | Module configuration reference — detailed module docs on meshtastic.org | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/settings-module-admin.html#related-topics",
    
    "relUrl": "/is-rIS/user/settings-module-admin.html#related-topics"
  },"4345": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": " ",
    "url": "/Meshtastic-Android/main/is-rIS/user/settings-module-admin.html",
    
    "relUrl": "/is-rIS/user/settings-module-admin.html"
  },"4346": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": "Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled. 💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders: . . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/settings-module-admin.html#settings--modules--admin",
    
    "relUrl": "/lt-rLT/user/settings-module-admin.html#settings--modules--admin"
  },"4347": {
    "doc": "Settings — Modules & Admin",
    "title": "Modulio konfigūracija",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Aprašymas | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Aprašymas | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Aprašymas | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Baigėsi laikas | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Aprašymas | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Output duration (milliseconds) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Aprašymas | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Aprašymas | . | Range test enabled | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Aprašymas | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Aprašymas | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Messages | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Aprašymas | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Aprašymas | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Aprašymas | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update interval (seconds) | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Aprašymas | . | LED state | Turn the LED on or off | . | Current | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Aprašymas | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum broadcast (seconds) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Aprašymas | . | Paxcounter enabled | Activate people counting | . | Update interval (seconds) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/settings-module-admin.html#modulio-konfig%C5%ABracija",
    
    "relUrl": "/lt-rLT/user/settings-module-admin.html#modulio-konfigūracija"
  },"4348": {
    "doc": "Settings — Modules & Admin",
    "title": "Administravimas",
    "content": "Nuotolinis administravimas . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Perkrauti | Restarts the node | . | Išjungti | Powers the node down | . | Gamyklinis atstatymas | Returns every setting to its factory default | . | NodeDB perkrauti | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Derinimo skydelis . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Apie . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/settings-module-admin.html#administravimas",
    
    "relUrl": "/lt-rLT/user/settings-module-admin.html#administravimas"
  },"4349": {
    "doc": "Settings — Modules & Admin",
    "title": "Related Topics",
    "content": ". | Settings — Radio & User — core node and user profile settings | Module configuration reference — detailed module docs on meshtastic.org | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/settings-module-admin.html#related-topics",
    
    "relUrl": "/lt-rLT/user/settings-module-admin.html#related-topics"
  },"4350": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": " ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/settings-module-admin.html",
    
    "relUrl": "/lt-rLT/user/settings-module-admin.html"
  },"4351": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": "Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled. 💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders: . . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/settings-module-admin.html#settings--modules--admin",
    
    "relUrl": "/gl-rES/user/settings-module-admin.html#settings--modules--admin"
  },"4352": {
    "doc": "Settings — Modules & Admin",
    "title": "Configuración de módulo",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Descrición | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Descrición | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Descrición | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Timeout | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Descrición | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Output duration (milliseconds) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Descrición | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Descrición | . | Range test enabled | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Descrición | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Descrición | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Messages | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Descrición | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Descrición | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Descrición | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update interval (seconds) | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Descrición | . | LED state | Turn the LED on or off | . | Current | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Descrición | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum broadcast (seconds) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Descrición | . | Paxcounter enabled | Activate people counting | . | Update interval (seconds) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/settings-module-admin.html#configuraci%C3%B3n-de-m%C3%B3dulo",
    
    "relUrl": "/gl-rES/user/settings-module-admin.html#configuración-de-módulo"
  },"4353": {
    "doc": "Settings — Modules & Admin",
    "title": "Administration",
    "content": "Remote Administration . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Reiniciar | Restarts the node | . | Apagar | Powers the node down | . | Restablecemento de fábrica | Returns every setting to its factory default | . | Restablecer NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Panel de depuración . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Acerca de . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/settings-module-admin.html#administration",
    
    "relUrl": "/gl-rES/user/settings-module-admin.html#administration"
  },"4354": {
    "doc": "Settings — Modules & Admin",
    "title": "Related Topics",
    "content": ". | Settings — Radio & User — core node and user profile settings | Module configuration reference — detailed module docs on meshtastic.org | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/settings-module-admin.html#related-topics",
    
    "relUrl": "/gl-rES/user/settings-module-admin.html#related-topics"
  },"4355": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": " ",
    "url": "/Meshtastic-Android/main/gl-rES/user/settings-module-admin.html",
    
    "relUrl": "/gl-rES/user/settings-module-admin.html"
  },"4356": {
    "doc": "設定：モジュールと管理",
    "title": "設定：モジュールと管理",
    "content": "オプションの機能モジュールを設定し、デバイスの管理を行います。モジュールは、専用の機能で Meshtastic を拡張します。それぞれ個別に有効・無効を切り替えられます。 . 💡 ヒント： 実際に使うモジュールだけを有効にすれば十分です。使わないモジュールを無効にすると、電波利用時間が減り、バッテリーを節約でき、設定もシンプルになります。 A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. モジュールの設定は、トグルスイッチ、ドロップダウン、テキストフィールド、スライダーを備えたカード形式のレイアウトを使用します： . . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/settings-module-admin.html",
    
    "relUrl": "/ja-rJP/user/settings-module-admin.html"
  },"4357": {
    "doc": "設定：モジュールと管理",
    "title": "追加機能の設定",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . インターネット接続のために、メッシュのメッセージを MQTT サーバーとの間で橋渡しします。 This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | 設定項目 | 説明 | . | MQTTを有効化 | MQTT ブリッジを切り替え | . | アドレス | MQTT サーバーのアドレス | . | ユーザー名 | 認証用のユーザー名 | . | パスワード | 認証用のパスワード | . | 暗号化の有効化 | MQTT ペイロードを暗号化 | . | JSON出力の有効化 | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS の有効化 | セキュアな接続を使用 | . | ルート トピック | MQTT のベーストピックパス | . | クライアントへのプロキシの有効化 | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | このスマートフォンの MQTT プロキシ | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | マップレポート | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | 設定項目 | 説明 | . | 同意します。 | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | マップレポートの間隔 (秒) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . 暗号化、プライバシー、サーバーの設定を含む詳しい使い方は、MQTT を参照してください。 . Serial module . 外部デバイスとの連携（GPS モジュール、センサー、カスタムハードウェア）のために、シリアルポート通信を有効にします。有効にすると、ノードのシリアルポートで protobuf またはテキストデータを送受信でき、外部のマイコンやコンピューターがメッシュとやり取りできるようになります。 . | 設定項目 | 説明 | . | シリアル通信を有効化 | シリアル通信を有効化 | . | Echoを有効化 | 受信したシリアルデータをそのまま返す | . | シリアルモード | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | シリアルボーレイト | Port speed | . | タイムアウト | How long to wait before considering an incoming message complete | . | コンソールのシリアルポートを上書き | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. メッセージ到着時に物理的に知らせる必要があるデバイスに便利です。特に無人設置や屋外設置で役立ちます。 . There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | 設定項目 | 説明 | . | 外部通知を有効化 | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | LED出力 (GPIO) | Pin the LED is wired to | . | LED出力 アクティブハイ | Whether the LED pin is active high or low | . | ブザー出力(GPIO) | Pin the buzzer is wired to | . | バイブレーション出力 (GPIO) | Pin the vibration motor is wired to | . | PWMブザーを使用 | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | I2Sをブザーとして使用 | Send the alert through an I2S audio output instead | . | 出力時間 (ミリ秒) | How long a single alert lasts | . | 繰り返し通知間隔（秒） | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | 着信音 | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . 一時的にオフラインだったノードのためにメッセージをバッファリングし、それらのノードが再接続したときに再送します。ノードが頻繁に圏内・圏外を行き来するメッシュに不可欠です。短時間の切断中にメッセージが失われないようにします。 . | 設定項目 | 説明 | . | 一時保管と転送の有効化 | ストア＆フォワードを有効化 | . | ハートビート | このノードのストア＆フォワード機能を定期的に告知する | . | サーバーの最大保管レコード数 (デフォルト 約11,000レコード) | 保存するメッセージの最大数 | . | リクエスト可能な最大の履歴件数 | 再送するメッセージの最大数 | . | リクエスト可能な履歴の期間 (分) | 再送する時間の範囲 | . | サーバー | メッシュのストア＆フォワードサーバーとして動作する（十分なメモリが必要、例：PSRAM 搭載の ESP32） | . 💡 ヒント： ストア＆フォワードは、十分なメモリを持つノード（PSRAM 搭載の ESP32）で最も良く機能します。ルーターノードは通常は常時起動しているため、理想的な候補です。 . Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. ノード間のリンク品質を評価するための、自動レンジテストツールです。有効にすると、ノードはカウンターを増やしながらテストメッセージを定期的に送信します。受信側のノードがこれらのメッセージを記録するため、歩いたり車で移動したりして、後からどの距離でメッセージが届かなくなったかを分析できます。 . | 設定項目 | 説明 | . | レンジテストを有効化 | レンジテストを有効化 | . | 送信者のメッセージ間隔 (秒) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | ストレージにCSVファイルを保存(ESP32のみ) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . ノードがメッシュと共有するテレメトリデータを制御します。テレメトリには、デバイスの状態（バッテリー、連続稼働時間）と環境センサーのデータ（温度、湿度、気圧）が含まれます。 . Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | 設定項目 | 説明 | . | デバイステレメトリを送信 | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | デバイスメトリクスの更新間隔 | How often to report battery, uptime and channel utilization | . | 環境メトリクスモジュールを有効化 | Report the attached environment sensors | . | 環境メトリクスの更新間隔 | How often to report them | . | 環境メトリクスを画面上で有効化 | Also show these readings on the device’s own display | . | 環境メトリクスは華氏を使用 | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | 空気品質測定モジュールを有効化 | Report particulate and CO₂ sensor data | . | 空気品質メトリクスの更新間隔 | How often to report them | . | 電源メトリクスモジュール有効 | Report the per-channel voltage and current readings | . | 電源メトリクスの更新間隔 | How often to report them | . | 電源メトリクスを画面上で有効化 | Also show power readings on the device’s display | . 対応センサーと設定の推奨事項については、テレメトリとセンサー を参照してください。 . Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). スマートフォンを接続していなくても送信できる、クイック送信メッセージのリストを定義します。フィールドでの使用に最適です。 . | 設定項目 | 説明 | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | メッセージ | 改行で区切ったメッセージのリスト | . | ベルを送信 | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | ロータリーエンコーダ #1 を有効化 | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | 上下/選択入力を有効化 | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . メッシュ上での低帯域幅の音声通信のための、Codec2 音声サポートです。これは、Codec2 コーデックを使って音声を非常に小さなデータパケットにエンコードする、実験的な機能です。 . | 設定項目 | 説明 | . | CODEC 2 を有効化 | オーディオモジュールを有効化 | . | CODEC2 サンプルレート | 音質と帯域幅のトレードオフ | . | PTT端子 | GPIO pin for the push-to-talk button | . | I2S ワードセレクト | I2S WS 用の GPIO ピン | . | I2S データ IN | I2S DIN 用の GPIO ピン | . | I2S データ OUT | I2S DOUT 用の GPIO ピン | . | I2S クロック | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). 音質は非常に低帯域です。「聞き取れる無線の声」程度で、電話並みの品質ではないと考えてください。 . Remote Hardware module . メッシュネットワーク経由での GPIO 制御です。リモートのノードが、別のノードの GPIO ピンを読み書きできるようにします。リレーの作動、スイッチの読み取り、離れた場所からの外部ハードウェア制御に便利です。 . ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | 設定項目 | 説明 | . | リモートハードウェアを有効化 | リモート GPIO アクセスを有効化 | . | 未定義のピンへのアクセスを許可 | 任意の GPIO ピンへのアクセスを許可（セキュリティリスク） | . | 使用可能な端子 | このノードがリモートの読み書き用に公開する GPIO ピン（最大 4 個） | . Neighbor Info module . 直接受信した隣接ノードの情報をブロードキャストし、メッシュのトポロジーマッピングを可能にします。有効にした各ノードは、受信できる他のノードとその信号品質のリストを定期的に共有します。 . | 設定項目 | 説明 | . | 近隣ノード情報を有効化 | 隣接ノードのブロードキャストを有効化 | . | 更新間隔 (秒) | 隣接ノードのリストをブロードキャストする頻度 | . | LoRaで送信 | MQTT／スマートフォンだけでなく、LoRa 経由でも隣接ノード情報をブロードキャストします。デフォルトの鍵と名前を使用しているチャンネルでは利用できません | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . 対応ハードウェア上の、オンボードの NeoPixel やその他のアドレサブル RGB LED を制御します。視覚的なステータス表示、通知ライト、装飾的な演出に使用できます。 . | 設定項目 | 説明 | . | LEDの状態 | LED のオン／オフを切り替え | . | 電流 | LED の電流制限（0〜31） | . | 赤／緑／青 | 各色チャンネルの値（0〜255） | . Detection Sensor module . ノードを、動きやドアを検知するセンサーアラートシステムに変えます。 GPIO ピンが状態の変化（動きの検知、ドアの開放）を検出すると、ノードはメッシュ経由でアラートメッセージをブロードキャストします。 . | 設定項目 | 説明 | . | 検出センサーを有効化 | 検知センサーを有効化 | . | モニターのGPIOピン | センサーに接続された GPIO ピン | . | 検出トリガーの種類 | ピンの状態を検知イベントにどう対応させるか（例：アクティブハイ／ロー、エッジトリガー） | . | INPUT_PULLUP モードを使用 | ピンの内蔵プルアップ抵抗を有効にする | . | 最小ブロードキャスト間隔(秒) | アラートのブロードキャスト間の最小時間 | . | 状態のブロードキャスト間隔 (秒) | 定期的な状態ブロードキャストの間隔 | . | アラートメッセージ付きのベルを送信 | アラートにベル文字を含める | . | 名前 | このセンサーのカスタム名 | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. スマートフォンやノートパソコンがネットワークを探すときに発するプローブ要求を受動的に受信して、近くのデバイスを数えます。 ESP32 デバイスでのみ利用できます。 . | 設定 | 説明 | . | Paxcounter を有効化 | 人数カウントを有効化 | . | 更新間隔 (秒) | カウントを報告する頻度 | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 ヒント： Paxcounter は、登山口やイベント会場などの人出を推定するのに便利です。カウントはおおよその値です。1 人が複数のデバイスを持っていることがあります。 . Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . ATAK および WinTAK と相互運用するための、Team Awareness Kit 連携です。 Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. 詳しい設定と使い方は、TAK 連携 を参照してください。 . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/settings-module-admin.html#%E8%BF%BD%E5%8A%A0%E6%A9%9F%E8%83%BD%E3%81%AE%E8%A8%AD%E5%AE%9A",
    
    "relUrl": "/ja-rJP/user/settings-module-admin.html#追加機能の設定"
  },"4358": {
    "doc": "設定：モジュールと管理",
    "title": "管理",
    "content": "リモート管理 . 管理者鍵を共有しているノードをリモートで設定します： . | ノードリストで対象のノードを選択します。 | そのノードの「設定」に移動します。 | 設定を変更します。 | 「保存」をタップします。変更がメッシュ経由で送信されます。 | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | 操作 | 内容 | . | 時刻を設定 | Sends your phone’s clock to the node | . | 再起動 | Restarts the node | . | シャットダウン | Powers the node down | . | 出荷時にリセット | Returns every setting to its factory default | . | NodeDBをリセット | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. バックアップと復元 . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. 詳細設定 . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. ノードデータベースの整理 . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. デバッグ . 診断出力の表示・絞り込み・エクスポートを行う「パケット」タブと「アプリログ」タブを開きます。詳しい手順は、デバッグログ を参照してください。 . App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. 概要 . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. 謝辞 . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | 「対象ノードから応答がありません」：対象が圏外、オフライン、または管理者鍵が一致していない可能性があります。両方のノードで管理者鍵が一致しているか確認してください。 | 変更が適用されない：一部の設定は、反映に再起動が必要です。保存後に「再起動」を実行してみてください。 | リモートの設定が表示されない：自分のノードに、対象ノードの管理者鍵があることを確認してください。管理チャンネルは、管理者鍵を設定すると自動的に構成されます。 | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/settings-module-admin.html#%E7%AE%A1%E7%90%86",
    
    "relUrl": "/ja-rJP/user/settings-module-admin.html#管理"
  },"4359": {
    "doc": "設定：モジュールと管理",
    "title": "関連トピック",
    "content": ". | Settings — Radio & User — core node and user profile settings | モジュール設定リファレンス：meshtastic.org にある詳細なモジュールのドキュメント | FAQ：meshtastic.org のよくある質問 | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/settings-module-admin.html#%E9%96%A2%E9%80%A3%E3%83%88%E3%83%94%E3%83%83%E3%82%AF",
    
    "relUrl": "/ja-rJP/user/settings-module-admin.html#関連トピック"
  },"4360": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": "Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled. 💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders: . . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/settings-module-admin.html#settings--modules--admin",
    
    "relUrl": "/de-rDE/user/settings-module-admin.html#settings--modules--admin"
  },"4361": {
    "doc": "Settings — Modules & Admin",
    "title": "Moduleinstellungen",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Einstellung | Beschreibung | . | MQTT aktiviert | Toggle MQTT bridge | . | Adresse | MQTT broker address | . | Benutzername | Authentication username | . | Passwort | Authentication password | . | Verschlüsselung aktiviert | Encrypt MQTT payloads | . | JSON-Ausgabe aktiviert | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS aktiviert | Use secure connection | . | Hauptthema | Base MQTT topic path | . | Proxy zu Client aktiviert | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT Proxy auf diesem Handy | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Kartenberichte | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Einstellung | Beschreibung | . | Ich stimme zu. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Kartenberichtsintervall (Sekunden) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Einstellung | Beschreibung | . | Serielle Schnittstelle aktiviert | Activate serial communication | . | Echo aktiviert | Echo received serial data back | . | Serieller Modus | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serielle Baudrate | Port speed | . | Zeitlimit erreicht | How long to wait before considering an incoming message complete | . | Seriellen Anschluss der Konsole überschreiben | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Einstellung | Beschreibung | . | Externe Benachrichtigungen aktiviert | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Ausgabe LED (GPIO) | Pin the LED is wired to | . | Ausgabe LED aktiv hoch | Whether the LED pin is active high or low | . | Ausgabe Summer (GPIO) | Pin the buzzer is wired to | . | Ausgabe Vibration (GPIO) | Pin the vibration motor is wired to | . | Benutze PWM Summer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | I2S als Buzzer verwenden | Send the alert through an I2S audio output instead | . | Ausgabedauer (GPIO) | How long a single alert lasts | . | Nervige Verzögerung (Sekunden) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Klingelton | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Einstellung | Beschreibung | . | Speichern & Weiterleiten aktiviert | Activate store and forward | . | Puls | Periodically announce this node’s store-and-forward capability | . | Anzahl Einträge | Maximum stored messages | . | Verlauf Rückgabewert maximal | Max messages to replay | . | Zeitraum Rückgabewert | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Einstellung | Beschreibung | . | Reichweitentest aktiviert | Activate range testing | . | Sendernachrichtenintervall (Sekunden) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Speichere .CSV im Speicher (nur ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Einstellung | Beschreibung | . | Gerätetelemetrie senden | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Aktualisierungsintervall für Gerätedaten | How often to report battery, uptime and channel utilization | . | Modul Umweltdaten aktiviert | Report the attached environment sensors | . | Aktualisierungsintervall für Umweltdaten | How often to report them | . | Umweltdatenanzeige aktiviert | Also show these readings on the device’s own display | . | Umweltdaten in Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Modul Luftqualität aktiviert | Report particulate and CO₂ sensor data | . | Aktualisierungsintervall der Luftqualität | How often to report them | . | Modul Energiedaten aktiviert | Report the per-channel voltage and current readings | . | Aktualisierungsintervall für Energiedaten | How often to report them | . | Energiedatenanzeige aktiviert | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Einstellung | Beschreibung | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Nachrichten | Newline-separated list of messages | . | Glocke senden | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Drehencoder #1 aktiviert | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select Eingang aktiviert | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Einstellung | Beschreibung | . | CODEC 2 aktiviert | Activate audio module | . | CODEC2 Abtastrate | Audio quality/bandwidth tradeoff | . | GPIO Pin PTT | GPIO pin for the push-to-talk button | . | I2S Wortauswahl | GPIO pin for I2S WS | . | I2S Daten Eingang | GPIO pin for I2S DIN | . | I2S Daten Ausgang | GPIO pin for I2S DOUT | . | I2S Takt | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Einstellung | Beschreibung | . | Einstellung entfernte Hardware | Activate remote GPIO access | . | Erlaube undefinierten Pin-Zugriff | Allow access to any GPIO pin (security risk) | . | Verfügbare Pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Einstellung | Beschreibung | . | Nachbarinformationen aktiviert | Activate neighbor broadcasting | . | Aktualisierungsintervall (Sekunden) | How often to broadcast neighbor list | . | Übertragen über LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Einstellung | Beschreibung | . | LED Zustand | Turn the LED on or off | . | Stromstärke | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Einstellung | Beschreibung | . | Erkennungssensor aktiviert | Activate detection sensor | . | Zu überwachender GPIO-Pin | GPIO pin connected to sensor | . | Typ der Erkennungsauslösung | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Eingang PULLUP Einstellung | Enable the pin’s internal pull-up resistor | . | Minimale Übertragungszeit (Sekunden) | Minimum time between alert broadcasts | . | Statusübertragung (Sekunden) | Periodic state broadcast interval | . | Glocke mit Warnmeldung senden | Include bell character in alerts | . | Anzeigename | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Einstellung | Beschreibung | . | Besucherzähler aktiviert | Activate people counting | . | Aktualisierungsintervall (Sekunden) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. Siehe TAK Integration für detaillierte Einrichtung und Nutzung. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/settings-module-admin.html#moduleinstellungen",
    
    "relUrl": "/de-rDE/user/settings-module-admin.html#moduleinstellungen"
  },"4362": {
    "doc": "Settings — Modules & Admin",
    "title": "Einstellung",
    "content": "Ferneinstellung . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Neustart | Restarts the node | . | Herunterfahren | Powers the node down | . | Auf Werkseinstellungen zurücksetzen | Returns every setting to its factory default | . | Node-Datenbank zurücksetzen | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Sichern & Wiederherstellen . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Fortgeschritten . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Knotendatenbank leeren . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Debug-Ausgaben . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Einstellungen . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Über . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Danksagungen . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/settings-module-admin.html#einstellung",
    
    "relUrl": "/de-rDE/user/settings-module-admin.html#einstellung"
  },"4363": {
    "doc": "Settings — Modules & Admin",
    "title": "Related Topics",
    "content": ". | Settings — Radio & User — core node and user profile settings | Module configuration reference — detailed module docs on meshtastic.org | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/settings-module-admin.html#related-topics",
    
    "relUrl": "/de-rDE/user/settings-module-admin.html#related-topics"
  },"4364": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": " ",
    "url": "/Meshtastic-Android/main/de-rDE/user/settings-module-admin.html",
    
    "relUrl": "/de-rDE/user/settings-module-admin.html"
  },"4365": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": "Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled. 💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders: . . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/settings-module-admin.html#settings--modules--admin",
    
    "relUrl": "/ar-rSA/user/settings-module-admin.html#settings--modules--admin"
  },"4366": {
    "doc": "Settings — Modules & Admin",
    "title": "إعدادات الجهاز",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | الوصف | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | الوصف | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | الوصف | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | استغرق وقت طويل | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | الوصف | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Output duration (milliseconds) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | الوصف | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | الوصف | . | Range test enabled | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | الوصف | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | الوصف | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | الرسائل | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | الوصف | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | الوصف | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | الوصف | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update interval (seconds) | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | الوصف | . | LED state | Turn the LED on or off | . | الحالي | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | الوصف | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum broadcast (seconds) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | الوصف | . | Paxcounter enabled | Activate people counting | . | Update interval (seconds) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/settings-module-admin.html#%D8%A5%D8%B9%D8%AF%D8%A7%D8%AF%D8%A7%D8%AA-%D8%A7%D9%84%D8%AC%D9%87%D8%A7%D8%B2",
    
    "relUrl": "/ar-rSA/user/settings-module-admin.html#إعدادات-الجهاز"
  },"4367": {
    "doc": "Settings — Modules & Admin",
    "title": "الإدارة",
    "content": "Remote Administration . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | إعادة التشغيل | Restarts the node | . | Shutdown | Powers the node down | . | Factory reset | Returns every setting to its factory default | . | NodeDB reset | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Debug Panel . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. حول . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/settings-module-admin.html#%D8%A7%D9%84%D8%A5%D8%AF%D8%A7%D8%B1%D8%A9",
    
    "relUrl": "/ar-rSA/user/settings-module-admin.html#الإدارة"
  },"4368": {
    "doc": "Settings — Modules & Admin",
    "title": "Related Topics",
    "content": ". | Settings — Radio & User — core node and user profile settings | Module configuration reference — detailed module docs on meshtastic.org | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/settings-module-admin.html#related-topics",
    
    "relUrl": "/ar-rSA/user/settings-module-admin.html#related-topics"
  },"4369": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": " ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/settings-module-admin.html",
    
    "relUrl": "/ar-rSA/user/settings-module-admin.html"
  },"4370": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": "Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled. 💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders: . . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/settings-module-admin.html#settings--modules--admin",
    
    "relUrl": "/hr-rHR/user/settings-module-admin.html#settings--modules--admin"
  },"4371": {
    "doc": "Settings — Modules & Admin",
    "title": "Konfiguracija modula",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Opis | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Opis | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Opis | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Timeout | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Opis | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Output duration (milliseconds) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Opis | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Opis | . | Range test enabled | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Opis | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Opis | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Messages | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Opis | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Opis | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Opis | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update interval (seconds) | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Opis | . | LED state | Turn the LED on or off | . | Current | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Opis | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum broadcast (seconds) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Opis | . | Paxcounter enabled | Activate people counting | . | Update interval (seconds) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/settings-module-admin.html#konfiguracija-modula",
    
    "relUrl": "/hr-rHR/user/settings-module-admin.html#konfiguracija-modula"
  },"4372": {
    "doc": "Settings — Modules & Admin",
    "title": "Administration",
    "content": "Remote Administration . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Ponovno pokreni | Restarts the node | . | Isključi | Powers the node down | . | Vraćanje na tvorničke postavke | Returns every setting to its factory default | . | Resetiraj NodeDB bazu | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Otklanjanje pogrešaka . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. O programu . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/settings-module-admin.html#administration",
    
    "relUrl": "/hr-rHR/user/settings-module-admin.html#administration"
  },"4373": {
    "doc": "Settings — Modules & Admin",
    "title": "Related Topics",
    "content": ". | Settings — Radio & User — core node and user profile settings | Module configuration reference — detailed module docs on meshtastic.org | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/settings-module-admin.html#related-topics",
    
    "relUrl": "/hr-rHR/user/settings-module-admin.html#related-topics"
  },"4374": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": " ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/settings-module-admin.html",
    
    "relUrl": "/hr-rHR/user/settings-module-admin.html"
  },"4375": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": "Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled. 💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders: . . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/settings-module-admin.html#settings--modules--admin",
    
    "relUrl": "/pt-rPT/user/settings-module-admin.html#settings--modules--admin"
  },"4376": {
    "doc": "Settings — Modules & Admin",
    "title": "Configurações dos módulos",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Descrição | . | MQTT ativo | Toggle MQTT bridge | . | Endereço | MQTT broker address | . | Utilizador | Authentication username | . | Palavra-passe | Authentication password | . | Encriptação ativada | Encrypt MQTT payloads | . | Saída JSON ativada | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | Ativar TLS | Use secure connection | . | Tópico principal | Base MQTT topic path | . | Enviar através do cliente | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Enviar para o mapa | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Descrição | . | Estou de acordo. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Intervalo de envio (segundos) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Descrição | . | Série ativada | Activate serial communication | . | Eco ativado | Echo received serial data back | . | Modo de série | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Taxa de transmissão série | Port speed | . | Timeout | How long to wait before considering an incoming message complete | . | Substituir porta série do console | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Descrição | . | Ativar notificações externas | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | LED de Saída (GPIO) | Pin the LED is wired to | . | LED de saída ativo alto | Whether the LED pin is active high or low | . | Buzzer de saída (GPIO) | Pin the buzzer is wired to | . | Vibra de saída (GPIO) | Pin the vibration motor is wired to | . | Usar um buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Usar I2S como buzzer | Send the alert through an I2S audio output instead | . | Duração da Saída (milissegundos) | How long a single alert lasts | . | Tempo limite a incomodar (segundos) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Toque | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Descrição | . | Guardar & encaminhar ativo | Activate store and forward | . | Batimento | Periodically announce this node’s store-and-forward capability | . | Número de registos | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Servidor | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Descrição | . | Ativar Teste de alcance | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Guardar .CSV no armazenamento (apenas ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Descrição | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Módulo de métricas de ambiente ativado | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Mostrar métricas de ambiente no ecrã | Also show these readings on the device’s own display | . | Métricas de Ambiente usam Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Módulo de métricas de qualidade do ar ativado | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Módulo de métricas de energia ativado | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Mostrar métricas de energia no ecrã | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Descrição | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Mensagens | Newline-separated list of messages | . | Enviar sino | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Ativar Codificador rotativo #1 | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Entrada Cima/Baixo/Selecionar ativa | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Descrição | . | CODEC 2 ativado | Activate audio module | . | Taxa de amostragem CODEC2 | Audio quality/bandwidth tradeoff | . | Pin de PTT | GPIO pin for the push-to-talk button | . | Selecionar palavra I2S | GPIO pin for I2S WS | . | Entrada de dados I2S | GPIO pin for I2S DIN | . | Saída de dados I2S | GPIO pin for I2S DOUT | . | Relógio I2S | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Descrição | . | Hardware Remoto ativado | Activate remote GPIO access | . | Permitir acesso indefinido ao pin | Allow access to any GPIO pin (security risk) | . | Pins disponíveis | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Descrição | . | Enviar informações de vizinhos | Activate neighbor broadcasting | . | Intervalo de atualização (segundos) | How often to broadcast neighbor list | . | Enviar por LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Descrição | . | Estado do LED | Turn the LED on or off | . | Atual | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Descrição | . | Sensor de deteção ativado | Activate detection sensor | . | Pin GPIO para monitorizar | GPIO pin connected to sensor | . | Tipo de gatilho de deteção | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Usar o modo INPUT_PULLUP | Enable the pin’s internal pull-up resistor | . | Transmissão mínima (segundos) | Minimum time between alert broadcasts | . | Transmissão de estado (segundos) | Periodic state broadcast interval | . | Enviar sino com mensagem de alerta | Include bell character in alerts | . | Nome amigável | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Descrição | . | Ativar contador de pessoas | Activate people counting | . | Intervalo de atualização (segundos) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/settings-module-admin.html#configura%C3%A7%C3%B5es-dos-m%C3%B3dulos",
    
    "relUrl": "/pt-rPT/user/settings-module-admin.html#configurações-dos-módulos"
  },"4377": {
    "doc": "Settings — Modules & Admin",
    "title": "Administração",
    "content": "Administração Remota . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Reiniciar | Restarts the node | . | Desligar | Powers the node down | . | Redefinição de fábrica | Returns every setting to its factory default | . | Redefinir NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restauro . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Painel de depuração . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Sobre . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/settings-module-admin.html#administra%C3%A7%C3%A3o",
    
    "relUrl": "/pt-rPT/user/settings-module-admin.html#administração"
  },"4378": {
    "doc": "Settings — Modules & Admin",
    "title": "Related Topics",
    "content": ". | Settings — Radio & User — core node and user profile settings | Module configuration reference — detailed module docs on meshtastic.org | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/settings-module-admin.html#related-topics",
    
    "relUrl": "/pt-rPT/user/settings-module-admin.html#related-topics"
  },"4379": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": " ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/settings-module-admin.html",
    
    "relUrl": "/pt-rPT/user/settings-module-admin.html"
  },"4380": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": "Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled. 💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders: . . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/settings-module-admin.html#settings--modules--admin",
    
    "relUrl": "/pl-rPL/user/settings-module-admin.html#settings--modules--admin"
  },"4381": {
    "doc": "Settings — Modules & Admin",
    "title": "Ustawienia modułu",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Opis | . | Włącz MQTT | Toggle MQTT bridge | . | Adres | MQTT broker address | . | Nazwa użytkownika | Authentication username | . | Hasło | Authentication password | . | Szyfrowanie włączone | Encrypt MQTT payloads | . | Włącz wyjście JSON | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | Włącz TLS | Use secure connection | . | Główny wątek | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Raportowanie map | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Opis | . | Zgadzam się. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Interwał raportowania map (sekundy) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Opis | . | Włącz tryb serial | Activate serial communication | . | Włącz echo | Echo received serial data back | . | Tryb serial | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Prędkość transmisji | Port speed | . | Limit czasu | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Opis | . | Powiadomienia zewnętrzne włączone | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Wyjście LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Wyjście buzzera (GPIO) | Pin the buzzer is wired to | . | Wyjście silnika wibracyjnego (GPIO) | Pin the vibration motor is wired to | . | Użyj buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Użyj I2S jako buzzer | Send the alert through an I2S audio output instead | . | Czas trwania (w milisekundach) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Dzwonek | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Opis | . | Store & Forward enabled | Activate store and forward | . | Bicie serca | Periodically announce this node’s store-and-forward capability | . | Liczba rekordów | Maximum stored messages | . | Maks zwrotnej historii | Max messages to replay | . | Okno zwrotu historii | Time window for replay | . | Serwer | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Opis | . | Range test enabled | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Opis | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Włącz moduł metryk jakości powietrza | Report particulate and CO₂ sensor data | . | Czas aktualizacji metryk jakości powietrza | How often to report them | . | Włącz moduł metryk zasilania | Report the per-channel voltage and current readings | . | Czas aktualizacji metryk zasilania | How often to report them | . | Wyświetlaj metryki zasilania na ekranie | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Opis | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Wiadomości | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Opis | . | CODEC 2 włączony | Activate audio module | . | Częstotliwość próbkowania CODEC2 | Audio quality/bandwidth tradeoff | . | Pin PTT (Push-To-Talk) | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | Zegar I2S | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Opis | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Dostępne piny | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Opis | . | Włącz informacje o sąsiedzie | Activate neighbor broadcasting | . | Częstotliwość aktualizacji (w sekundach) | How often to broadcast neighbor list | . | Nadaj przez LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Opis | . | Stan diody LED | Turn the LED on or off | . | Natężenie | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Opis | . | Czujnik detekcji włączony | Activate detection sensor | . | Pin GPIO do monitorowania | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Użyj trybu INPUT_PULLUP | Enable the pin’s internal pull-up resistor | . | Minimalny czas transmisji (sekundy) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Przyjazna nazwa | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Opis | . | Paxcounter enabled | Activate people counting | . | Częstotliwość aktualizacji (w sekundach) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/settings-module-admin.html#ustawienia-modu%C5%82u",
    
    "relUrl": "/pl-rPL/user/settings-module-admin.html#ustawienia-modułu"
  },"4382": {
    "doc": "Settings — Modules & Admin",
    "title": "Zarządzanie",
    "content": "Zdalne zarządzanie . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Uruchom ponownie | Restarts the node | . | Wyłącz | Powers the node down | . | Ustawienia fabryczne | Returns every setting to its factory default | . | Zresetuj NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Kopia zapasowa i przywracanie . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Zaawansowane . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Wyczyść bazę węzłów . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Panel debugowania . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. O aplikacji . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Potwierdzenia . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/settings-module-admin.html#zarz%C4%85dzanie",
    
    "relUrl": "/pl-rPL/user/settings-module-admin.html#zarządzanie"
  },"4383": {
    "doc": "Settings — Modules & Admin",
    "title": "Related Topics",
    "content": ". | Settings — Radio & User — core node and user profile settings | Module configuration reference — detailed module docs on meshtastic.org | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/settings-module-admin.html#related-topics",
    
    "relUrl": "/pl-rPL/user/settings-module-admin.html#related-topics"
  },"4384": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": " ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/settings-module-admin.html",
    
    "relUrl": "/pl-rPL/user/settings-module-admin.html"
  },"4385": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": "Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled. 💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders: . . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/settings-module-admin.html#settings--modules--admin",
    
    "relUrl": "/zh-rCN/user/settings-module-admin.html#settings--modules--admin"
  },"4386": {
    "doc": "Settings — Modules & Admin",
    "title": "模块设定",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | 说明 | . | 启用MQTT | Toggle MQTT bridge | . | 地址 | MQTT broker address | . | 用户名称 | Authentication username | . | 密码 | Authentication password | . | 启用加密 | Encrypt MQTT payloads | . | 启用JSON输出 | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | 启用TLS | Use secure connection | . | 根主题 | Base MQTT topic path | . | 启用客户端代理 | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | 在此手机上开启 MQTT 代理 | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | 地图报告 | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | 说明 | . | 我同意。 | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | 地图报告间隔 (秒) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | 说明 | . | 启用串口 | Activate serial communication | . | 启用Echo | Echo received serial data back | . | 串口模式 | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | 串口波特率 | Port speed | . | 超时 | How long to wait before considering an incoming message complete | . | 覆盖控制台串口端口 | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | 说明 | . | 启用外部通知 | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | 输出 LED (GPIO) | Pin the LED is wired to | . | 输出 LED 活动高 | Whether the LED pin is active high or low | . | 输出震动(GPIO) | Pin the buzzer is wired to | . | 输出振动 (GPIO) | Pin the vibration motor is wired to | . | 使用 PWM 蜂鸣器 | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | 使用 I2S 作为蜂鸣器 | Send the alert through an I2S audio output instead | . | 输出持续时间 (毫秒) | How long a single alert lasts | . | 屏幕超时(秒) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | 铃声 | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | 说明 | . | 启用存储和转发 | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | 记录数 | Maximum stored messages | . | 历史记录最大返回值 | Max messages to replay | . | 历史记录返回窗口 | Time window for replay | . | 服务器 | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | 说明 | . | 启用范围测试 | Activate range testing | . | 发件人消息间隔(秒) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | 保存 CSV 到存储 (仅ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | 说明 | . | 发送设备远程数据 | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | 设备计量更新间隔 | How often to report battery, uptime and channel utilization | . | 启用环境计量模块 | Report the attached environment sensors | . | 环境计量更新间隔 | How often to report them | . | 屏幕显示环境指标 | Also show these readings on the device’s own display | . | 环境测量值使用华氏度 | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | 启用空气质量计量模块 | Report particulate and CO₂ sensor data | . | 空气质量计量更新间隔 | How often to report them | . | 启用电源计量模块 | Report the per-channel voltage and current readings | . | 电量计更新间隔 | How often to report them | . | 在屏幕上启用电源指标 | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | 说明 | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | 消息 | Newline-separated list of messages | . | 发送响铃 | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | 启用旋转编码器 #1 | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | 启用Up/Down/select 输入 | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | 说明 | . | 启用CODEC2 | Activate audio module | . | CODEC2 采样率 | Audio quality/bandwidth tradeoff | . | PTT 引脚 | GPIO pin for the push-to-talk button | . | I2S 字选择 | GPIO pin for I2S WS | . | I2S 数据 IN | GPIO pin for I2S DIN | . | I2S 数据 OUT | GPIO pin for I2S DOUT | . | I2S 时钟 | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | 说明 | . | 启用远程硬件 | Activate remote GPIO access | . | 允许未定义的引脚访问 | Allow access to any GPIO pin (security risk) | . | 可用引脚 | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | 说明 | . | 启用邻居信息 | Activate neighbor broadcasting | . | 更新间隔（秒） | How often to broadcast neighbor list | . | 通过 LoRa 传输 | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | 说明 | . | LED 状态 | Turn the LED on or off | . | 电流 | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | 说明 | . | 启用检测传感器 | Activate detection sensor | . | 显示器的 GPIO 引脚 | GPIO pin connected to sensor | . | 检测触发器类型 | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | 使用 输入上拉 模式 | Enable the pin’s internal pull-up resistor | . | 最小广播时间(秒) | Minimum time between alert broadcasts | . | 状态广播(秒) | Periodic state broadcast interval | . | 发送带有警报消息的响铃声 | Include bell character in alerts | . | 友好名称 | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | 说明 | . | 启用 Paxcount | Activate people counting | . | 更新间隔（秒） | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/settings-module-admin.html#%E6%A8%A1%E5%9D%97%E8%AE%BE%E5%AE%9A",
    
    "relUrl": "/zh-rCN/user/settings-module-admin.html#模块设定"
  },"4387": {
    "doc": "Settings — Modules & Admin",
    "title": "管理员",
    "content": "远程管理 . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | 设置时间 | Sends your phone’s clock to the node | . | 重启 | Restarts the node | . | 关机 | Powers the node down | . | 恢复出厂设置 | Returns every setting to its factory default | . | 重置节点数据库 | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. 备份与恢复 . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. 高级 . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. 清理节点数据库 . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. 调试面板 . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App 设置 . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. 关于 . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. 开源 . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/settings-module-admin.html#%E7%AE%A1%E7%90%86%E5%91%98",
    
    "relUrl": "/zh-rCN/user/settings-module-admin.html#管理员"
  },"4388": {
    "doc": "Settings — Modules & Admin",
    "title": "Related Topics",
    "content": ". | Settings — Radio & User — core node and user profile settings | Module configuration reference — detailed module docs on meshtastic.org | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/settings-module-admin.html#related-topics",
    
    "relUrl": "/zh-rCN/user/settings-module-admin.html#related-topics"
  },"4389": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": " ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/settings-module-admin.html",
    
    "relUrl": "/zh-rCN/user/settings-module-admin.html"
  },"4390": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": "Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled. 💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders: . . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/settings-module-admin.html#settings--modules--admin",
    
    "relUrl": "/sq-rAL/user/settings-module-admin.html#settings--modules--admin"
  },"4391": {
    "doc": "Settings — Modules & Admin",
    "title": "Konfigurimi i modulit",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Përshkrimi | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Përshkrimi | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Përshkrimi | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Koha e skaduar | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Përshkrimi | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Output duration (milliseconds) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Përshkrimi | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Përshkrimi | . | Range test enabled | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Përshkrimi | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Përshkrimi | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | 訊息 | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Përshkrimi | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Përshkrimi | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Përshkrimi | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update interval (seconds) | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Përshkrimi | . | LED state | Turn the LED on or off | . | Current | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Përshkrimi | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum broadcast (seconds) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Përshkrimi | . | Paxcounter enabled | Activate people counting | . | Update interval (seconds) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/settings-module-admin.html#konfigurimi-i-modulit",
    
    "relUrl": "/sq-rAL/user/settings-module-admin.html#konfigurimi-i-modulit"
  },"4392": {
    "doc": "Settings — Modules & Admin",
    "title": "Administratë",
    "content": "Administratë e Largët . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Rindiz | Restarts the node | . | Fik | Powers the node down | . | Përditësim i fabrikës | Returns every setting to its factory default | . | Përditësimi i NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Paneli i debug-ut . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Rreth . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/settings-module-admin.html#administrat%C3%AB",
    
    "relUrl": "/sq-rAL/user/settings-module-admin.html#administratë"
  },"4393": {
    "doc": "Settings — Modules & Admin",
    "title": "Related Topics",
    "content": ". | Settings — Radio & User — core node and user profile settings | Module configuration reference — detailed module docs on meshtastic.org | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/settings-module-admin.html#related-topics",
    
    "relUrl": "/sq-rAL/user/settings-module-admin.html#related-topics"
  },"4394": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": " ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/settings-module-admin.html",
    
    "relUrl": "/sq-rAL/user/settings-module-admin.html"
  },"4395": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": "Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled. 💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders: . . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/settings-module-admin.html#settings--modules--admin",
    
    "relUrl": "/zh-rTW/user/settings-module-admin.html#settings--modules--admin"
  },"4396": {
    "doc": "Settings — Modules & Admin",
    "title": "模組設定",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | 設定 | 描述說明 | . | 啟用MQTT服務器 | Toggle MQTT bridge | . | 地址 | MQTT broker address | . | 使用者名稱 | Authentication username | . | 密碼 | Authentication password | . | 加密已啟用 | Encrypt MQTT payloads | . | JSON輸出已啟用 | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS已啟用 | Use secure connection | . | 根話題 | Base MQTT topic path | . | 啟用對客戶端的代理 | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | 地圖報告 | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | 設定 | 描述說明 | . | 我同意。 | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | 地圖報告間隔（秒） | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | 設定 | 描述說明 | . | 啟用序列埠 | Activate serial communication | . | 啟用 Echo | Echo received serial data back | . | 序列埠模式 | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | 序列埠鮑率 | Port speed | . | Timeout - 超時 | How long to wait before considering an incoming message complete | . | 覆蓋控制台序列埠 | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | 設定 | 描述說明 | . | 啟用外部通知 | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | 輸出LED（GPIO） | Pin the LED is wired to | . | 輸出LED 高電平觸發 | Whether the LED pin is active high or low | . | 輸出蜂鳴（GPIO） | Pin the buzzer is wired to | . | 輸出振動（GPIO） | Pin the vibration motor is wired to | . | 使用PWM調製的蜂鳴 | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | 使用 I2S 控制蜂鳴器 | Send the alert through an I2S audio output instead | . | 輸出持續時間（毫秒） | How long a single alert lasts | . | 通知逾時時間（秒） | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | 鈴聲 | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | 設定 | 描述說明 | . | 啟用儲存並轉發 | Activate store and forward | . | 心跳 | Periodically announce this node’s store-and-forward capability | . | 紀錄數目 | Maximum stored messages | . | 歴史紀錄最大返回值 | Max messages to replay | . | 歴史紀錄返回視窗 | Time window for replay | . | 伺服器 | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | 設定 | 描述說明 | . | 啟用範圍測試 | Activate range testing | . | 訊息發送間隔(秒) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | 將 .CSV 保存到內部儲存空間(僅限ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | 設定 | 描述說明 | . | 傳送裝置遙測資料 | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | 裝置資訊更新間隔 | How often to report battery, uptime and channel utilization | . | 啟用環境資訊模組 | Report the attached environment sensors | . | 環境資訊更新間隔 | How often to report them | . | 在螢幕上顯示環境資訊 | Also show these readings on the device’s own display | . | 環境指標以華氏溫度顯示 | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | 啟用空氣品質模組 | Report particulate and CO₂ sensor data | . | 空氣品質資訊更新間隔 | How often to report them | . | 啟用電池資訊模組 | Report the per-channel voltage and current readings | . | 電源資訊更新間隔 | How often to report them | . | 在螢幕上顯示電量資訊 | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | 設定 | 描述說明 | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | 訊息 | Newline-separated list of messages | . | 發送振鈴 | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | 啟用旋轉編碼器#1 | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | 啟用上下選擇輸入 | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | 設定 | 描述說明 | . | 啟用 CODEC 2 | Activate audio module | . | CODEC2 取樣率 | Audio quality/bandwidth tradeoff | . | PTT針腳 | GPIO pin for the push-to-talk button | . | I2S WS 訊號選擇 | GPIO pin for I2S WS | . | I2S 數據輸入 | GPIO pin for I2S DIN | . | I2S 數據輸出 | GPIO pin for I2S DOUT | . | I2S 時鐘 | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | 設定 | 描述說明 | . | 啟動遠端硬體 | Activate remote GPIO access | . | 允許未定義腳位連接 | Allow access to any GPIO pin (security risk) | . | 可用腳位 | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | 設定 | 描述說明 | . | 啟用鄰居資訊 | Activate neighbor broadcasting | . | 更新間隔（秒） | How often to broadcast neighbor list | . | 通過Lora無線電傳輸 | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | 設定 | 描述說明 | . | LED狀態 | Turn the LED on or off | . | 目前 | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | 設定 | 描述說明 | . | 啟用偵測感測器 | Activate detection sensor | . | 螢幕的 GPIO 腳位 | GPIO pin connected to sensor | . | 偵測觸發類型 | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | 使用輸入上拉模式 | Enable the pin’s internal pull-up resistor | . | 最短廣播間隔 (秒) | Minimum time between alert broadcasts | . | 狀態廣播間隔 (秒) | Periodic state broadcast interval | . | 告警訊息發送提示音 | Include bell character in alerts | . | 顯示名稱 | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | 設定 | 描述說明 | . | 已啟用人流計數（Paxcount） | Activate people counting | . | 更新間隔（秒） | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/settings-module-admin.html#%E6%A8%A1%E7%B5%84%E8%A8%AD%E5%AE%9A",
    
    "relUrl": "/zh-rTW/user/settings-module-admin.html#模組設定"
  },"4397": {
    "doc": "Settings — Modules & Admin",
    "title": "管理",
    "content": "遠端管理 . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | 動作 | What it does | . | Set time | Sends your phone’s clock to the node | . | 重新開機 | Restarts the node | . | 關機 | Powers the node down | . | 恢復出廠設置 | Returns every setting to its factory default | . | 重設節點資料庫 | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. 備份與還原 . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. 進階 . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. 清除節點資料庫 . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. 偵錯面板 . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings 應用程式設定 . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. About（關於） . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. 致謝 . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/settings-module-admin.html#%E7%AE%A1%E7%90%86",
    
    "relUrl": "/zh-rTW/user/settings-module-admin.html#管理"
  },"4398": {
    "doc": "Settings — Modules & Admin",
    "title": "Related Topics",
    "content": ". | Settings — Radio & User — core node and user profile settings | Module configuration reference — detailed module docs on meshtastic.org | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/settings-module-admin.html#related-topics",
    
    "relUrl": "/zh-rTW/user/settings-module-admin.html#related-topics"
  },"4399": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": " ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/settings-module-admin.html",
    
    "relUrl": "/zh-rTW/user/settings-module-admin.html"
  },"4400": {
    "doc": "Sätted - moodulid & admin",
    "title": "Sätted - moodulid & admin",
    "content": "Konfi valikulisi funktsioonimooduleid ja teosta seadme haldamist. Moodulid laiendavad Meshtasticut spetsiaalsete võimalustega – igaüht saab eraldi lubada või keelata. 💡 Vihje: Pead lubama ainult need moodulid, mida sa tegelikult kasutad. Kasutamata moodulite keelamine vähendab eetriaega, säästab akut ja lihtsustab seadistamist. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Mooduli seaded kasutavad kaardipõhist paigutust koos lülitite, rippmenüüde, tekstiväljade ja liuguritega: . . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/settings-module-admin.html#s%C3%A4tted---moodulid--admin",
    
    "relUrl": "/et-rEE/user/settings-module-admin.html#sätted---moodulid--admin"
  },"4401": {
    "doc": "Sätted - moodulid & admin",
    "title": "Mooduli sätted",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Sildab võrgusõnumeid MQTT vahendajasse ja sealt internetiühenduse loomiseks. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Sätted | Kirjeldus | . | MQTT lubatud | Lükka MQTT sild sisse | . | Aadress | MQTT vahendaja aadress | . | Kasutajatunnus | Authentication username | . | Parool | Authentication password | . | Krüpteerimine lubatud | Krüpteeri MQTT kasutus | . | JSON väljund lubatud | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS lubatud | Use secure connection | . | Juurteema | Baas MQTT teema teekond | . | Kliendi proksi lubatud | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | Selle telefoni MQTT puhverserver | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Kaardi raport | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Sätted | Kirjeldus | . | Nõustun. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Kaardi raporti sagedus (sekund) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . Vaata MQTT üksikasjalikumat kasutusjuhendit, mis sisaldab teavet krüpteerimise, privaatsuse ja vahendaja seadistamise kohta,. Serial module . Võimaldab jadapordi sidet väliste seadmete integreerimiseks (GPS-moodulid, andurid või kohandatud riistvara). Kui lubatud, saab sõlme jadaühendus saata ja vastu võtta protobuf- või tekstiandmeid, võimaldades välistel mikrokontrolleritel või arvutitel võrguga suhelda. | Sätted | Kirjeldus | . | Jadaport lubatud | Aktiveeri jadapordi ühendus | . | Kaja lubatud | Kaja sai jadaandmed tagasi | . | Jadapordi režiim | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Jadapordi kiirus | Port speed | . | Aegunud | How long to wait before considering an incoming message complete | . | Konsooli jadapordi alistamine | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Kasulik seadmetele, mis peavad sõnumi saabumisest füüsiliselt märku andma – eriti kasulik järelevalveta või välistingimustes paigaldamise korral. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Sätted | Kirjeldus | . | Luba Välised teated | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Väljund LED (GPIO) | Pin the LED is wired to | . | Väljund LED aktiivne | Whether the LED pin is active high or low | . | Väljund summer (GPIO) | Pin the buzzer is wired to | . | Väljund värin (GPIO) | Pin the vibration motor is wired to | . | Kasuta PWM summerit | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Kasuta I2S summerina | Send the alert through an I2S audio output instead | . | Väljundi kestvus (millisekundit) | How long a single alert lasts | . | Häire ajalõpp (sekundit) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Helin | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Puhverdab ajutiselt võrguühenduseta olnud sõlmede sõnumeid ja esitab need uuesti, kui need sõlmed taasühenduvad. Hädavajalik kärgvõrgu jaoks, kus sõlmed regulaarselt levialasse lähevad ja levialast välja lähevad — tagab, et lühikeste katkestuste ajal sõnumid kaotsi ei lähe. | Sätted | Kirjeldus | . | Salvesta & Edasta lubatud | Aktiveeri salvesta ja saada | . | Südamelöögid | Periodically announce this node’s store-and-forward capability | . | Kirjete arv | Maximum stored messages | . | Ajalookirjete maksimaalne arv | Max messages to replay | . | Ajalookirjete aken | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Vihje: Salvesta ja edasta töötab kõige paremini rohke mäluga sõlmedes (ESP32 koos PSRAM-iga). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automatiseeritud vahemiku testimise tööriist sõlmede vahelise ühenduse kvaliteedi hindamiseks. Kui lubatud, edastab sõlm perioodiliselt testsõnumeid kasvavate loenduritega. Vastuvõtusõlm logib need sõnumid, võimaldades kõndida või minema sõita ning hiljem analüüsida, millisel kaugusel sõnumite saabumine lakkas. | Sätted | Kirjeldus | . | Ulatustest lubatud | Aktiveeri levi test | . | Saatja sõnumi sagedus (sekundit) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Salvesta .CSV faili (ainult ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Juhib, milliseid telemeetriaandmeid sõlm võrguga jagab. Telemeetria sisaldab seadme tervist (aku, tööaeg) ja keskkonnaandurite andmeid (temperatuur, niiskus, rõhk). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Sätted | Kirjeldus | . | Saada seadme telemeetria | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Seadme mõõdikute värskendamise intervall | How often to report battery, uptime and channel utilization | . | Keskkonnamõõdikute lubamine | Report the attached environment sensors | . | Keskkonnamõõdikute värskendamise intervall | How often to report them | . | Keskkonnamõõdikute ekraanil kuvamine lubatud | Also show these readings on the device’s own display | . | Keskkonnamõõdikud kasutavad Fahrenheiti | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Õhukvaliteedi moodul on lubatud | Report particulate and CO₂ sensor data | . | Õhukvaliteedi näidikute värskendamise intervall | How often to report them | . | Toitemõõdiku moodul on lubatud | Report the per-channel voltage and current readings | . | Toitemõõdikute värskendamise intervall | How often to report them | . | Toitemõõdiku ekraanil kuvamine lubatud | Also show power readings on the device’s display | . Vaata Telemeetria & Sensorid toetatud andurite ja sätete soovituste kohta. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Määra nimekiri kiirsõnumitest, mida saab edastada ilma telefoni ühendamata – ideaalne välitöödeks. | Sätted | Kirjeldus | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Sõnumid | Reavahetusega eraldatud sõnumite loend | . | Saada Kõll | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Pöördvalik #1 lubatud | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Üles/Alla/Vali sisend lubatud | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. See on eksperimentaalne funktsioon, mis kodeerib hääle Codec2 koodeki abil väga väikesteks andmepakettideks. | Sätted | Kirjeldus | . | CODEC 2 lubatud | Aktiveeri audio moodul | . | CODEC2 test sagedus | Audio quality/bandwidth tradeoff | . | PTT klemm | GPIO pin for the push-to-talk button | . | I2S sõna valik | GPIO sisend I2S WS jaoks | . | I2S info sisse | GPIO sisend I2S DIN jaoks | . | I2S info välja | GPIO sisend I2S DOUT jaoks | . | I2S kell | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO juhtimine kärgvõrgu kaudu. Võimaldab kaugsõlmel lugeda või kirjutada GPIO sisendkontakte teisel sõlmel – kasulik releede aktiveerimiseks, lülitite lugemiseks või välise riistvara kaugjuhtimiseks. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Sätted | Kirjeldus | . | Kaug riistvara lubatud | Aktiveeri kaugjuurdepääs GPIO-le | . | Luba määratlemata klemmi juurdepääs | Luba juurdepääs mis tahes GPIO sisendile (turvarisk) | . | Saadaval klemmid | Kuni 4 GPIO sisendit, mida see sõlm kauglugemiseks/-kirjutamiseks avab | . Neighbor Info module . Levitab teavet otse kuuldud naabrite kohta, võimaldades kärgvõrgu topoloogia kaardistamist. Iga lubatud sõlm jagab perioodiliselt nimekirja teistest sõlmedest, mida ta kuuleb ja nende signaali kvaliteedist. | Sätted | Kirjeldus | . | Naabruskonna teave lubatud | Aktiveeri naabrite leviring | . | Uuenduste sagedus (sekundit) | Kui tihti naabrite nimekirja levitada | . | Saada LoRa kaudu | Edasta naabriinfot ka LoRa kaudu, mitte ainult MQTT/telefoni kaudu. Vaikimisi võtit ja nime kasutavat kanalit pole saadaval | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Juhib toetatud riistvaral NeoPixeli või muid adresseeritavaid RGB LEDe. Saab kasutada visuaalsete olekuindikaatorite, märgutulede või dekoratiivsete efektide jaoks. | Sätted | Kirjeldus | . | LED olek | Turn the LED on or off | . | Pinge | LED current limit (0–31) | . | Punane / Roheline / Sinine | Individuaalsete värvikanalite väärtused (0–255) | . Detection Sensor module . Muudab sõlme liikumis- või ukseanduri hoiatussüsteemiks. Kui GPIO sisend tuvastab oleku muutuse (liikumine tuvastatud, uks avatud), levitab sõlm kärgvõrgu kaudu hoiatusteate. | Sätted | Kirjeldus | . | Tuvastusandur lubatud | Aktiveeri tuvastusandur | . | GPIO klemmi jälgimine | GPIO sisend on anduriga ühendatud | . | Identifitseerimistüüp | Kuidas klemmi olek vastab tuvastussündmusele (nt aktiivne kõrge/madal, serva poolt käivitatav) | . | Kasuta INPUT_PULLUP režiimi | Enable the pin’s internal pull-up resistor | . | Minimaalne edastusaeg (sekund) | Minimaalne aeg hoiatusteadete levitamisel | . | Oleku edastus (sekund) | Perioodilise oleku levitamise intervall | . | Saada kõll koos hoiatussõnumiga | Lisa märguannetesse hoiatuskella sümbol | . | Kasutajasõbralik nimi | Selle anduri kohandatud nimi | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Loendab lähedalasuvaid seadmeid, kuulates passiivselt sondimistaotlusi, mida telefonid ja sülearvutid võrkude skannimisel edastavad. Available only on ESP32 devices. | Sätted | Kirjeldus | . | Paxcounter lubatud | Aktiveeri inimeste loendamine | . | Uuenduste sagedus (sekundit) | Kui tihti loendeid esitada | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Vihje: Paxloendur on kasulik jalakäijate liikluse hindamiseks matkaradade alguses, ürituste toimumiskohtades või muudes kohtades. Arvud on ligikaudsed – üks inimene võib kaasas kanda mitut seadet. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Meeskonna teadlikkuse komplekti integratsioon ATAKi ja WinTAKi koostalitlusvõime tagamiseks. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. Vaata TAK Integration täpsema seadistamise ja kasutamise kohta. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/settings-module-admin.html#mooduli-s%C3%A4tted",
    
    "relUrl": "/et-rEE/user/settings-module-admin.html#mooduli-sätted"
  },"4402": {
    "doc": "Sätted - moodulid & admin",
    "title": "Haldus",
    "content": "Kaughaldus . Administraatori võtit jagavate sõlmede kaugkonfigureerimine: . | Vali sõlmede loendist sihtsõlm. | Mine selle sõlme Seadetesse. | Muuda seadistust. | Puuduta Salvesta – muudatused saadetakse kärgvõrgu kaudu. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Määra aeg | Sends your phone’s clock to the node | . | Taaskäivita | Restarts the node | . | Lülita välja | Powers the node down | . | Tehasesätted | Returns every setting to its factory default | . | NodeDB lähtestamine | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Varunda ja taasta . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Täpsem . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Tühjenda sõlmede andmebaas . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Arendaja paneel . Avab vahekaardid Paketid ja Rakenduse logid diagnostilise väljundi vaatamiseks, filtreerimiseks ja eksportimiseks. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Teave . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Tänusõnad . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “Sihtsõlmelt ei ole vastust” — sihtsõlm võib olla leviulatusest väljas, võrguühenduseta või sellel võib olla sobimatu administraatori võti. Veendu, et administraatori võti sobiks mõlemas sõlmele. | Muudatused ei rakendu — mõnede sätete jõustumiseks on vaja taaskäivitada. Pärast salvestamist proovi taaskäivitust. | Ei näe kaugseadeid — veendu, et sõlmel oleks sihtsõlme administraatori võti ja et administraatori kanal oleks turbekonfiguratsioonis lubatud. Administraatori kanal seadistatakse automaatselt, kui administraatori võti on määratud. | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/settings-module-admin.html#haldus",
    
    "relUrl": "/et-rEE/user/settings-module-admin.html#haldus"
  },"4403": {
    "doc": "Sätted - moodulid & admin",
    "title": "Seotud teemad",
    "content": ". | Settings — Radio & User — core node and user profile settings | Mooduli konfiguratsiooni viide — üksikasjalik mooduli dokumentatsioon aadressil meshtastic.org | KKK — meshtastic.org sageli esitatavad küsimused | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/settings-module-admin.html#seotud-teemad",
    
    "relUrl": "/et-rEE/user/settings-module-admin.html#seotud-teemad"
  },"4404": {
    "doc": "Sätted - moodulid & admin",
    "title": "Sätted - moodulid & admin",
    "content": " ",
    "url": "/Meshtastic-Android/main/et-rEE/user/settings-module-admin.html",
    
    "relUrl": "/et-rEE/user/settings-module-admin.html"
  },"4405": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": "Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled. 💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders: . . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/settings-module-admin.html#settings--modules--admin",
    
    "relUrl": "/fr-rFR/user/settings-module-admin.html#settings--modules--admin"
  },"4406": {
    "doc": "Settings — Modules & Admin",
    "title": "Réglages du module",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Description | . | MQTT activé | Toggle MQTT bridge | . | Adresse | MQTT broker address | . | Nom d’utilisateur | Authentication username | . | Mot de passe | Authentication password | . | Chiffrement activé | Encrypt MQTT payloads | . | Sortie JSON activée | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS activé | Use secure connection | . | Sujet principal | Base MQTT topic path | . | Proxy pour le client activé | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Rapport cartographique | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Description | . | J’accepte. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Intervalle de rapport cartographique (secondes) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Description | . | Série activée | Activate serial communication | . | Écho activé | Echo received serial data back | . | Mode série | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Vitesse de transmission série | Port speed | . | Délai d’expiration | How long to wait before considering an incoming message complete | . | Outrepasser le port série de la console | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Description | . | Notifications externes activées | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | LED extérieure (GPIO) | Pin the LED is wired to | . | Sortie LED active à l’état haut | Whether the LED pin is active high or low | . | Buzzer extérieur (GPIO) | Pin the buzzer is wired to | . | Sortie vibreur (GPIO) | Pin the vibration motor is wired to | . | Utiliser le buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Utiliser l’I2S comme buzzer | Send the alert through an I2S audio output instead | . | Durée de sortie (en millisecondes) | How long a single alert lasts | . | Durée de répétition de la sortie (secondes) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Sonnerie | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Description | . | Stocker & Transférer activé | Activate store and forward | . | Battement de cœur (heartbeat) | Periodically announce this node’s store-and-forward capability | . | Nombre d’enregistrements | Maximum stored messages | . | Limite d’historique renvoyé | Max messages to replay | . | Fenêtre de retour d’historique | Time window for replay | . | Serveur | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Description | . | Test de portée activé | Activate range testing | . | Intervalle de message de l’expéditeur (secondes) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Enregistrer .CSV dans le stockage (ESP32 seulement) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Description | . | Envoyer la télémétrie de l’appareil | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Intervalle de mise à jour des mesures | How often to report battery, uptime and channel utilization | . | Module de métriques de l’environnement activé | Report the attached environment sensors | . | Intervalle de mise à jour des mesures d’environnement | How often to report them | . | Mesures d’environnement à l’écran activées | Also show these readings on the device’s own display | . | Les mesures environnementales utilisent Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Module de mesure de la qualité de l’air activé | Report particulate and CO₂ sensor data | . | Intervalle de mise à jour des mesures de qualité d’air | How often to report them | . | Module de mesure de puissance activé | Report the per-channel voltage and current readings | . | Intervalle de mise à jour des mesures d’alimentation | How often to report them | . | Indicateurs d’alimentation à l’écran activés | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Description | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Messages | Newline-separated list of messages | . | Envoyer une sonnerie | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Encodeur rotatif #1 activé | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Entrée Haut/Bas/Select activée | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Description | . | CODEC 2 activé | Activate audio module | . | Taux d’échantillonnage CODEC2 | Audio quality/bandwidth tradeoff | . | Broche PTT | GPIO pin for the push-to-talk button | . | Selection de mot I2S | GPIO pin for I2S WS | . | Données d’entrée I2S | GPIO pin for I2S DIN | . | Données de sortie I2S | GPIO pin for I2S DOUT | . | Horloge I2C | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Description | . | Matériel distant activé | Activate remote GPIO access | . | Autoriser l’accès non défini aux broches | Allow access to any GPIO pin (security risk) | . | Broches disponibles | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Description | . | Infos de voisinage activées | Activate neighbor broadcasting | . | Intervalle de mise à jour (secondes) | How often to broadcast neighbor list | . | Transmettre par LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Description | . | État de la LED | Turn the LED on or off | . | Actif | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Description | . | Capteur de détection activé | Activate detection sensor | . | Broche GPIO à surveiller | GPIO pin connected to sensor | . | Type du déclencheur de détection | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Utiliser le mode INPUT_PULLUP | Enable the pin’s internal pull-up resistor | . | Diffusion minimale (secondes) | Minimum time between alert broadcasts | . | Diffusion de l’État (secondes) | Periodic state broadcast interval | . | Envoyer une sonnerie avec un message d’alerte | Include bell character in alerts | . | Nom convivial | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Paramètre | Description | . | Paxcounter activé | Activate people counting | . | Intervalle de mise à jour (secondes) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/settings-module-admin.html#r%C3%A9glages-du-module",
    
    "relUrl": "/fr-rFR/user/settings-module-admin.html#réglages-du-module"
  },"4407": {
    "doc": "Settings — Modules & Admin",
    "title": "Administration",
    "content": "Administration à distance . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Redémarrer | Restarts the node | . | Éteindre | Powers the node down | . | Réinitialisation d’usine | Returns every setting to its factory default | . | Reconfiguration de NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Sauvegarder & Restaurer . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Avancé . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Nettoyer la base de données des nœuds . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Panneau de débogage . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. A propros . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Remerciements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/settings-module-admin.html#administration",
    
    "relUrl": "/fr-rFR/user/settings-module-admin.html#administration"
  },"4408": {
    "doc": "Settings — Modules & Admin",
    "title": "Related Topics",
    "content": ". | Settings — Radio & User — core node and user profile settings | Module configuration reference — detailed module docs on meshtastic.org | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/settings-module-admin.html#related-topics",
    
    "relUrl": "/fr-rFR/user/settings-module-admin.html#related-topics"
  },"4409": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": " ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/settings-module-admin.html",
    
    "relUrl": "/fr-rFR/user/settings-module-admin.html"
  },"4410": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": "Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled. 💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders: . . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/settings-module-admin.html#settings--modules--admin",
    
    "relUrl": "/tr-rTR/user/settings-module-admin.html#settings--modules--admin"
  },"4411": {
    "doc": "Settings — Modules & Admin",
    "title": "Modül ayarları",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Açıklaması | . | MQTT etkin | Toggle MQTT bridge | . | Adres | MQTT broker address | . | Kullanıcı adı | Authentication username | . | Şifre | Authentication password | . | Şifreleme etkin | Encrypt MQTT payloads | . | JSON çıktısı etkin | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS etkin | Use secure connection | . | Ana konu | Base MQTT topic path | . | Vekilden istemciye etkin | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Harita raporlama | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Açıklaması | . | Katılıyorum. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Harita raporlama aralığı (saniye) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Açıklaması | . | Seri etkin | Activate serial communication | . | Eko etkin | Echo received serial data back | . | Seri modu | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Seri baud hızı | Port speed | . | Zaman Aşımı | How long to wait before considering an incoming message complete | . | Konsol seri portunu geçersiz kıl | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Açıklaması | . | Harici bildirim etkin | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Çıktı LED (GPIO) | Pin the LED is wired to | . | Çıktı LED aktif yüksek | Whether the LED pin is active high or low | . | Çıktı zırnı (GPIO) | Pin the buzzer is wired to | . | Çıktı titreşim (GPIO) | Pin the vibration motor is wired to | . | PWM zırnı kullan | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | I2S’yi zırnı olarak kullan | Send the alert through an I2S audio output instead | . | Çıktı süresi (milisaniye) | How long a single alert lasts | . | Nag zaman aşımı (saniye) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Zil tipi | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Açıklaması | . | Kaydet & Yönlendir etkin | Activate store and forward | . | Kalp atışı | Periodically announce this node’s store-and-forward capability | . | Kayıt sayısı | Maximum stored messages | . | Geçmiş geri dönüş maksimum | Max messages to replay | . | Geçmiş geri dönüş penceresi | Time window for replay | . | Sunucu | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Açıklaması | . | Menzi testi etkin | Activate range testing | . | Gönderen mesaj aralığı (saniye) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | .CSV’yi depolamada kaydet (sadece ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Açıklaması | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Çevre metrikleri modülü etkin | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Çevre metrikleri ekran üzerinde etkin | Also show these readings on the device’s own display | . | Çevre metrikleri Fahrenheit kullan | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Hava kalitesi metrikleri modülü etkin | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Güç metrikleri modülü etkin | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Güç metrikleri ekran üzerinde etkin | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Açıklaması | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Mesajlar | Newline-separated list of messages | . | Zil gönder | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Dönen kodlayıcı #1 etkinleştirildi | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Yukarı/Aşağı/Seçme girişi etkinleştirildi | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Açıklaması | . | CODEC 2 etkinleştirildi | Activate audio module | . | CODEC2 örnekleme hızı | Audio quality/bandwidth tradeoff | . | PTT pini | GPIO pin for the push-to-talk button | . | I2S kelime seçimi | GPIO pin for I2S WS | . | I2S veri girişi | GPIO pin for I2S DIN | . | I2S veri çıkışı | GPIO pin for I2S DOUT | . | I2S saati | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Açıklaması | . | Uzak Donanım etkin | Activate remote GPIO access | . | Tanımlanmamış pin erişimine izin ver | Allow access to any GPIO pin (security risk) | . | Mevcut pinler | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Açıklaması | . | Komşu Bilgisi etkin | Activate neighbor broadcasting | . | Güncelleme aralığı (saniye) | How often to broadcast neighbor list | . | LoRa üzerinden ilet | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Açıklaması | . | LED durumu | Turn the LED on or off | . | Akım | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Açıklaması | . | Algılama Sensörü etkinleştirildi | Activate detection sensor | . | İzlenecek GPIO pini | GPIO pin connected to sensor | . | Algılama tetikleme türü | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | INPUT_PULLUP modu kullan | Enable the pin’s internal pull-up resistor | . | Minimum yayın (saniye) | Minimum time between alert broadcasts | . | Durum yayını (saniye) | Periodic state broadcast interval | . | Uyarı mesajı ile zil gönder | Include bell character in alerts | . | Arkadaşça isim | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Açıklaması | . | Pax sayacı etkin | Activate people counting | . | Güncelleme aralığı (saniye) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/settings-module-admin.html#mod%C3%BCl-ayarlar%C4%B1",
    
    "relUrl": "/tr-rTR/user/settings-module-admin.html#modül-ayarları"
  },"4412": {
    "doc": "Settings — Modules & Admin",
    "title": "Yönetim",
    "content": "Uzaktan Yönetim . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Yeniden başlat | Restarts the node | . | Kapat | Powers the node down | . | Fabrika ayarları | Returns every setting to its factory default | . | NodeDB sıfırla | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Yedekleme & Geri yükleme . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Gelişmiş . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Hata Ayıklama Paneli . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Hakkında . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/settings-module-admin.html#y%C3%B6netim",
    
    "relUrl": "/tr-rTR/user/settings-module-admin.html#yönetim"
  },"4413": {
    "doc": "Settings — Modules & Admin",
    "title": "Related Topics",
    "content": ". | Settings — Radio & User — core node and user profile settings | Module configuration reference — detailed module docs on meshtastic.org | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/settings-module-admin.html#related-topics",
    
    "relUrl": "/tr-rTR/user/settings-module-admin.html#related-topics"
  },"4414": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": " ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/settings-module-admin.html",
    
    "relUrl": "/tr-rTR/user/settings-module-admin.html"
  },"4415": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": "Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled. 💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders: . . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/settings-module-admin.html#settings--modules--admin",
    
    "relUrl": "/el-rGR/user/settings-module-admin.html#settings--modules--admin"
  },"4416": {
    "doc": "Settings — Modules & Admin",
    "title": "Ρυθμίσεις πρόσθετου",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Περιγραφή | . | MQTT enabled | Toggle MQTT bridge | . | Διεύθυνση | MQTT broker address | . | Όνομα χρήστη | Authentication username | . | Κωδικός πρόσβασης | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Περιγραφή | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Περιγραφή | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Λήξη χρονικού ορίου | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Περιγραφή | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Output duration (milliseconds) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Περιγραφή | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Περιγραφή | . | Range test enabled | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Περιγραφή | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Περιγραφή | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Μηνύματα | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Περιγραφή | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Περιγραφή | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Περιγραφή | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update interval (seconds) | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Περιγραφή | . | LED state | Turn the LED on or off | . | Current | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Περιγραφή | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum broadcast (seconds) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Περιγραφή | . | Paxcounter enabled | Activate people counting | . | Update interval (seconds) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/settings-module-admin.html#%CF%81%CF%85%CE%B8%CE%BC%CE%AF%CF%83%CE%B5%CE%B9%CF%82-%CF%80%CF%81%CF%8C%CF%83%CE%B8%CE%B5%CF%84%CE%BF%CF%85",
    
    "relUrl": "/el-rGR/user/settings-module-admin.html#ρυθμίσεις-πρόσθετου"
  },"4417": {
    "doc": "Settings — Modules & Admin",
    "title": "Διαχείριση",
    "content": "Απομακρυσμένη Διαχείριση . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Επανεκκίνηση | Restarts the node | . | Τερματισμός λειτουργίας | Powers the node down | . | Επαναφορά εργοστασιακών ρυθμίσεων | Returns every setting to its factory default | . | NodeDB reset | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Πίνακας αποσφαλμάτωσης . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Σχετικά . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/settings-module-admin.html#%CE%B4%CE%B9%CE%B1%CF%87%CE%B5%CE%AF%CF%81%CE%B9%CF%83%CE%B7",
    
    "relUrl": "/el-rGR/user/settings-module-admin.html#διαχείριση"
  },"4418": {
    "doc": "Settings — Modules & Admin",
    "title": "Related Topics",
    "content": ". | Settings — Radio & User — core node and user profile settings | Module configuration reference — detailed module docs on meshtastic.org | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/settings-module-admin.html#related-topics",
    
    "relUrl": "/el-rGR/user/settings-module-admin.html#related-topics"
  },"4419": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": " ",
    "url": "/Meshtastic-Android/main/el-rGR/user/settings-module-admin.html",
    
    "relUrl": "/el-rGR/user/settings-module-admin.html"
  },"4420": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": "Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled. 💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders: . . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/settings-module-admin.html#settings--modules--admin",
    
    "relUrl": "/ro-rRO/user/settings-module-admin.html#settings--modules--admin"
  },"4421": {
    "doc": "Settings — Modules & Admin",
    "title": "Configurare modul",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Descriere | . | MQTT activat | Toggle MQTT bridge | . | Adresă | MQTT broker address | . | Nume de utilizator | Authentication username | . | Parolă | Authentication password | . | Criptare activată | Encrypt MQTT payloads | . | Ieșire JSON activată | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS activat | Use secure connection | . | Temă rădăcină | Base MQTT topic path | . | Proxy-ul pentru client activat | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Raportarea hărții | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Descriere | . | Sunt de acord | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Intervalul de raportare hartă (secunde) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Descriere | . | Serial activat | Activate serial communication | . | Echo activat | Echo received serial data back | . | Mod serial | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Rata baud-ului serial | Port speed | . | Expirat | How long to wait before considering an incoming message complete | . | Suprascrie portul serial al consolei | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Descriere | . | Notificare externă activată | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | LED ieșire (GPIO) | Pin the LED is wired to | . | LED de ieșire activ ridicat | Whether the LED pin is active high or low | . | Buzzer ieșire (GPIO) | Pin the buzzer is wired to | . | Ieșire vibrație (GPIO) | Pin the vibration motor is wired to | . | Utilizează buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Utilizează I2S ca buzzer | Send the alert through an I2S audio output instead | . | Durată ieșire (milisecunde) | How long a single alert lasts | . | Durată notificare (secunde) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Sonerie | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Descriere | . | Reținere și redirecționare activată | Activate store and forward | . | Puls | Periodically announce this node’s store-and-forward capability | . | Numarul de inregistrari | Maximum stored messages | . | istoric număr maxim de retur | Max messages to replay | . | Fereastra de returnare a istoricului | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Descriere | . | Testul de gamă activat | Activate range testing | . | Interval mesaj expeditor (secunde) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Salvați .CSV doar în memorie (ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Descriere | . | Trimite telemetrie dispozitiv | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Intervalul de actualizare a parametrilor dispozitivului | How often to report battery, uptime and channel utilization | . | Modul de măsurare mediu activat | Report the attached environment sensors | . | Interval actualizare valori mediu | How often to report them | . | Valorile de mediu pe ecran sunt activate | Also show these readings on the device’s own display | . | Valorile de mediu utilizează Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Interval actualizare măsurători de calitate a aerului | How often to report them | . | Modul de măsurare putere activat | Report the per-channel voltage and current readings | . | Interval actualizare măsurători de putere | How often to report them | . | Valori pe ecran activate | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Descriere | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Mesaje | Newline-separated list of messages | . | Trimite clopoțel | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Encoder rotativ #1 activat | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Intrare sus/jos/selectare activată | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Descriere | . | CODEC 2 activat | Activate audio module | . | Rată de eșantionare CODEC2 | Audio quality/bandwidth tradeoff | . | Pin PTT | GPIO pin for the push-to-talk button | . | Selectare cuvânt I2S | GPIO pin for I2S WS | . | Intrare date I2S | GPIO pin for I2S DIN | . | Ieșire date I2S | GPIO pin for I2S DOUT | . | Ceas I2S | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Descriere | . | Hardware extern activat | Activate remote GPIO access | . | Permite acces Pin nedefinit | Allow access to any GPIO pin (security risk) | . | Pin-uri disponibile | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Descriere | . | Info vecin activat | Activate neighbor broadcasting | . | Interval de actualizare (secunde) | How often to broadcast neighbor list | . | Transmite peste LoRA | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Descriere | . | Stare LED | Turn the LED on or off | . | Actual | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Descriere | . | Senzor detectare activat | Activate detection sensor | . | Pin GPIO de monitorizat | GPIO pin connected to sensor | . | Tip declanșator detectare | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Folosește modul INPUT_PULLUP | Enable the pin’s internal pull-up resistor | . | Difuzare minimă (secunde) | Minimum time between alert broadcasts | . | Difuzare stare (secunde) | Periodic state broadcast interval | . | Trimite clopoțelul cu mesaj de alertă | Include bell character in alerts | . | Nume comun | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Descriere | . | Paxcounter activat | Activate people counting | . | Interval de actualizare (secunde) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/settings-module-admin.html#configurare-modul",
    
    "relUrl": "/ro-rRO/user/settings-module-admin.html#configurare-modul"
  },"4422": {
    "doc": "Settings — Modules & Admin",
    "title": "Administrare",
    "content": "Administrare la distanță . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Restartează | Restarts the node | . | Oprire | Powers the node down | . | Resetare la setările din fabrică | Returns every setting to its factory default | . | Resetare NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Copie de rezervă și restaurare . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Avansate . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Curăță baza de date a nodurilor . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Panou de depanare . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Despre . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Mulțumiri . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/settings-module-admin.html#administrare",
    
    "relUrl": "/ro-rRO/user/settings-module-admin.html#administrare"
  },"4423": {
    "doc": "Settings — Modules & Admin",
    "title": "Related Topics",
    "content": ". | Settings — Radio & User — core node and user profile settings | Module configuration reference — detailed module docs on meshtastic.org | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/settings-module-admin.html#related-topics",
    
    "relUrl": "/ro-rRO/user/settings-module-admin.html#related-topics"
  },"4424": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": " ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/settings-module-admin.html",
    
    "relUrl": "/ro-rRO/user/settings-module-admin.html"
  },"4425": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": "Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled. 💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders: . . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/settings-module-admin.html#settings--modules--admin",
    
    "relUrl": "/iw-rIL/user/settings-module-admin.html#settings--modules--admin"
  },"4426": {
    "doc": "Settings — Modules & Admin",
    "title": "הגדרות מודולות",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | תיאור | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | תיאור | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | תיאור | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Timeout | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | תיאור | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Output duration (milliseconds) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | תיאור | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | תיאור | . | Range test enabled | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | תיאור | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | תיאור | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | הודעות | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | תיאור | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | תיאור | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | תיאור | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update interval (seconds) | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | תיאור | . | LED state | Turn the LED on or off | . | Current | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | תיאור | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum broadcast (seconds) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | תיאור | . | Paxcounter enabled | Activate people counting | . | Update interval (seconds) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/settings-module-admin.html#%D7%94%D7%92%D7%93%D7%A8%D7%95%D7%AA-%D7%9E%D7%95%D7%93%D7%95%D7%9C%D7%95%D7%AA",
    
    "relUrl": "/iw-rIL/user/settings-module-admin.html#הגדרות-מודולות"
  },"4427": {
    "doc": "Settings — Modules & Admin",
    "title": "Administration",
    "content": "Remote Administration . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | אתחול מחדש | Restarts the node | . | כיבוי | Powers the node down | . | איפוס להגדרות היצרן | Returns every setting to its factory default | . | איפוס NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. פאנל דיבאג . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. אודות . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/settings-module-admin.html#administration",
    
    "relUrl": "/iw-rIL/user/settings-module-admin.html#administration"
  },"4428": {
    "doc": "Settings — Modules & Admin",
    "title": "Related Topics",
    "content": ". | Settings — Radio & User — core node and user profile settings | Module configuration reference — detailed module docs on meshtastic.org | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/settings-module-admin.html#related-topics",
    
    "relUrl": "/iw-rIL/user/settings-module-admin.html#related-topics"
  },"4429": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": " ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/settings-module-admin.html",
    
    "relUrl": "/iw-rIL/user/settings-module-admin.html"
  },"4430": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": "Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled. 💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders: . . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/settings-module-admin.html#settings--modules--admin",
    
    "relUrl": "/pt-rBR/user/settings-module-admin.html#settings--modules--admin"
  },"4431": {
    "doc": "Settings — Modules & Admin",
    "title": "Configuração de módulos",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Descrição | . | MQTT habilitado | Toggle MQTT bridge | . | Endereço | MQTT broker address | . | Nome de usuário | Authentication username | . | Senha | Authentication password | . | Criptografia ativada | Encrypt MQTT payloads | . | Saída JSON ativada | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS ativado | Use secure connection | . | Tópico principal | Base MQTT topic path | . | Proxy para cliente ativado | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Relatório de mapa | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Descrição | . | Eu concordo. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Intervalo de relatório de mapa (segundos) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Descrição | . | Serial ativado | Activate serial communication | . | Eco habilitado | Echo received serial data back | . | Modo de série | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Taxa de transmissão série | Port speed | . | Tempo esgotado | How long to wait before considering an incoming message complete | . | Substituir porta série do console | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Descrição | . | Notificação Externa habilitada | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | LED de Saída (GPIO) | Pin the LED is wired to | . | LED de saída habilitado alto | Whether the LED pin is active high or low | . | Saída Campainha (GPIO) | Pin the buzzer is wired to | . | Vibra de saída (GPIO) | Pin the vibration motor is wired to | . | Usar uma campainha PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Usar I2S como campainha | Send the alert through an I2S audio output instead | . | Duração da Saída (milissegundos) | How long a single alert lasts | . | Tempo limite do Nag (segundos) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Toque | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Descrição | . | Guardar e Encaminhar ativado | Activate store and forward | . | Batimento | Periodically announce this node’s store-and-forward capability | . | Número de registros | Maximum stored messages | . | Histórico de retorno máximo | Max messages to replay | . | Janela de retorno do histórico | Time window for replay | . | Servidor | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Descrição | . | Teste de distância ativado | Activate range testing | . | Intervalo de mensagem do remetente (segundos) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Salvar .CSV no armazenamento (apenas ESP32) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Descrição | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Módulo de métricas do ambiente ativado | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Métricas de ambiente na tela habilitado | Also show these readings on the device’s own display | . | Métricas de Ambiente usam Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Módulo de métricas de qualidade do ar habilitado | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Módulo de métricas de energia habilitado | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Métricas de ambiente na tela habilitado | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Descrição | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Mensagens | Newline-separated list of messages | . | Enviar sino | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Codificador rotativo #1 ativado | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Entrada Cima/Baixo/Selecionar ativada | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Descrição | . | CODEC 2 ativado | Activate audio module | . | Taxa de amostragem CODEC2 | Audio quality/bandwidth tradeoff | . | Pino de PTT | GPIO pin for the push-to-talk button | . | CS I2S | GPIO pin for I2S WS | . | MOSI I2S | GPIO pin for I2S DIN | . | MISO I2S | GPIO pin for I2S DOUT | . | CLK I2S | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Descrição | . | Hardware Remoto ativado | Activate remote GPIO access | . | Permitir acesso indefinido ao pino | Allow access to any GPIO pin (security risk) | . | Pinos disponíveis | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Descrição | . | Informações do Vizinho ativado | Activate neighbor broadcasting | . | Intervalo de atualização (segundos) | How often to broadcast neighbor list | . | Transmitir por LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Descrição | . | Estado do LED | Turn the LED on or off | . | Atual | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Descrição | . | Sensor de Detecção ativado | Activate detection sensor | . | Pino GPIO para monitorar | GPIO pin connected to sensor | . | Tipo de gatilho de deteção | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Usar o modo INPUT_PULLUP | Enable the pin’s internal pull-up resistor | . | Transmissão mínima (segundos) | Minimum time between alert broadcasts | . | Transmissão de estado (segundos) | Periodic state broadcast interval | . | Enviar sino com mensagem de alerta | Include bell character in alerts | . | Nome amigável | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Descrição | . | Contador de Pessoas ativado | Activate people counting | . | Intervalo de atualização (segundos) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/settings-module-admin.html#configura%C3%A7%C3%A3o-de-m%C3%B3dulos",
    
    "relUrl": "/pt-rBR/user/settings-module-admin.html#configuração-de-módulos"
  },"4432": {
    "doc": "Settings — Modules & Admin",
    "title": "Administração",
    "content": "Administração Remota . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Reiniciar | Restarts the node | . | Desligar | Powers the node down | . | Redefinição de fábrica | Returns every setting to its factory default | . | Redefinir NodeDB | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup e Restaurar . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Avançado . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Limpar Banco de Dados de Nó . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Painel de depuração . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. Sobre . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Agradecimentos . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/settings-module-admin.html#administra%C3%A7%C3%A3o",
    
    "relUrl": "/pt-rBR/user/settings-module-admin.html#administração"
  },"4433": {
    "doc": "Settings — Modules & Admin",
    "title": "Related Topics",
    "content": ". | Settings — Radio & User — core node and user profile settings | Module configuration reference — detailed module docs on meshtastic.org | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/settings-module-admin.html#related-topics",
    
    "relUrl": "/pt-rBR/user/settings-module-admin.html#related-topics"
  },"4434": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": " ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/settings-module-admin.html",
    
    "relUrl": "/pt-rBR/user/settings-module-admin.html"
  },"4435": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": "Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled. 💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces airtime, saves battery, and simplifies your configuration. A module you expect can be missing for three reasons: your node’s role doesn’t enable it, your firmware is older than the release that added it, or the firmware build excludes it for this hardware. Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders: . . ",
    "url": "/Meshtastic-Android/main/en/user/settings-module-admin.html#settings--modules--admin",
    
    "relUrl": "/en/user/settings-module-admin.html#settings--modules--admin"
  },"4436": {
    "doc": "Settings — Modules & Admin",
    "title": "Module configuration",
    "content": "Every module lives under Settings → Module configuration. ⚠️ Important: Saving a module screen restarts the node — the button reads Save & restart, and the node is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are the exceptions: their button reads Save, and the node may still restart for some changes. MQTT module . Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond LoRa range or integrate with home automation systems. | Setting | Description | . | MQTT enabled | Toggle MQTT bridge | . | Address | MQTT broker address | . | Username | Authentication username | . | Password | Authentication password | . | Encryption enabled | Encrypt MQTT payloads | . | JSON output enabled | Publish and consume MQTT messages as JSON. Marked deprecated in the protobuf schema, but it is still the only toggle for this behavior and the firmware still honors it | . | TLS enabled | Use secure connection | . | Root topic | Base MQTT topic path | . | Proxy to client enabled | Let a connected phone carry the node’s MQTT traffic, instead of the node reaching the broker itself | . | MQTT proxy on this phone | The phone-side half of Proxy to client enabled: whether this phone acts as that relay. See MQTT | . | Map reporting | Publish position to the public map — see the Map reporting group that follows | . Turning Map reporting on reveals a consent card headed Consent to Share Unencrypted Node Data via MQTT, with an I agree. switch under it. The rest of the card doesn’t exist on screen until you agree: . | Setting | Description | . | I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn’t start without it | . | Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads ± the resulting distance, in your own units | . | Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered | . See MQTT for a detailed usage guide including encryption, privacy, and broker setup. Serial module . Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node’s serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh. | Setting | Description | . | Serial enabled | Activate serial communication | . | Echo enabled | Echo received serial data back | . | Serial mode | Which protocol the port speaks — Default, Simple, Proto, Text message, NMEA, CalTopo, WS85 weather station, VE.Direct, MeshSolar config, Log, or Log (text only) | . | RX / TX | GPIO pins for the serial connection | . | Serial baud rate | Port speed | . | Timeout | How long to wait before considering an incoming message complete | . | Override console serial port | Take over the port the debug console normally uses | . External Notification module . Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations. There are two independent triggers — an incoming message, and a received bell character — and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles. | Setting | Description | . | External notification enabled | Master toggle for the module | . | Alert message LED / buzzer / vibra | Which outputs fire on an incoming message | . | Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character | . | Output LED (GPIO) | Pin the LED is wired to | . | Output LED active high | Whether the LED pin is active high or low | . | Output buzzer (GPIO) | Pin the buzzer is wired to | . | Output vibra (GPIO) | Pin the vibration motor is wired to | . | Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch | . | Use I2S as buzzer | Send the alert through an I2S audio output instead | . | Output duration (milliseconds) | How long a single alert lasts | . | Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging | . | Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file | . Store & Forward module . Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren’t lost during brief disconnections. | Setting | Description | . | Store & Forward enabled | Activate store and forward | . | Heartbeat | Periodically announce this node’s store-and-forward capability | . | Number of records | Maximum stored messages | . | History return max | Max messages to replay | . | History return window | Time window for replay | . | Server | Act as a store-and-forward server for the mesh (requires ample memory, e.g. ESP32 with PSRAM) | . 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes are ideal candidates since they’re typically always-on. Range Test module . ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel still uses the default channel key, the interval and CSV controls stay disabled — you can still switch an already-enabled module off — and saving force-disables the module if the channel has reverted to public. Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving. | Setting | Description | . | Range test enabled | Activate range testing | . | Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals | . | Save .CSV in storage (ESP32 only) | Log received test data to the node’s own filesystem. ESP32 hardware only | . Telemetry module . Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure). Each of the four metric groups has its own enable toggle and its own interval, so you can report battery health often and sensors rarely. | Setting | Description | . | Send Device Telemetry | Master toggle for device metrics. Only shown on firmware 2.7.12 and newer | . | Device metrics update interval | How often to report battery, uptime and channel utilization | . | Environment metrics module enabled | Report the attached environment sensors | . | Environment metrics update interval | How often to report them | . | Environment metrics on-screen enabled | Also show these readings on the device’s own display | . | Environment metrics use Fahrenheit | Use °F on the device’s display. This is the node’s screen only — the app follows your phone’s locale, see Units & Locale | . | Air quality metrics module enabled | Report particulate and CO₂ sensor data | . | Air quality metrics update interval | How often to report them | . | Power metrics module enabled | Report the per-channel voltage and current readings | . | Power metrics update interval | How often to report them | . | Power metrics on-screen enabled | Also show power readings on the device’s display | . See Telemetry & Sensors for supported sensors and configuration recommendations. Canned Message module . Pre-configured messages accessible from the node’s physical buttons (for nodes with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use. | Setting | Description | . | Canned message enabled | ⚠️ Deprecated in the protobuf schema | . | Messages | Newline-separated list of messages | . | Send bell | Send a bell character alongside the message, so a receiving node’s External Notification module can sound | . | Rotary encoder #1 enabled | Use a rotary encoder as the input device | . | GPIO pin for rotary encoder A / B / Press port | The three pins the encoder is wired to | . | Generate input event on Press / CW / CCW | Which key event each encoder action produces | . | Up/Down/Select input enabled | A separate, simpler input scheme using up/down/select buttons rather than an encoder | . | Allow input source | ⚠️ Deprecated in the protobuf schema | . Audio module . Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec. | Setting | Description | . | CODEC 2 enabled | Activate audio module | . | CODEC2 sample rate | Audio quality/bandwidth tradeoff | . | PTT pin | GPIO pin for the push-to-talk button | . | I2S word select | GPIO pin for I2S WS | . | I2S data in | GPIO pin for I2S DIN | . | I2S data out | GPIO pin for I2S DOUT | . | I2S clock | GPIO pin for the I2S bit clock | . ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very low-bandwidth — think “understandable radio voice,” not phone-call quality. Remote Hardware module . GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance. ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins, which could interfere with the node’s own hardware. Turn it on only on dedicated GPIO nodes. | Setting | Description | . | Remote Hardware enabled | Activate remote GPIO access | . | Allow undefined pin access | Allow access to any GPIO pin (security risk) | . | Available pins | Up to 4 GPIO pins this node exposes for remote read/write | . Neighbor Info module . Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality. | Setting | Description | . | Neighbor Info enabled | Activate neighbor broadcasting | . | Update interval (seconds) | How often to broadcast neighbor list | . | Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name | . See Local Mesh Discovery for how to use neighbor data for mesh topology exploration. Ambient Lighting module . Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects. | Setting | Description | . | LED state | Turn the LED on or off | . | Current | LED current limit (0–31) | . | Red / Green / Blue | Individual color channel values (0–255) | . Detection Sensor module . Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh. | Setting | Description | . | Detection Sensor enabled | Activate detection sensor | . | GPIO pin to monitor | GPIO pin connected to sensor | . | Detection trigger type | How the pin’s state maps to a detection event (e.g. active high/low, edge-triggered) | . | Use INPUT_PULLUP mode | Enable the pin’s internal pull-up resistor | . | Minimum broadcast (seconds) | Minimum time between alert broadcasts | . | State broadcast (seconds) | Periodic state broadcast interval | . | Send bell with alert message | Include bell character in alerts | . | Friendly name | Custom name for this sensor | . Paxcounter module . People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices. | Setting | Description | . | Paxcounter enabled | Activate people counting | . | Update interval (seconds) | How often to report counts | . | Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren’t counted (defaults to −80 dBm) | . | BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) | . 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices. Status Message module . The status message has no module screen. It is edited with the rest of the node’s identity, on Settings — Radio & User. Mesh Beacon module . Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only on nodes running firmware 2.8.0 or newer. See Local Mesh Discovery for the full walkthrough. TAK module . Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be true before the entry appears in the module list: the node runs firmware 2.8.0 or newer, and its Device Role on Settings → Device configuration → Device is set to TAK or TAK_TRACKER. See TAK Integration for detailed setup and usage. ",
    "url": "/Meshtastic-Android/main/en/user/settings-module-admin.html#module-configuration",
    
    "relUrl": "/en/user/settings-module-admin.html#module-configuration"
  },"4437": {
    "doc": "Settings — Modules & Admin",
    "title": "Administration",
    "content": "Remote Administration . Remotely configure nodes that share your admin key: . | Select the target node in the node list. | Navigate to Settings for that node. | Modify configuration. | Tap Save — changes are sent over the mesh. | . ⚠️ Important: Requires an admin key configured on both your node and the target node. Device Actions . Settings → Administration holds five one-shot actions, each behind a confirmation dialog: . | Action | What it does | . | Set time | Sends your phone’s clock to the node | . | Reboot | Restarts the node | . | Shutdown | Powers the node down | . | Factory reset | Returns every setting to its factory default | . | NodeDB reset | Clears the node database. This dialog carries a Preserve Favorites? switch | . ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before you reset, use Export configuration to save the node’s settings and Backup Keys on the Security screen to save its keys, so you can put both back afterwards. Backup & Restore . Settings → Backup & Restore writes the connected node’s whole configuration to a file with Export configuration, and reads a saved file back in with Import configuration. Export before a factory reset, or to copy one node’s setup onto another. The section is shown for your own node only, not over remote admin. Advanced . Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown for your own node only: Firmware Update on OTA-capable hardware, Clean Node Database, TAK Server, Local Mesh Discovery, and the Debug Panel. Clean Node Database . Prunes nodes from your node database — from the app’s copy and from the node’s own, so this is not a display-only cleanup. The two filters combine rather than acting separately; the screen puts it as Selections are additive. | Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to 365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0. | Clean up only unknown nodes — narrows the same purge to nodes that never sent their user info. The age limit still applies on top of it. | . The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the purge out, after one more confirmation, and it can’t be undone. Favorited nodes, ignored nodes, and nodes with a public key heard in the last seven days are never removed, whatever the filters say — that is why the queued list can be shorter than you expect. Debug Panel . Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough. App Settings . The App Settings block on the Settings screen configures the app rather than the node, and appears only when your own node is selected. It is grouped rather than flat: . Privacy . | Allow analytics and crash reporting — opt in or out of diagnostics. | Provide phone location to mesh — share this phone’s position when the node has no GPS fix. | Homoglyph encoding — how look-alike characters in names are handled. | . Appearance . | Units — metric, imperial, or follow the system. This is the entry Units & Locale sends you to. | Theme and Language. | Show full message timestamps. | . Persistence . | A cache limit for how much history is kept. | Export rangetest packets, Export all packets and Export node database. | . On their own . | Node Layout — how much detail each row of the node list shows. | Wi-Fi Provisioning for mPWRD-OS — see Connections. | Message Filter — hides incoming messages that contain words you list. With no words configured it does nothing. | System AI — appears only where app functions are available; see App Functions. | . A Permissions block sits above App Settings, so a user who skipped a permission during onboarding can get back to it, and App Info sits below. About . Settings → About carries the app’s own identity rather than the node’s: . Three sections: . | What is Meshtastic? — a short description of the project. | Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out to where to buy one. It also lists the GitHub repository, the running app version, and Acknowledgements (see the next section). | Project information — links to the website, to this documentation, and to the GNU GPL v3 license the app is released under. | . The footer states the copyright and that the app is free software with no warranty, which you may redistribute under the same license. Acknowledgements . Reached from About, this lists every open-source library the app ships, with its license, generated at build time by AboutLibraries. It was previously called the license screen. Troubleshooting remote admin . | “No response from target node” — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes. | Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving. | Can’t see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set. | . ",
    "url": "/Meshtastic-Android/main/en/user/settings-module-admin.html#administration",
    
    "relUrl": "/en/user/settings-module-admin.html#administration"
  },"4438": {
    "doc": "Settings — Modules & Admin",
    "title": "Related Topics",
    "content": ". | Settings — Radio & User — core node and user profile settings | Module configuration reference — detailed module docs on meshtastic.org | FAQ — common questions on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/en/user/settings-module-admin.html#related-topics",
    
    "relUrl": "/en/user/settings-module-admin.html#related-topics"
  },"4439": {
    "doc": "Settings — Modules & Admin",
    "title": "Settings — Modules & Admin",
    "content": " ",
    "url": "/Meshtastic-Android/main/en/user/settings-module-admin.html",
    
    "relUrl": "/en/user/settings-module-admin.html"
  },"4440": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/settings-radio-user.html#settings--radio--user",
    
    "relUrl": "/sk-rSK/user/settings-radio-user.html#settings--radio--user"
  },"4441": {
    "doc": "Settings — Radio & User",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Screenshot | . | Dropdown | | . | Toggle | | . | Slider | | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/sk-rSK/user/settings-radio-user.html#how-these-screens-work"
  },"4442": {
    "doc": "Settings — Radio & User",
    "title": "User Settings",
    "content": "User Profile . On Settings → User. | Setting | Popis | . | Dlhé Meno | Your display name (up to 39 characters) | . | Krátke Meno | 4-character abbreviated name | . | Status Message | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | Unmessageable | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/settings-radio-user.html#user-settings",
    
    "relUrl": "/sk-rSK/user/settings-radio-user.html#user-settings"
  },"4443": {
    "doc": "Settings — Radio & User",
    "title": "Configuration",
    "content": "Konfigurácia Zariadenia . On Settings → Device configuration → Device. | Setting | Popis | Predvolené | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . Konfigurácia LoRa . On Settings → LoRa. | Setting | Popis | Predvolené | . | Región | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Šírka pásma | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Rýchlosť | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Konfigurácia Displeju . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Popis | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Otoč Obrazovku | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Popis | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcastový Interval | How often the position is shared with the mesh | . | Inteligentná poloha | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixná Pozícia | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Popis | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Konfigurácia siete . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Popis | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Heslo | Network password | . | Ethernet zapnutý | Use a wired connection on hardware that has one | . | IPv4 režim | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Konfigurácia Bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Popis | . | Bluetooth zapnuté | Enable/disable BLE radio | . | Režim párovania | Fixed PIN, Random PIN, or No PIN | . | Pevný PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Popis | . | Verejný kľúč | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Súkromný kľúč | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/settings-radio-user.html#configuration",
    
    "relUrl": "/sk-rSK/user/settings-radio-user.html#configuration"
  },"4444": {
    "doc": "Settings — Radio & User",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — optional feature modules and device administration | Signal Meter — how modem presets affect signal quality thresholds | LoRa configuration — detailed LoRa settings reference on meshtastic.org | Initial configuration — region setup guide on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/settings-radio-user.html#related-topics",
    
    "relUrl": "/sk-rSK/user/settings-radio-user.html#related-topics"
  },"4445": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": " ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/settings-radio-user.html",
    
    "relUrl": "/sk-rSK/user/settings-radio-user.html"
  },"4446": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/settings-radio-user.html#settings--radio--user",
    
    "relUrl": "/be-rBY/user/settings-radio-user.html#settings--radio--user"
  },"4447": {
    "doc": "Settings — Radio & User",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Screenshot | . | Dropdown | | . | Toggle | | . | Slider | | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/be-rBY/user/settings-radio-user.html#how-these-screens-work"
  },"4448": {
    "doc": "Settings — Radio & User",
    "title": "User Settings",
    "content": "User Profile . On Settings → User. | Setting | Апісанне | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Status Message | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | Unmessageable | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/settings-radio-user.html#user-settings",
    
    "relUrl": "/be-rBY/user/settings-radio-user.html#user-settings"
  },"4449": {
    "doc": "Settings — Radio & User",
    "title": "Конфигурация",
    "content": "Device Config . On Settings → Device configuration → Device. | Setting | Апісанне | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Уключана | . | LED Heartbeat | Blink the status LED periodically | Уключана | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Апісанне | Default | . | Рэгіён | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Хуткасць | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Апісанне | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | Тып OLED | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Апісанне | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Апісанне | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Апісанне | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Пароль | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Config . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Апісанне | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Апісанне | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Прыватны ключ | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/settings-radio-user.html#%D0%BA%D0%BE%D0%BD%D1%84%D0%B8%D0%B3%D1%83%D1%80%D0%B0%D1%86%D0%B8%D1%8F",
    
    "relUrl": "/be-rBY/user/settings-radio-user.html#конфигурация"
  },"4450": {
    "doc": "Settings — Radio & User",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — optional feature modules and device administration | Signal Meter — how modem presets affect signal quality thresholds | LoRa configuration — detailed LoRa settings reference on meshtastic.org | Initial configuration — region setup guide on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/settings-radio-user.html#related-topics",
    
    "relUrl": "/be-rBY/user/settings-radio-user.html#related-topics"
  },"4451": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": " ",
    "url": "/Meshtastic-Android/main/be-rBY/user/settings-radio-user.html",
    
    "relUrl": "/be-rBY/user/settings-radio-user.html"
  },"4452": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/settings-radio-user.html#settings--radio--user",
    
    "relUrl": "/it-rIT/user/settings-radio-user.html#settings--radio--user"
  },"4453": {
    "doc": "Settings — Radio & User",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Screenshot | . | Dropdown | | . | Toggle | | . | Slider | | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/it-rIT/user/settings-radio-user.html#how-these-screens-work"
  },"4454": {
    "doc": "Settings — Radio & User",
    "title": "Impostazioni Utente",
    "content": "User Profile . On Settings → User. | Impostazione | Descrizione | . | Nome Lungo | Your display name (up to 39 characters) | . | Nome Breve | 4-character abbreviated name | . | Messaggio di Stato | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | Non messaggiabile | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/settings-radio-user.html#impostazioni-utente",
    
    "relUrl": "/it-rIT/user/settings-radio-user.html#impostazioni-utente"
  },"4455": {
    "doc": "Settings — Radio & User",
    "title": "Configurazione",
    "content": "Configurazione Dispositivo . On Settings → Device configuration → Device. | Impostazione | Descrizione | Predefinito | . | Ruolo Del Dispositivo | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Modalità Ritrasmissione | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Intervallo Di Trasmissione Info Nodo | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Doppio tocco come pressione pulsante | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Abilitato | . | Battito Cuore Led | Blink the status LED periodically | Abilitato | . | Fuso Orario | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . Configurazione LoRa . On Settings → LoRa. | Impostazione | Descrizione | Predefinito | . | Regione | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Preset | Speed/range tradeoff | LongFast | . | Numero di Hop | Maximum retransmit hops | 3 | . | Potenza di Trasmissione | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Sovrascrivi Frequenza | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Usa Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Larghezza di banda | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Slot di Frequenza | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Trasmissione Abilitata | Turning this off makes the node receive-only | On | . | Ignora limite di Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Disattivato | . | Ignora MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | OK per MQTT | Allow your packets to be forwarded to MQTT by gateways | Disattivato | . | Migliora guadagno in Ricezione | Extra receive gain on SX126x radios; costs a little current | Disattivato | . | Ventola PA disabilitata | Turn off the power-amplifier fan on hardware that has one | Disattivato | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Velocità | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6,25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3,52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1,95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0,34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0,18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Configurazione Schermo . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Impostazione | Descrizione | . | Tieni lo schermo acceso per | How long the display stays lit before sleeping | . | Durata di ogni schermata | How often the node cycles between screens on its own | . | Modalità schermo | Screen layout/density used by the firmware | . | Unità di misura visualizzata | Metric or Imperial on the node’s screen | . | Usa formato orologio 12h | Show the node’s clock as 12-hour rather than 24-hour | . | Intestazione in grassetto | Draw the screen’s heading text in bold | . | Capovolgi schermo | Rotate the display 180° for an inverted mounting | . | Tipo OLED | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Accendi lo schermo al tocco o al movimento | Light the screen when the node is tapped or moved | . | Orientamento bussola | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Punta sempre a nord | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Configurazione Posizione . On Settings → Device configuration → Position. | Impostazione | Descrizione | . | Modalità GPS (Hardware Fisico) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | Intervallo Interrogazione GPS | How often the node asks its GPS for a fix | . | Intervallo Di Trasmissione | How often the position is shared with the mesh | . | Posizione Smart | Broadcast based on movement rather than purely on the clock | . | Intervallo Intelligente | With Smart Position on, the shortest gap between broadcasts | . | Distanza Intelligente | With Smart Position on, how far you must move before broadcasting | . | Posizione Fissa | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Flag Di Posizione | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Configurazione Alimentazione . On Settings → Device configuration → Power. | Impostazione | Descrizione | . | Abilita modalità risparmio energetico | Let the node sleep aggressively between activity | . | Spegnimento in mancanza di alimentazione | Power the device down after external power disappears | . | Durata super deep sleep | How long the deepest sleep state lasts | . | Tempo minimo di risveglio | The shortest time the node stays awake once woken | . | Durata attesa Bluetooth | How long to wait for a phone to connect before sleeping | . | Sovrascrivi moltiplicatore ADC | Turn on a manual correction for battery-voltage readings | . | Sovrascrivi rapporto moltiplicatore ADC | The correction factor itself, used only when the override is on | . | Indirizzo INA_2XX I2C della batteria | Address of an external INA-series power sensor, if fitted | . Configurazione Della Rete . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Impostazione | Descrizione | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Password di rete | . | Ethernet abilitato | Use a wired connection on hardware that has one | . | Modalità IPv4 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | Trasmissione UDP | Share mesh traffic with other nodes over the local network | . | Server NTP | Time synchronization server | . | server rsyslog | Remote logging server | . Configurazione Bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Impostazione | Descrizione | . | Bluetooth attivo | Enable/disable BLE radio | . | Modalità abbinamento | Fixed PIN, Random PIN, or No PIN | . | PIN Fisso | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Configurazione Sicurezza . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Impostazione | Descrizione | . | Chiave Pubblica | Your node’s public key (read-only) | . | Chiave Amministratore | Keys permitted to administer this node remotely — up to three | . | Chiave Privata | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Rigenera Chiavi Private | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Console seriale | Serial console over the Stream API | . | Debug log API abilitato | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Modalità Gestita | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup chiavi | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Livello di protezione | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Avvii rimanenti | How many device boots the unlocked state survives | . | Ore alla scadenza | Wall-clock lifetime of the unlocked state | . | Limite di sessione (minuti) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/settings-radio-user.html#configurazione",
    
    "relUrl": "/it-rIT/user/settings-radio-user.html#configurazione"
  },"4456": {
    "doc": "Settings — Radio & User",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — optional feature modules and device administration | Signal Meter — how modem presets affect signal quality thresholds | LoRa configuration — detailed LoRa settings reference on meshtastic.org | Initial configuration — region setup guide on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/settings-radio-user.html#related-topics",
    
    "relUrl": "/it-rIT/user/settings-radio-user.html#related-topics"
  },"4457": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": " ",
    "url": "/Meshtastic-Android/main/it-rIT/user/settings-radio-user.html",
    
    "relUrl": "/it-rIT/user/settings-radio-user.html"
  },"4458": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/es-rES/user/settings-radio-user.html#settings--radio--user",
    
    "relUrl": "/es-rES/user/settings-radio-user.html#settings--radio--user"
  },"4459": {
    "doc": "Settings — Radio & User",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Screenshot | . | Dropdown | | . | Toggle | | . | Slider | | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/es-rES/user/settings-radio-user.html#how-these-screens-work"
  },"4460": {
    "doc": "Settings — Radio & User",
    "title": "User Settings",
    "content": "User Profile . On Settings → User. | Setting | Descripción | . | Nombre largo | Your display name (up to 39 characters) | . | Nombre Corto | 4-character abbreviated name | . | Status Message | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | No se puede enviar mensajes | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/es-rES/user/settings-radio-user.html#user-settings",
    
    "relUrl": "/es-rES/user/settings-radio-user.html#user-settings"
  },"4461": {
    "doc": "Settings — Radio & User",
    "title": "Configuración",
    "content": "Configuración del dispositivo . On Settings → Device configuration → Device. | Setting | Descripción | Por defecto | . | Rol del dispositivo | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Modo de retransmisión | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Intervalo de transmisión de información del nodo | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Doble pulsación como botón | Treat a double tap as a button press | Disabled | . | Triple pulsación para enviar un ping | Send an ad-hoc position ping on a triple click | Habilitado | . | Latido LED | Blink the status LED periodically | Habilitado | . | Zona horaria | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . Configuración LoRa . On Settings → LoRa. | Setting | Descripción | Por defecto | . | Región | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Predefinidos | Speed/range tradeoff | LongFast | . | Número de saltos | Maximum retransmit hops | 3 | . | Potencia de transmisión | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Sobreescribir frecuencia | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Usar predefinido | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Factor de dispersión | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Ratio de Codificación | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Ancho de banda | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Banda de Frecuencia | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmisión habilitada | Turning this off makes the node receive-only | On | . | Sobreescribir el Tiempo de Trabajo | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignorar Paquetes MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Permitir MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | Aumentar ganancia de RX | Extra receive gain on SX126x radios; costs a little current | Off | . | Ventilador del Amplificador apagado | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Velocidad | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Configuración de pantalla . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Descripción | . | Pantalla activa durante | How long the display stays lit before sleeping | . | Intervalo de carrusel | How often the node cycles between screens on its own | . | Modo de la pantalla | Screen layout/density used by the firmware | . | Unidades en pantalla | Metric or Imperial on the node’s screen | . | Utilizar el formato de 12h para el reloj | Show the node’s clock as 12-hour rather than 24-hour | . | Encabezado en negrita | Draw the screen’s heading text in bold | . | Girar la pantalla 180º | Rotate the display 180° for an inverted mounting | . | Tipo de OLED | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Despertar al tocar o al mover | Light the screen when the node is tapped or moved | . | Orientación de la brújula | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Siempre apuntar al norte | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Configuración de la posición . On Settings → Device configuration → Position. | Setting | Descripción | . | Modo GPS (dispositivo físico) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Intervalo de Difusión | How often the position is shared with the mesh | . | Ubicación inteligente | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Posición fija | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Marcas de posición | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Configuración de elecenergía . On Settings → Device configuration → Power. | Setting | Descripción | . | Activar el modo ahorro de energía | Let the node sleep aggressively between activity | . | Apagar al perder energía | Power the device down after external power disappears | . | Duración del sueño súper profundo | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Esperar Bluetooth durante | How long to wait for a phone to connect before sleeping | . | Sobreescribir multiplicador ADC | Turn on a manual correction for battery-voltage readings | . | Sobreescribir relación del multiplicador ADC | The correction factor itself, used only when the override is on | . | Dirección I2C del INA_2xx para la batería | Address of an external INA-series power sensor, if fitted | . Configuración de la red . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Descripción | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID (Nombre la Red) | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Contraseña | Contraseña de red | . | Ethernet del Nodo Activado | Use a wired connection on hardware that has one | . | Modo IPv4 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | Servidor NTP | Time synchronization server | . | Servidor rsyslog | Remote logging server | . Configuración Bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Descripción | . | Bluetooth activado | Enable/disable BLE radio | . | Modo de emparejamiento | Fixed PIN, Random PIN, or No PIN | . | Pin fijo | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Configuración de la seguridad . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Descripción | . | Clave Pública | Your node’s public key (read-only) | . | Contraseña de administrador | Keys permitted to administer this node remotely — up to three | . | Clave privada | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerar clave privada | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Consola serial | Serial console over the Stream API | . | API de registro de depuración habilitada | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Modo “ya terminado de configurar” | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/es-rES/user/settings-radio-user.html#configuraci%C3%B3n",
    
    "relUrl": "/es-rES/user/settings-radio-user.html#configuración"
  },"4462": {
    "doc": "Settings — Radio & User",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — optional feature modules and device administration | Signal Meter — how modem presets affect signal quality thresholds | LoRa configuration — detailed LoRa settings reference on meshtastic.org | Initial configuration — region setup guide on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/settings-radio-user.html#related-topics",
    
    "relUrl": "/es-rES/user/settings-radio-user.html#related-topics"
  },"4463": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": " ",
    "url": "/Meshtastic-Android/main/es-rES/user/settings-radio-user.html",
    
    "relUrl": "/es-rES/user/settings-radio-user.html"
  },"4464": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/settings-radio-user.html#settings--radio--user",
    
    "relUrl": "/sl-rSI/user/settings-radio-user.html#settings--radio--user"
  },"4465": {
    "doc": "Settings — Radio & User",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Screenshot | . | Dropdown | | . | Toggle | | . | Slider | | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/sl-rSI/user/settings-radio-user.html#how-these-screens-work"
  },"4466": {
    "doc": "Settings — Radio & User",
    "title": "User Settings",
    "content": "User Profile . On Settings → User. | Setting | Opis | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Status Message | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | Unmessageable | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/settings-radio-user.html#user-settings",
    
    "relUrl": "/sl-rSI/user/settings-radio-user.html#user-settings"
  },"4467": {
    "doc": "Settings — Radio & User",
    "title": "Configuration",
    "content": "Device Config . On Settings → Device configuration → Device. | Setting | Opis | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Opis | Default | . | Regija | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Opis | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Opis | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Opis | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Opis | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Config . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Opis | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Opis | . | Javni ključ | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Zasebni ključ | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/settings-radio-user.html#configuration",
    
    "relUrl": "/sl-rSI/user/settings-radio-user.html#configuration"
  },"4468": {
    "doc": "Settings — Radio & User",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — optional feature modules and device administration | Signal Meter — how modem presets affect signal quality thresholds | LoRa configuration — detailed LoRa settings reference on meshtastic.org | Initial configuration — region setup guide on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/settings-radio-user.html#related-topics",
    
    "relUrl": "/sl-rSI/user/settings-radio-user.html#related-topics"
  },"4469": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": " ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/settings-radio-user.html",
    
    "relUrl": "/sl-rSI/user/settings-radio-user.html"
  },"4470": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/settings-radio-user.html#settings--radio--user",
    
    "relUrl": "/no-rNO/user/settings-radio-user.html#settings--radio--user"
  },"4471": {
    "doc": "Settings — Radio & User",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Screenshot | . | Dropdown | | . | Toggle | | . | Slider | | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/no-rNO/user/settings-radio-user.html#how-these-screens-work"
  },"4472": {
    "doc": "Settings — Radio & User",
    "title": "User Settings",
    "content": "User Profile . On Settings → User. | Setting | Beskrivelse | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Status Message | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | Unmessageable | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/settings-radio-user.html#user-settings",
    
    "relUrl": "/no-rNO/user/settings-radio-user.html#user-settings"
  },"4473": {
    "doc": "Settings — Radio & User",
    "title": "Configuration",
    "content": "Device Config . On Settings → Device configuration → Device. | Setting | Beskrivelse | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Beskrivelse | Default | . | Region | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Beskrivelse | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Beskrivelse | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Beskrivelse | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Beskrivelse | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Config . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Beskrivelse | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Beskrivelse | . | Offentlig nøkkel | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Privat nøkkel | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/settings-radio-user.html#configuration",
    
    "relUrl": "/no-rNO/user/settings-radio-user.html#configuration"
  },"4474": {
    "doc": "Settings — Radio & User",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — optional feature modules and device administration | Signal Meter — how modem presets affect signal quality thresholds | LoRa configuration — detailed LoRa settings reference on meshtastic.org | Initial configuration — region setup guide on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/settings-radio-user.html#related-topics",
    
    "relUrl": "/no-rNO/user/settings-radio-user.html#related-topics"
  },"4475": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": " ",
    "url": "/Meshtastic-Android/main/no-rNO/user/settings-radio-user.html",
    
    "relUrl": "/no-rNO/user/settings-radio-user.html"
  },"4476": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/settings-radio-user.html#settings--radio--user",
    
    "relUrl": "/hu-rHU/user/settings-radio-user.html#settings--radio--user"
  },"4477": {
    "doc": "Settings — Radio & User",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Screenshot | . | Dropdown | | . | Toggle | | . | Slider | | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/hu-rHU/user/settings-radio-user.html#how-these-screens-work"
  },"4478": {
    "doc": "Settings — Radio & User",
    "title": "User Settings",
    "content": "User Profile . On Settings → User. | Setting | Leírás | . | Hosszú név | Your display name (up to 39 characters) | . | Rövid név | 4-character abbreviated name | . | Status Message | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | Nem üzenetképes | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/settings-radio-user.html#user-settings",
    
    "relUrl": "/hu-rHU/user/settings-radio-user.html#user-settings"
  },"4479": {
    "doc": "Settings — Radio & User",
    "title": "Configuration",
    "content": "Eszközbeállítások . On Settings → Device configuration → Device. | Setting | Leírás | Alapértelmezett | . | Eszköz szerepköre | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Újrasugárzási mód | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Csomópont-információ sugárzási időköze | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Dupla koppintás mint gomb | Treat a double tap as a button press | Disabled | . | Háromszori kattintás – ad hoc ping | Send an ad-hoc position ping on a triple click | Engedélyezve | . | LED ütemjelzés | Blink the status LED periodically | Engedélyezve | . | Időzóna | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa beállítások . On Settings → LoRa. | Setting | Leírás | Alapértelmezett | . | Régió | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Előbeállítások | Speed/range tradeoff | LongFast | . | Ugrások száma | Maximum retransmit hops | 3 | . | Adásteljesítmény | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frekvencia felülbírálása | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Előbeállítás használata | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Szórási Faktor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Kódolási ráta | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Sávszélesség | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frekvencia sáv | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Adás engedélyezve | Turning this off makes the node receive-only | On | . | Duty Cycle felülbírálása | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | MQTT figyelmen kívül hagyása | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | MQTT-re továbbítható | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX fokozott erősítés | Extra receive gain on SX126x radios; costs a little current | Off | . | PA ventilátor letiltva | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Sebesség | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Kijelző beállítások . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Leírás | . | Kijelző bekapcsolva ennyi ideig | How long the display stays lit before sleeping | . | Karusszel időköz | How often the node cycles between screens on its own | . | Kijelző mód | Screen layout/density used by the firmware | . | Mértékegységek megjelenítése | Metric or Imperial on the node’s screen | . | 12 órás időformátum használata | Show the node’s clock as 12-hour rather than 24-hour | . | Félkövér címsor | Draw the screen’s heading text in bold | . | Kijelző megfordítása | Rotate the display 180° for an inverted mounting | . | OLED típus | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Érintésre vagy mozgásra ébresztés | Light the screen when the node is tapped or moved | . | Iránytű tájolás | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Mindig észak felé mutasson | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Pozíció beállítások . On Settings → Device configuration → Position. | Setting | Leírás | . | GPS mód (fizikai hardver) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Sugárzási időköz | How often the position is shared with the mesh | . | Intelligens pozíció | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Rögzített pozíció | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Pozíció jelzők (flags) | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Energia-beállítások . On Settings → Device configuration → Power. | Setting | Leírás | . | Energiatakarékos mód engedélyezése | Let the node sleep aggressively between activity | . | Leállítás áramszünet esetén | Power the device down after external power disappears | . | Szuper mélyalvás időtartama | How long the deepest sleep state lasts | . | Minimális ébrenléti idő | The shortest time the node stays awake once woken | . | Bluetooth-várakozás időtartama | How long to wait for a phone to connect before sleeping | . | ADC szorzó felülbírálása | Turn on a manual correction for battery-voltage readings | . | ADC szorzó felülbírálási arány | The correction factor itself, used only when the override is on | . | Akkumulátor INA_2XX I2C-cím | Address of an external INA-series power sensor, if fitted | . Hálózati beállítások . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Leírás | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Jelszó | Network password | . | Ethernet engedélyezve | Use a wired connection on hardware that has one | . | IPv4 mód | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP szerver | Time synchronization server | . | rsyslog szerver | Remote logging server | . Bluetooth beállítások . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Leírás | . | Bluetooth engedélyezve | Enable/disable BLE radio | . | Párosítási mód | Fixed PIN, Random PIN, or No PIN | . | Rögzített PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Biztonsági beállítások . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Leírás | . | Nyilvános kulcs | Your node’s public key (read-only) | . | Admin kulcs | Keys permitted to administer this node remotely — up to three | . | Privát kulcs | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Privát kulcs újragenerálása | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Soros konzol | Serial console over the Stream API | . | Hibakeresési napló API engedélyezve | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Felügyelt mód | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/settings-radio-user.html#configuration",
    
    "relUrl": "/hu-rHU/user/settings-radio-user.html#configuration"
  },"4480": {
    "doc": "Settings — Radio & User",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — optional feature modules and device administration | Signal Meter — how modem presets affect signal quality thresholds | LoRa configuration — detailed LoRa settings reference on meshtastic.org | Initial configuration — region setup guide on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/settings-radio-user.html#related-topics",
    
    "relUrl": "/hu-rHU/user/settings-radio-user.html#related-topics"
  },"4481": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": " ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/settings-radio-user.html",
    
    "relUrl": "/hu-rHU/user/settings-radio-user.html"
  },"4482": {
    "doc": "Настройки - Радио и пользователь",
    "title": "Настройки - Радио и пользователь",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/settings-radio-user.html",
    
    "relUrl": "/ru-rRU/user/settings-radio-user.html"
  },"4483": {
    "doc": "Настройки - Радио и пользователь",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Настройки используют стандартные элементы управления предпочтениями — выпадающие списки, переключатели и ползунки: . | Управление | Снимок экрана | . | Выпадающий список | | . | Переключатель | | . | Ползунок | | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/ru-rRU/user/settings-radio-user.html#how-these-screens-work"
  },"4484": {
    "doc": "Настройки - Радио и пользователь",
    "title": "Настройки пользователя",
    "content": "Профиль пользователя . On Settings → User. | Настройка | Описание | . | Полное имя | Ваше отображаемое имя (до 39 символов) | . | Короткое имя | 4-символьное сокращённое имя | . | Состояние сообщения | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | Без сообщений | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/settings-radio-user.html#%D0%BD%D0%B0%D1%81%D1%82%D1%80%D0%BE%D0%B9%D0%BA%D0%B8-%D0%BF%D0%BE%D0%BB%D1%8C%D0%B7%D0%BE%D0%B2%D0%B0%D1%82%D0%B5%D0%BB%D1%8F",
    
    "relUrl": "/ru-rRU/user/settings-radio-user.html#настройки-пользователя"
  },"4485": {
    "doc": "Настройки - Радио и пользователь",
    "title": "Настройки",
    "content": "Настройки устройства . On Settings → Device configuration → Device. | Настройка | Описание | По умолчанию | . | Роль устройства | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Режим ретрансляции | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Интервал вещания передачи информации об узле | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Двойное нажатие как кнопка | Treat a double tap as a button press | Включено | . | Маякнуть при тройном нажатии | Send an ad-hoc position ping on a triple click | Включено | . | Сердцебиение светодиодом | Blink the status LED periodically | Включено | . | Часовой пояс | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . Настройка LoRa . On Settings → LoRa. | Настройка | Описание | По умолчанию | . | Регион / Страна | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Не установлено (необходимо настроить) | . | Шаблоны | Компромисс между скоростью и дальностью | LongFast | . | Количество прыжков | Максимальное количество ретрансляций | 3 | . | Мощность передатчика | Мощность передачи (дБм); 0 = максимально разрешённая для региона | 0 (максимум региона) | . | Переопределить частоту | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Использовать шаблон | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Коэффициент распространения | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Частота кодирования | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Ширина канала | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Частота слота | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Передача включена | Turning this off makes the node receive-only | On | . | Переопределить рабочий цикл | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Выкл | . | Игнорировать MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | ОК в MQTT | Allow your packets to be forwarded to MQTT by gateways | Выкл | . | Усиление RX | Extra receive gain on SX126x radios; costs a little current | Выкл | . | PA вентилятор выключен | Turn off the power-amplifier fan on hardware that has one | Выкл | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. Смотрите руководство по настройке региона на сайте meshtastic.org для получения подробной информации. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Совет: Значения порога SNR специально отрицательные. LoRa может декодировать сигналы ниже уровня шума, поэтому более отрицательный предел означает, что пресет допускает более слабый, шумный сигнал (больший радиус действия). Смотрите Как работает измеритель сигнала для полного объяснения. | Предустановка | Диапазон | Скорость | Предел SNR | Лучше всего для | . | Short Turbo | ~1 км | 21.9 кб/с | −7.5 дБ | Плотная городская застройка с прямой видимостью; приложения, требующие высокой передачи данных | . | Short Fast | ~3 км | 10.9 кб/с | −7.5 дБ | Городские районы; здания в пределах нескольких кварталов | . | Short Slow | ~5 км | 6.25 kbps | -10 дБ | Пригородная зона с коротким диапазоном; умеренная плотность застройки | . | Medium Fast | ~5 км | 3.52 kbps | −12.5 дБ | Пригородные районы; умеренная плотность застройки | . | Medium Slow | ~8 км | 1.95 kbps | -15 дБ | Пригородный/сельский; умеренный диапазон со сниженной скоростью | . | Long Turbo | ~10 км | 1.34 kbps | −17.5 дБ | Диапазон, похожий на Long Fast, но с полосой пропускания 500 кГц; более высокая пропускная способность | . | Long Fast | ~10 км | 1.1 кб/с | −17.5 дБ | Общее использование (по умолчанию) — сбалансированный диапазон и скорость | . | Long Moderate | ~20 км | 0.34 кб/с | −17.5 дБ | Сельская местность с некоторым рельефом; случайное использование | . | Lite Fast | ~5 км | 1.76 kbps | −12.5 дБ | Диапазон RU 866 МГц SRD (ширина полосы 125 кГц); аналогично Medium Fast | . | Lite Slow | ~10 км | 0.98 kbps | -15 дБ | Диапазон RU 866 МГц SRD (ширина полосы 125 кГц); аналогично Long Fast | . | Narrow Fast | ~5 км | 2.28 kbps | −7.5 дБ | Диапазон RU 868 МГц (полоса пропускания 62,5 кГц); предотвращает помехи с другими устройствами | . | Narrow Slow | ~10 км | 1.30 kbps | -10 дБ | Диапазон RU 868 МГц (ширина полосы 62,5 кГц); аналогично Long Fast | . | Medium Turbo | ~5 км | 7.0 kbps | −12.5 дБ | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 км | 0.68 kbps | −7.5 дБ | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 км | 0.33 kbps | -10 дБ | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 км | 0.18 кб/с | −20 дБ | ⚠️ Устарел — всё ещё доступен для выбора, но может быть удален в будущих версиях прошивки | . | Very Long Slow | ~40+ км | 0.09 кб/с | −20 дБ | ⚠️ Устарел — всё ещё доступен для выбора, но может быть удален в будущих версиях прошивки | . i Примечание: В этой таблице используются общие короткие имена. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . Предустановка модема управляет основным компромиссом между дальностью и скоростью передачи данных: . | Медленные предустановки используют большее распространение, что позволяет декодировать сигналы при более слабых уровнях сигнала (ниже порога SNR). Это означает большую дальность, но меньше байт в секунду. | Быстрые предустановки передают больше данных за одну передачу, но требуют более сильного сигнала для декодирования. | . Практическое руководство: . | Городская сеть (много нод, короткие расстояния): Используй Long Fast (по умолчанию) или Short Fast. Более высокая скорость означает меньшее переполнение канала эфирного времени, когда многие ноды используют канал. | Сельская/разреженная сеть (мало нод, большие расстояния): Используй Long Moderate. Дальность важнее скорости, когда ноды находятся далеко друг от друга. | Соответствие нормативным требованиям RU 866/868 МГц: Используй Lite Fast, Lite Slow, Narrow Fast или Narrow Slow — они оптимизированы для диапазонов RU SRD/868 МГц с более узкой полосой пропускания. | Фиксированные инфраструктурные связи: Используй Short Turbo или Long Turbo для выделенных соединений точка-точка с хорошими антеннами и прямой видимостью. | Смешанные среды: Используй Long Fast — это настройка по умолчанию в сообществе и она обеспечит совместимость с другими в вашем регионе. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Преимущество высоты (вершина холма, крыша) значительно увеличивает эффективную дальность. Хорошо размещённый маршрутизатор с Long Fast часто может превзойти наземную ноду с Long Slow. Параметры дисплея . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Настройка | Описание | . | Включать экран на | How long the display stays lit before sleeping | . | Интервал карусели | How often the node cycles between screens on its own | . | Режим экрана | Screen layout/density used by the firmware | . | Система измерения | Metric or Imperial on the node’s screen | . | Использовать 12-часовой формат времени | Show the node’s clock as 12-hour rather than 24-hour | . | Выделять заголовок жирным | Draw the screen’s heading text in bold | . | Повернуть экран | Rotate the display 180° for an inverted mounting | . | Тип OLED | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Включать экран при касании или движении | Light the screen when the node is tapped or moved | . | Направление компаса | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Всегда указывать на север | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Настройки местоположения . On Settings → Device configuration → Position. | Настройка | Описание | . | Режим GPS (физическое оборудование) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | Интервал опроса GPS | How often the node asks its GPS for a fix | . | Период рассылки | How often the position is shared with the mesh | . | Умная позиция | Broadcast based on movement rather than purely on the clock | . | Умный интервал | With Smart Position on, the shortest gap between broadcasts | . | Умное расстояние | With Smart Position on, how far you must move before broadcasting | . | Фиксированная позиция | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Флаги позиции | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Настройка питания . On Settings → Device configuration → Power. | Настройка | Описание | . | Включить режим энергосбережения | Let the node sleep aggressively between activity | . | Выключение при потере мощности | Power the device down after external power disappears | . | Длительность супер-глубокого сна | How long the deepest sleep state lasts | . | Минимальное время бодрствования | The shortest time the node stays awake once woken | . | Длительность ожидания Bluetooth | How long to wait for a phone to connect before sleeping | . | Коэффициент переопределения ADC | Turn on a manual correction for battery-voltage readings | . | Коэффициент переопределения ADC | The correction factor itself, used only when the override is on | . | I2C-адрес INA_2XX батареи | Address of an external INA-series power sensor, if fitted | . Настройка сети . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Настройка | Описание | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | Название сети | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Пароль | Пароль сети | . | Ethernet включен | Use a wired connection on hardware that has one | . | Режим IPv4 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP трансляция | Share mesh traffic with other nodes over the local network | . | NTP-сервер | Сервер синхронизации времени | . | Сервер rsyslog | Удалённый сервер логирования | . Настройка Bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Настройка | Описание | . | Bluetooth включен | Включение/отключение BLE радиостанции | . | Режим сопряжения | Фиксированный PIN, случайный PIN или без PIN | . | Фиксированный PIN-код | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Настройки безопасности . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Настройка | Описание | . | Публичный ключ | Публичный ключ твоей ноды (только для чтения) | . | Ключ администратора | Keys permitted to administer this node remotely — up to three | . | Приватный ключ | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Пересоздать приватный ключ | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Канал администратора включен | ⚠️ Удалено — теперь настраивается автоматически при установке ключа администратора | . | Консоль COM-порта | Serial console over the Stream API | . | API журнала отладки включен | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Управляемый режим | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Резервное копирование | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Восстановить ключи | Запишисать сохранённые ключи обратно на ноду (доступно, как только есть резервная копия) | . | Удалить резервную копию ключа | Remove the stored key backup from this phone | . | Уровень защиты | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | Что она делает | . | Осталось загрузок | How many device boots the unlocked state survives | . | Часов до истечения | Wall-clock lifetime of the unlocked state | . | Ограничение сессии (минуты) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/settings-radio-user.html#%D0%BD%D0%B0%D1%81%D1%82%D1%80%D0%BE%D0%B9%D0%BA%D0%B8",
    
    "relUrl": "/ru-rRU/user/settings-radio-user.html#настройки"
  },"4486": {
    "doc": "Настройки - Радио и пользователь",
    "title": "Связанные темы",
    "content": ". | Настройки — Модули и администрирование — дополнительные модули и управление устройством | Измеритель сигнала — как предустановки модема влияют на пороги качества сигнала | Конфигурация LoRa — подробная справка по настройкам LoRa на meshtastic.org | Начальная конфигурация — руководство по настройке региона на meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/settings-radio-user.html#%D1%81%D0%B2%D1%8F%D0%B7%D0%B0%D0%BD%D0%BD%D1%8B%D0%B5-%D1%82%D0%B5%D0%BC%D1%8B",
    
    "relUrl": "/ru-rRU/user/settings-radio-user.html#связанные-темы"
  },"4487": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/settings-radio-user.html#settings--radio--user",
    
    "relUrl": "/cs-rCZ/user/settings-radio-user.html#settings--radio--user"
  },"4488": {
    "doc": "Settings — Radio & User",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Screenshot | . | Dropdown | | . | Toggle | | . | Slider | | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/cs-rCZ/user/settings-radio-user.html#how-these-screens-work"
  },"4489": {
    "doc": "Settings — Radio & User",
    "title": "User Settings",
    "content": "User Profile . On Settings → User. | Nastavení | Popis | . | Dlouhé jméno | Your display name (up to 39 characters) | . | Krátké jméno | 4-character abbreviated name | . | Stavová zpráva | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | Nepřijímá zprávy | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/settings-radio-user.html#user-settings",
    
    "relUrl": "/cs-rCZ/user/settings-radio-user.html#user-settings"
  },"4490": {
    "doc": "Settings — Radio & User",
    "title": "Nastavení",
    "content": "Nastavení zařízení . On Settings → Device configuration → Device. | Nastavení | Popis | Výchozí | . | Role zařízení | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Režim opětovného vysílání | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Interval vysílání Node Info | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Dvojité klepnutí jako stisk tlačítka | Treat a double tap as a button press | Disabled | . | Okamžitý ping (trojitý stisk) | Send an ad-hoc position ping on a triple click | Povoleno | . | Blikání LED při provozu | Blink the status LED periodically | Povoleno | . | Časové pásmo | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa nastavení . On Settings → LoRa. | Nastavení | Popis | Výchozí | . | Region | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Předvolby | Speed/range tradeoff | LongFast | . | Počet skoků | Maximum retransmit hops | 3 | . | Vysílací výkon | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Ruční nastavení frekvence | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Použít předvolbu | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Šířka pásma | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frekvenční slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Vysílání povoleno | Turning this off makes the node receive-only | On | . | Přepsat pracovní cyklus | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Vypnuto | . | Ignorovat MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | OK do MQTT | Allow your packets to be forwarded to MQTT by gateways | Vypnuto | . | Zvýšené zesílení přijímače (RX) | Extra receive gain on SX126x radios; costs a little current | Vypnuto | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Vypnuto | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Rychlost | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Nastavení zobrazení . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Nastavení | Popis | . | Obrazovka zapnutá po dobu | How long the display stays lit before sleeping | . | Interval přepínání obrazovek | How often the node cycles between screens on its own | . | Režim obrazovky | Screen layout/density used by the firmware | . | Zobrazení jednotek | Metric or Imperial on the node’s screen | . | Použít 12h formát hodin | Show the node’s clock as 12-hour rather than 24-hour | . | Tučný nadpis | Draw the screen’s heading text in bold | . | Překlopit obrazovku | Rotate the display 180° for an inverted mounting | . | Typ OLED displeje | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Probuzení klepnutím nebo pohybem | Light the screen when the node is tapped or moved | . | Orientace kompasu | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Vždy ukazovat na sever | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Nastavení pozice . On Settings → Device configuration → Position. | Nastavení | Popis | . | Režim GPS (fyzický modul) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | Interval aktualizace GPS | How often the node asks its GPS for a fix | . | Interval vysílání | How often the position is shared with the mesh | . | Chytrá poloha | Broadcast based on movement rather than purely on the clock | . | Chytrý Interval | With Smart Position on, the shortest gap between broadcasts | . | Chytrá vzdálenost | With Smart Position on, how far you must move before broadcasting | . | Pevná poloha | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Příznaky polohy | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Nastavení napájení . On Settings → Device configuration → Power. | Nastavení | Popis | . | Povolit úsporný režim | Let the node sleep aggressively between activity | . | Vypnutí při ztrátě napájení | Power the device down after external power disappears | . | Doba super hlubokého spánku | How long the deepest sleep state lasts | . | Minimální doba probuzení | The shortest time the node stays awake once woken | . | Doba čekání na Bluetooth | How long to wait for a phone to connect before sleeping | . | Přepsání násobiče ADC | Turn on a manual correction for battery-voltage readings | . | Vlastní hodnota násobiče pro ADC | The correction factor itself, used only when the override is on | . | Adresa INA_2XX I2C baterie | Address of an external INA-series power sensor, if fitted | . Nastavení sítě . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Nastavení | Popis | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Heslo | Network password | . | Ethernet povolen | Use a wired connection on hardware that has one | . | Režim IPv4 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP vysílání | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Nastavení bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Nastavení | Popis | . | Bluetooth povoleno | Enable/disable BLE radio | . | Režim párování | Fixed PIN, Random PIN, or No PIN | . | Pevný PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Nastavení zabezpečení . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Nastavení | Popis | . | Veřejný klíč | Your node’s public key (read-only) | . | Administrátorský klíč | Keys permitted to administer this node remotely — up to three | . | Soukromý klíč | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Obnovit soukromý klíč | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Sériová komunikace | Serial console over the Stream API | . | Ladící protokol API povolen | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Řízený režim | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Záloha klíčů | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Obnovit klíče | Write the backed-up keys back to the node (available once a backup exists) | . | Smazat zálohu klíče | Remove the stored key backup from this phone | . | Úroveň ochrany | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Zbývající počet restartů | How many device boots the unlocked state survives | . | Hodiny do vypršení platnosti | Wall-clock lifetime of the unlocked state | . | Limit relace (minuty) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/settings-radio-user.html#nastaven%C3%AD",
    
    "relUrl": "/cs-rCZ/user/settings-radio-user.html#nastavení"
  },"4491": {
    "doc": "Settings — Radio & User",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — optional feature modules and device administration | Signal Meter — how modem presets affect signal quality thresholds | LoRa configuration — detailed LoRa settings reference on meshtastic.org | Initial configuration — region setup guide on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/settings-radio-user.html#related-topics",
    
    "relUrl": "/cs-rCZ/user/settings-radio-user.html#related-topics"
  },"4492": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": " ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/settings-radio-user.html",
    
    "relUrl": "/cs-rCZ/user/settings-radio-user.html"
  },"4493": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/settings-radio-user.html#settings--radio--user",
    
    "relUrl": "/bg-rBG/user/settings-radio-user.html#settings--radio--user"
  },"4494": {
    "doc": "Settings — Radio & User",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Екранна снимка | . | Dropdown | | . | Toggle | | . | Slider | | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/bg-rBG/user/settings-radio-user.html#how-these-screens-work"
  },"4495": {
    "doc": "Settings — Radio & User",
    "title": "Потребителски настройки",
    "content": "User Profile . On Settings → User. | Настройка | Описание | . | Дълго име | Your display name (up to 39 characters) | . | Кратко име | 4-character abbreviated name | . | Status Message | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | Без съобщения | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/settings-radio-user.html#%D0%BF%D0%BE%D1%82%D1%80%D0%B5%D0%B1%D0%B8%D1%82%D0%B5%D0%BB%D1%81%D0%BA%D0%B8-%D0%BD%D0%B0%D1%81%D1%82%D1%80%D0%BE%D0%B9%D0%BA%D0%B8",
    
    "relUrl": "/bg-rBG/user/settings-radio-user.html#потребителски-настройки"
  },"4496": {
    "doc": "Settings — Radio & User",
    "title": "Конфигурация",
    "content": "Конфигуриране на устройството . On Settings → Device configuration → Device. | Настройка | Описание | По подразбиране | . | Роля на устройството | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Режим на препредаване | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Активиран | . | LED Heartbeat | Blink the status LED periodically | Активиран | . | Часова зона | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . Конфигуриране на LoRa . On Settings → LoRa. | Настройка | Описание | По подразбиране | . | Регион | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Предварително зададени | Speed/range tradeoff | LongFast | . | Брой отскоци | Maximum retransmit hops | 3 | . | Мощност на предаване | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Използване на предварително зададени настройки | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Широчина на честотната лента | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Честотен слот | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Предаването е активирано | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Игнориране на MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Диапазон | Скорост | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Конфигуриране на дисплея . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Настройка | Описание | . | Екранът е включен за | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Режим на дисплея | Screen layout/density used by the firmware | . | Показвани единици | Metric or Imperial on the node’s screen | . | Използване на 12ч формат | Show the node’s clock as 12-hour rather than 24-hour | . | Удебелен заглавен шрифт | Draw the screen’s heading text in bold | . | Обръщане на екрана | Rotate the display 180° for an inverted mounting | . | Тип на OLED | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Събуждане при докосване или движение | Light the screen when the node is tapped or moved | . | Ориентация на компаса | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Конфигуриране на позицията . On Settings → Device configuration → Position. | Настройка | Описание | . | Режим на GPS (физически хардуер) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Интервал на излъчване | How often the position is shared with the mesh | . | Интелигентна позиция | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Фиксирана позиция | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Конфигуриране на захранването . On Settings → Device configuration → Power. | Настройка | Описание | . | Активиране на енергоспестяващ режим | Let the node sleep aggressively between activity | . | Изключване при загуба на захранване | Power the device down after external power disappears | . | Продължителност на супер дълбок сън | How long the deepest sleep state lasts | . | Минимално време за събуждане | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | I2C адрес на батерията INA_2XX | Address of an external INA-series power sensor, if fitted | . Конфигуриране на мрежата . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Настройка | Описание | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Парола | Парола за мрежата | . | Ethernet е активиран | Use a wired connection on hardware that has one | . | Режим на IPv4 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP сървър | Time synchronization server | . | rsyslog сървър | Remote logging server | . Конфигуриране на Bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Настройка | Описание | . | Bluetooth е активиран | Enable/disable BLE radio | . | Режим на сдвояване | Fixed PIN, Random PIN, or No PIN | . | Фиксиран ПИН | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Конфигуриране на сигурността . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Настройка | Описание | . | Публичен ключ | Your node’s public key (read-only) | . | Администраторски ключ | Keys permitted to administer this node remotely — up to three | . | Частен ключ | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Регенериране на частния ключ | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Серийна конзола | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Управляем режим | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | Какво прави | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/settings-radio-user.html#%D0%BA%D0%BE%D0%BD%D1%84%D0%B8%D0%B3%D1%83%D1%80%D0%B0%D1%86%D0%B8%D1%8F",
    
    "relUrl": "/bg-rBG/user/settings-radio-user.html#конфигурация"
  },"4497": {
    "doc": "Settings — Radio & User",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — optional feature modules and device administration | Signal Meter — how modem presets affect signal quality thresholds | LoRa configuration — detailed LoRa settings reference on meshtastic.org | Initial configuration — region setup guide on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/settings-radio-user.html#related-topics",
    
    "relUrl": "/bg-rBG/user/settings-radio-user.html#related-topics"
  },"4498": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": " ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/settings-radio-user.html",
    
    "relUrl": "/bg-rBG/user/settings-radio-user.html"
  },"4499": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/settings-radio-user.html#settings--radio--user",
    
    "relUrl": "/ga-rIE/user/settings-radio-user.html#settings--radio--user"
  },"4500": {
    "doc": "Settings — Radio & User",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Screenshot | . | Dropdown | | . | Toggle | | . | Slider | | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/ga-rIE/user/settings-radio-user.html#how-these-screens-work"
  },"4501": {
    "doc": "Settings — Radio & User",
    "title": "User Settings",
    "content": "User Profile . On Settings → User. | Setting | Cur síos | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Status Message | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | Unmessageable | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/settings-radio-user.html#user-settings",
    
    "relUrl": "/ga-rIE/user/settings-radio-user.html#user-settings"
  },"4502": {
    "doc": "Settings — Radio & User",
    "title": "Configuration",
    "content": "Device Config . On Settings → Device configuration → Device. | Setting | Cur síos | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Cur síos | Default | . | Réigiún | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Cur síos | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Cur síos | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Cur síos | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Cur síos | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Config . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Cur síos | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Cur síos | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Private Key | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/settings-radio-user.html#configuration",
    
    "relUrl": "/ga-rIE/user/settings-radio-user.html#configuration"
  },"4503": {
    "doc": "Settings — Radio & User",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — optional feature modules and device administration | Signal Meter — how modem presets affect signal quality thresholds | LoRa configuration — detailed LoRa settings reference on meshtastic.org | Initial configuration — region setup guide on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/settings-radio-user.html#related-topics",
    
    "relUrl": "/ga-rIE/user/settings-radio-user.html#related-topics"
  },"4504": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": " ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/settings-radio-user.html",
    
    "relUrl": "/ga-rIE/user/settings-radio-user.html"
  },"4505": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/settings-radio-user.html#settings--radio--user",
    
    "relUrl": "/fr-rCA/user/settings-radio-user.html#settings--radio--user"
  },"4506": {
    "doc": "Settings — Radio & User",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Screenshot | . | Dropdown | | . | Toggle | | . | Slider | | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/fr-rCA/user/settings-radio-user.html#how-these-screens-work"
  },"4507": {
    "doc": "Settings — Radio & User",
    "title": "Paramètres utilisateur",
    "content": "User Profile . On Settings → User. | Setting | Description | . | Nom long | Your display name (up to 39 characters) | . | Nom court | 4-character abbreviated name | . | Statut du message | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | Non joignable par message | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/settings-radio-user.html#param%C3%A8tres-utilisateur",
    
    "relUrl": "/fr-rCA/user/settings-radio-user.html#paramètres-utilisateur"
  },"4508": {
    "doc": "Settings — Radio & User",
    "title": "Configuration",
    "content": "Configuration de l’appareil . On Settings → Device configuration → Device. | Setting | Description | Par défaut | . | Rôle de l’appareil | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Mode de réémission | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Intervalle de diffusion des infos nœud | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double clic comme appui sur le bouton | Treat a double tap as a button press | Désactivé | . | Triple clic pour faire un ping Ad Hoc | Send an ad-hoc position ping on a triple click | Activé | . | LED de vérification de fonctionnement (heartbeat) | Blink the status LED periodically | Activé | . | Fuseau horaire | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . Configuration LoRa . On Settings → LoRa. | Setting | Description | Par défaut | . | Région | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Préréglages | Speed/range tradeoff | LongFast | . | Nombre de sauts | Maximum retransmit hops | 3 | . | Puissance d’émission | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Remplacer la fréquence | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Utiliser un préréglage | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Facteur de propagation | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Taux de codage | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bande Passante | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Slot de fréquence | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmission activée | Turning this off makes the node receive-only | On | . | Autoriser le dépassement du temps d’émission autorisé par heure | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Éteint | . | Ignorer MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Transmission des paquets vers MQTT | Allow your packets to be forwarded to MQTT by gateways | Éteint | . | Gain RX Boosté | Extra receive gain on SX126x radios; costs a little current | Éteint | . | Ventilateur PA désactivé | Turn off the power-amplifier fan on hardware that has one | Éteint | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Vitesse | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Configuration de l’écran . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Description | . | Écran allumé pour | How long the display stays lit before sleeping | . | Intervalle du carrousel | How often the node cycles between screens on its own | . | Mode d’affichage | Screen layout/density used by the firmware | . | Unités d’affichage | Metric or Imperial on the node’s screen | . | Utiliser le format horaire 12h | Show the node’s clock as 12-hour rather than 24-hour | . | Titre en gras | Draw the screen’s heading text in bold | . | Inverser l’écran | Rotate the display 180° for an inverted mounting | . | Type d’OLED | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Réveil par appui ou mouvement | Light the screen when the node is tapped or moved | . | Orientation de la boussole | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Toujours pointer vers le nord | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Configuration de la position . On Settings → Device configuration → Position. | Setting | Description | . | Mode GPS (matériel physique) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | Fréquence de récupération GPS | How often the node asks its GPS for a fix | . | Intervalle de diffusion | How often the position is shared with the mesh | . | Position Intelligente | Broadcast based on movement rather than purely on the clock | . | Intervalle intelligent | With Smart Position on, the shortest gap between broadcasts | . | Distance intelligente | With Smart Position on, how far you must move before broadcasting | . | Position fixe | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Champs de position | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Configuration de l’alimentation . On Settings → Device configuration → Power. | Setting | Description | . | Activer le mode économie d’énergie | Let the node sleep aggressively between activity | . | Arrêt en cas de perte d’alimentation | Power the device down after external power disappears | . | Durée du sommeil extra profond | How long the deepest sleep state lasts | . | Durée minimale de réveil | The shortest time the node stays awake once woken | . | Durée d’attente max du Bluetooth | How long to wait for a phone to connect before sleeping | . | Remplacer le multiplicateur ADC | Turn on a manual correction for battery-voltage readings | . | Facteur de remplacement du multiplicateur ADC | The correction factor itself, used only when the override is on | . | Adresse I2C de la batterie INA_2XX | Address of an external INA-series power sensor, if fitted | . Configuration du réseau . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Description | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Mot de passe | Mot de passe du réseau | . | Ethernet activé | Use a wired connection on hardware that has one | . | Mode IPv4 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | Serveur NTP | Time synchronization server | . | Serveur Rsyslog | Remote logging server | . Configuration Bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Description | . | Bluetooth activé | Enable/disable BLE radio | . | Mode d’appariement | Fixed PIN, Random PIN, or No PIN | . | Code PIN fixe | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Configuration de sécurité . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Description | . | Clé publique | Your node’s public key (read-only) | . | Clé Admin | Keys permitted to administer this node remotely — up to three | . | Clé privée | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Régénérer la clé privée | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Console série | Serial console over the Stream API | . | API de journalisation de débogage activée | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Mode géré | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Sauvegarder les clés | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Heures jusqu’à expiration | Wall-clock lifetime of the unlocked state | . | Limite de sessions (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/settings-radio-user.html#configuration",
    
    "relUrl": "/fr-rCA/user/settings-radio-user.html#configuration"
  },"4509": {
    "doc": "Settings — Radio & User",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — optional feature modules and device administration | Signal Meter — how modem presets affect signal quality thresholds | LoRa configuration — detailed LoRa settings reference on meshtastic.org | Initial configuration — region setup guide on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/settings-radio-user.html#related-topics",
    
    "relUrl": "/fr-rCA/user/settings-radio-user.html#related-topics"
  },"4510": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": " ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/settings-radio-user.html",
    
    "relUrl": "/fr-rCA/user/settings-radio-user.html"
  },"4511": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/srp/user/settings-radio-user.html#settings--radio--user",
    
    "relUrl": "/srp/user/settings-radio-user.html#settings--radio--user"
  },"4512": {
    "doc": "Settings — Radio & User",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Screenshot | . | Dropdown | | . | Toggle | | . | Slider | | . ",
    "url": "/Meshtastic-Android/main/srp/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/srp/user/settings-radio-user.html#how-these-screens-work"
  },"4513": {
    "doc": "Settings — Radio & User",
    "title": "User Settings",
    "content": "User Profile . On Settings → User. | Setting | Опис | . | Дуго име | Your display name (up to 39 characters) | . | Кратко име | 4-character abbreviated name | . | Status Message | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | Unmessageable | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/srp/user/settings-radio-user.html#user-settings",
    
    "relUrl": "/srp/user/settings-radio-user.html#user-settings"
  },"4514": {
    "doc": "Settings — Radio & User",
    "title": "Configuration",
    "content": "Подешавања уређаја . On Settings → Device configuration → Device. | Setting | Опис | Подразумевано | . | Улога уређаја | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Режим реемитовања | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Интервал емитовања информација о чвору | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Двоструки додир као дугме | Treat a double tap as a button press | Онемогућено | . | Троструки клик за Ad Hoc пинг | Send an ad-hoc position ping on a triple click | Омогућено | . | LED срчани откуцаји | Blink the status LED periodically | Омогућено | . | Временска зона | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRA подешавања . On Settings → LoRa. | Setting | Опис | Подразумевано | . | Регион | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Унапред подешено | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Измена фреквенције | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Користи предефинисано подешавање | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Фактор ширења | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Стопа кодирања | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Проток | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Фреквенцијски слот | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Трансмитер укључен | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Искључен | . | Игнориши MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Позитиван за MQTT | Allow your packets to be forwarded to MQTT by gateways | Искључен | . | Појачање пријемника | Extra receive gain on SX126x radios; costs a little current | Искључен | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Искључен | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Брзина | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Подешавања приказа . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Опис | . | Екран укључен за | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Увек усмеравајте на север | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Подешавања позиције . On Settings → Device configuration → Position. | Setting | Опис | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Интервал емитовања | How often the position is shared with the mesh | . | Паметно позиционирање | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Фиксна локација | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Заставице позиције | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Подешавања напајња . On Settings → Device configuration → Power. | Setting | Опис | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Конфигурација мреже . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Опис | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Лозинка | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Блутут подешавања . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Опис | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Сигурносна подешавања . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Опис | . | Јавни кључ | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Приватни кључ | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/srp/user/settings-radio-user.html#configuration",
    
    "relUrl": "/srp/user/settings-radio-user.html#configuration"
  },"4515": {
    "doc": "Settings — Radio & User",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — optional feature modules and device administration | Signal Meter — how modem presets affect signal quality thresholds | LoRa configuration — detailed LoRa settings reference on meshtastic.org | Initial configuration — region setup guide on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/srp/user/settings-radio-user.html#related-topics",
    
    "relUrl": "/srp/user/settings-radio-user.html#related-topics"
  },"4516": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": " ",
    "url": "/Meshtastic-Android/main/srp/user/settings-radio-user.html",
    
    "relUrl": "/srp/user/settings-radio-user.html"
  },"4517": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/settings-radio-user.html#settings--radio--user",
    
    "relUrl": "/ca-rES/user/settings-radio-user.html#settings--radio--user"
  },"4518": {
    "doc": "Settings — Radio & User",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Screenshot | . | Dropdown | | . | Toggle | | . | Slider | | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/ca-rES/user/settings-radio-user.html#how-these-screens-work"
  },"4519": {
    "doc": "Settings — Radio & User",
    "title": "User Settings",
    "content": "User Profile . On Settings → User. | Setting | Descripció | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Status Message | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | Unmessageable | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/settings-radio-user.html#user-settings",
    
    "relUrl": "/ca-rES/user/settings-radio-user.html#user-settings"
  },"4520": {
    "doc": "Settings — Radio & User",
    "title": "Configuration",
    "content": "Device Config . On Settings → Device configuration → Device. | Setting | Descripció | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Descripció | Default | . | Regió | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Descripció | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Descripció | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Descripció | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Descripció | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Config . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Descripció | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Descripció | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Private Key | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/settings-radio-user.html#configuration",
    
    "relUrl": "/ca-rES/user/settings-radio-user.html#configuration"
  },"4521": {
    "doc": "Settings — Radio & User",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — optional feature modules and device administration | Signal Meter — how modem presets affect signal quality thresholds | LoRa configuration — detailed LoRa settings reference on meshtastic.org | Initial configuration — region setup guide on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/settings-radio-user.html#related-topics",
    
    "relUrl": "/ca-rES/user/settings-radio-user.html#related-topics"
  },"4522": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": " ",
    "url": "/Meshtastic-Android/main/ca-rES/user/settings-radio-user.html",
    
    "relUrl": "/ca-rES/user/settings-radio-user.html"
  },"4523": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/settings-radio-user.html#settings--radio--user",
    
    "relUrl": "/ko-rKR/user/settings-radio-user.html#settings--radio--user"
  },"4524": {
    "doc": "Settings — Radio & User",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Screenshot | . | Dropdown | | . | Toggle | | . | Slider | | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/ko-rKR/user/settings-radio-user.html#how-these-screens-work"
  },"4525": {
    "doc": "Settings — Radio & User",
    "title": "User Settings",
    "content": "User Profile . On Settings → User. | Setting | 설명 | . | 긴 이름 | Your display name (up to 39 characters) | . | 짧은 이름 | 4-character abbreviated name | . | Status Message | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | 메시지 제한 | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/settings-radio-user.html#user-settings",
    
    "relUrl": "/ko-rKR/user/settings-radio-user.html#user-settings"
  },"4526": {
    "doc": "Settings — Radio & User",
    "title": "설정",
    "content": "장치 설정 . On Settings → Device configuration → Device. | Setting | 설명 | 기본값 | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | 중계 모드 | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | 노드 정보 발송 주기 | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | 활성화 | . | LED Heartbeat | Blink the status LED periodically | 활성화 | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa 설정 . On Settings → LoRa. | Setting | 설명 | 기본값 | . | 지역 | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | 전송 출력 | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | 프리셋 사용 | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | 대역폭 | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | 주파수 슬롯 | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | 전송 활성화 | Turning this off makes the node receive-only | On | . | Duty Cycle 무시 | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | MQTT로 부터 수신 무시 | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan 비활성화됨 | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. 화면 설정 . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | 설명 | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | 디스플레이 모드 | Screen layout/density used by the firmware | . | 단위 표시 | Metric or Imperial on the node’s screen | . | 12시간제 보기 | Show the node’s clock as 12-hour rather than 24-hour | . | 상태표시줄 볼드체 | Draw the screen’s heading text in bold | . | 화면 뒤집기 | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | 나침반 방향 | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . 위치 설정 . On Settings → Device configuration → Position. | Setting | 설명 | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | 전송 간격 | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . 전원 설정 . On Settings → Device configuration → Power. | Setting | 설명 | . | 저전력 모드 설정 | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . 네트워크 설정 . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | 설명 | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | 비밀번호 | 네트워크 암호 | . | 이더넷 활성화 | Use a wired connection on hardware that has one | . | IPv4 모드 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP 서버 | Time synchronization server | . | rsyslog 서버 | Remote logging server | . 블루투스 설정 . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | 설명 | . | 블루투스 활성화 | Enable/disable BLE radio | . | 페어링 모드 | Fixed PIN, Random PIN, or No PIN | . | 고정 PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . 보안 설정 . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | 설명 | . | 공개 키 | Your node’s public key (read-only) | . | Admin 키 | Keys permitted to administer this node remotely — up to three | . | 개인 키 | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | 개인 키 다시 생성하기 | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | 시리얼 콘솔 | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | 관리 모드 | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/settings-radio-user.html#%EC%84%A4%EC%A0%95",
    
    "relUrl": "/ko-rKR/user/settings-radio-user.html#설정"
  },"4527": {
    "doc": "Settings — Radio & User",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — optional feature modules and device administration | Signal Meter — how modem presets affect signal quality thresholds | LoRa configuration — detailed LoRa settings reference on meshtastic.org | Initial configuration — region setup guide on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/settings-radio-user.html#related-topics",
    
    "relUrl": "/ko-rKR/user/settings-radio-user.html#related-topics"
  },"4528": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": " ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/settings-radio-user.html",
    
    "relUrl": "/ko-rKR/user/settings-radio-user.html"
  },"4529": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/settings-radio-user.html#settings--radio--user",
    
    "relUrl": "/sv-rSE/user/settings-radio-user.html#settings--radio--user"
  },"4530": {
    "doc": "Settings — Radio & User",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Screenshot | . | Dropdown | | . | Toggle | | . | Slider | | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/sv-rSE/user/settings-radio-user.html#how-these-screens-work"
  },"4531": {
    "doc": "Settings — Radio & User",
    "title": "Användarinställningar",
    "content": "User Profile . On Settings → User. | Setting | Beskrivning | . | Långt namn | Your display name (up to 39 characters) | . | Kort namn | 4-character abbreviated name | . | Statusmeddelande | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | Meddelanden läses ej | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/settings-radio-user.html#anv%C3%A4ndarinst%C3%A4llningar",
    
    "relUrl": "/sv-rSE/user/settings-radio-user.html#användarinställningar"
  },"4532": {
    "doc": "Settings — Radio & User",
    "title": "Konfiguration",
    "content": "Enhetskonfiguration . On Settings → Device configuration → Device. | Setting | Beskrivning | Förvald | . | Enhetens roll | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Återutsändningsläge | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Sändningsintervall för nod-info | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Dubbeltryck som knapptryck | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Aktiverad | . | LED pulsering | Blink the status LED periodically | Aktiverad | . | Tidszon | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Beskrivning | Förvald | . | Region | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Förval | Speed/range tradeoff | LongFast | . | Antal hopp | Maximum retransmit hops | 3 | . | Sändningseffekt | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Åsidosätt | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Använd förinställning | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spridningsfaktor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Kodningshastighet | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandbredd | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frekvens-slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Sändning aktiverad | Turning this off makes the node receive-only | On | . | Ersätt gräns för driftsperiod | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Av | . | Ignorera MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok till MQTT | Allow your packets to be forwarded to MQTT by gateways | Av | . | RX förstärkt gain | Extra receive gain on SX126x radios; costs a little current | Av | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Av | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Hastighet | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Beskrivning | . | Håll skärmen tänd | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Visningsläge | Screen layout/density used by the firmware | . | Visa enheter | Metric or Imperial on the node’s screen | . | Använd 12-timmarsformat | Show the node’s clock as 12-hour rather than 24-hour | . | Fetstil för rubriktext | Draw the screen’s heading text in bold | . | Vänd skärmen | Rotate the display 180° for an inverted mounting | . | OLED-typ | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Vakna vid tryck eller rörelse | Light the screen when the node is tapped or moved | . | Kompassriktning | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Peka alltid mot norr | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Beskrivning | . | GPS-läge (fysisk maskinvara) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | Intervall för hämtning av GPS-position | How often the node asks its GPS for a fix | . | Sändningsintervall | How often the position is shared with the mesh | . | Smart position | Broadcast based on movement rather than purely on the clock | . | Smart intervall | With Smart Position on, the shortest gap between broadcasts | . | Smart distans | With Smart Position on, how far you must move before broadcasting | . | Fast plats | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Positionsflaggor | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Ströminställningar . On Settings → Device configuration → Power. | Setting | Beskrivning | . | Aktivera strömsparläge | Let the node sleep aggressively between activity | . | Stäng av vid strömförlust | Power the device down after external power disappears | . | Tid för djup strömsparläge | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Vänta in Bluetooth (sekunder) | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Batteriets INA_2XX I2C-adress | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Beskrivning | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Lösenord | Nätverkslösenord | . | Ethernet är aktiverat | Use a wired connection on hardware that has one | . | IPv4-läge | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP-server | Time synchronization server | . | rsyslog-server | Remote logging server | . Bluetooth-inställningar . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Beskrivning | . | Bluetooth är aktiverad | Enable/disable BLE radio | . | Parkopplingsläge | Fixed PIN, Random PIN, or No PIN | . | Fast PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Beskrivning | . | Publik nyckel | Your node’s public key (read-only) | . | Admin-nyckel | Keys permitted to administer this node remotely — up to three | . | Privat nyckel | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Förnya nyckel | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Seriell konsol | Serial console over the Stream API | . | API för debugloggen igång | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Hanterat läge | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Säkerhetskopiera nycklar | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Skyddsnivå | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/settings-radio-user.html#konfiguration",
    
    "relUrl": "/sv-rSE/user/settings-radio-user.html#konfiguration"
  },"4533": {
    "doc": "Settings — Radio & User",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — optional feature modules and device administration | Signal Meter — how modem presets affect signal quality thresholds | LoRa configuration — detailed LoRa settings reference on meshtastic.org | Initial configuration — region setup guide on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/settings-radio-user.html#related-topics",
    
    "relUrl": "/sv-rSE/user/settings-radio-user.html#related-topics"
  },"4534": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": " ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/settings-radio-user.html",
    
    "relUrl": "/sv-rSE/user/settings-radio-user.html"
  },"4535": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/settings-radio-user.html#settings--radio--user",
    
    "relUrl": "/ht-rHT/user/settings-radio-user.html#settings--radio--user"
  },"4536": {
    "doc": "Settings — Radio & User",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Screenshot | . | Dropdown | | . | Toggle | | . | Slider | | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/ht-rHT/user/settings-radio-user.html#how-these-screens-work"
  },"4537": {
    "doc": "Settings — Radio & User",
    "title": "User Settings",
    "content": "User Profile . On Settings → User. | Setting | Deskripsyon | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Status Message | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | Unmessageable | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/settings-radio-user.html#user-settings",
    
    "relUrl": "/ht-rHT/user/settings-radio-user.html#user-settings"
  },"4538": {
    "doc": "Settings — Radio & User",
    "title": "Configuration",
    "content": "Device Config . On Settings → Device configuration → Device. | Setting | Deskripsyon | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Deskripsyon | Default | . | Rejyon | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Deskripsyon | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Deskripsyon | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Deskripsyon | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Deskripsyon | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Config . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Deskripsyon | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Deskripsyon | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Private Key | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/settings-radio-user.html#configuration",
    
    "relUrl": "/ht-rHT/user/settings-radio-user.html#configuration"
  },"4539": {
    "doc": "Settings — Radio & User",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — optional feature modules and device administration | Signal Meter — how modem presets affect signal quality thresholds | LoRa configuration — detailed LoRa settings reference on meshtastic.org | Initial configuration — region setup guide on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/settings-radio-user.html#related-topics",
    
    "relUrl": "/ht-rHT/user/settings-radio-user.html#related-topics"
  },"4540": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": " ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/settings-radio-user.html",
    
    "relUrl": "/ht-rHT/user/settings-radio-user.html"
  },"4541": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/settings-radio-user.html#settings--radio--user",
    
    "relUrl": "/sr-rLatn/user/settings-radio-user.html#settings--radio--user"
  },"4542": {
    "doc": "Settings — Radio & User",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Screenshot | . | Dropdown | | . | Toggle | | . | Slider | | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/sr-rLatn/user/settings-radio-user.html#how-these-screens-work"
  },"4543": {
    "doc": "Settings — Radio & User",
    "title": "User Settings",
    "content": "User Profile . On Settings → User. | Setting | Опис | . | Дуго име | Your display name (up to 39 characters) | . | Кратко име | 4-character abbreviated name | . | Status Message | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | Unmessageable | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/settings-radio-user.html#user-settings",
    
    "relUrl": "/sr-rLatn/user/settings-radio-user.html#user-settings"
  },"4544": {
    "doc": "Settings — Radio & User",
    "title": "Configuration",
    "content": "Подешавања уређаја . On Settings → Device configuration → Device. | Setting | Опис | Подразумевано | . | Улога уређаја | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Режим реемитовања | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Интервал емитовања информација о чвору | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Двоструки додир као дугме | Treat a double tap as a button press | Онемогућено | . | Троструки клик за Ad Hoc пинг | Send an ad-hoc position ping on a triple click | Омогућено | . | LED срчани откуцаји | Blink the status LED periodically | Омогућено | . | Временска зона | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRA подешавања . On Settings → LoRa. | Setting | Опис | Подразумевано | . | Регион | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Унапред подешено | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Измена фреквенције | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Користи предефинисано подешавање | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Фактор ширења | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Стопа кодирања | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Проток | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Фреквенцијски слот | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Трансмитер укључен | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Искључен | . | Игнориши MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Позитиван за MQTT | Allow your packets to be forwarded to MQTT by gateways | Искључен | . | Појачање пријемника | Extra receive gain on SX126x radios; costs a little current | Искључен | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Искључен | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Брзина | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Подешавања приказа . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Опис | . | Екран укључен за | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Увек усмеравајте на север | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Подешавања позиције . On Settings → Device configuration → Position. | Setting | Опис | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Интервал емитовања | How often the position is shared with the mesh | . | Паметно позиционирање | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Фиксна локација | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Заставице позиције | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Подешавања напајња . On Settings → Device configuration → Power. | Setting | Опис | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Конфигурација мреже . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Опис | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Лозинка | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Блутут подешавања . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Опис | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Сигурносна подешавања . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Опис | . | Javni ključ | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Privatni ključ | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/settings-radio-user.html#configuration",
    
    "relUrl": "/sr-rLatn/user/settings-radio-user.html#configuration"
  },"4545": {
    "doc": "Settings — Radio & User",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — optional feature modules and device administration | Signal Meter — how modem presets affect signal quality thresholds | LoRa configuration — detailed LoRa settings reference on meshtastic.org | Initial configuration — region setup guide on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/settings-radio-user.html#related-topics",
    
    "relUrl": "/sr-rLatn/user/settings-radio-user.html#related-topics"
  },"4546": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": " ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/settings-radio-user.html",
    
    "relUrl": "/sr-rLatn/user/settings-radio-user.html"
  },"4547": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/settings-radio-user.html#settings--radio--user",
    
    "relUrl": "/nl-rNL/user/settings-radio-user.html#settings--radio--user"
  },"4548": {
    "doc": "Settings — Radio & User",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Screenshot | . | Dropdown | | . | Toggle | | . | Slider | | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/nl-rNL/user/settings-radio-user.html#how-these-screens-work"
  },"4549": {
    "doc": "Settings — Radio & User",
    "title": "User Settings",
    "content": "User Profile . On Settings → User. | Setting | Beschrijving | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Status Message | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | Niet berichtbaar | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/settings-radio-user.html#user-settings",
    
    "relUrl": "/nl-rNL/user/settings-radio-user.html#user-settings"
  },"4550": {
    "doc": "Settings — Radio & User",
    "title": "Configuration",
    "content": "Apparaat Configuratie . On Settings → Device configuration → Device. | Setting | Beschrijving | Standaard | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Configuratie . On Settings → LoRa. | Setting | Beschrijving | Standaard | . | Regio | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandbreedte | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Overschrijf Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Negeer MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Weergave Configuratie . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Beschrijving | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Weergavemodus | Screen layout/density used by the firmware | . | Geef eenheden weer | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Scherm omdraaien | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Kompas oriëntatie | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Positie Configuratie . On Settings → Device configuration → Position. | Setting | Beschrijving | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Energie configuratie . On Settings → Device configuration → Power. | Setting | Beschrijving | . | Energiebesparingsmodus inschakelen | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Netwerkconfiguratie . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Beschrijving | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Wachtwoord | Network password | . | Ethernet ingeschakeld | Use a wired connection on hardware that has one | . | IPv4 modus | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Configuratie . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Beschrijving | . | Bluetooth ingeschakeld | Enable/disable BLE radio | . | Koppelmodus | Fixed PIN, Random PIN, or No PIN | . | Vaste PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Beveiligings Configuratie . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Beschrijving | . | Publieke sleutel | Your node’s public key (read-only) | . | Admin Sleutel | Keys permitted to administer this node remotely — up to three | . | Privésleutel | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Seriële console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Beheerde modus | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/settings-radio-user.html#configuration",
    
    "relUrl": "/nl-rNL/user/settings-radio-user.html#configuration"
  },"4551": {
    "doc": "Settings — Radio & User",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — optional feature modules and device administration | Signal Meter — how modem presets affect signal quality thresholds | LoRa configuration — detailed LoRa settings reference on meshtastic.org | Initial configuration — region setup guide on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/settings-radio-user.html#related-topics",
    
    "relUrl": "/nl-rNL/user/settings-radio-user.html#related-topics"
  },"4552": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": " ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/settings-radio-user.html",
    
    "relUrl": "/nl-rNL/user/settings-radio-user.html"
  },"4553": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/settings-radio-user.html#settings--radio--user",
    
    "relUrl": "/uk-rUA/user/settings-radio-user.html#settings--radio--user"
  },"4554": {
    "doc": "Settings — Radio & User",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Screenshot | . | Dropdown | | . | Toggle | | . | Slider | | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/uk-rUA/user/settings-radio-user.html#how-these-screens-work"
  },"4555": {
    "doc": "Settings — Radio & User",
    "title": "User Settings",
    "content": "User Profile . On Settings → User. | Setting | Опис | . | Довга назва | Your display name (up to 39 characters) | . | Коротка назва | 4-character abbreviated name | . | Статус повідомлення | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | Недоступний для повідомлень | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/settings-radio-user.html#user-settings",
    
    "relUrl": "/uk-rUA/user/settings-radio-user.html#user-settings"
  },"4556": {
    "doc": "Settings — Radio & User",
    "title": "Налаштування",
    "content": "Налаштування пристрою . On Settings → Device configuration → Device. | Setting | Опис | За замовчуванням | . | Роль пристрою | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Режим ретрансляції | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Інтервал розсилки даних про вузол | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Подвійний дотик як натискання кнопки | Treat a double tap as a button press | Disabled | . | Швидка перевірка зв’язку потрійним натисканням | Send an ad-hoc position ping on a triple click | Увімкнено | . | Частота мигання світлодіоду | Blink the status LED periodically | Увімкнено | . | Часовий пояс | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . Налаштування LoRa . On Settings → LoRa. | Setting | Опис | За замовчуванням | . | Регіон | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Пресети | Speed/range tradeoff | LongFast | . | К-ть стрибків | Maximum retransmit hops | 3 | . | Потужність передачі | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Перевизначити частоту | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Використовувати пресет | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Показник розширення сигналу | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Швидкість кодування | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Ширина смуги пропускання | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Слот частоти | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Передача активована | Turning this off makes the node receive-only | On | . | Ігнорувати обмеження завантаженості каналу | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ігнорувати MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | MQTT: Готово | Allow your packets to be forwarded to MQTT by gateways | Off | . | Підсилення передачі | Extra receive gain on SX126x radios; costs a little current | Off | . | Вентилятор вимкнений | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Швидкість | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Налаштування дисплею . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Опис | . | Екран включено для | How long the display stays lit before sleeping | . | Інтервал гортання каруселі | How often the node cycles between screens on its own | . | Режим екрану | Screen layout/density used by the firmware | . | Одиниці виміру | Metric or Imperial on the node’s screen | . | Використовувати 12-г формат часу | Show the node’s clock as 12-hour rather than 24-hour | . | Жирні заголовки | Draw the screen’s heading text in bold | . | Перевернути екран | Rotate the display 180° for an inverted mounting | . | Тип OLED | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Прокидання дотиком або рухом | Light the screen when the node is tapped or moved | . | Орієнтація компаса | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Завжди вказувати на північ | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Опис | . | Режим GPS (Фізичний пристрій) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | Інтервал опитування GPS | How often the node asks its GPS for a fix | . | Інтервал трансляції | How often the position is shared with the mesh | . | Інтелектуальне передавання позиції | Broadcast based on movement rather than purely on the clock | . | Інтелектуальний інтервал | With Smart Position on, the shortest gap between broadcasts | . | Інтелектуальна дистанція | With Smart Position on, how far you must move before broadcasting | . | Фіксована позиція | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Прапорці місцеположення | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Налаштування живлення . On Settings → Device configuration → Power. | Setting | Опис | . | Увімкнути енергоощадний режим | Let the node sleep aggressively between activity | . | Вимкнути при втраті живлення | Power the device down after external power disappears | . | Тривалість глибокого сну | How long the deepest sleep state lasts | . | Мінімальний час в робочому режимі | The shortest time the node stays awake once woken | . | Тривалість очікування Bluetooth | How long to wait for a phone to connect before sleeping | . | Корекція множника напруги | Turn on a manual correction for battery-voltage readings | . | Множник корекції напруги | The correction factor itself, used only when the override is on | . | I2C адреса INA_2XX батареї | Address of an external INA-series power sensor, if fitted | . Налаштування мережі . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Опис | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Пароль | Network password | . | Ethernet увімкнено | Use a wired connection on hardware that has one | . | Режим IPv4 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP-сервер | Time synchronization server | . | rsyslog-сервер | Remote logging server | . Налаштування Bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Опис | . | Bluetooth увімкнено | Enable/disable BLE radio | . | Режим створення пари | Fixed PIN, Random PIN, or No PIN | . | Фіксований PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Налаштування безпеки . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Опис | . | Відкритий ключ | Your node’s public key (read-only) | . | Ключ адміністратора | Keys permitted to administer this node remotely — up to three | . | Приватний ключ | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Згенерувати закритий ключ | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Серійна консоль | Serial console over the Stream API | . | API журналу відладки увімкнено | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Керований режим | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Резервні ключі | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/settings-radio-user.html#%D0%BD%D0%B0%D0%BB%D0%B0%D1%88%D1%82%D1%83%D0%B2%D0%B0%D0%BD%D0%BD%D1%8F",
    
    "relUrl": "/uk-rUA/user/settings-radio-user.html#налаштування"
  },"4557": {
    "doc": "Settings — Radio & User",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — optional feature modules and device administration | Signal Meter — how modem presets affect signal quality thresholds | LoRa configuration — detailed LoRa settings reference on meshtastic.org | Initial configuration — region setup guide on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/settings-radio-user.html#related-topics",
    
    "relUrl": "/uk-rUA/user/settings-radio-user.html#related-topics"
  },"4558": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": " ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/settings-radio-user.html",
    
    "relUrl": "/uk-rUA/user/settings-radio-user.html"
  },"4559": {
    "doc": "Asetukset — Radio ja käyttäjä",
    "title": "Asetukset — Radio ja käyttäjä",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/settings-radio-user.html",
    
    "relUrl": "/fi-rFI/user/settings-radio-user.html"
  },"4560": {
    "doc": "Asetukset — Radio ja käyttäjä",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Asetukset käyttävät tavallisia asetussäätimiä — pudotusvalikoita, kytkimiä ja liukusäätimiä: . | Säädin | Kuvakaappaus | . | Pudotusvalikko | | . | Kytkin | | . | Liukusäädin | | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/fi-rFI/user/settings-radio-user.html#how-these-screens-work"
  },"4561": {
    "doc": "Asetukset — Radio ja käyttäjä",
    "title": "Käyttäjäasetukset",
    "content": "Käyttäjäprofiili . On Settings → User. | Asetus | Kuvaus | . | Pitkä nimi | Näyttönimesi (enintään 39 merkkiä) | . | Lyhytnimi | 4-merkkinen lyhytnimi | . | Tilaviesti | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Edellyttää laiteohjelmistoversiota 2.8 tai uudempaa. Muussa tapauksessa tätä ei näytetä | . | Ei vastaanota viestejä | Merkitsee radion sellaiseksi, jolle kenenkään ei pitäisi yrittää lähettää viestejä – tarkoitettu valvomattomalle tai infrastruktuuriradiolle. Muut sovellukset piilottavat sen yhteystietoluettelosta. Edellyttää yhteensopivaa laiteohjelmistoa | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. Tilaviesti tallennetaan samalla Tallenna-painikkeella, mutta se ei koskaan käynnistä radiota uudelleen. Kuten muitakin tämän näkymän asetuksia, sitä voidaan muokata etähallittavassa radiossa. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/settings-radio-user.html#k%C3%A4ytt%C3%A4j%C3%A4asetukset",
    
    "relUrl": "/fi-rFI/user/settings-radio-user.html#käyttäjäasetukset"
  },"4562": {
    "doc": "Asetukset — Radio ja käyttäjä",
    "title": "Asetukset",
    "content": "Laitteen asetukset . On Settings → Device configuration → Device. | Asetus | Kuvaus | Oletus | . | Laitteen rooli | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Uudelleenlähetyksen tila | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Laitteen tietojen lähetyksen aikaväli | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Kaksoisnapautus painikkeena | Käsittele kaksoisnapautus painikkeen painalluksena | Ei käytössä | . | Kolmoisklikkaus Ad Hoc -pingille | Lähetä kertaluonteinen sijaintipyyntö kolminkertaisella painalluksella | Käytössä | . | Ledin valvontasignaali | Vilkuta tilan merkkilediä säännöllisesti | Käytössä | . | Aikavyöhyke | Laitteen kellon POSIX-aikavyöhyke. Painikkeilla voit kopioida puhelimesi aikavyöhykkeen tai tyhjentää kentän | — | . | Painikkeen / summerin GPIO | Lisäasetukset: GPIO-nastat, joihin painike ja summeri on kytketty | — | . LoRa:n asetukset . On Settings → LoRa. | Asetus | Kuvaus | Oletus | . | Alue | Taajuusalueen sääntelyalue. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Ei asetettu (on määritettävä) | . | Esiasetukset | Nopeuden ja kantaman välinen kompromissi | LongFast | . | Hyppyjen määrä | Suurin hyppyjen määrä | 3 | . | Lähetysteho | Lähetysteho (dBm): 0 = alueen sallima enimmäisteho | 0 (alueen enimmäisteho) | . | Taajuuden ohitus | Ohittaa lasketun käyttötaajuuden (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (käytä laskettua arvoa) | . | Käytä esiasetusta | Oletusarvoisesti käytössä. Poista tämä käytöstä, jos haluat määrittää hajotuskerroin-, koodausnopeus- ja kaistanleveysasetukset käsin modeemiesiasetuksen sijaan | Käytössä | . | Levennyskerroin (Spread Factor) | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | Esiasetuksesta | . | Koodausnopeus | Vain manuaalitilassa: 5–8. Suurempi virheenkorjaus lisää lähetysaikaa | Esiasetuksesta | . | Kaistanleveys | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | Esiasetuksesta | . | Taajuuspaikka | Määrittää, mitä alueen taajuusväliä käytetään. 0 muodostetaan ensisijaisen kanavan nimestä | 0 (automaattinen) | . | Lähetys käytössä | Tämän poistaminen käytöstä tekee radiosta vain vastaanottavan | Käytössä | . | Ohita käyttöaste (Duty Cycle) | Ohittaa alueen lähetysajan käyttörajoituksen. Laitonta useimmilla alueilla. Ota käyttöön vain, jos radioamatöörilupasi sallii sen | Pois | . | Ohita MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | MQTT päällä | Salli yhdyskäytävien välittää pakettisi MQTT:hen | Pois | . | RX tehostettu vahvistus | Lisävastaanottovahvistus SX126x-radioille. Kuluttaa hieman enemmän virtaa | Pois | . | PA tuuletin pois käytöstä | Poista päätevahvistimen tuuletin käytöstä laitteissa, joissa sellainen on | Pois | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Tärkeää: Käyttö väärällä alueasetuksella voi rikkoa paikallisia radiomääräyksiä. Katso alueasetusten määritysopas meshtastic.org-sivustolta saadaksesi lisätietoja. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Vinkki: SNR-raja-arvot ovat tarkoituksella negatiivisia. LoRa pystyy purkamaan signaaleja kohinatason alapuolelta, joten negatiivisempi raja tarkoittaa, että esiasetus sietää heikomman ja kohinaisemman signaalin (suurempi kantama). Katso Miten signaalimittari toimii saadaksesi täydellisen selityksen. | Esiasetus | Kantama | Nopeus | SNR-raja | Paras käyttöön | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Tiheä kaupunkiympäristö suoralla näköyhteydellä; paljon dataa siirtävät sovellukset | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Kaupunkialueet, rakennuksia muutaman korttelin säteellä | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Lyhyen kantaman esikaupunkialueet; kohtalainen rakennustiheys | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Esikaupunkialueet; kohtalainen rakennustiheys | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Esikaupunki-/maaseutualueet; kohtalainen kantama ja hitaampi nopeus | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Samankaltainen kantama kuin Long Fast -asetuksella, mutta 500 kHz:n kaistanleveydellä; suurempi tiedonsiirtonopeus | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | Yleiskäyttö (oletus) — tasapaino kantaman ja nopeuden välillä | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Maaseutualueet, joissa on jonkin verran maastonmuotoja; satunnainen käyttö | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD -alue (125 kHz BW); verrattavissa Medium Fast -asetukseen | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD -alue (125 kHz BW); verrattavissa Long Fast -asetukseen | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz -alue (62,5 kHz BW); välttää häiriöitä muiden laitteiden kanssa | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz -alue (62,5 kHz BW); verrattavissa Long Fast -asetukseen | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Vanhentunut — edelleen valittavissa, mutta voidaan poistaa tulevassa laiteohjelmistoversiossa | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Vanhentunut — edelleen valittavissa, mutta voidaan poistaa tulevassa laiteohjelmistoversiossa | . ℹ️ Huomautus: Tässä taulukossa käytetään yleisesti käytössä olevia lyhyitä nimiä. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . Modeemiesiasetus määrittää tärkeimmän kompromissin kantaman ja tiedonsiirtonopeuden välillä: . | Hitaammat esiasetukset käyttävät enemmän hajautusta, jolloin signaali voidaan purkaa heikommilla signaalitasoilla (alempi SNR-raja). Tämä tarkoittaa pidempää kantamaa, mutta vähemmän tavuja sekunnissa. | Nopeammat esiasetukset siirtävät enemmän dataa, mutta vaativat vahvemman signaalin purkamista varten. | . Käytännön ohje: . | Kaupunkiverkko (paljon radioita, lyhyet etäisyydet): Käytä Long Fast -asetusta (oletus) tai Short Fast -asetusta. Suurempi nopeus tarkoittaa vähemmän käyttöasteruuhkaa, kun monet radiot jakavat saman kanavan. | Maaseutu tai harva verkko (vähän radioita, pitkät etäisyydet): Käytä Long Moderate -asetusta. Kantama on tärkeämpi kuin nopeus, kun radiot ovat kaukana toisistaan. | EU 866/868 MHz -alueen säädösten noudattaminen: Käytä Lite Fast, Lite Slow, Narrow Fast tai Narrow Slow -asetuksia — ne on optimoitu EU:n SRD/868 MHz -alueille kapeammilla kaistanleveyksillä. | Kiinteät infrastruktuurilinkit: Käytä Short Turbo- tai Long Turbo -asetusta erillisille pisteestä pisteeseen -linkeille, joissa on hyvät antennit ja suora näköyhteys. | Sekaverkot: Pysy Long Fast -asetuksessa — se on yhteisön oletusasetus ja varmistaa yhteensopivuuden alueesi muiden käyttäjien kanssa. | . Kaikkien samalla kanavalla olevien radioiden on käytettävä samaa modeemiesiasetusta. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. Modeemiesiasetukset-taulukon kantama-arviot perustuvat tasaiseen maastoon ja vaatimattomiin antenneihin. Korkeuseroetu (mäki, rakennuksen katto) kasvattaa käytännön kantamaa huomattavasti. Hyvin sijoitettu Long Fast -asetusta käyttävä Router voi usein toimia paremmin kuin maan tasalla oleva Long Slow -asetusta käyttävä radio. Näytön asetukset . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Asetus | Kuvaus | . | Näytön päälläoloaika | Kuinka kauan näyttö pysyy päällä ennen siirtymistä lepotilaan | . | Karusellin aikaväli | How often the node cycles between screens on its own | . | Näyttötila | Laiteohjelmiston käyttämä näytön asettelu/tiheys | . | Näyttöyksiköt | Metric or Imperial on the node’s screen | . | Käytä 12 tunnin kelloa | Show the node’s clock as 12-hour rather than 24-hour | . | Lihavoitu otsikko | Näytä näytön otsikkoteksti lihavoituna | . | Käännä näyttö | Kierrä näyttö 180° ylösalaisin asennusta varten | . | OLED-tyyppi | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Herätä napautuksesta tai liikkeestä | Light the screen when the node is tapped or moved | . | Kompassin suuntaus | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Osoita aina pohjoiseen | Lukitsee kompassinäytön näyttämään pohjoiseen sen sijaan, että se kääntyisi kulkusuunnan mukaan. Riippumaton kompassin suunnasta — kumpikaan ei korvaa toista | . Sijainnin asetukset . On Settings → Device configuration → Position. | Asetus | Kuvaus | . | GPS-tila (fyysinen laitteisto) | Kolmitilainen: GPS käytössä, poistettu käytöstä tai ei käytettävissä. Ei pelkkä käytössä / poistettu käytöstä -asetus | . | GPS-kyselyn aikaväli | How often the node asks its GPS for a fix | . | Lähetyksen aikaväli | Kuinka usein sijainti jaetaan mesh-verkkoon | . | Älykäs sijainti | Lähettää sijainnin liikkeen perusteella pelkän aikavälin sijaan | . | Älykäs aikaväli | Älykäs sijainti -toiminnon ollessa käytössä lyhin sallittu aika sijaintilähetysten välillä | . | Älykäs etäisyys | Älykäs sijainti -toiminnon ollessa käytössä, kuinka pitkän matkan on liikuttava ennen sijainnin lähettämistä | . | Kiinteä sijainti | Käytä käsin syötettyä leveyspiiriä, pituuspiiriä ja korkeutta GPS:n sijaan | . | Sijaintimerkinnät | Asetusryhmä, jolla valitaan, mitkä tiedot liitetään sijaintiin — kuten korkeus, viitekehys, tarkkuus, näkyvissä olevat satelliitit, aikaleima ja muut tiedot | . | GPS EN / Vastaanotto / Lähetys GPIO | Lisäasetukset: nastat, joihin GPS-moduuli on kytketty | . Virran asetukset . On Settings → Device configuration → Power. | Asetus | Kuvaus | . | Ota virransäästötila käyttöön | Let the node sleep aggressively between activity | . | Sammuta virran katketessa | Sammuta laite, kun ulkoinen virta katkeaa | . | Super-syväunen kesto | Kuinka kauan syvin lepotila kestää | . | Vähimmäisherätyksen kesto | The shortest time the node stays awake once woken | . | Bluetoothin odotusaika | Kuinka kauan odotetaan puhelimen yhteyden muodostumista ennen lepotilaan siirtymistä | . | ADC-kertoimen ohitus | Ota akun jännitemittauksille käyttöön manuaalinen korjaus | . | Korvaava AD-muuntimen kerroin | Korjauskerroin, käytössä vain kun manuaalinen korjaus on käytössä | . | INA_2XX-akun valvontapiirin I2C-osoite | Ulkoisen INA-sarjan tehoanturin osoite, jos sellainen on asennettu | . Verkon asetukset . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Asetus | Kuvaus | . | WiFi käytössä | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Verkon nimi, johon yhdistetään. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Salasana | Verkon salasana | . | Ethernet käytössä | Käytä langallista yhteyttä sitä tukevalla laitteistolla | . | IPv4-tila | DHCP, or a static address configured with the four fields that follow | . | WiFi IP / Aliverkko / Yhdyskäytävä / DNS | Kiinteä IP-osoite, käytössä vain kun IPv4-tila on kiinteä | . | UDP-lähetys | Jaa mesh-verkon liikenne muiden radioiden kanssa lähiverkon kautta | . | NTP palvelin | Ajan synkronointipalvelin (NTP-palvelin) | . | rsyslog-palvelin | Etätietojen palvelin | . Bluetooth asetukset . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Asetus | Kuvaus | . | Bluetooth käytössä | Ota Bluetooth-radio käyttöön tai poista käytöstä | . | Paritustila | Kiinteä PIN-koodi, satunnainen PIN-koodi tai ei PIN-koodia | . | Kiinteä PIN-koodi | Pariliitoksen PIN-koodi. Siinä on oltava täsmälleen kuusi numeroa — kenttä hylkää kaikki muut arvot | . Turvallisuusasetukset . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Asetus | Kuvaus | . | Julkinen avain | Radiosi julkinen avain (vain luku) | . | Ylläpitäjän avain | Avaimet, joilla tätä radiota voidaan hallita etänä – enintään kolme | . | Yksityinen avain | Radiosi yksityinen avain (säilytä turvallisesti). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Luo uusi yksityinen avain | Luo tälle radiolle uuden avainparin vahvistuksen jälkeen. Kaikkien vanhan avaimesi tunteneiden vertaisradioiden on opittava uusi avain | . | Ylläpitokanava käytössä | ⚠️ Poistettu — määritetään nyt automaattisesti, kun ylläpitoavain asetetaan | . | Sarjaporttikonsoli | Serial console over the Stream API | . | Vianetsintälokirajapinta käytössä | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Hallintatila | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Voidaan valita vasta, kun järjestelmänvalvojan avain on määritetty | . | Varmuuskopioi avaimet | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Palauta avaimet | Kirjoita varmuuskopioidut avaimet takaisin radioon (käytettävissä, kun varmuuskopio on olemassa) | . | Poista avaimen varmuuskopio | Remove the stored key backup from this phone | . | Suojaustaso | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lukitustila . Lukitustila salaa laitteen tallennustilan ja edellyttää tunnuslausetta jokaiselle yhteydelle. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Tunnuslauseen lisäksi määrität rajat, joiden täyttyessä istunto päättyy automaattisesti: . | Kenttä | Mitä se tekee | . | Jäljellä olevat käynnistykset | Kuinka monen käynnistyksen ajan avattu tila säilyy | . | Tuntia vanhenemiseen saakka | Avatun tilan enimmäiskesto | . | Istunnon enimmäiskesto (minuuttia) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Kun lukitustila on käytössä, tässä lukee Aktiivinen – tallennustila salattu, tämä yhteys todennettu, kun yhteys on avattu, tai Aktiivinen – avaa tämä yhteys antamalla tunnuslause, kun sitä ei ole avattu. Lukitse nyt päättää nykyisen istunnon välittömästi. Toistuvat virheelliset tunnuslauseet rajoitetaan odotusajalla, ennen kuin voit yrittää uudelleen. ⚠️ Varoitus: Tunnuslausetta ei voi palauttaa. Jos kadotat sen, laite on tyhjennettävä sen palauttamiseksi, jolloin sen avaimet, kanavat ja asetukset poistuvat. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/settings-radio-user.html#asetukset",
    
    "relUrl": "/fi-rFI/user/settings-radio-user.html#asetukset"
  },"4563": {
    "doc": "Asetukset — Radio ja käyttäjä",
    "title": "Aiheeseen liittyvät aiheet",
    "content": ". | Asetukset — Moduulit ja ylläpito — valinnaiset ominaisuusmoduulit ja laitteen ylläpitotoiminnot | Signaalimittari — miten modeemiesiasetukset vaikuttavat signaalin laadun raja-arvoihin | LoRa-määritykset — yksityiskohtainen LoRa-asetusten viite meshtastic.org-sivustolla | Alkumääritykset — alueasetusten määritysopas meshtastic.org-sivustolla | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/settings-radio-user.html#aiheeseen-liittyv%C3%A4t-aiheet",
    
    "relUrl": "/fi-rFI/user/settings-radio-user.html#aiheeseen-liittyvät-aiheet"
  },"4564": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/settings-radio-user.html#settings--radio--user",
    
    "relUrl": "/is-rIS/user/settings-radio-user.html#settings--radio--user"
  },"4565": {
    "doc": "Settings — Radio & User",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Screenshot | . | Dropdown | | . | Toggle | | . | Slider | | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/is-rIS/user/settings-radio-user.html#how-these-screens-work"
  },"4566": {
    "doc": "Settings — Radio & User",
    "title": "User Settings",
    "content": "User Profile . On Settings → User. | Setting | Lýsing | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Status Message | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | Unmessageable | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/settings-radio-user.html#user-settings",
    
    "relUrl": "/is-rIS/user/settings-radio-user.html#user-settings"
  },"4567": {
    "doc": "Settings — Radio & User",
    "title": "Configuration",
    "content": "Device Config . On Settings → Device configuration → Device. | Setting | Lýsing | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Lýsing | Default | . | Svæði | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Lýsing | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Lýsing | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Lýsing | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Lýsing | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Config . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Lýsing | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Lýsing | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Private Key | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/settings-radio-user.html#configuration",
    
    "relUrl": "/is-rIS/user/settings-radio-user.html#configuration"
  },"4568": {
    "doc": "Settings — Radio & User",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — optional feature modules and device administration | Signal Meter — how modem presets affect signal quality thresholds | LoRa configuration — detailed LoRa settings reference on meshtastic.org | Initial configuration — region setup guide on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/settings-radio-user.html#related-topics",
    
    "relUrl": "/is-rIS/user/settings-radio-user.html#related-topics"
  },"4569": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": " ",
    "url": "/Meshtastic-Android/main/is-rIS/user/settings-radio-user.html",
    
    "relUrl": "/is-rIS/user/settings-radio-user.html"
  },"4570": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/settings-radio-user.html#settings--radio--user",
    
    "relUrl": "/lt-rLT/user/settings-radio-user.html#settings--radio--user"
  },"4571": {
    "doc": "Settings — Radio & User",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Screenshot | . | Dropdown | | . | Toggle | | . | Slider | | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/lt-rLT/user/settings-radio-user.html#how-these-screens-work"
  },"4572": {
    "doc": "Settings — Radio & User",
    "title": "User Settings",
    "content": "User Profile . On Settings → User. | Setting | Aprašymas | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Status Message | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | Unmessageable | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/settings-radio-user.html#user-settings",
    
    "relUrl": "/lt-rLT/user/settings-radio-user.html#user-settings"
  },"4573": {
    "doc": "Settings — Radio & User",
    "title": "Configuration",
    "content": "Device Config . On Settings → Device configuration → Device. | Setting | Aprašymas | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Aprašymas | Default | . | Regionas | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Aprašymas | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Aprašymas | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Aprašymas | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Aprašymas | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Config . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Aprašymas | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Aprašymas | . | Viešasis raktas | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Privatus raktas | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/settings-radio-user.html#configuration",
    
    "relUrl": "/lt-rLT/user/settings-radio-user.html#configuration"
  },"4574": {
    "doc": "Settings — Radio & User",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — optional feature modules and device administration | Signal Meter — how modem presets affect signal quality thresholds | LoRa configuration — detailed LoRa settings reference on meshtastic.org | Initial configuration — region setup guide on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/settings-radio-user.html#related-topics",
    
    "relUrl": "/lt-rLT/user/settings-radio-user.html#related-topics"
  },"4575": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": " ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/settings-radio-user.html",
    
    "relUrl": "/lt-rLT/user/settings-radio-user.html"
  },"4576": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/settings-radio-user.html#settings--radio--user",
    
    "relUrl": "/gl-rES/user/settings-radio-user.html#settings--radio--user"
  },"4577": {
    "doc": "Settings — Radio & User",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Screenshot | . | Dropdown | | . | Toggle | | . | Slider | | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/gl-rES/user/settings-radio-user.html#how-these-screens-work"
  },"4578": {
    "doc": "Settings — Radio & User",
    "title": "User Settings",
    "content": "User Profile . On Settings → User. | Setting | Descrición | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Status Message | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | Unmessageable | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/settings-radio-user.html#user-settings",
    
    "relUrl": "/gl-rES/user/settings-radio-user.html#user-settings"
  },"4579": {
    "doc": "Settings — Radio & User",
    "title": "Configuration",
    "content": "Device Config . On Settings → Device configuration → Device. | Setting | Descrición | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Descrición | Default | . | Rexión | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Descrición | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Descrición | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Descrición | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Descrición | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Config . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Descrición | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Descrición | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Private Key | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/settings-radio-user.html#configuration",
    
    "relUrl": "/gl-rES/user/settings-radio-user.html#configuration"
  },"4580": {
    "doc": "Settings — Radio & User",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — optional feature modules and device administration | Signal Meter — how modem presets affect signal quality thresholds | LoRa configuration — detailed LoRa settings reference on meshtastic.org | Initial configuration — region setup guide on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/settings-radio-user.html#related-topics",
    
    "relUrl": "/gl-rES/user/settings-radio-user.html#related-topics"
  },"4581": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": " ",
    "url": "/Meshtastic-Android/main/gl-rES/user/settings-radio-user.html",
    
    "relUrl": "/gl-rES/user/settings-radio-user.html"
  },"4582": {
    "doc": "設定：無線機とユーザー",
    "title": "設定：無線機とユーザー",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/settings-radio-user.html",
    
    "relUrl": "/ja-rJP/user/settings-radio-user.html"
  },"4583": {
    "doc": "設定：無線機とユーザー",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. 設定には、標準的な設定コントロール（ドロップダウン、トグル、スライダー）を使用します： . | コントロール | スクリーンショット | . | ドロップダウン | | . | トグル | | . | スライダー | | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/ja-rJP/user/settings-radio-user.html#how-these-screens-work"
  },"4584": {
    "doc": "設定：無線機とユーザー",
    "title": "ユーザー設定",
    "content": "ユーザープロファイル . On Settings → User. | 設定項目 | 説明 | . | 正式名称 | 表示名（最大 39 文字） | . | 短縮名 | 4 文字の短縮名 | . | ステータスメッセージ | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | メッセージ不可 | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/settings-radio-user.html#%E3%83%A6%E3%83%BC%E3%82%B6%E3%83%BC%E8%A8%AD%E5%AE%9A",
    
    "relUrl": "/ja-rJP/user/settings-radio-user.html#ユーザー設定"
  },"4585": {
    "doc": "設定：無線機とユーザー",
    "title": "設定",
    "content": "デバイスの設定 . On Settings → Device configuration → Device. | 設定項目 | 説明 | デフォルト | . | デバイスの役割 | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | 再ブロードキャストモード | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | ノード情報のブロードキャスト間隔 | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | ダブルタップをボタンとして使用 | Treat a double tap as a button press | 無効 | . | トリプルクリックでアドホック Ping | Send an ad-hoc position ping on a triple click | 有効 | . | LED ハートビート | Blink the status LED periodically | 有効 | . | タイムゾーン | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa設定 . On Settings → LoRa. | 設定項目 | 説明 | デフォルト | . | リージョン | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | 未設定（要設定） | . | プリセット | 速度と距離のトレードオフ | LongFast | . | ホップ数 | 再送信の最大ホップ数 | 3 | . | 送信出力 | 送信出力（dBm）。0 = リージョンで許可された最大値 | 0（リージョン最大） | . | 周波数の上書き | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | プリセットを使用 | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | 拡散率 | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | 符号化レート | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | 帯域 | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | 周波数スロット | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | 送信を有効化 | Turning this off makes the node receive-only | On | . | デューティサイクルを上書き | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | オフ | . | MQTT を無視 | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | MQTT への送信を許可 | Allow your packets to be forwarded to MQTT by gateways | オフ | . | RX ブーストゲイン | Extra receive gain on SX126x radios; costs a little current | オフ | . | PAファン無効 | Turn off the power-amplifier fan on hardware that has one | オフ | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. 詳しくは、meshtastic.org の リージョン設定ガイド を参照してください。 . Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 ヒント： SNR 限界の値は意図的に負の数になっています。 LoRa はノイズフロアを下回る信号でも復調できるため、より負の大きい限界値ほど、そのプリセットは弱くノイズの多い信号に耐えられます（より遠くまで届きます）。詳しい説明は、信号メーターの仕組み を参照してください。 . | プリセット | 距離 | 速度 | SNR 限界 | 最適な用途 | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | 見通しのある高密度な都市部。データ量の多い用途 | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | 都市の住宅街。数ブロック以内の建物 | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | 郊外の短距離。中程度の建物密度 | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | 郊外エリア。中程度の建物密度 | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | 郊外・地方。中程度の距離で低速 | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Long Fast と同程度の距離だが 500 kHz 帯域幅。スループットが速い | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | 一般用途（デフォルト）：距離と速度のバランスが良い | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | 起伏のある地方。ときどき使う用途 | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD 帯（125 kHz 帯域幅）。Medium Fast に相当 | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD 帯（125 kHz 帯域幅）。Long Fast に相当 | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz 帯（62.5 kHz 帯域幅）。他のデバイスとの干渉を避ける | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz 帯（62.5 kHz 帯域幅）。Long Fast に相当 | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ 非推奨：まだ選択できますが、将来のファームウェアリリースで削除される可能性があります | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ 非推奨：まだ選択できますが、将来のファームウェアリリースで削除される可能性があります | . ℹ️ 注意： この表では、一般的な短い名前を使用しています。 The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . モデムプリセットは、距離とデータ速度の基本的なトレードオフを制御します： . | 遅いプリセットは拡散をより多く使い、より弱い信号レベルでも復調できるようにします（SNR 限界が低い）。これは、より遠くまで届く一方で、1 秒あたりのバイト数が少ないことを意味します。 | 速いプリセットは 1 回の送信でより多くのデータを詰め込みますが、復調にはより強い信号が必要です。 | . 実用的な指針： . | 都市部のメッシュ（多数のノード、短距離）： Long Fast（デフォルト）または Short Fast を使用します。速度が速いほど、多くのノードがチャンネルを共有するときの電波利用時間の輻輳が減ります。 | 地方・まばらなメッシュ（少数のノード、長距離）： Long Moderate を使用します。ノードが離れている場合は、速度よりも距離が重要です。 | EU 866／868 MHz の規制対応： Lite Fast、Lite Slow、Narrow Fast、Narrow Slow を使用します。これらは、より狭い帯域幅で EU の SRD／868 MHz 帯に最適化されています。 | 固定インフラのリンク： 良好なアンテナと見通しがある専用のポイントツーポイントリンクには、Short Turbo または Long Turbo を使用します。 | 混在した環境： Long Fast のままにします。これはコミュニティのデフォルトで、地域内の他のユーザーとの互換性を確保します。 | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. 高所（丘の上、屋上）にあると、実効的な距離が大幅に伸びます。適切に設置された Long Fast のルーターは、地上に置かれた Long Slow のノードを上回ることがよくあります。 . 表示設定 . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | 設定項目 | 説明 | . | 画面オンの時間 | How long the display stays lit before sleeping | . | カルーセルの間隔 | How often the node cycles between screens on its own | . | 表示モード | Screen layout/density used by the firmware | . | 表示単位 | Metric or Imperial on the node’s screen | . | 12時間の時計形式を使用 | Show the node’s clock as 12-hour rather than 24-hour | . | 太字の見出し | Draw the screen’s heading text in bold | . | 画面反転 | Rotate the display 180° for an inverted mounting | . | OLED タイプ | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | タップまたは動作で起動 | Light the screen when the node is tapped or moved | . | コンパスの向き | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | 常に北を上にする | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . 位置情報設定 . On Settings → Device configuration → Position. | 設定項目 | 説明 | . | GPS モード（物理ハードウェア） | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS ポーリング間隔 | How often the node asks its GPS for a fix | . | ブロードキャスト間隔 | How often the position is shared with the mesh | . | スマート位置 | Broadcast based on movement rather than purely on the clock | . | スマート間隔 | With Smart Position on, the shortest gap between broadcasts | . | スマート距離 | With Smart Position on, how far you must move before broadcasting | . | 固定位置 | Use a manually entered latitude, longitude and altitude instead of the GPS | . | 位置情報フラグ | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . 電源設定 . On Settings → Device configuration → Power. | 設定項目 | 説明 | . | 省電力モードを有効化 | Let the node sleep aggressively between activity | . | 電源喪失時にシャットダウン | Power the device down after external power disappears | . | スーパーディープスリープの時間 | How long the deepest sleep state lasts | . | 最小起動時間 | The shortest time the node stays awake once woken | . | Bluetooth 待機時間 | How long to wait for a phone to connect before sleeping | . | ADC倍率のオーバーライド | Turn on a manual correction for battery-voltage readings | . | ADC倍率のオーバーライド比 | The correction factor itself, used only when the override is on | . | バッテリー INA_2XX I2C アドレス | Address of an external INA-series power sensor, if fitted | . ネットワーク設定 . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | 設定項目 | 説明 | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | パスワード | ネットワークのパスワード | . | イーサネット有効 | Use a wired connection on hardware that has one | . | IPv4 モード | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP ブロードキャスト | Share mesh traffic with other nodes over the local network | . | NTPサーバー | 時刻同期サーバー | . | rsyslogサーバー | リモートログサーバー | . Bluetooth 設定 . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | 設定項目 | 説明 | . | Bluetoothを有効 | BLE 無線の有効／無効 | . | ペアリングモード | 固定 PIN、ランダム PIN、または PIN なし | . | 固定 PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . セキュリティ設定 . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | 設定項目 | 説明 | . | 公開鍵 | ノードの公開鍵（読み取り専用） | . | 管理者鍵 | Keys permitted to administer this node remotely — up to three | . | 秘密鍵 | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | 秘密鍵を再生成 | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | 管理チャンネルを有効化 | ⚠️ 削除されました：管理者キーを設定すると自動的に構成されるようになりました | . | シリアルコンソール | Serial console over the Stream API | . | デバッグログAPIを有効化 | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | 管理モード | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | 鍵をバックアップ | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | 鍵を復元 | バックアップした鍵をノードに書き戻します（バックアップがある場合に利用可能） | . | 鍵のバックアップを削除 | Remove the stored key backup from this phone | . | 保護レベル | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | 内容 | . | 残りの起動回数 | How many device boots the unlocked state survives | . | 有効期限までの時間 | Wall-clock lifetime of the unlocked state | . | セッション上限（分） | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/settings-radio-user.html#%E8%A8%AD%E5%AE%9A",
    
    "relUrl": "/ja-rJP/user/settings-radio-user.html#設定"
  },"4586": {
    "doc": "設定：無線機とユーザー",
    "title": "関連トピック",
    "content": ". | 設定：モジュールと管理：オプションの機能モジュールとデバイスの管理 | 信号メーター：モデムプリセットが信号品質のしきい値に与える影響 | LoRa 設定：meshtastic.org にある詳細な LoRa 設定リファレンス | 初期設定：meshtastic.org にあるリージョン設定ガイド | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/settings-radio-user.html#%E9%96%A2%E9%80%A3%E3%83%88%E3%83%94%E3%83%83%E3%82%AF",
    
    "relUrl": "/ja-rJP/user/settings-radio-user.html#関連トピック"
  },"4587": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/settings-radio-user.html#settings--radio--user",
    
    "relUrl": "/de-rDE/user/settings-radio-user.html#settings--radio--user"
  },"4588": {
    "doc": "Settings — Radio & User",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Bildschirmfoto | . | Dropdown | | . | Toggle | | . | Slider | | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/de-rDE/user/settings-radio-user.html#how-these-screens-work"
  },"4589": {
    "doc": "Settings — Radio & User",
    "title": "Benutzereinstellungen",
    "content": "User Profile . On Settings → User. | Einstellung | Beschreibung | . | Langer Name | Your display name (up to 39 characters) | . | Kurzname | 4-character abbreviated name | . | Statusmeldung | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | Nicht erreichbar | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/settings-radio-user.html#benutzereinstellungen",
    
    "relUrl": "/de-rDE/user/settings-radio-user.html#benutzereinstellungen"
  },"4590": {
    "doc": "Settings — Radio & User",
    "title": "Einstellungen",
    "content": "Geräteeinstellungen . On Settings → Device configuration → Device. | Einstellung | Beschreibung | Standardwert | . | Geräterolle | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | ‘CLIENT’ | . | Weiterleitungsmodus | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Knoteninfo Übertragungsintervall | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Doppelklick als Taste | Treat a double tap as a button press | Deaktiviert | . | Dreifachklick für Ping | Send an ad-hoc position ping on a triple click | Aktiviert | . | Puls LED | Blink the status LED periodically | Aktiviert | . | Zeitzone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Einstellungen . On Settings → LoRa. | Einstellung | Beschreibung | Standardwert | . | Region | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Voreinstellungen | Speed/range tradeoff | LongFast | . | Anzahl der Weiterleitungen | Maximum retransmit hops | 3 | . | Sendeleistung | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequenz überschreiben | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Voreinstellung verwenden | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spreizfaktor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Fehlerkorrektur | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandbreite | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequenzschlitz | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Senden aktiviert | Turning this off makes the node receive-only | On | . | Duty-Cycle überschreiben | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Aus | . | MQTT ignorieren | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | OK für MQTT | Allow your packets to be forwarded to MQTT by gateways | Aus | . | Empfangsverstärkung | Extra receive gain on SX126x radios; costs a little current | Aus | . | PA Fan deaktiviert | Turn off the power-amplifier fan on hardware that has one | Aus | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Bereich | Geschwindigkeit | SNR Limit | Best For | . | SHORT_TURBO | ~1 km | 21.9 kbps | −7,5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6,25 kbit/s | −10 dB | Suburban short-range; moderate building density | . | MEDIUM_FAST | ~5 km | 3,52 kbit/s | −12.5 dB | Suburban areas; moderate building density | . | MEDIUM_SLOW | ~8 km | 1,95 kbit/s | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0,34 kbit/s | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7,5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12,5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7,5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0,18 kbit/s | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | Einhaltung der EU-Vorschriften für 866/868 MHz: Verwenden Sie Lite Fast, Lite Slow, Narrow Fast oder Narrow Slow – diese sind für die EU-SRD-/868-MHz-Bänder mit geringerer Bandbreite optimiert. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Anzeigeeinstellungen . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Einstellung | Beschreibung | . | Bildschirm eingeschaltet für | How long the display stays lit before sleeping | . | Karussellintervall | How often the node cycles between screens on its own | . | Anzeigemodus | Screen layout/density used by the firmware | . | Anzeigeeinheiten | Metric or Imperial on the node’s screen | . | 12h Uhrformat verwenden | Show the node’s clock as 12-hour rather than 24-hour | . | Fette Überschrift | Draw the screen’s heading text in bold | . | Bildschirm spiegeln | Rotate the display 180° for an inverted mounting | . | OLED Typ | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Aufwachen durch Tippen oder Bewegung | Light the screen when the node is tapped or moved | . | Kompassausrichtung | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Immer nach Norden zeigen | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Standorteinstellungen . On Settings → Device configuration → Position. | Einstellung | Beschreibung | . | GPS-Chip (Hardware) Modus | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Abfrageintervall | How often the node asks its GPS for a fix | . | Übertragungsintervall | How often the position is shared with the mesh | . | Intelligente Position | Broadcast based on movement rather than purely on the clock | . | Intelligentes Intervall | With Smart Position on, the shortest gap between broadcasts | . | Intelligente Entfernung | With Smart Position on, how far you must move before broadcasting | . | Fester Standort | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Standort Optionen | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Energie Einstellungen . On Settings → Device configuration → Power. | Einstellung | Beschreibung | . | Energiesparmodus aktivieren | Let the node sleep aggressively between activity | . | Herunterfahren bei Stromausfall | Power the device down after external power disappears | . | Dauer Supertiefschlaf | How long the deepest sleep state lasts | . | Minimale Aufwachzeit | The shortest time the node stays awake once woken | . | Zeit für Warten auf Bluetooth | How long to wait for a phone to connect before sleeping | . | ADC Multiplikationsfaktor | Turn on a manual correction for battery-voltage readings | . | ADC Multiplikator Überschreibungsverhältnis | The correction factor itself, used only when the override is on | . | Akku INA_2XX I2C Adresse | Address of an external INA-series power sensor, if fitted | . Netzwerkeinstellungen . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Einstellung | Beschreibung | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Passwort | Netzwerkpasswort | . | Ethernet aktiviert | Use a wired connection on hardware that has one | . | IPv4 Modus | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP Übertragung | Share mesh traffic with other nodes over the local network | . | NTP Server | Time synchronization server | . | rsyslog Server | Remote logging server | . Bluetooth Einstellungen . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Einstellung | Beschreibung | . | Bluetooth aktiviert | Enable/disable BLE radio | . | Kopplungsmodus | Fixed PIN, Random PIN, or No PIN | . | Feste PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Sicherheitseinstellungen . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Einstellung | Beschreibung | . | Öffentlicher Schlüssel | Your node’s public key (read-only) | . | Administrativer Schlüssel | Keys permitted to administer this node remotely — up to three | . | Privater Schlüssel | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Privaten Schlüssel neu erstellen | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serielle Konsole | Serial console over the Stream API | . | Debug-Protokoll-API aktiviert | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Verwalteter Modus | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Schlüssel sichern | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Schutzstufe | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Stunden bis zum Ablauf | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/settings-radio-user.html#einstellungen",
    
    "relUrl": "/de-rDE/user/settings-radio-user.html#einstellungen"
  },"4591": {
    "doc": "Settings — Radio & User",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — optional feature modules and device administration | Signal Meter — how modem presets affect signal quality thresholds | LoRa configuration — detailed LoRa settings reference on meshtastic.org | Initial configuration — region setup guide on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/settings-radio-user.html#related-topics",
    
    "relUrl": "/de-rDE/user/settings-radio-user.html#related-topics"
  },"4592": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": " ",
    "url": "/Meshtastic-Android/main/de-rDE/user/settings-radio-user.html",
    
    "relUrl": "/de-rDE/user/settings-radio-user.html"
  },"4593": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/settings-radio-user.html#settings--radio--user",
    
    "relUrl": "/ar-rSA/user/settings-radio-user.html#settings--radio--user"
  },"4594": {
    "doc": "Settings — Radio & User",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Screenshot | . | Dropdown | | . | Toggle | | . | Slider | | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/ar-rSA/user/settings-radio-user.html#how-these-screens-work"
  },"4595": {
    "doc": "Settings — Radio & User",
    "title": "User Settings",
    "content": "User Profile . On Settings → User. | Setting | الوصف | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Status Message | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | Unmessageable | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/settings-radio-user.html#user-settings",
    
    "relUrl": "/ar-rSA/user/settings-radio-user.html#user-settings"
  },"4596": {
    "doc": "Settings — Radio & User",
    "title": "Configuration",
    "content": "Device Config . On Settings → Device configuration → Device. | Setting | الوصف | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | الوصف | Default | . | الجهة | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | الوصف | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | الوصف | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | الوصف | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | الوصف | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Config . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | الوصف | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | الوصف | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Private Key | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/settings-radio-user.html#configuration",
    
    "relUrl": "/ar-rSA/user/settings-radio-user.html#configuration"
  },"4597": {
    "doc": "Settings — Radio & User",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — optional feature modules and device administration | Signal Meter — how modem presets affect signal quality thresholds | LoRa configuration — detailed LoRa settings reference on meshtastic.org | Initial configuration — region setup guide on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/settings-radio-user.html#related-topics",
    
    "relUrl": "/ar-rSA/user/settings-radio-user.html#related-topics"
  },"4598": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": " ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/settings-radio-user.html",
    
    "relUrl": "/ar-rSA/user/settings-radio-user.html"
  },"4599": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/settings-radio-user.html#settings--radio--user",
    
    "relUrl": "/hr-rHR/user/settings-radio-user.html#settings--radio--user"
  },"4600": {
    "doc": "Settings — Radio & User",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Screenshot | . | Dropdown | | . | Toggle | | . | Slider | | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/hr-rHR/user/settings-radio-user.html#how-these-screens-work"
  },"4601": {
    "doc": "Settings — Radio & User",
    "title": "User Settings",
    "content": "User Profile . On Settings → User. | Setting | Opis | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Status Message | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | Unmessageable | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/settings-radio-user.html#user-settings",
    
    "relUrl": "/hr-rHR/user/settings-radio-user.html#user-settings"
  },"4602": {
    "doc": "Settings — Radio & User",
    "title": "Configuration",
    "content": "Device Config . On Settings → Device configuration → Device. | Setting | Opis | Zadano | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Opis | Zadano | . | Regija | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Opis | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Opis | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Opis | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Opis | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Postavke Bluetootha . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Opis | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Opis | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Private Key | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/settings-radio-user.html#configuration",
    
    "relUrl": "/hr-rHR/user/settings-radio-user.html#configuration"
  },"4603": {
    "doc": "Settings — Radio & User",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — optional feature modules and device administration | Signal Meter — how modem presets affect signal quality thresholds | LoRa configuration — detailed LoRa settings reference on meshtastic.org | Initial configuration — region setup guide on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/settings-radio-user.html#related-topics",
    
    "relUrl": "/hr-rHR/user/settings-radio-user.html#related-topics"
  },"4604": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": " ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/settings-radio-user.html",
    
    "relUrl": "/hr-rHR/user/settings-radio-user.html"
  },"4605": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/settings-radio-user.html#settings--radio--user",
    
    "relUrl": "/pt-rPT/user/settings-radio-user.html#settings--radio--user"
  },"4606": {
    "doc": "Settings — Radio & User",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Screenshot | . | Dropdown | | . | Toggle | | . | Slider | | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/pt-rPT/user/settings-radio-user.html#how-these-screens-work"
  },"4607": {
    "doc": "Settings — Radio & User",
    "title": "User Settings",
    "content": "User Profile . On Settings → User. | Setting | Descrição | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Status Message | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | Impossível enviar mensagens | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/settings-radio-user.html#user-settings",
    
    "relUrl": "/pt-rPT/user/settings-radio-user.html#user-settings"
  },"4608": {
    "doc": "Settings — Radio & User",
    "title": "Configuração",
    "content": "Configuração do Dispositivo . On Settings → Device configuration → Device. | Setting | Descrição | Predefinição | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . Configuração de LoRa . On Settings → LoRa. | Setting | Descrição | Predefinição | . | Região | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Largura de banda | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Ignorar ciclo de trabalho | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignorar MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Configuração do Ecrã . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Descrição | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Modo de visualização | Screen layout/density used by the firmware | . | Unidade de visualização | Metric or Imperial on the node’s screen | . | Usar formato de relógio 12h | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Inverter ecrã | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Orientação da bússola | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Configuração da posição . On Settings → Device configuration → Position. | Setting | Descrição | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Intervalo de difusão | How often the position is shared with the mesh | . | Posição Inteligente | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Posição fixa | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Configuração de Energia . On Settings → Device configuration → Power. | Setting | Descrição | . | Ativar modo de poupança de energia | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | Alterar rácio do multiplicador ADC | The correction factor itself, used only when the override is on | . | Endereço I2C da bateria INA_2XX | Address of an external INA-series power sensor, if fitted | . Configuração de Rede . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Descrição | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Palavra-passe | Network password | . | Ethernet ativada | Use a wired connection on hardware that has one | . | Modo IPv4 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | Servidor NTP | Time synchronization server | . | servidor rsyslog | Remote logging server | . Configuração de Bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Descrição | . | Bluetooth ativado | Enable/disable BLE radio | . | Modo de emparelhamento | Fixed PIN, Random PIN, or No PIN | . | PIN fixo | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Configuração de Segurança . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Descrição | . | Chave pública | Your node’s public key (read-only) | . | Chave do Administrador | Keys permitted to administer this node remotely — up to three | . | Chave privada | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Consola de série | Serial console over the Stream API | . | API de histórico de depuração ativada | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Modo Administrado | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/settings-radio-user.html#configura%C3%A7%C3%A3o",
    
    "relUrl": "/pt-rPT/user/settings-radio-user.html#configuração"
  },"4609": {
    "doc": "Settings — Radio & User",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — optional feature modules and device administration | Signal Meter — how modem presets affect signal quality thresholds | LoRa configuration — detailed LoRa settings reference on meshtastic.org | Initial configuration — region setup guide on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/settings-radio-user.html#related-topics",
    
    "relUrl": "/pt-rPT/user/settings-radio-user.html#related-topics"
  },"4610": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": " ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/settings-radio-user.html",
    
    "relUrl": "/pt-rPT/user/settings-radio-user.html"
  },"4611": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/settings-radio-user.html#settings--radio--user",
    
    "relUrl": "/pl-rPL/user/settings-radio-user.html#settings--radio--user"
  },"4612": {
    "doc": "Settings — Radio & User",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Screenshot | . | Dropdown | | . | Toggle | | . | Slider | | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/pl-rPL/user/settings-radio-user.html#how-these-screens-work"
  },"4613": {
    "doc": "Settings — Radio & User",
    "title": "User Settings",
    "content": "User Profile . On Settings → User. | Setting | Opis | . | Długa nazwa | Your display name (up to 39 characters) | . | Krótka nazwa | 4-character abbreviated name | . | Status Message | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | Nie przyjmuje wiadomości | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/settings-radio-user.html#user-settings",
    
    "relUrl": "/pl-rPL/user/settings-radio-user.html#user-settings"
  },"4614": {
    "doc": "Settings — Radio & User",
    "title": "Konfiguracja",
    "content": "Konfiguracja urządzenia . On Settings → Device configuration → Device. | Setting | Opis | Domyślny | . | Rola urządzenia | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Tryb retransmisji | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Interwał transmisji informacji o węźle | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Podwójne dotknięcie jako naciśnięcie przycisku | Treat a double tap as a button press | Wyłączony | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Włączony | . | LED bicia serca | Blink the status LED periodically | Włączony | . | Strefa czasowa | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . Konfiguracja LoRa . On Settings → LoRa. | Setting | Opis | Domyślny | . | Region | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presety | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Moc nadawania | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Użyj predefiniowanych ustawień | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Szybkość kodowania | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Pasmo | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Slot częstotliwości | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmisja włączona | Turning this off makes the node receive-only | On | . | Nadpisz cykl pracy | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Wyłączony | . | Zignoruj MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok dla MQTT | Allow your packets to be forwarded to MQTT by gateways | Wyłączony | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Wyłączony | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Wyłączony | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Prędkość | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Konfiguracja wyświetlacza . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Opis | . | Ekran włączony na | How long the display stays lit before sleeping | . | Interwał karuzeli | How often the node cycles between screens on its own | . | Tryb wyświetlania | Screen layout/density used by the firmware | . | Wyświetlana jednostka | Metric or Imperial on the node’s screen | . | Użyj formatu 12-godzinnego | Show the node’s clock as 12-hour rather than 24-hour | . | Pogrubiony nagłówek | Draw the screen’s heading text in bold | . | Odwróć ekran | Rotate the display 180° for an inverted mounting | . | Typ ekranu OLED | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wybudź przy dotknięciu lub ruchu | Light the screen when the node is tapped or moved | . | Orientacja kompasu | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Zawsze wskazywać na północ | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Konfiguracja pozycjonowania . On Settings → Device configuration → Position. | Setting | Opis | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Interwał transmisji | How often the position is shared with the mesh | . | Inteligentne Pozycjonowanie | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Położenie stałe | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Flagi położenia | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Konfiguracja zarządzania energią . On Settings → Device configuration → Power. | Setting | Opis | . | Włącz tryb oszczędzania energii | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Konfiguracja sieci . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Opis | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Hasło | Hasło do sieci | . | Ethernet włączony | Use a wired connection on hardware that has one | . | Tryb IPv4 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | Serwer NTP | Time synchronization server | . | Serwer rsyslog | Remote logging server | . Konfiguracja Bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Opis | . | Bluetooth włączony | Enable/disable BLE radio | . | Tryb parowania | Fixed PIN, Random PIN, or No PIN | . | Stały PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Konfiguracja zabezpieczeń . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Opis | . | Klucz publiczny | Your node’s public key (read-only) | . | Klucz administratora | Keys permitted to administer this node remotely — up to three | . | Klucz prywatny | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Klucze zapasowe | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/settings-radio-user.html#konfiguracja",
    
    "relUrl": "/pl-rPL/user/settings-radio-user.html#konfiguracja"
  },"4615": {
    "doc": "Settings — Radio & User",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — optional feature modules and device administration | Signal Meter — how modem presets affect signal quality thresholds | LoRa configuration — detailed LoRa settings reference on meshtastic.org | Initial configuration — region setup guide on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/settings-radio-user.html#related-topics",
    
    "relUrl": "/pl-rPL/user/settings-radio-user.html#related-topics"
  },"4616": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": " ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/settings-radio-user.html",
    
    "relUrl": "/pl-rPL/user/settings-radio-user.html"
  },"4617": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/settings-radio-user.html#settings--radio--user",
    
    "relUrl": "/zh-rCN/user/settings-radio-user.html#settings--radio--user"
  },"4618": {
    "doc": "Settings — Radio & User",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Screenshot | . | Dropdown | | . | Toggle | | . | Slider | | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/zh-rCN/user/settings-radio-user.html#how-these-screens-work"
  },"4619": {
    "doc": "Settings — Radio & User",
    "title": "用户设置",
    "content": "User Profile . On Settings → User. | Setting | 说明 | . | 长名称 | Your display name (up to 39 characters) | . | 短名称 | 4-character abbreviated name | . | 状态消息 | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | 无法发送消息 | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/settings-radio-user.html#%E7%94%A8%E6%88%B7%E8%AE%BE%E7%BD%AE",
    
    "relUrl": "/zh-rCN/user/settings-radio-user.html#用户设置"
  },"4620": {
    "doc": "Settings — Radio & User",
    "title": "Configuration",
    "content": "设备配置 . On Settings → Device configuration → Device. | Setting | 说明 | 默认 | . | 设备角色 | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | 转播模式 | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | 节点信息广播间隔 | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | 双击作为按钮 | Treat a double tap as a button press | 禁用 | . | 快速按3下 向所有节点发送紧急广播 | Send an ad-hoc position ping on a triple click | Enabled | . | LED 心跳 | Blink the status LED periodically | Enabled | . | 时区 | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa 配置 . On Settings → LoRa. | Setting | 说明 | 默认 | . | 区域 | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | 预设 | Speed/range tradeoff | LongFast | . | 节点数 | Maximum retransmit hops | 3 | . | 发送强度 | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | 频率覆盖 | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | 使用预设 | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | 扩散因子 | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | 编码率 | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | 带宽 | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | 频率时隙 | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | 启用传输 | Turning this off makes the node receive-only | On | . | 覆盖占空比 | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | 关闭 | . | 忽略 MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | 使用MQTT | Allow your packets to be forwarded to MQTT by gateways | 关闭 | . | RX 增益 | Extra receive gain on SX126x radios; costs a little current | 关闭 | . | PA风扇已禁用 | Turn off the power-amplifier fan on hardware that has one | 关闭 | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | 速度 | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. 屏幕配置 . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | 说明 | . | 开启屏幕 | How long the display stays lit before sleeping | . | 轮播间隔 | How often the node cycles between screens on its own | . | 显示模式 | Screen layout/density used by the firmware | . | 显示单位 | Metric or Imperial on the node’s screen | . | 使用 12 小时制格式 | Show the node’s clock as 12-hour rather than 24-hour | . | 加粗标题 | Draw the screen’s heading text in bold | . | 翻转屏幕 | Rotate the display 180° for an inverted mounting | . | OLED 类型 | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | 点击或移动时唤醒屏幕 | Light the screen when the node is tapped or moved | . | 罗盘方向 | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | 总是朝北 | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . 定位配置 . On Settings → Device configuration → Position. | Setting | 说明 | . | GPS 模式 (物理硬件) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS 轮询间隔 | How often the node asks its GPS for a fix | . | 广播间隔 | How often the position is shared with the mesh | . | 智能位置 | Broadcast based on movement rather than purely on the clock | . | 自动时间间隔 | With Smart Position on, the shortest gap between broadcasts | . | 自动距离大小 | With Smart Position on, how far you must move before broadcasting | . | 固定位置 | Use a manually entered latitude, longitude and altitude instead of the GPS | . | 位置信息数据包 | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . 电源配置 . On Settings → Device configuration → Power. | Setting | 说明 | . | 启用节能模式 | Let the node sleep aggressively between activity | . | 断电时关机 | Power the device down after external power disappears | . | 深度睡眠时间 | How long the deepest sleep state lasts | . | 最小唤醒时间 | The shortest time the node stays awake once woken | . | 等待蓝牙持续时间 | How long to wait for a phone to connect before sleeping | . | ADC 倍数覆盖 | Turn on a manual correction for battery-voltage readings | . | ADC乘数修正比率 | The correction factor itself, used only when the override is on | . | 电池INA_2XX I2C 地址 | Address of an external INA-series power sensor, if fitted | . 网络配置 . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | 说明 | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | 密码 | 网络密码 | . | 启用以太网 | Use a wired connection on hardware that has one | . | IPv4模式 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP 广播 | Share mesh traffic with other nodes over the local network | . | NTP 服务器 | Time synchronization server | . | rsyslog 服务器 | Remote logging server | . 蓝牙配置 . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | 说明 | . | 启用蓝牙 | Enable/disable BLE radio | . | 配对模式 | Fixed PIN, Random PIN, or No PIN | . | 固定PIN码 | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . 安全配置 . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | 说明 | . | 公钥 | Your node’s public key (read-only) | . | 管理员密钥 | Keys permitted to administer this node remotely — up to three | . | 私钥 | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | 重新生成私钥 | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | 串口控制 | Serial console over the Stream API | . | 启用调试日志 API | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | 管理模式 | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | 备份密钥 | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | 恢复密钥 | Write the backed-up keys back to the node (available once a backup exists) | . | 删除密钥备份 | Remove the stored key backup from this phone | . | 安全等级 | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | 剩余启动次数 | How many device boots the unlocked state survives | . | 距离失效还有多少小时 | Wall-clock lifetime of the unlocked state | . | 会话上限 (分钟) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/settings-radio-user.html#configuration",
    
    "relUrl": "/zh-rCN/user/settings-radio-user.html#configuration"
  },"4621": {
    "doc": "Settings — Radio & User",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — optional feature modules and device administration | Signal Meter — how modem presets affect signal quality thresholds | LoRa configuration — detailed LoRa settings reference on meshtastic.org | Initial configuration — region setup guide on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/settings-radio-user.html#related-topics",
    
    "relUrl": "/zh-rCN/user/settings-radio-user.html#related-topics"
  },"4622": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": " ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/settings-radio-user.html",
    
    "relUrl": "/zh-rCN/user/settings-radio-user.html"
  },"4623": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/settings-radio-user.html#settings--radio--user",
    
    "relUrl": "/sq-rAL/user/settings-radio-user.html#settings--radio--user"
  },"4624": {
    "doc": "Settings — Radio & User",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Screenshot | . | Dropdown | | . | Toggle | | . | Slider | | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/sq-rAL/user/settings-radio-user.html#how-these-screens-work"
  },"4625": {
    "doc": "Settings — Radio & User",
    "title": "User Settings",
    "content": "User Profile . On Settings → User. | Setting | Përshkrimi | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Status Message | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | Unmessageable | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/settings-radio-user.html#user-settings",
    
    "relUrl": "/sq-rAL/user/settings-radio-user.html#user-settings"
  },"4626": {
    "doc": "Settings — Radio & User",
    "title": "Configuration",
    "content": "Device Config . On Settings → Device configuration → Device. | Setting | Përshkrimi | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Përshkrimi | Default | . | Rajon | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Përshkrimi | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Përshkrimi | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Përshkrimi | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Përshkrimi | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Config . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Përshkrimi | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Përshkrimi | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Private Key | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/settings-radio-user.html#configuration",
    
    "relUrl": "/sq-rAL/user/settings-radio-user.html#configuration"
  },"4627": {
    "doc": "Settings — Radio & User",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — optional feature modules and device administration | Signal Meter — how modem presets affect signal quality thresholds | LoRa configuration — detailed LoRa settings reference on meshtastic.org | Initial configuration — region setup guide on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/settings-radio-user.html#related-topics",
    
    "relUrl": "/sq-rAL/user/settings-radio-user.html#related-topics"
  },"4628": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": " ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/settings-radio-user.html",
    
    "relUrl": "/sq-rAL/user/settings-radio-user.html"
  },"4629": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/settings-radio-user.html#settings--radio--user",
    
    "relUrl": "/zh-rTW/user/settings-radio-user.html#settings--radio--user"
  },"4630": {
    "doc": "Settings — Radio & User",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | 螢幕截圖 | . | Dropdown | | . | Toggle | | . | Slider | | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/zh-rTW/user/settings-radio-user.html#how-these-screens-work"
  },"4631": {
    "doc": "Settings — Radio & User",
    "title": "使用者設定",
    "content": "User Profile . On Settings → User. | 設定 | 描述說明 | . | 長名稱 | Your display name (up to 39 characters) | . | 簡短名稱 | 4-character abbreviated name | . | 狀態訊息 | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | 不接收訊息 | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/settings-radio-user.html#%E4%BD%BF%E7%94%A8%E8%80%85%E8%A8%AD%E5%AE%9A",
    
    "relUrl": "/zh-rTW/user/settings-radio-user.html#使用者設定"
  },"4632": {
    "doc": "Settings — Radio & User",
    "title": "設定",
    "content": "設備設置 . On Settings → Device configuration → Device. | 設定 | 描述說明 | 默認 | . | 裝置角色 | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | ## Rebroadcast Mode轉發廣播模式 | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | 節點資訊廣播間隔 | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | 雙擊觸發按鈕功能 | Treat a double tap as a button press | Disabled | . | 三擊執行 Ad Hoc Ping | Send an ad-hoc position ping on a triple click | 已啟用 | . | LED 心跳指示 | Blink the status LED periodically | 已啟用 | . | 時區 | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa規劃 . On Settings → LoRa. | 設定 | 描述說明 | 默認 | . | 地區 | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | 預設配置 | Speed/range tradeoff | LongFast | . | 中繼次數 | Maximum retransmit hops | 3 | . | 傳輸功率 | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | 手動設定頻率 | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | 使用預設值 | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | 擴頻因子 | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | 編碼率 | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | 頻寬 | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | 頻率槽 | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | 已啟用發射 | Turning this off makes the node receive-only | On | . | 覆蓋工作週期/佔空比 | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | 忽略 MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | 允許轉發至 MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | 接收增益提升 | Extra receive gain on SX126x radios; costs a little current | Off | . | 停用PA風扇 | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | 範圍 | 速度 | SNR Limit | Best For | . | 短 Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | 短 快 | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | 短 慢 | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | 中等快 | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | 中等慢 | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | 長度中等的 | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. 顯示設置 . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | 設定 | 描述說明 | . | 螢幕開啟持續時間 | How long the display stays lit before sleeping | . | 輪播間隔 | How often the node cycles between screens on its own | . | 顯示模式 | Screen layout/density used by the firmware | . | 顯示單位 | Metric or Imperial on the node’s screen | . | 使用12小時制 | Show the node’s clock as 12-hour rather than 24-hour | . | 粗體字 | Draw the screen’s heading text in bold | . | 翻轉畫面 | Rotate the display 180° for an inverted mounting | . | OLED 類型 | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | 輕觸或移動喚醒 | Light the screen when the node is tapped or moved | . | 羅盤朝向 | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | 始終指向北方 | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . 位置設定 . On Settings → Device configuration → Position. | 設定 | 描述說明 | . | GPS 模式（實體硬體） | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS 輪詢間隔 | How often the node asks its GPS for a fix | . | 廣播間隔 | How often the position is shared with the mesh | . | 智慧定位 | Broadcast based on movement rather than purely on the clock | . | 智慧間隔 | With Smart Position on, the shortest gap between broadcasts | . | 智慧距離 | With Smart Position on, how far you must move before broadcasting | . | 固定位置 | Use a manually entered latitude, longitude and altitude instead of the GPS | . | 位置旗標 | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . 電源設定 . On Settings → Device configuration → Power. | 設定 | 描述說明 | . | 啟用省電模式 | Let the node sleep aggressively between activity | . | 電源中斷時關機 | Power the device down after external power disappears | . | 超深度睡眠時長 | How long the deepest sleep state lasts | . | 最小喚醒時間 | The shortest time the node stays awake once woken | . | 藍牙等待持續時間 | How long to wait for a phone to connect before sleeping | . | ADC 校正係數 | Turn on a manual correction for battery-voltage readings | . | ADC乘數修正比率 | The correction factor itself, used only when the override is on | . | 電池 INA_2XX I2C 地址 | Address of an external INA-series power sensor, if fitted | . 網路配置 . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | 設定 | 描述說明 | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | 密碼 | 網路密碼 | . | 啟用以太網 | Use a wired connection on hardware that has one | . | 第四代IP模式 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP 廣播 | Share mesh traffic with other nodes over the local network | . | 時間伺服器 | Time synchronization server | . | rsyslog伺服器 | Remote logging server | . 藍牙配置 . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | 設定 | 描述說明 | . | 藍牙已啟用 | Enable/disable BLE radio | . | 配對模式 | Fixed PIN, Random PIN, or No PIN | . | 固定 PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . 安全性設定 . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | 設定 | 描述說明 | . | 公鑰 | Your node’s public key (read-only) | . | 管理金鑰 | Keys permitted to administer this node remotely — up to three | . | 私鑰 | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | 重新產生私鑰 | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | 序列控制台 | Serial console over the Stream API | . | 啟用除錯日誌 API | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | 管理模式 | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | 備份金鑰 | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/settings-radio-user.html#%E8%A8%AD%E5%AE%9A",
    
    "relUrl": "/zh-rTW/user/settings-radio-user.html#設定"
  },"4633": {
    "doc": "Settings — Radio & User",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — optional feature modules and device administration | Signal Meter — how modem presets affect signal quality thresholds | LoRa configuration — detailed LoRa settings reference on meshtastic.org | Initial configuration — region setup guide on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/settings-radio-user.html#related-topics",
    
    "relUrl": "/zh-rTW/user/settings-radio-user.html#related-topics"
  },"4634": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": " ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/settings-radio-user.html",
    
    "relUrl": "/zh-rTW/user/settings-radio-user.html"
  },"4635": {
    "doc": "Seaded — raadio ja kasutaja",
    "title": "Seaded — raadio ja kasutaja",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/settings-radio-user.html",
    
    "relUrl": "/et-rEE/user/settings-radio-user.html"
  },"4636": {
    "doc": "Seaded — raadio ja kasutaja",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Seaded kasutavad standardseid eelistuste juhtelemente – rippmenüüsid, lülitid ja liugurid: . | Control | Screenshot | . | Dropdown | | . | Toggle | | . | Slider | | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/et-rEE/user/settings-radio-user.html#how-these-screens-work"
  },"4637": {
    "doc": "Seaded — raadio ja kasutaja",
    "title": "Kasutaja seaded",
    "content": "Kasutajaprofiil . On Settings → User. | Sätted | Kirjeldus | . | Täis nimi | Your display name (up to 39 characters) | . | Lühi nimi | 4-character abbreviated name | . | Oleku teavitus | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | Ei võta sõnumeid vastu | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/settings-radio-user.html#kasutaja-seaded",
    
    "relUrl": "/et-rEE/user/settings-radio-user.html#kasutaja-seaded"
  },"4638": {
    "doc": "Seaded — raadio ja kasutaja",
    "title": "Sätted",
    "content": "Seadme sätted . On Settings → Device configuration → Device. | Sätted | Kirjeldus | Vaikimisi | . | Seadme roll | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Kordusülekannete režiim | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Sõlme teabe edastamise intervall | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Topeltpuudutus nupuna | Treat a double tap as a button press | Keelatud | . | Kolmekordne klõps Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Lubatud | . | Südamelöögi LED | Blink the status LED periodically | Lubatud | . | Ajavöönd | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa sätted . On Settings → LoRa. | Sätted | Kirjeldus | Vaikimisi | . | Regioon | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Määramata (tuleb seadistada) | . | Eelseadistused | Speed/range tradeoff | LongFast | . | Hüpete arv | Maks uuesti saadetud hüpet | 3 | . | Saatevõimsus | Transmission power (dBm); 0 = max allowed for region | 0 (regiooni maks) | . | Tühista sagedus | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Kasuta eelseadistust | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Levitustegur | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Kodeerimiskiirus | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Ribalaius | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Sageduspesa | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Edastus lubatud | Turning this off makes the node receive-only | On | . | Töötsükli tühistamine | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Väljas | . | Keela MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok MQTTi | Allow your packets to be forwarded to MQTT by gateways | Väljas | . | RX võimendatud võimendus | Extra receive gain on SX126x radios; costs a little current | Väljas | . | PA ventilaator keelatud | Turn off the power-amplifier fan on hardware that has one | Väljas | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. Lisateabe saamiseks vaadake regiooni seadistamise juhendit aadressil meshtastic.org. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Vihje: SNR-i piirväärtused on meelega negatiivsed. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Kiirus | SNR limiit | Parim | . | Short Turbo | ~1 km | 21,9 kbps | −7,5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10,9 kbps | −7,5 dB | Linnaosad; hooned mõne kvartali raadiuses | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Äärelinna lühimaa; mõõdukas hoonestustihedus | . | Medium Fast | ~5 km | 3.52 kbps | −12,5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17,5 dB | Sarnane ulatus kui Pikk Kauge, aga 500 kHz ribalaiusega; kiirem läbilaskevõime | . | Long Fast | ~10 km | 1,1 kbps | −17,5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0,34 kbps | −17,5 dB | Maapiirkond, mõningase maastikuga; aeg-ajalt kasutatav | . | Lite Fast | ~5 km | 1.76 kbps | −12,5 dB | EL 866 MHz SRD sagedusala (125 kHz ribalaius); võrreldav Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EL 866 MHz SRD sagedusala (125 kHz ribalaius); võrreldav Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7,5 dB | EL 868 MHz sagedusala (62,5 kHz sagedusriba); väldib häireid teiste seadmetega | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EL 868 MHz sagedusala (62,5 kHz ribalaius); võrreldav Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12,5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7,5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0,18 kbps | −20 dB | ⚠️ Vananenud — endiselt valitav, kuid võidakse tulevases püsivara versioonis eemaldada | . | Very Long Slow | ~40+ km | 0,09 kbps | −20 dB | ⚠️ Vananenud — endiselt valitav, kuid võidakse tulevases püsivara versioonis eemaldada | . ℹ️ Märkus: Selles tabelis kasutatakse üldlevinud lühinimesid. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). See tähendab pikemat ulatust, aga vähem baite sekundis. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Linnavõrk (palju sõlmi, lühikesed vahemaad): Kasutage valikut Long Fast (vaikimisi) või Short Fast. Suurem kiirus tähendab väiksemat eetriaega, kui kanalit jagavad paljud sõlmed. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | Vastavus EL 866/868 MHz regulatsioonidele: Kasuta Lite Fast, Lite Slow, Narrow Fast või Narrow Slow – need on optimeeritud kitsama ribalaiusega EL SRD/868 MHz sagedusaladele. | Fikseeritud taristuühendused: Kasutage Short Turbo või Long Turbo spetsiaalsete punkt-punkti ühenduste jaoks, millel on head antennid ja otsenähtavus. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Kõrguse eelis (mäetipp, katus) suurendab märgatavalt efektiivset ulatust. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Ekraani sätted . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Sätted | Kirjeldus | . | Ekraan sisse lülitatud | How long the display stays lit before sleeping | . | Karusselli intervall | How often the node cycles between screens on its own | . | Ekraani režiim | Screen layout/density used by the firmware | . | Ekraani ühikud | Metric or Imperial on the node’s screen | . | Kasuta 12 tunni formaati | Show the node’s clock as 12-hour rather than 24-hour | . | Paks pealkiri | Draw the screen’s heading text in bold | . | Keera ekraani | Rotate the display 180° for an inverted mounting | . | OLED tüüp | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Ärata puudutusega või liigutusega | Light the screen when the node is tapped or moved | . | Kompassi suund | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Suund alati põhi | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Asukoha sätted . On Settings → Device configuration → Position. | Sätted | Kirjeldus | . | GPS-režiim (riistvara) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS-i küsimise intervall | How often the node asks its GPS for a fix | . | Levitamise inteintervall | How often the position is shared with the mesh | . | Nutikas asukoht | Broadcast based on movement rather than purely on the clock | . | Nutikas intervall | With Smart Position on, the shortest gap between broadcasts | . | Nutikas kaugus | With Smart Position on, how far you must move before broadcasting | . | Määratud asukoht | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Asukoha lipp | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Toite sätted . On Settings → Device configuration → Power. | Sätted | Kirjeldus | . | Luba energiasäästurežiim | Let the node sleep aggressively between activity | . | Väljalülitamine voolukatkestuse korral | Power the device down after external power disappears | . | Super sügava une kestus | How long the deepest sleep state lasts | . | Minimaalne ärkveloleku aeg | The shortest time the node stays awake once woken | . | Oota Bluetoothi ​​kestust | How long to wait for a phone to connect before sleeping | . | ADC kordaja tühistamine | Turn on a manual correction for battery-voltage readings | . | Asenda ADC kordistaja suhe | The correction factor itself, used only when the override is on | . | Aku INA_2XX I2C aadress | Address of an external INA-series power sensor, if fitted | . Võrgu sätted . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Sätted | Kirjeldus | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Parool | Network password | . | Ethernet lubatud | Use a wired connection on hardware that has one | . | IPv4 režiim | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP levitamine | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Kauglogimise server | . Sinihamba sätted . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Sätted | Kirjeldus | . | Sinihammas lubatud | Enable/disable BLE radio | . | Sidumine | Määratud PIN kood, juhuslik PIN kood või PIN koodi pole | . | Fikseeritud PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Turva sätted . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Sätted | Kirjeldus | . | Avalik võti | Sinu sõlme avalik võti (kirjutuskaitstud) | . | Administraatori võti | Keys permitted to administer this node remotely — up to three | . | Salajane võti | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Loo uus privaatvõti | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin kanal lubatud | ⚠️ Eemaldatud — nüüd seadistatakse automaatselt, kui administraatori võti on määratud | . | Jadapordi konsool | Serial console over the Stream API | . | Silumislogi API lubatud | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Hallatud režiim | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Taastevõtmed | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Taasta võtmed | Kirjuta varundatud võtmed tagasi sõlme (saadaval siis, kui varukoopia on olemas) | . | Kustuta taastevõtmed | Remove the stored key backup from this phone | . | Kaitsetase | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Käivitusi alles | How many device boots the unlocked state survives | . | Tunde kuni kehtivusaja lõpuni | Wall-clock lifetime of the unlocked state | . | Seansi limiit (minutid) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/settings-radio-user.html#s%C3%A4tted",
    
    "relUrl": "/et-rEE/user/settings-radio-user.html#sätted"
  },"4639": {
    "doc": "Seaded — raadio ja kasutaja",
    "title": "Seotud teemad",
    "content": ". | Seaded — moodulid ja admin — valikulised funktsioonimoodulid ja seadme haldamine | Signal Meter — how modem presets affect signal quality thresholds | LoRa konfiguratsioon — üksikasjalik LoRa sätete juhend aadressil meshtastic.org | Esialgne konfiguratsioon — piirkonna seadistamise juhend meshtastic.org lehel | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/settings-radio-user.html#seotud-teemad",
    
    "relUrl": "/et-rEE/user/settings-radio-user.html#seotud-teemad"
  },"4640": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/settings-radio-user.html#settings--radio--user",
    
    "relUrl": "/fr-rFR/user/settings-radio-user.html#settings--radio--user"
  },"4641": {
    "doc": "Settings — Radio & User",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Screenshot | . | Dropdown | | . | Toggle | | . | Slider | | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/fr-rFR/user/settings-radio-user.html#how-these-screens-work"
  },"4642": {
    "doc": "Settings — Radio & User",
    "title": "Paramètres utilisateur",
    "content": "User Profile . On Settings → User. | Setting | Description | . | Nom long | Your display name (up to 39 characters) | . | Nom court | 4-character abbreviated name | . | Statut du message | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | Non joignable par message | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/settings-radio-user.html#param%C3%A8tres-utilisateur",
    
    "relUrl": "/fr-rFR/user/settings-radio-user.html#paramètres-utilisateur"
  },"4643": {
    "doc": "Settings — Radio & User",
    "title": "Configuration",
    "content": "Configuration de l’appareil . On Settings → Device configuration → Device. | Setting | Description | Par défaut | . | Rôle de l’appareil | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Mode de réémission | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Intervalle de diffusion des infos nœud | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double clic comme appui sur le bouton | Treat a double tap as a button press | Désactivé | . | Triple clic pour faire un ping Ad Hoc | Send an ad-hoc position ping on a triple click | Activé | . | LED de vérification de fonctionnement (heartbeat) | Blink the status LED periodically | Activé | . | Fuseau horaire | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . Configuration LoRa . On Settings → LoRa. | Setting | Description | Par défaut | . | Région | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Préréglages | Speed/range tradeoff | LongFast | . | Nombre de sauts | Maximum retransmit hops | 3 | . | Puissance d’émission | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Remplacer la fréquence | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Utiliser un préréglage | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Facteur de propagation | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Taux de codage | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bande Passante | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Slot de fréquence | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmission activée | Turning this off makes the node receive-only | On | . | Autoriser le dépassement du temps d’émission autorisé par heure | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Éteint | . | Ignorer MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Transmission des paquets vers MQTT | Allow your packets to be forwarded to MQTT by gateways | Éteint | . | Gain RX Boosté | Extra receive gain on SX126x radios; costs a little current | Éteint | . | Ventilateur PA désactivé | Turn off the power-amplifier fan on hardware that has one | Éteint | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Vitesse | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Configuration de l’écran . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Description | . | Écran allumé pour | How long the display stays lit before sleeping | . | Intervalle du carrousel | How often the node cycles between screens on its own | . | Mode d’affichage | Screen layout/density used by the firmware | . | Unités d’affichage | Metric or Imperial on the node’s screen | . | Utiliser le format horaire 12h | Show the node’s clock as 12-hour rather than 24-hour | . | Titre en gras | Draw the screen’s heading text in bold | . | Inverser l’écran | Rotate the display 180° for an inverted mounting | . | Type d’OLED | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Réveil par appui ou mouvement | Light the screen when the node is tapped or moved | . | Orientation de la boussole | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Toujours pointer vers le nord | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Configuration de la position . On Settings → Device configuration → Position. | Setting | Description | . | Mode GPS (matériel physique) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | Fréquence de récupération GPS | How often the node asks its GPS for a fix | . | Intervalle de diffusion | How often the position is shared with the mesh | . | Position Intelligente | Broadcast based on movement rather than purely on the clock | . | Intervalle intelligent | With Smart Position on, the shortest gap between broadcasts | . | Distance intelligente | With Smart Position on, how far you must move before broadcasting | . | Position fixe | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Champs de position | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Configuration de l’alimentation . On Settings → Device configuration → Power. | Setting | Description | . | Activer le mode économie d’énergie | Let the node sleep aggressively between activity | . | Arrêt en cas de perte d’alimentation | Power the device down after external power disappears | . | Durée du sommeil extra profond | How long the deepest sleep state lasts | . | Durée minimale de réveil | The shortest time the node stays awake once woken | . | Durée d’attente max du Bluetooth | How long to wait for a phone to connect before sleeping | . | Remplacer le multiplicateur ADC | Turn on a manual correction for battery-voltage readings | . | Facteur de remplacement du multiplicateur ADC | The correction factor itself, used only when the override is on | . | Adresse I2C de la batterie INA_2XX | Address of an external INA-series power sensor, if fitted | . Configuration du réseau . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Description | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Mot de passe | Mot de passe du réseau | . | Ethernet activé | Use a wired connection on hardware that has one | . | Mode IPv4 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | Serveur NTP | Time synchronization server | . | Serveur Rsyslog | Remote logging server | . Configuration Bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Description | . | Bluetooth activé | Enable/disable BLE radio | . | Mode d’appariement | Fixed PIN, Random PIN, or No PIN | . | Code PIN fixe | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Configuration de sécurité . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Description | . | Clé publique | Your node’s public key (read-only) | . | Clé Admin | Keys permitted to administer this node remotely — up to three | . | Clé privée | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Régénérer la clé privée | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Console série | Serial console over the Stream API | . | API de journalisation de débogage activée | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Mode géré | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Sauvegarder les clés | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Heures jusqu’à expiration | Wall-clock lifetime of the unlocked state | . | Limite de sessions (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/settings-radio-user.html#configuration",
    
    "relUrl": "/fr-rFR/user/settings-radio-user.html#configuration"
  },"4644": {
    "doc": "Settings — Radio & User",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — optional feature modules and device administration | Signal Meter — how modem presets affect signal quality thresholds | LoRa configuration — detailed LoRa settings reference on meshtastic.org | Initial configuration — region setup guide on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/settings-radio-user.html#related-topics",
    
    "relUrl": "/fr-rFR/user/settings-radio-user.html#related-topics"
  },"4645": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": " ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/settings-radio-user.html",
    
    "relUrl": "/fr-rFR/user/settings-radio-user.html"
  },"4646": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/settings-radio-user.html#settings--radio--user",
    
    "relUrl": "/tr-rTR/user/settings-radio-user.html#settings--radio--user"
  },"4647": {
    "doc": "Settings — Radio & User",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Screenshot | . | Dropdown | | . | Toggle | | . | Slider | | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/tr-rTR/user/settings-radio-user.html#how-these-screens-work"
  },"4648": {
    "doc": "Settings — Radio & User",
    "title": "User Settings",
    "content": "User Profile . On Settings → User. | Setting | Açıklaması | . | Uzun Ad | Your display name (up to 39 characters) | . | Kısa Ad | 4-character abbreviated name | . | Status Message | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | Mesaj gönderilemez | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/settings-radio-user.html#user-settings",
    
    "relUrl": "/tr-rTR/user/settings-radio-user.html#user-settings"
  },"4649": {
    "doc": "Settings — Radio & User",
    "title": "Yapılandırma",
    "content": "Cihaz Ayarı . On Settings → Device configuration → Device. | Setting | Açıklaması | Varsayılan | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Bilgisi Yayın Aralığı | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Açık | . | LED Heartbeat | Blink the status LED periodically | Açık | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Ayarı . On Settings → LoRa. | Setting | Açıklaması | Varsayılan | . | Bölge | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bant genişliği | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Görev Döngüsünü Geçersiz Kıl | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | MQTT’yi Yoksay | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fanı devre dışı | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Akran Ayarı . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Açıklaması | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Görüntü Modu | Screen layout/density used by the firmware | . | Görüntü Birimleri | Metric or Imperial on the node’s screen | . | 12h saat formatını kullan | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Ekranı Çevir | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Pusula yönü | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Konum Ayarı . On Settings → Device configuration → Position. | Setting | Açıklaması | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Güç Ayarı . On Settings → Device configuration → Power. | Setting | Açıklaması | . | Güç tasarrufu modunu etkinleştir | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC çarpanını geçersiz kılma oranı | The correction factor itself, used only when the override is on | . | Pilin INA_2XX I2C adresi | Address of an external INA-series power sensor, if fitted | . Ağ Ayarı . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Açıklaması | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Şifre | Ağ şifresi | . | Ethernet etkin | Use a wired connection on hardware that has one | . | IPv4 modu | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP sunucusu | Time synchronization server | . | rsyslog sunucusu | Remote logging server | . Bluetooth Ayarı . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Açıklaması | . | Bluetooth Etkin | Enable/disable BLE radio | . | Eşleştirme Modu | Fixed PIN, Random PIN, or No PIN | . | Sabit PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Güvenlik Ayarı . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Açıklaması | . | Genel Anahtar | Your node’s public key (read-only) | . | Yönetici Anahtarı | Keys permitted to administer this node remotely — up to three | . | Özel Anahtar | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Seri konsol | Serial console over the Stream API | . | Hata ayıklama kaydı API’si etkin | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Yönetilen Mod | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Anahtarları Yedekle | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/settings-radio-user.html#yap%C4%B1land%C4%B1rma",
    
    "relUrl": "/tr-rTR/user/settings-radio-user.html#yapılandırma"
  },"4650": {
    "doc": "Settings — Radio & User",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — optional feature modules and device administration | Signal Meter — how modem presets affect signal quality thresholds | LoRa configuration — detailed LoRa settings reference on meshtastic.org | Initial configuration — region setup guide on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/settings-radio-user.html#related-topics",
    
    "relUrl": "/tr-rTR/user/settings-radio-user.html#related-topics"
  },"4651": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": " ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/settings-radio-user.html",
    
    "relUrl": "/tr-rTR/user/settings-radio-user.html"
  },"4652": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/settings-radio-user.html#settings--radio--user",
    
    "relUrl": "/el-rGR/user/settings-radio-user.html#settings--radio--user"
  },"4653": {
    "doc": "Settings — Radio & User",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Screenshot | . | Dropdown | | . | Toggle | | . | Slider | | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/el-rGR/user/settings-radio-user.html#how-these-screens-work"
  },"4654": {
    "doc": "Settings — Radio & User",
    "title": "User Settings",
    "content": "User Profile . On Settings → User. | Setting | Περιγραφή | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Status Message | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | Unmessageable | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/settings-radio-user.html#user-settings",
    
    "relUrl": "/el-rGR/user/settings-radio-user.html#user-settings"
  },"4655": {
    "doc": "Settings — Radio & User",
    "title": "Configuration",
    "content": "Device Config . On Settings → Device configuration → Device. | Setting | Περιγραφή | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Περιγραφή | Default | . | Περιφέρεια | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Περιγραφή | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Περιγραφή | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Περιγραφή | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Περιγραφή | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Κωδικός πρόσβασης | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Ρυθμίσεις Bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Περιγραφή | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Περιγραφή | . | Δημόσιο Κλειδί | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Ιδιωτικό Κλειδί | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/settings-radio-user.html#configuration",
    
    "relUrl": "/el-rGR/user/settings-radio-user.html#configuration"
  },"4656": {
    "doc": "Settings — Radio & User",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — optional feature modules and device administration | Signal Meter — how modem presets affect signal quality thresholds | LoRa configuration — detailed LoRa settings reference on meshtastic.org | Initial configuration — region setup guide on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/settings-radio-user.html#related-topics",
    
    "relUrl": "/el-rGR/user/settings-radio-user.html#related-topics"
  },"4657": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": " ",
    "url": "/Meshtastic-Android/main/el-rGR/user/settings-radio-user.html",
    
    "relUrl": "/el-rGR/user/settings-radio-user.html"
  },"4658": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/settings-radio-user.html#settings--radio--user",
    
    "relUrl": "/ro-rRO/user/settings-radio-user.html#settings--radio--user"
  },"4659": {
    "doc": "Settings — Radio & User",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Screenshot | . | Dropdown | | . | Toggle | | . | Slider | | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/ro-rRO/user/settings-radio-user.html#how-these-screens-work"
  },"4660": {
    "doc": "Settings — Radio & User",
    "title": "User Settings",
    "content": "User Profile . On Settings → User. | Setting | Descriere | . | Nume lung | Your display name (up to 39 characters) | . | Nume scurt | 4-character abbreviated name | . | Mesaj de stare: | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | Netransmisibil | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/settings-radio-user.html#user-settings",
    
    "relUrl": "/ro-rRO/user/settings-radio-user.html#user-settings"
  },"4661": {
    "doc": "Settings — Radio & User",
    "title": "Configuration",
    "content": "Device Config . On Settings → Device configuration → Device. | Setting | Descriere | Prestabilit | . | Rolul dispozitivului | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Mod de redifuzare | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Intervalul de difuzare a informațiilor nodului | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Apăsare dublă ca buton | Treat a double tap as a button press | Disabled | . | Apăsare triplă pentru ping Ad Hoc | Send an ad-hoc position ping on a triple click | Activat | . | Puls LED | Blink the status LED periodically | Activat | . | Fus orar | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Descriere | Prestabilit | . | Regiune | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presetări | Speed/range tradeoff | LongFast | . | Numărul de Hops | Maximum retransmit hops | 3 | . | Putere transmisie | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Suprascriere frecvență | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Utilizare presetare | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Factor de răspândire | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Rata de codificare | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Lățime bandă | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Slot pentru frecvenţă | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmisie activată | Turning this off makes the node receive-only | On | . | Suprascrie ciclul de obligații | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignoră MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Acceptă MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | Amplificare RX amplificată | Extra receive gain on SX126x radios; costs a little current | Off | . | Ventilator PA dezactivat | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Viteza | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Descriere | . | Ecran pornit pentru | How long the display stays lit before sleeping | . | Intervalul caruselului | How often the node cycles between screens on its own | . | Mod ecran | Screen layout/density used by the firmware | . | Unități de măsură afișate | Metric or Imperial on the node’s screen | . | Utilizaţi formatul ceasului 12h | Show the node’s clock as 12-hour rather than 24-hour | . | Direcție îngroșat | Draw the screen’s heading text in bold | . | Rotire ecran | Rotate the display 180° for an inverted mounting | . | Tip OLED | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Trezire la apăsare sau mișcare | Light the screen when the node is tapped or moved | . | Orientarea busolei | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Indică mereu spre nord | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Descriere | . | Mod GPS (hardware fizic) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | Interval de actualizare GPS | How often the node asks its GPS for a fix | . | Interval de difuzare | How often the position is shared with the mesh | . | Poziție inteligentă | Broadcast based on movement rather than purely on the clock | . | Interval inteligent | With Smart Position on, the shortest gap between broadcasts | . | Distanță inteligentă | With Smart Position on, how far you must move before broadcasting | . | Poziție fixă | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Steaguri poziție | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Configurare Putere . On Settings → Device configuration → Power. | Setting | Descriere | . | Activează modul de economisire a energiei | Let the node sleep aggressively between activity | . | Închidere la pierderea de energie | Power the device down after external power disappears | . | Durată maximă de somn | How long the deepest sleep state lasts | . | Durata minimă a trezirii | The shortest time the node stays awake once woken | . | Așteptați pentru durata Bluetooth | How long to wait for a phone to connect before sleeping | . | Suprascriere multiplicator ADC | Turn on a manual correction for battery-voltage readings | . | Raportul suprascrierii multiplicatorului ADC | The correction factor itself, used only when the override is on | . | Adresa baterie INA_2XX I2C | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Descriere | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | Numele rețelei | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Parolă | Network password | . | Ethernet activat | Use a wired connection on hardware that has one | . | Mod IPv4 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | Server NTP | Time synchronization server | . | server rsyslog | Remote logging server | . Configurare Bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Descriere | . | Bluetooth activat | Enable/disable BLE radio | . | Mod împerechere | Fixed PIN, Random PIN, or No PIN | . | PIN fix | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Descriere | . | Chei publice | Your node’s public key (read-only) | . | Cheie Administrator | Keys permitted to administer this node remotely — up to three | . | Cheia privată | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerează Cheia privată | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Consolă serială | Serial console over the Stream API | . | Debug log API activat | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Mod Gestionat | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/settings-radio-user.html#configuration",
    
    "relUrl": "/ro-rRO/user/settings-radio-user.html#configuration"
  },"4662": {
    "doc": "Settings — Radio & User",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — optional feature modules and device administration | Signal Meter — how modem presets affect signal quality thresholds | LoRa configuration — detailed LoRa settings reference on meshtastic.org | Initial configuration — region setup guide on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/settings-radio-user.html#related-topics",
    
    "relUrl": "/ro-rRO/user/settings-radio-user.html#related-topics"
  },"4663": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": " ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/settings-radio-user.html",
    
    "relUrl": "/ro-rRO/user/settings-radio-user.html"
  },"4664": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/settings-radio-user.html#settings--radio--user",
    
    "relUrl": "/iw-rIL/user/settings-radio-user.html#settings--radio--user"
  },"4665": {
    "doc": "Settings — Radio & User",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Screenshot | . | Dropdown | | . | Toggle | | . | Slider | | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/iw-rIL/user/settings-radio-user.html#how-these-screens-work"
  },"4666": {
    "doc": "Settings — Radio & User",
    "title": "User Settings",
    "content": "User Profile . On Settings → User. | Setting | תיאור | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Status Message | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | Unmessageable | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/settings-radio-user.html#user-settings",
    
    "relUrl": "/iw-rIL/user/settings-radio-user.html#user-settings"
  },"4667": {
    "doc": "Settings — Radio & User",
    "title": "Configuration",
    "content": "Device Config . On Settings → Device configuration → Device. | Setting | תיאור | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | תיאור | Default | . | אזור | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | תיאור | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | תיאור | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | תיאור | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | תיאור | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Config . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | תיאור | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | תיאור | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Private Key | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/settings-radio-user.html#configuration",
    
    "relUrl": "/iw-rIL/user/settings-radio-user.html#configuration"
  },"4668": {
    "doc": "Settings — Radio & User",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — optional feature modules and device administration | Signal Meter — how modem presets affect signal quality thresholds | LoRa configuration — detailed LoRa settings reference on meshtastic.org | Initial configuration — region setup guide on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/settings-radio-user.html#related-topics",
    
    "relUrl": "/iw-rIL/user/settings-radio-user.html#related-topics"
  },"4669": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": " ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/settings-radio-user.html",
    
    "relUrl": "/iw-rIL/user/settings-radio-user.html"
  },"4670": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/settings-radio-user.html#settings--radio--user",
    
    "relUrl": "/pt-rBR/user/settings-radio-user.html#settings--radio--user"
  },"4671": {
    "doc": "Settings — Radio & User",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Screenshot | . | Dropdown | | . | Toggle | | . | Slider | | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/pt-rBR/user/settings-radio-user.html#how-these-screens-work"
  },"4672": {
    "doc": "Settings — Radio & User",
    "title": "User Settings",
    "content": "User Profile . On Settings → User. | Setting | Descrição | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Status Message | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | Impossível enviar mensagens | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/settings-radio-user.html#user-settings",
    
    "relUrl": "/pt-rBR/user/settings-radio-user.html#user-settings"
  },"4673": {
    "doc": "Settings — Radio & User",
    "title": "Configuration",
    "content": "Configuração do Dispositivo . On Settings → Device configuration → Device. | Setting | Descrição | Padrão | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . Configuração do LoRa . On Settings → LoRa. | Setting | Descrição | Padrão | . | Região | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Largura da banda | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Ignorar ciclo de trabalho | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignorar MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | Ventilador do PA desativado | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Velocidade | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Configuração da Tela . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Descrição | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Modo da tela | Screen layout/density used by the firmware | . | Unidades de exibição | Metric or Imperial on the node’s screen | . | Usar formato de relógio 12h | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Inverter tela | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Orientação da bússola | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Configuração da Posição . On Settings → Device configuration → Position. | Setting | Descrição | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Configuração de Energia . On Settings → Device configuration → Power. | Setting | Descrição | . | Ativar modo de economia de energia | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | Alterar proporção do multiplicador ADC | The correction factor itself, used only when the override is on | . | Endereço I2C da bateria INA_2XX | Address of an external INA-series power sensor, if fitted | . Configuração de Rede . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Descrição | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Senha | Network password | . | Ethernet ativado | Use a wired connection on hardware that has one | . | Modo IPv4 | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | Servidor NTP | Time synchronization server | . | Servidor rsyslog | Remote logging server | . Configuração do Bluetooth . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Descrição | . | Bluetooth habilitado | Enable/disable BLE radio | . | Modo de pareamento | Fixed PIN, Random PIN, or No PIN | . | PIN fixo | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Configurações de Segurança . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Descrição | . | Chave Publica | Your node’s public key (read-only) | . | Chave do Administrador | Keys permitted to administer this node remotely — up to three | . | Chave Privada | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerar a chave privada | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Console serial | Serial console over the Stream API | . | API de logs de depuração ativada | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Modo Administrado | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/settings-radio-user.html#configuration",
    
    "relUrl": "/pt-rBR/user/settings-radio-user.html#configuration"
  },"4674": {
    "doc": "Settings — Radio & User",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — optional feature modules and device administration | Signal Meter — how modem presets affect signal quality thresholds | LoRa configuration — detailed LoRa settings reference on meshtastic.org | Initial configuration — region setup guide on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/settings-radio-user.html#related-topics",
    
    "relUrl": "/pt-rBR/user/settings-radio-user.html#related-topics"
  },"4675": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": " ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/settings-radio-user.html",
    
    "relUrl": "/pt-rBR/user/settings-radio-user.html"
  },"4676": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": "Configure your node’s user identity, region and LoRa parameters, position and power behavior, network and Bluetooth connectivity, and security settings. ",
    "url": "/Meshtastic-Android/main/en/user/settings-radio-user.html#settings--radio--user",
    
    "relUrl": "/en/user/settings-radio-user.html#settings--radio--user"
  },"4677": {
    "doc": "Settings — Radio & User",
    "title": "How these screens work",
    "content": "Everything here is on the Settings screen. User, LoRa, Channels and Security are listed there directly. Device, Position, Power, Network, Display and Bluetooth are one level down, under Settings → Device configuration. Network appears only on nodes with Wi-Fi or Ethernet, and Bluetooth only on nodes with Bluetooth. Settings use standard preference controls — dropdowns, toggles, and sliders: . | Control | Screenshot | . | Dropdown | | . | Toggle | | . | Slider | | . ",
    "url": "/Meshtastic-Android/main/en/user/settings-radio-user.html#how-these-screens-work",
    
    "relUrl": "/en/user/settings-radio-user.html#how-these-screens-work"
  },"4678": {
    "doc": "Settings — Radio & User",
    "title": "User Settings",
    "content": "User Profile . On Settings → User. | Setting | Description | . | Long Name | Your display name (up to 39 characters) | . | Short Name | 4-character abbreviated name | . | Status Message | A short, public free-text status other nodes display alongside your node — up to 80 bytes, cleared with the ✕ in the field. The node broadcasts it to the mesh when you change it and again every 12 hours. Needs firmware 2.8 or newer, and is absent otherwise | . | Unmessageable | Marks the node as one nobody should try to message — for an unmonitored or infrastructure node. Other clients hide it from the contact list. Needs supporting firmware | . | Licensed amateur node (Ham) | Enable if you hold an amateur node license (permits higher power). Turning it on is staged behind a confirmation dialog. On your own node it then relabels Long Name as Call sign and adds a separate Long Name field; over remote admin the field stays Long Name | . Applying changes . The footer appears as soon as you change something. Discard throws the change away, and the other button writes it to the node: it reads Save & restart on the screens the firmware applies with a reboot — Position, Network, Bluetooth, Security, and most module screens — and Save everywhere else. The status message is saved with the same Save, but it never reboots the node — and, like the rest of this screen, it can be edited on a remote node you administer. For your own node there is a shortcut while it is connected: touch & hold your node in the node list and choose Update status. Older firmware and a disconnected node have no shortcut — the field itself is still the way in. ",
    "url": "/Meshtastic-Android/main/en/user/settings-radio-user.html#user-settings",
    
    "relUrl": "/en/user/settings-radio-user.html#user-settings"
  },"4679": {
    "doc": "Settings — Radio & User",
    "title": "Configuration",
    "content": "Device Config . On Settings → Device configuration → Device. | Setting | Description | Default | . | Device Role | Node behavior. The picker lists the firmware names (CLIENT, ROUTER, ROUTER_LATE, TAK, and so on), and the description of whichever role is selected appears under the field. Choosing ROUTER or ROUTER_LATE asks you to confirm you have read the device-role guidance first | CLIENT | . | Rebroadcast Mode | How the node retransmits messages. As with the role, the picker lists the firmware names and describes only the selected one | ALL | . | Node Info Broadcast Interval | How often the node re-announces itself. A dropdown of fixed intervals — Unset, then 3 to 72 hours — not a value you type in seconds | 3 hours | . | Double Tap as Button | Treat a double tap as a button press | Disabled | . | Triple Click Ad Hoc Ping | Send an ad-hoc position ping on a triple click | Enabled | . | LED Heartbeat | Blink the status LED periodically | Enabled | . | Time Zone | POSIX time-zone string for the device clock, with buttons to copy your phone’s zone or clear it | — | . | Button / Buzzer GPIO | Advanced: which pins the button and buzzer are wired to | — | . LoRa Config . On Settings → LoRa. | Setting | Description | Default | . | Region | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node’s identity key and gives it a new node number | Unset (must configure) | . | Presets | Speed/range tradeoff | LongFast | . | Number of Hops | Maximum retransmit hops | 3 | . | Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) | . | Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn’t offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) | . | Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On | . | Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn’t accept 5 or 6 and uses 11 instead | From preset | . | Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset | . | Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn’t on that list shows as Unsupported and blocks saving until you pick a supported one | From preset | . | Frequency Slot | Which slot within the region’s band to use. 0 derives it from the primary channel name | 0 (automatic) | . | Transmit Enabled | Turning this off makes the node receive-only | On | . | Override Duty Cycle | Ignores the region’s duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off | . | Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region | . | Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off | . | RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off | . | PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off | . The preset list is also filtered to what your region legally permits, so a preset allowed in one region doesn’t appear in another. Changing region can therefore leave your current preset illegal — the app repairs it for you, switching to the region’s own default rather than leaving an unusable setting in place. The region list itself is filtered by what your firmware supports, so the newer regions appear only on 2.8 or later, alongside whichever region the node already has set. Some regions are amateur-node allocations whose presets only licensed operators may use. On firmware 2.8 or newer the app knows which regions those are and grays the whole Presets list out until Licensed amateur node (Ham) is turned on for the node you are configuring; the text under the field says so while it is grayed out. ⚠️ Important: Operating without the correct region may violate local radio regulations. See the region configuration guide on meshtastic.org for details. Modem presets . The Lite, Narrow, Medium Turbo, and Tiny presets need firmware 2.8 or newer — the app hides them on older nodes. 💡 Tip: The SNR Limit values are negative on purpose. LoRa can decode signals below the noise floor, so a more-negative limit means the preset tolerates a weaker, noisier signal (more range). See How the Signal Meter Works for the full explanation. | Preset | Range | Speed | SNR Limit | Best For | . | Short Turbo | ~1 km | 21.9 kbps | −7.5 dB | Dense urban with line-of-sight; data-heavy applications | . | Short Fast | ~3 km | 10.9 kbps | −7.5 dB | Urban neighborhoods; buildings within a few blocks | . | Short Slow | ~5 km | 6.25 kbps | −10 dB | Suburban short-range; moderate building density | . | Medium Fast | ~5 km | 3.52 kbps | −12.5 dB | Suburban areas; moderate building density | . | Medium Slow | ~8 km | 1.95 kbps | −15 dB | Suburban/rural; moderate range with slower speed | . | Long Turbo | ~10 km | 1.34 kbps | −17.5 dB | Similar range to Long Fast but with 500 kHz bandwidth; faster throughput | . | Long Fast | ~10 km | 1.1 kbps | −17.5 dB | General use (default) — balanced range and speed | . | Long Moderate | ~20 km | 0.34 kbps | −17.5 dB | Rural with some terrain; occasional use | . | Lite Fast | ~5 km | 1.76 kbps | −12.5 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Medium Fast | . | Lite Slow | ~10 km | 0.98 kbps | −15 dB | EU 866 MHz SRD band (125 kHz BW); comparable to Long Fast | . | Narrow Fast | ~5 km | 2.28 kbps | −7.5 dB | EU 868 MHz band (62.5 kHz BW); avoids interference with other devices | . | Narrow Slow | ~10 km | 1.30 kbps | −10 dB | EU 868 MHz band (62.5 kHz BW); comparable to Long Fast | . | Medium Turbo | ~5 km | 7.0 kbps | −12.5 dB | Like Medium Fast but with 500 kHz bandwidth; not legal in every region. Needs firmware 2.8 or newer | . | Tiny Fast | ~10 km | 0.68 kbps | −7.5 dB | Amateur bands that cap occupied bandwidth; these presets use 15.6 kHz. Needs firmware 2.8 or newer, an SX126x or SX127x radio, and a TCXO of ±5 ppm or better | . | Tiny Slow | ~20 km | 0.33 kbps | −10 dB | Same band restrictions as Tiny Fast, longer range. Same firmware, node, and TCXO requirements | . | Long Slow | ~30 km | 0.18 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . | Very Long Slow | ~40+ km | 0.09 kbps | −20 dB | ⚠️ Deprecated — still selectable but may be removed in a future firmware release | . ℹ️ Note: This table uses the common short names. The app’s Presets dropdown lists the raw firmware names instead — SHORT_FAST, LONG_FAST, LITE_FAST, NARROW_FAST, and so on. Local Mesh Discovery shows the same presets as Long Fast and Short Turbo. Choosing a modem preset . The modem preset controls the fundamental tradeoff between range and data rate: . | Slower presets use more spreading, making signals decodable at weaker signal levels (lower SNR limit). This means longer range but fewer bytes per second. | Faster presets pack more data per transmission but require a stronger signal to decode. | . Practical guidance: . | Urban mesh (many nodes, short distances): Use Long Fast (default) or Short Fast. Higher speed means less airtime congestion when many nodes share the channel. | Rural/sparse mesh (few nodes, long distances): Use Long Moderate. Range matters more than speed when nodes are far apart. | EU 866/868 MHz regulatory compliance: Use Lite Fast, Lite Slow, Narrow Fast, or Narrow Slow — these are optimized for the EU SRD/868 MHz bands with narrower bandwidths. | Fixed infrastructure links: Use Short Turbo or Long Turbo for dedicated point-to-point links with good antennas and line-of-sight. | Mixed environments: Stick with Long Fast — it’s the community default and ensures compatibility with others in your area. | . All nodes on the same channel must use the same modem preset. Nodes with mismatched presets can’t communicate even if they share the same frequency and encryption key. The range estimates in the Modem Presets table assume flat terrain and modest antennas. Elevation advantage (hilltop, rooftop) dramatically increases effective range. A well-placed Router with Long Fast can often outperform a ground-level node with Long Slow. Display Config . On Settings → Device configuration → Display. These control the node’s own screen, not the app’s. | Setting | Description | . | Screen on for | How long the display stays lit before sleeping | . | Carousel interval | How often the node cycles between screens on its own | . | Display mode | Screen layout/density used by the firmware | . | Display units | Metric or Imperial on the node’s screen | . | Use 12h clock format | Show the node’s clock as 12-hour rather than 24-hour | . | Bold Heading | Draw the screen’s heading text in bold | . | Flip screen | Rotate the display 180° for an inverted mounting | . | OLED type | Six values, shown as the raw constants: OLED_AUTO, OLED_SSD1306, OLED_SH1106, OLED_SH1107, OLED_SH1107_128_128, OLED_SH1107_ROTATED | . | Wake on tap or motion | Light the screen when the node is tapped or moved | . | Compass orientation | Rotation offset for the compass rose. Eight values, shown as the raw constants DEGREES_0 through DEGREES_270 plus an _INVERTED variant of each | . | Always point north | Locks the compass rose north-up instead of rotating it with your heading. Independent of Compass orientation — neither replaces the other | . Position Config . On Settings → Device configuration → Position. | Setting | Description | . | GPS Mode (Physical Hardware) | Three-state: GPS enabled, disabled, or not present. Not a simple on/off | . | GPS Polling Interval | How often the node asks its GPS for a fix | . | Broadcast Interval | How often the position is shared with the mesh | . | Smart Position | Broadcast based on movement rather than purely on the clock | . | Smart Interval | With Smart Position on, the shortest gap between broadcasts | . | Smart Distance | With Smart Position on, how far you must move before broadcasting | . | Fixed Position | Use a manually entered latitude, longitude and altitude instead of the GPS | . | Position Flags | A group of toggles choosing which fields ride along with a position — altitude, its reference and precision, satellites in view, timestamp, and so on | . | GPS EN / Receive / Transmit GPIO | Advanced: the pins the GPS module is wired to | . Power Config . On Settings → Device configuration → Power. | Setting | Description | . | Enable power saving mode | Let the node sleep aggressively between activity | . | Shutdown on power loss | Power the device down after external power disappears | . | Super deep sleep duration | How long the deepest sleep state lasts | . | Minimum wake time | The shortest time the node stays awake once woken | . | Wait for Bluetooth duration | How long to wait for a phone to connect before sleeping | . | ADC multiplier override | Turn on a manual correction for battery-voltage readings | . | ADC multiplier override ratio | The correction factor itself, used only when the override is on | . | Battery INA_2XX I2C address | Address of an external INA-series power sensor, if fitted | . Network Config . On Settings → Device configuration → Network, on nodes with Wi-Fi or Ethernet. ⚠️ Warning: Turning on Wi-Fi enabled or Ethernet enabled ends the Bluetooth connection between your phone and the node. Reconnect over the network afterwards from the Connections screen, or turn Wi-Fi off again from the node’s own screen or over USB. Saving this screen also always reboots the node. | Setting | Description | . | Wi-Fi enabled | Enable the Wi-Fi node (ESP32 nodes) | . | SSID | Network name to connect to. Appears only once Wi-Fi enabled is on, along with Password. Scan Wi-Fi QR code fills both from a standard Wi-Fi QR code; on Android, holding the phone against a Wi-Fi NFC tag while this screen is open fills them the same way, and the app offers to open system settings if NFC is turned off | . | Password | Network password | . | Ethernet enabled | Use a wired connection on hardware that has one | . | IPv4 mode | DHCP, or a static address configured with the four fields that follow | . | Wi-Fi IP / Subnet / Gateway / DNS | The static address, only used when IPv4 mode is static | . | UDP broadcasting | Share mesh traffic with other nodes over the local network | . | NTP server | Time synchronization server | . | rsyslog server | Remote logging server | . Bluetooth Config . On Settings → Device configuration → Bluetooth, on nodes with Bluetooth. | Setting | Description | . | Bluetooth enabled | Enable/disable BLE radio | . | Pairing mode | Fixed PIN, Random PIN, or No PIN | . | Fixed PIN | PIN code for pairing. Must be exactly six digits — the field rejects anything else | . Security Config . On Settings → Security. The screen is grouped into cards: Packet authenticity, Direct Message Key (your node’s key pair), Admin Keys, Logs, and Administration. | Setting | Description | . | Public Key | Your node’s public key (read-only) | . | Admin Key | Keys permitted to administer this node remotely — up to three | . | Private Key | Your node’s private key (handle securely). Shown redacted when you are viewing another node over remote admin — the firmware doesn’t send it | . | Regenerate Private Key | Issues a new keypair for this node, behind a confirmation. Every peer that knew your old key must learn the new one | . | Admin Channel Enabled | ⚠️ Removed — now configured automatically when an admin key is set | . | Serial console | Serial console over the Stream API | . | Debug log API enabled | Output live debug logging over serial, and view and export position-redacted node logs over Bluetooth | . | Managed Mode | Locks the whole Configuration list, not just channels — every setting on the node becomes read-only and only an admin can change anything. Only selectable once an Admin Key is set | . | Backup Keys | Save an encrypted backup of the node’s keys on this phone (Android only, and only for your own node) | . | Restore Keys | Write the backed-up keys back to the node (available once a backup exists) | . | Delete Key Backup | Remove the stored key backup from this phone | . | Protection level | How unsigned or relayed packets are treated: Strict — Require authentication, Balanced — Prefer authenticated, or Compatible — Accept unsigned (requires supporting firmware; Strict asks for confirmation) | . Lockdown Mode . Lockdown encrypts the device’s storage and requires a passphrase for each connection. It needs supporting firmware; the row doesn’t appear otherwise. Enabling it asks you to set and confirm a passphrase, and to acknowledge that it locks the debug (SWD) port on hardware where the lockout takes effect. That part isn’t reversible from the app. Turning lockdown off later decrypts your storage and reboots the device, but the port stays locked. Reopening it takes a full chip erase with a debug probe, which destroys everything on the device. Alongside the passphrase you set the limits that end a session automatically: . | Field | What it does | . | Boots remaining | How many device boots the unlocked state survives | . | Hours until expiry | Wall-clock lifetime of the unlocked state | . | Session cap (minutes) | A per-boot uptime cap on the unlocked state. 0, the default, means no cap | . Once active, the row reads Active — storage encrypted, this connection authenticated when unlocked, or Active — enter your passphrase to unlock this connection when not. Lock Now ends the current session immediately. Repeated wrong passphrases are rate-limited with a back-off before you can try again. ⚠️ Warning: There is no passphrase recovery. Losing it means erasing the device to get it back, which destroys its keys, channels and settings. ",
    "url": "/Meshtastic-Android/main/en/user/settings-radio-user.html#configuration",
    
    "relUrl": "/en/user/settings-radio-user.html#configuration"
  },"4680": {
    "doc": "Settings — Radio & User",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — optional feature modules and device administration | Signal Meter — how modem presets affect signal quality thresholds | LoRa configuration — detailed LoRa settings reference on meshtastic.org | Initial configuration — region setup guide on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/en/user/settings-radio-user.html#related-topics",
    
    "relUrl": "/en/user/settings-radio-user.html#related-topics"
  },"4681": {
    "doc": "Settings — Radio & User",
    "title": "Settings — Radio & User",
    "content": " ",
    "url": "/Meshtastic-Android/main/en/user/settings-radio-user.html",
    
    "relUrl": "/en/user/settings-radio-user.html"
  },"4682": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "How the Meshtastic Signal Meter Works",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/signal-meter.html",
    
    "relUrl": "/sk-rSK/user/signal-meter.html"
  },"4683": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/sk-rSK/user/signal-meter.html#rssi-and-snr"
  },"4684": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/sk-rSK/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4685": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | Level | Bars | Criteria | Meaning | . | Dobrý | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | . | Primeraný | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | . | Zlý | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | . | Žiadny | 1 | more than 7.5 dB below limit | Far below the preset’s floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/sk-rSK/user/signal-meter.html#rating-signal-quality"
  },"4686": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/sk-rSK/user/signal-meter.html#diagnosing-local-interference"
  },"4687": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Where Signal Information Appears",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Traceroute — per-hop signal quality for each relay node | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/signal-meter.html#where-signal-information-appears",
    
    "relUrl": "/sk-rSK/user/signal-meter.html#where-signal-information-appears"
  },"4688": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Related Topics",
    "content": ". | Nodes — where signal bars appear in the node list | Node Metrics — SNR/RSSI history and the per-node signal quality reference | Settings — Radio & User — modem presets and their SNR limits | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/signal-meter.html#related-topics",
    
    "relUrl": "/sk-rSK/user/signal-meter.html#related-topics"
  },"4689": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "How the Meshtastic Signal Meter Works",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/signal-meter.html",
    
    "relUrl": "/be-rBY/user/signal-meter.html"
  },"4690": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/be-rBY/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/be-rBY/user/signal-meter.html#rssi-and-snr"
  },"4691": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/be-rBY/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/be-rBY/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4692": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | Level | Bars | Criteria | Meaning | . | Good | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | . | Fair | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | . | Bad | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | . | Нічога | 1 | more than 7.5 dB below limit | Far below the preset’s floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/be-rBY/user/signal-meter.html#rating-signal-quality"
  },"4693": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/be-rBY/user/signal-meter.html#diagnosing-local-interference"
  },"4694": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Where Signal Information Appears",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Traceroute — per-hop signal quality for each relay node | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/signal-meter.html#where-signal-information-appears",
    
    "relUrl": "/be-rBY/user/signal-meter.html#where-signal-information-appears"
  },"4695": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Related Topics",
    "content": ". | Nodes — where signal bars appear in the node list | Node Metrics — SNR/RSSI history and the per-node signal quality reference | Settings — Radio & User — modem presets and their SNR limits | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/signal-meter.html#related-topics",
    
    "relUrl": "/be-rBY/user/signal-meter.html#related-topics"
  },"4696": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "How the Meshtastic Signal Meter Works",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/signal-meter.html",
    
    "relUrl": "/it-rIT/user/signal-meter.html"
  },"4697": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/it-rIT/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/it-rIT/user/signal-meter.html#rssi-and-snr"
  },"4698": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/it-rIT/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/it-rIT/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4699": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | Level | Bars | Criteria | Meaning | . | Buono | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | . | Discreto | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | . | Scarso | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | . | Nessuno | 1 | more than 7.5 dB below limit | Far below the preset’s floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/it-rIT/user/signal-meter.html#rating-signal-quality"
  },"4700": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/it-rIT/user/signal-meter.html#diagnosing-local-interference"
  },"4701": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Where Signal Information Appears",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Traceroute — per-hop signal quality for each relay node | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/signal-meter.html#where-signal-information-appears",
    
    "relUrl": "/it-rIT/user/signal-meter.html#where-signal-information-appears"
  },"4702": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Related Topics",
    "content": ". | Nodes — where signal bars appear in the node list | Node Metrics — SNR/RSSI history and the per-node signal quality reference | Settings — Radio & User — modem presets and their SNR limits | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/signal-meter.html#related-topics",
    
    "relUrl": "/it-rIT/user/signal-meter.html#related-topics"
  },"4703": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "How the Meshtastic Signal Meter Works",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/es-rES/user/signal-meter.html",
    
    "relUrl": "/es-rES/user/signal-meter.html"
  },"4704": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/es-rES/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/es-rES/user/signal-meter.html#rssi-and-snr"
  },"4705": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/es-rES/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/es-rES/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4706": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | Level | Bars | Criteria | Meaning | . | Bien | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | . | Aceptable | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | . | Mal | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | . | Ninguna | 1 | more than 7.5 dB below limit | Far below the preset’s floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/es-rES/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/es-rES/user/signal-meter.html#rating-signal-quality"
  },"4707": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/es-rES/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/es-rES/user/signal-meter.html#diagnosing-local-interference"
  },"4708": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Where Signal Information Appears",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Traceroute — per-hop signal quality for each relay node | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/signal-meter.html#where-signal-information-appears",
    
    "relUrl": "/es-rES/user/signal-meter.html#where-signal-information-appears"
  },"4709": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Related Topics",
    "content": ". | Nodes — where signal bars appear in the node list | Node Metrics — SNR/RSSI history and the per-node signal quality reference | Settings — Radio & User — modem presets and their SNR limits | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/signal-meter.html#related-topics",
    
    "relUrl": "/es-rES/user/signal-meter.html#related-topics"
  },"4710": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "How the Meshtastic Signal Meter Works",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/signal-meter.html",
    
    "relUrl": "/sl-rSI/user/signal-meter.html"
  },"4711": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/sl-rSI/user/signal-meter.html#rssi-and-snr"
  },"4712": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/sl-rSI/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4713": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | Level | Bars | Criteria | Meaning | . | Dober | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | . | Precejšen | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | . | Slab | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | . | Brez | 1 | more than 7.5 dB below limit | Far below the preset’s floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/sl-rSI/user/signal-meter.html#rating-signal-quality"
  },"4714": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/sl-rSI/user/signal-meter.html#diagnosing-local-interference"
  },"4715": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Where Signal Information Appears",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Traceroute — per-hop signal quality for each relay node | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/signal-meter.html#where-signal-information-appears",
    
    "relUrl": "/sl-rSI/user/signal-meter.html#where-signal-information-appears"
  },"4716": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Related Topics",
    "content": ". | Nodes — where signal bars appear in the node list | Node Metrics — SNR/RSSI history and the per-node signal quality reference | Settings — Radio & User — modem presets and their SNR limits | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/signal-meter.html#related-topics",
    
    "relUrl": "/sl-rSI/user/signal-meter.html#related-topics"
  },"4717": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "How the Meshtastic Signal Meter Works",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/signal-meter.html",
    
    "relUrl": "/no-rNO/user/signal-meter.html"
  },"4718": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/no-rNO/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/no-rNO/user/signal-meter.html#rssi-and-snr"
  },"4719": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/no-rNO/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/no-rNO/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4720": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | Level | Bars | Criteria | Meaning | . | Godt | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | . | Middelmådig | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | . | Dårlig | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | . | Ingen | 1 | more than 7.5 dB below limit | Far below the preset’s floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/no-rNO/user/signal-meter.html#rating-signal-quality"
  },"4721": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/no-rNO/user/signal-meter.html#diagnosing-local-interference"
  },"4722": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Where Signal Information Appears",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Traceroute — per-hop signal quality for each relay node | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/signal-meter.html#where-signal-information-appears",
    
    "relUrl": "/no-rNO/user/signal-meter.html#where-signal-information-appears"
  },"4723": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Related Topics",
    "content": ". | Nodes — where signal bars appear in the node list | Node Metrics — SNR/RSSI history and the per-node signal quality reference | Settings — Radio & User — modem presets and their SNR limits | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/signal-meter.html#related-topics",
    
    "relUrl": "/no-rNO/user/signal-meter.html#related-topics"
  },"4724": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "How the Meshtastic Signal Meter Works",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/signal-meter.html",
    
    "relUrl": "/hu-rHU/user/signal-meter.html"
  },"4725": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/hu-rHU/user/signal-meter.html#rssi-and-snr"
  },"4726": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/hu-rHU/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4727": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | Level | Bars | Criteria | Meaning | . | Jó | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | . | Megfelelő | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | . | Rossz | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | . | Semmi | 1 | more than 7.5 dB below limit | Far below the preset’s floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/hu-rHU/user/signal-meter.html#rating-signal-quality"
  },"4728": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/hu-rHU/user/signal-meter.html#diagnosing-local-interference"
  },"4729": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Where Signal Information Appears",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Traceroute — per-hop signal quality for each relay node | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/signal-meter.html#where-signal-information-appears",
    
    "relUrl": "/hu-rHU/user/signal-meter.html#where-signal-information-appears"
  },"4730": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Related Topics",
    "content": ". | Nodes — where signal bars appear in the node list | Node Metrics — SNR/RSSI history and the per-node signal quality reference | Settings — Radio & User — modem presets and their SNR limits | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/signal-meter.html#related-topics",
    
    "relUrl": "/hu-rHU/user/signal-meter.html#related-topics"
  },"4731": {
    "doc": "Как работает измеритель сигнала Meshtastic",
    "title": "Как работает измеритель сигнала Meshtastic",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/signal-meter.html",
    
    "relUrl": "/ru-rRU/user/signal-meter.html"
  },"4732": {
    "doc": "Как работает измеритель сигнала Meshtastic",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/ru-rRU/user/signal-meter.html#rssi-and-snr"
  },"4733": {
    "doc": "Как работает измеритель сигнала Meshtastic",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/ru-rRU/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4734": {
    "doc": "Как работает измеритель сигнала Meshtastic",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | Уровень | Деления | Критерии | Значение | . | Хороший | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | . | Средний | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | . | Плохой | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | . | Отсутствует | 1 | more than 7.5 dB below limit | Far below the preset’s floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/ru-rRU/user/signal-meter.html#rating-signal-quality"
  },"4735": {
    "doc": "Как работает измеритель сигнала Meshtastic",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/ru-rRU/user/signal-meter.html#diagnosing-local-interference"
  },"4736": {
    "doc": "Как работает измеритель сигнала Meshtastic",
    "title": "Где появляется информация о сигнале",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Трассировка — качество сигнала на каждой промежуточной ноде | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/signal-meter.html#%D0%B3%D0%B4%D0%B5-%D0%BF%D0%BE%D1%8F%D0%B2%D0%BB%D1%8F%D0%B5%D1%82%D1%81%D1%8F-%D0%B8%D0%BD%D1%84%D0%BE%D1%80%D0%BC%D0%B0%D1%86%D0%B8%D1%8F-%D0%BE-%D1%81%D0%B8%D0%B3%D0%BD%D0%B0%D0%BB%D0%B5",
    
    "relUrl": "/ru-rRU/user/signal-meter.html#где-появляется-информация-о-сигнале"
  },"4737": {
    "doc": "Как работает измеритель сигнала Meshtastic",
    "title": "Связанные темы",
    "content": ". | Ноды — там, где в списке нод появляются индикаторы сигнала | Метрики ноды — история SNR/RSSI и эталон качества сигнала для каждой ноды | Настройки — Радио и Пользователь — пресеты модема и их пределы SNR | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/signal-meter.html#%D1%81%D0%B2%D1%8F%D0%B7%D0%B0%D0%BD%D0%BD%D1%8B%D0%B5-%D1%82%D0%B5%D0%BC%D1%8B",
    
    "relUrl": "/ru-rRU/user/signal-meter.html#связанные-темы"
  },"4738": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "How the Meshtastic Signal Meter Works",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/signal-meter.html",
    
    "relUrl": "/cs-rCZ/user/signal-meter.html"
  },"4739": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/cs-rCZ/user/signal-meter.html#rssi-and-snr"
  },"4740": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/cs-rCZ/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4741": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | Level | Bars | Criteria | Meaning | . | Silný | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | . | Slabý | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | . | Špatný | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | . | Žádný | 1 | more than 7.5 dB below limit | Far below the preset’s floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/cs-rCZ/user/signal-meter.html#rating-signal-quality"
  },"4742": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/cs-rCZ/user/signal-meter.html#diagnosing-local-interference"
  },"4743": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Where Signal Information Appears",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Traceroute — per-hop signal quality for each relay node | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/signal-meter.html#where-signal-information-appears",
    
    "relUrl": "/cs-rCZ/user/signal-meter.html#where-signal-information-appears"
  },"4744": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Related Topics",
    "content": ". | Nodes — where signal bars appear in the node list | Node Metrics — SNR/RSSI history and the per-node signal quality reference | Settings — Radio & User — modem presets and their SNR limits | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/signal-meter.html#related-topics",
    
    "relUrl": "/cs-rCZ/user/signal-meter.html#related-topics"
  },"4745": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "How the Meshtastic Signal Meter Works",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/signal-meter.html",
    
    "relUrl": "/bg-rBG/user/signal-meter.html"
  },"4746": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/bg-rBG/user/signal-meter.html#rssi-and-snr"
  },"4747": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/bg-rBG/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4748": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | Level | Bars | Criteria | Meaning | . | Добър | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | . | Задоволителен | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | . | Лош | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | . | Няма | 1 | more than 7.5 dB below limit | Far below the preset’s floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/bg-rBG/user/signal-meter.html#rating-signal-quality"
  },"4749": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/bg-rBG/user/signal-meter.html#diagnosing-local-interference"
  },"4750": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Where Signal Information Appears",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Traceroute — per-hop signal quality for each relay node | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/signal-meter.html#where-signal-information-appears",
    
    "relUrl": "/bg-rBG/user/signal-meter.html#where-signal-information-appears"
  },"4751": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Related Topics",
    "content": ". | Nodes — where signal bars appear in the node list | Node Metrics — SNR/RSSI history and the per-node signal quality reference | Settings — Radio & User — modem presets and their SNR limits | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/signal-meter.html#related-topics",
    
    "relUrl": "/bg-rBG/user/signal-meter.html#related-topics"
  },"4752": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "How the Meshtastic Signal Meter Works",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/signal-meter.html",
    
    "relUrl": "/ga-rIE/user/signal-meter.html"
  },"4753": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/ga-rIE/user/signal-meter.html#rssi-and-snr"
  },"4754": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/ga-rIE/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4755": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | Level | Bars | Criteria | Meaning | . | Maith | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | . | Ceart go leor | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | . | Go dona | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | . | Ní dhéanfaidh sé | 1 | more than 7.5 dB below limit | Far below the preset’s floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/ga-rIE/user/signal-meter.html#rating-signal-quality"
  },"4756": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/ga-rIE/user/signal-meter.html#diagnosing-local-interference"
  },"4757": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Where Signal Information Appears",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Traceroute — per-hop signal quality for each relay node | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/signal-meter.html#where-signal-information-appears",
    
    "relUrl": "/ga-rIE/user/signal-meter.html#where-signal-information-appears"
  },"4758": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Related Topics",
    "content": ". | Nodes — where signal bars appear in the node list | Node Metrics — SNR/RSSI history and the per-node signal quality reference | Settings — Radio & User — modem presets and their SNR limits | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/signal-meter.html#related-topics",
    
    "relUrl": "/ga-rIE/user/signal-meter.html#related-topics"
  },"4759": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "How the Meshtastic Signal Meter Works",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/signal-meter.html",
    
    "relUrl": "/fr-rCA/user/signal-meter.html"
  },"4760": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/fr-rCA/user/signal-meter.html#rssi-and-snr"
  },"4761": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/fr-rCA/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4762": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | Level | Bars | Criteria | Meaning | . | Bon | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | . | Passable | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | . | Mauvais | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | . | Aucun | 1 | more than 7.5 dB below limit | Far below the preset’s floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/fr-rCA/user/signal-meter.html#rating-signal-quality"
  },"4763": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/fr-rCA/user/signal-meter.html#diagnosing-local-interference"
  },"4764": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Where Signal Information Appears",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Traceroute — per-hop signal quality for each relay node | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/signal-meter.html#where-signal-information-appears",
    
    "relUrl": "/fr-rCA/user/signal-meter.html#where-signal-information-appears"
  },"4765": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Related Topics",
    "content": ". | Nodes — where signal bars appear in the node list | Node Metrics — SNR/RSSI history and the per-node signal quality reference | Settings — Radio & User — modem presets and their SNR limits | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/signal-meter.html#related-topics",
    
    "relUrl": "/fr-rCA/user/signal-meter.html#related-topics"
  },"4766": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "How the Meshtastic Signal Meter Works",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/srp/user/signal-meter.html",
    
    "relUrl": "/srp/user/signal-meter.html"
  },"4767": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/srp/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/srp/user/signal-meter.html#rssi-and-snr"
  },"4768": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/srp/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/srp/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4769": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | Ниво | Bars | Criteria | Meaning | . | Добро | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | . | Прихватљив | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | . | Лош | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | . | Ништа | 1 | more than 7.5 dB below limit | Far below the preset’s floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/srp/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/srp/user/signal-meter.html#rating-signal-quality"
  },"4770": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/srp/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/srp/user/signal-meter.html#diagnosing-local-interference"
  },"4771": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Where Signal Information Appears",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Traceroute — per-hop signal quality for each relay node | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/srp/user/signal-meter.html#where-signal-information-appears",
    
    "relUrl": "/srp/user/signal-meter.html#where-signal-information-appears"
  },"4772": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Related Topics",
    "content": ". | Nodes — where signal bars appear in the node list | Node Metrics — SNR/RSSI history and the per-node signal quality reference | Settings — Radio & User — modem presets and their SNR limits | . ",
    "url": "/Meshtastic-Android/main/srp/user/signal-meter.html#related-topics",
    
    "relUrl": "/srp/user/signal-meter.html#related-topics"
  },"4773": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "How the Meshtastic Signal Meter Works",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/signal-meter.html",
    
    "relUrl": "/ca-rES/user/signal-meter.html"
  },"4774": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/ca-rES/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/ca-rES/user/signal-meter.html#rssi-and-snr"
  },"4775": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/ca-rES/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/ca-rES/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4776": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | Level | Bars | Criteria | Meaning | . | Good | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | . | Fair | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | . | Bad | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | . | None | 1 | more than 7.5 dB below limit | Far below the preset’s floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/ca-rES/user/signal-meter.html#rating-signal-quality"
  },"4777": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/ca-rES/user/signal-meter.html#diagnosing-local-interference"
  },"4778": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Where Signal Information Appears",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Traceroute — per-hop signal quality for each relay node | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/signal-meter.html#where-signal-information-appears",
    
    "relUrl": "/ca-rES/user/signal-meter.html#where-signal-information-appears"
  },"4779": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Related Topics",
    "content": ". | Nodes — where signal bars appear in the node list | Node Metrics — SNR/RSSI history and the per-node signal quality reference | Settings — Radio & User — modem presets and their SNR limits | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/signal-meter.html#related-topics",
    
    "relUrl": "/ca-rES/user/signal-meter.html#related-topics"
  },"4780": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "How the Meshtastic Signal Meter Works",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/signal-meter.html",
    
    "relUrl": "/ko-rKR/user/signal-meter.html"
  },"4781": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/ko-rKR/user/signal-meter.html#rssi-and-snr"
  },"4782": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/ko-rKR/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4783": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | Level | Bars | Criteria | Meaning | . | 좋음 | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | . | 보통 | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | . | 나쁨 | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | . | 없음 | 1 | more than 7.5 dB below limit | Far below the preset’s floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/ko-rKR/user/signal-meter.html#rating-signal-quality"
  },"4784": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/ko-rKR/user/signal-meter.html#diagnosing-local-interference"
  },"4785": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Where Signal Information Appears",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Traceroute — per-hop signal quality for each relay node | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/signal-meter.html#where-signal-information-appears",
    
    "relUrl": "/ko-rKR/user/signal-meter.html#where-signal-information-appears"
  },"4786": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Related Topics",
    "content": ". | Nodes — where signal bars appear in the node list | Node Metrics — SNR/RSSI history and the per-node signal quality reference | Settings — Radio & User — modem presets and their SNR limits | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/signal-meter.html#related-topics",
    
    "relUrl": "/ko-rKR/user/signal-meter.html#related-topics"
  },"4787": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "How the Meshtastic Signal Meter Works",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/signal-meter.html",
    
    "relUrl": "/sv-rSE/user/signal-meter.html"
  },"4788": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/sv-rSE/user/signal-meter.html#rssi-and-snr"
  },"4789": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/sv-rSE/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4790": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | Level | Bars | Criteria | Meaning | . | Bra | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | . | Ok | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | . | Dålig | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | . | Ingen | 1 | more than 7.5 dB below limit | Far below the preset’s floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/sv-rSE/user/signal-meter.html#rating-signal-quality"
  },"4791": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/sv-rSE/user/signal-meter.html#diagnosing-local-interference"
  },"4792": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Where Signal Information Appears",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Traceroute — per-hop signal quality for each relay node | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/signal-meter.html#where-signal-information-appears",
    
    "relUrl": "/sv-rSE/user/signal-meter.html#where-signal-information-appears"
  },"4793": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Related Topics",
    "content": ". | Nodes — where signal bars appear in the node list | Node Metrics — SNR/RSSI history and the per-node signal quality reference | Settings — Radio & User — modem presets and their SNR limits | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/signal-meter.html#related-topics",
    
    "relUrl": "/sv-rSE/user/signal-meter.html#related-topics"
  },"4794": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "How the Meshtastic Signal Meter Works",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/signal-meter.html",
    
    "relUrl": "/ht-rHT/user/signal-meter.html"
  },"4795": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/ht-rHT/user/signal-meter.html#rssi-and-snr"
  },"4796": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/ht-rHT/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4797": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | Level | Bars | Criteria | Meaning | . | Bon | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | . | Mwayen | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | . | Move | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | . | Pa gen | 1 | more than 7.5 dB below limit | Far below the preset’s floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/ht-rHT/user/signal-meter.html#rating-signal-quality"
  },"4798": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/ht-rHT/user/signal-meter.html#diagnosing-local-interference"
  },"4799": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Where Signal Information Appears",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Traceroute — per-hop signal quality for each relay node | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/signal-meter.html#where-signal-information-appears",
    
    "relUrl": "/ht-rHT/user/signal-meter.html#where-signal-information-appears"
  },"4800": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Related Topics",
    "content": ". | Nodes — where signal bars appear in the node list | Node Metrics — SNR/RSSI history and the per-node signal quality reference | Settings — Radio & User — modem presets and their SNR limits | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/signal-meter.html#related-topics",
    
    "relUrl": "/ht-rHT/user/signal-meter.html#related-topics"
  },"4801": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "How the Meshtastic Signal Meter Works",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/signal-meter.html",
    
    "relUrl": "/sr-rLatn/user/signal-meter.html"
  },"4802": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/sr-rLatn/user/signal-meter.html#rssi-and-snr"
  },"4803": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/sr-rLatn/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4804": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | Ниво | Bars | Criteria | Meaning | . | Dobro | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | . | Prihvatljiv | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | . | Loš | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | . | Bez | 1 | more than 7.5 dB below limit | Far below the preset’s floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/sr-rLatn/user/signal-meter.html#rating-signal-quality"
  },"4805": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/sr-rLatn/user/signal-meter.html#diagnosing-local-interference"
  },"4806": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Where Signal Information Appears",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Traceroute — per-hop signal quality for each relay node | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/signal-meter.html#where-signal-information-appears",
    
    "relUrl": "/sr-rLatn/user/signal-meter.html#where-signal-information-appears"
  },"4807": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Related Topics",
    "content": ". | Nodes — where signal bars appear in the node list | Node Metrics — SNR/RSSI history and the per-node signal quality reference | Settings — Radio & User — modem presets and their SNR limits | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/signal-meter.html#related-topics",
    
    "relUrl": "/sr-rLatn/user/signal-meter.html#related-topics"
  },"4808": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "How the Meshtastic Signal Meter Works",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/signal-meter.html",
    
    "relUrl": "/nl-rNL/user/signal-meter.html"
  },"4809": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/nl-rNL/user/signal-meter.html#rssi-and-snr"
  },"4810": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/nl-rNL/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4811": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | Level | Bars | Criteria | Meaning | . | Goed | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | . | Matig | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | . | Slecht | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | . | Geen | 1 | more than 7.5 dB below limit | Far below the preset’s floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/nl-rNL/user/signal-meter.html#rating-signal-quality"
  },"4812": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/nl-rNL/user/signal-meter.html#diagnosing-local-interference"
  },"4813": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Where Signal Information Appears",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Traceroute — per-hop signal quality for each relay node | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/signal-meter.html#where-signal-information-appears",
    
    "relUrl": "/nl-rNL/user/signal-meter.html#where-signal-information-appears"
  },"4814": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Related Topics",
    "content": ". | Nodes — where signal bars appear in the node list | Node Metrics — SNR/RSSI history and the per-node signal quality reference | Settings — Radio & User — modem presets and their SNR limits | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/signal-meter.html#related-topics",
    
    "relUrl": "/nl-rNL/user/signal-meter.html#related-topics"
  },"4815": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "How the Meshtastic Signal Meter Works",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/signal-meter.html",
    
    "relUrl": "/uk-rUA/user/signal-meter.html"
  },"4816": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/uk-rUA/user/signal-meter.html#rssi-and-snr"
  },"4817": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/uk-rUA/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4818": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | Level | Bars | Criteria | Meaning | . | Хороший | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | . | Задовільний | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | . | Поганий | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | . | Жоден | 1 | more than 7.5 dB below limit | Far below the preset’s floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/uk-rUA/user/signal-meter.html#rating-signal-quality"
  },"4819": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/uk-rUA/user/signal-meter.html#diagnosing-local-interference"
  },"4820": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Where Signal Information Appears",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Traceroute — per-hop signal quality for each relay node | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/signal-meter.html#where-signal-information-appears",
    
    "relUrl": "/uk-rUA/user/signal-meter.html#where-signal-information-appears"
  },"4821": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Related Topics",
    "content": ". | Nodes — where signal bars appear in the node list | Node Metrics — SNR/RSSI history and the per-node signal quality reference | Settings — Radio & User — modem presets and their SNR limits | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/signal-meter.html#related-topics",
    
    "relUrl": "/uk-rUA/user/signal-meter.html#related-topics"
  },"4822": {
    "doc": "Kuinka Meshtastic-signaalimittari toimii",
    "title": "Kuinka Meshtastic-signaalimittari toimii",
    "content": "Meshtasticin signaalimittari — radion vieressä näkyvät palkit tai tilaväri — lasketaan eri tavalla kuin matkapuhelimen tai WiFi-reitittimen signaalipalkit. Tällä sivulla kerrotaan, mitä se mittaa ja miksi sama lukema voi tarkoittaa eri asiaa toisessa esiasetuksessa. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/signal-meter.html",
    
    "relUrl": "/fi-rFI/user/signal-meter.html"
  },"4823": {
    "doc": "Kuinka Meshtastic-signaalimittari toimii",
    "title": "RSSI ja SNR",
    "content": "Joka kerta kun LoRa-radio vastaanottaa viestin, se raportoi kaksi mittausta: . | RSSI (Received Signal Strength Indicator) — antenniin saapuvan signaalin raakateho. | SNR (Signal-to-Noise Ratio) — kuinka paljon signaali erottuu taustakohinan yläpuolelle. | . 💡 Vinkki: Ajattele RSSI:tä ystävän puheen voimakkuutena ja SNR:ää siinä, kuinka helposti erotat hänen äänensä huoneen taustamelusta. Ystävä, joka huutaa rock-konsertissa, voi kuulua kovaa (korkea RSSI) mutta olla epäselvä (huono SNR), kun taas hiljaisessa kirjastossa kuiskattu puhe voi olla vaimea (matala RSSI) mutta täysin selkeä (erinomainen SNR). ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/signal-meter.html#rssi-ja-snr",
    
    "relUrl": "/fi-rFI/user/signal-meter.html#rssi-ja-snr"
  },"4824": {
    "doc": "Kuinka Meshtastic-signaalimittari toimii",
    "title": "Vastaanotto kohinatason alapuolelta",
    "content": "Tavalliset radiot, kuten FM tai WiFi, menettävät signaalin kohinaan, kun taustakohina on sitä voimakkaampi (negatiivinen SNR). LoRan hajaspektrimodulaatio mahdollistaa signaalin vastaanottamisen kohinasta myös silloin, kun kohina on signaalia voimakkaampi, joten negatiiviset SNR-arvot ovat Meshtasticissa tavallisia ja odotettuja — esimerkiksi −10 dB tarkoittaa, että signaali on 10 desibeliä taustakohinaa heikompi. Jokaisella modeemiesiasetuksella on SNR-raja: pienin SNR-arvo, jolla kyseinen esiasetus pystyy vielä purkamaan viestin. Hitaammat esiasetukset sietävät heikomman ja kohinaisemman signaalin (negatiivisempi raja, pidempi kantama); nopeammat esiasetukset tarvitsevat voimakkaamman signaalin (vähemmän negatiivinen raja, lyhyempi kantama). ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/signal-meter.html#vastaanotto-kohinatason-alapuolelta",
    
    "relUrl": "/fi-rFI/user/signal-meter.html#vastaanotto-kohinatason-alapuolelta"
  },"4825": {
    "doc": "Kuinka Meshtastic-signaalimittari toimii",
    "title": "Signaalin laadun arviointi",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Koska arviointi suhteutetaan esiasetukseen, sama SNR saa eri arvioinnin eri esiasetuksilla. SNR −16 dB arvioidaan Hyväksi Long Fast -esiasetuksella (SNR-raja −17.5 dB), mutta Ei mitään -tasolle Short Fast -esiasetuksella (SNR-raja −7.5 dB). Jos raja tarkoittaa käytössä olevan esiasetuksen SNR-rajaa: . | Taso | Palkit | Kriteerit | Merkitys | . | Hyvä | Full | SNR yli rajan | Selvästi demodulointirajan yläpuolella — yhteys on hyvä. | . | Kohtalainen | 3 | alle 5.5 dB rajan alapuolella | Voidaan vielä purkaa, mutta lähellä rajaa. | . | Huono | 2 | 5.5–7.5 dB rajan alapuolella | Esiasetuksen vastaanottokyvyn rajalla. | . | ei mitään | 1 | yli 7.5 dB rajan alapuolella | Selvästi esiasetuksen rajan alapuolella; tältä radiolta tulevia lisäpaketteja todennäköisesti katoaa. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/signal-meter.html#signaalin-laadun-arviointi",
    
    "relUrl": "/fi-rFI/user/signal-meter.html#signaalin-laadun-arviointi"
  },"4826": {
    "doc": "Kuinka Meshtastic-signaalimittari toimii",
    "title": "Paikallisten häiriöiden tunnistaminen",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. Halpa virtalähde, häiriöinen tietokone tai lähellä oleva lähetin voi aiheuttaa niin paljon kohinaa, että muuten vahva signaali peittyy. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/signal-meter.html#paikallisten-h%C3%A4iri%C3%B6iden-tunnistaminen",
    
    "relUrl": "/fi-rFI/user/signal-meter.html#paikallisten-häiriöiden-tunnistaminen"
  },"4827": {
    "doc": "Kuinka Meshtastic-signaalimittari toimii",
    "title": "Missä signaalitieto näkyy",
    "content": "Sovelluksessa signaalitiedot näkyvät useassa paikassa: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Reitinselvitys — signaalin laatu jokaisessa välivaiheessa jokaiselle välittävälle radiolle | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/signal-meter.html#miss%C3%A4-signaalitieto-n%C3%A4kyy",
    
    "relUrl": "/fi-rFI/user/signal-meter.html#missä-signaalitieto-näkyy"
  },"4828": {
    "doc": "Kuinka Meshtastic-signaalimittari toimii",
    "title": "Aiheeseen liittyvät aiheet",
    "content": ". | Radiot — missä signaalipalkit näkyvät radioluettelossa | Radion mittarit — SNR ja RSSI-historia ja radion signaalin laadun viitearvot | Asetukset — Radio ja käyttäjä — modeemiesiasetukset ja niiden SNR-rajat | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/signal-meter.html#aiheeseen-liittyv%C3%A4t-aiheet",
    
    "relUrl": "/fi-rFI/user/signal-meter.html#aiheeseen-liittyvät-aiheet"
  },"4829": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "How the Meshtastic Signal Meter Works",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/signal-meter.html",
    
    "relUrl": "/is-rIS/user/signal-meter.html"
  },"4830": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/is-rIS/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/is-rIS/user/signal-meter.html#rssi-and-snr"
  },"4831": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/is-rIS/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/is-rIS/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4832": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | Level | Bars | Criteria | Meaning | . | Good | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | . | Fair | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | . | Bad | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | . | None | 1 | more than 7.5 dB below limit | Far below the preset’s floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/is-rIS/user/signal-meter.html#rating-signal-quality"
  },"4833": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/is-rIS/user/signal-meter.html#diagnosing-local-interference"
  },"4834": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Where Signal Information Appears",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Traceroute — per-hop signal quality for each relay node | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/signal-meter.html#where-signal-information-appears",
    
    "relUrl": "/is-rIS/user/signal-meter.html#where-signal-information-appears"
  },"4835": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Related Topics",
    "content": ". | Nodes — where signal bars appear in the node list | Node Metrics — SNR/RSSI history and the per-node signal quality reference | Settings — Radio & User — modem presets and their SNR limits | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/signal-meter.html#related-topics",
    
    "relUrl": "/is-rIS/user/signal-meter.html#related-topics"
  },"4836": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "How the Meshtastic Signal Meter Works",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/signal-meter.html",
    
    "relUrl": "/lt-rLT/user/signal-meter.html"
  },"4837": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/lt-rLT/user/signal-meter.html#rssi-and-snr"
  },"4838": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/lt-rLT/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4839": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | Level | Bars | Criteria | Meaning | . | Geras | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | . | Pakankamas | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | . | Silpnas | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | . | Nėra | 1 | more than 7.5 dB below limit | Far below the preset’s floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/lt-rLT/user/signal-meter.html#rating-signal-quality"
  },"4840": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/lt-rLT/user/signal-meter.html#diagnosing-local-interference"
  },"4841": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Where Signal Information Appears",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Traceroute — per-hop signal quality for each relay node | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/signal-meter.html#where-signal-information-appears",
    
    "relUrl": "/lt-rLT/user/signal-meter.html#where-signal-information-appears"
  },"4842": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Related Topics",
    "content": ". | Nodes — where signal bars appear in the node list | Node Metrics — SNR/RSSI history and the per-node signal quality reference | Settings — Radio & User — modem presets and their SNR limits | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/signal-meter.html#related-topics",
    
    "relUrl": "/lt-rLT/user/signal-meter.html#related-topics"
  },"4843": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "How the Meshtastic Signal Meter Works",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/signal-meter.html",
    
    "relUrl": "/gl-rES/user/signal-meter.html"
  },"4844": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/gl-rES/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/gl-rES/user/signal-meter.html#rssi-and-snr"
  },"4845": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/gl-rES/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/gl-rES/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4846": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | Level | Bars | Criteria | Meaning | . | Good | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | . | Fair | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | . | Bad | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | . | None | 1 | more than 7.5 dB below limit | Far below the preset’s floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/gl-rES/user/signal-meter.html#rating-signal-quality"
  },"4847": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/gl-rES/user/signal-meter.html#diagnosing-local-interference"
  },"4848": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Where Signal Information Appears",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Traceroute — per-hop signal quality for each relay node | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/signal-meter.html#where-signal-information-appears",
    
    "relUrl": "/gl-rES/user/signal-meter.html#where-signal-information-appears"
  },"4849": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Related Topics",
    "content": ". | Nodes — where signal bars appear in the node list | Node Metrics — SNR/RSSI history and the per-node signal quality reference | Settings — Radio & User — modem presets and their SNR limits | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/signal-meter.html#related-topics",
    
    "relUrl": "/gl-rES/user/signal-meter.html#related-topics"
  },"4850": {
    "doc": "Meshtastic の信号メーターの仕組み",
    "title": "Meshtastic の信号メーターの仕組み",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/signal-meter.html",
    
    "relUrl": "/ja-rJP/user/signal-meter.html"
  },"4851": {
    "doc": "Meshtastic の信号メーターの仕組み",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/ja-rJP/user/signal-meter.html#rssi-and-snr"
  },"4852": {
    "doc": "Meshtastic の信号メーターの仕組み",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/ja-rJP/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4853": {
    "doc": "Meshtastic の信号メーターの仕組み",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | レベル | バー | 基準 | 意味 | . | 良 | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | . | 普通 | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | . | 不良 | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | . | なし | 1 | more than 7.5 dB below limit | Far below the preset’s floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/ja-rJP/user/signal-meter.html#rating-signal-quality"
  },"4854": {
    "doc": "Meshtastic の信号メーターの仕組み",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/ja-rJP/user/signal-meter.html#diagnosing-local-interference"
  },"4855": {
    "doc": "Meshtastic の信号メーターの仕組み",
    "title": "信号情報が表示される場所",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | ルート追跡：各中継ノードの、ホップごとの信号品質 | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/signal-meter.html#%E4%BF%A1%E5%8F%B7%E6%83%85%E5%A0%B1%E3%81%8C%E8%A1%A8%E7%A4%BA%E3%81%95%E3%82%8C%E3%82%8B%E5%A0%B4%E6%89%80",
    
    "relUrl": "/ja-rJP/user/signal-meter.html#信号情報が表示される場所"
  },"4856": {
    "doc": "Meshtastic の信号メーターの仕組み",
    "title": "関連トピック",
    "content": ". | ノード：ノードリストで信号バーが表示される場所 | ノードメトリクス：SNR／RSSI の履歴と、ノードごとの信号品質の目安 | 設定：無線機とユーザー：モデムプリセットとその SNR 限界 | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/signal-meter.html#%E9%96%A2%E9%80%A3%E3%83%88%E3%83%94%E3%83%83%E3%82%AF",
    
    "relUrl": "/ja-rJP/user/signal-meter.html#関連トピック"
  },"4857": {
    "doc": "Wie das Meshtastic Signal Meter funktioniert",
    "title": "Wie das Meshtastic Signal Meter funktioniert",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/signal-meter.html",
    
    "relUrl": "/de-rDE/user/signal-meter.html"
  },"4858": {
    "doc": "Wie das Meshtastic Signal Meter funktioniert",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/de-rDE/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/de-rDE/user/signal-meter.html#rssi-and-snr"
  },"4859": {
    "doc": "Wie das Meshtastic Signal Meter funktioniert",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/de-rDE/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/de-rDE/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4860": {
    "doc": "Wie das Meshtastic Signal Meter funktioniert",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | Niveau | Balken | Kriterium | Bedeutung | . | Gut | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | . | Ordentliche Signalstärke | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | . | Schlecht | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | . | Keins | 1 | more than 7.5 dB below limit | Far below the preset’s floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/de-rDE/user/signal-meter.html#rating-signal-quality"
  },"4861": {
    "doc": "Wie das Meshtastic Signal Meter funktioniert",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/de-rDE/user/signal-meter.html#diagnosing-local-interference"
  },"4862": {
    "doc": "Wie das Meshtastic Signal Meter funktioniert",
    "title": "Where Signal Information Appears",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Traceroute — per-hop signal quality for each relay node | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/signal-meter.html#where-signal-information-appears",
    
    "relUrl": "/de-rDE/user/signal-meter.html#where-signal-information-appears"
  },"4863": {
    "doc": "Wie das Meshtastic Signal Meter funktioniert",
    "title": "Related Topics",
    "content": ". | Nodes — where signal bars appear in the node list | Node Metrics — SNR/RSSI history and the per-node signal quality reference | Settings — Radio & User — modem presets and their SNR limits | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/signal-meter.html#related-topics",
    
    "relUrl": "/de-rDE/user/signal-meter.html#related-topics"
  },"4864": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "How the Meshtastic Signal Meter Works",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/signal-meter.html",
    
    "relUrl": "/ar-rSA/user/signal-meter.html"
  },"4865": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/ar-rSA/user/signal-meter.html#rssi-and-snr"
  },"4866": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/ar-rSA/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4867": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | Level | Bars | Criteria | Meaning | . | جيد | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | . | مناسب | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | . | سيئ | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | . | لا يوجد | 1 | more than 7.5 dB below limit | Far below the preset’s floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/ar-rSA/user/signal-meter.html#rating-signal-quality"
  },"4868": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/ar-rSA/user/signal-meter.html#diagnosing-local-interference"
  },"4869": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Where Signal Information Appears",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Traceroute — per-hop signal quality for each relay node | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/signal-meter.html#where-signal-information-appears",
    
    "relUrl": "/ar-rSA/user/signal-meter.html#where-signal-information-appears"
  },"4870": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Related Topics",
    "content": ". | Nodes — where signal bars appear in the node list | Node Metrics — SNR/RSSI history and the per-node signal quality reference | Settings — Radio & User — modem presets and their SNR limits | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/signal-meter.html#related-topics",
    
    "relUrl": "/ar-rSA/user/signal-meter.html#related-topics"
  },"4871": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "How the Meshtastic Signal Meter Works",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/signal-meter.html",
    
    "relUrl": "/hr-rHR/user/signal-meter.html"
  },"4872": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/hr-rHR/user/signal-meter.html#rssi-and-snr"
  },"4873": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/hr-rHR/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4874": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | Level | Bars | Criteria | Meaning | . | Good | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | . | Fair | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | . | Bad | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | . | None | 1 | more than 7.5 dB below limit | Far below the preset’s floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/hr-rHR/user/signal-meter.html#rating-signal-quality"
  },"4875": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/hr-rHR/user/signal-meter.html#diagnosing-local-interference"
  },"4876": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Where Signal Information Appears",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Traceroute — per-hop signal quality for each relay node | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/signal-meter.html#where-signal-information-appears",
    
    "relUrl": "/hr-rHR/user/signal-meter.html#where-signal-information-appears"
  },"4877": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Related Topics",
    "content": ". | Nodes — where signal bars appear in the node list | Node Metrics — SNR/RSSI history and the per-node signal quality reference | Settings — Radio & User — modem presets and their SNR limits | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/signal-meter.html#related-topics",
    
    "relUrl": "/hr-rHR/user/signal-meter.html#related-topics"
  },"4878": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "How the Meshtastic Signal Meter Works",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/signal-meter.html",
    
    "relUrl": "/pt-rPT/user/signal-meter.html"
  },"4879": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/pt-rPT/user/signal-meter.html#rssi-and-snr"
  },"4880": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/pt-rPT/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4881": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | Level | Bars | Criteria | Meaning | . | Bom | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | . | Razoável | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | . | Mau | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | . | Nenhum | 1 | more than 7.5 dB below limit | Far below the preset’s floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/pt-rPT/user/signal-meter.html#rating-signal-quality"
  },"4882": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/pt-rPT/user/signal-meter.html#diagnosing-local-interference"
  },"4883": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Where Signal Information Appears",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Traceroute — per-hop signal quality for each relay node | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/signal-meter.html#where-signal-information-appears",
    
    "relUrl": "/pt-rPT/user/signal-meter.html#where-signal-information-appears"
  },"4884": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Related Topics",
    "content": ". | Nodes — where signal bars appear in the node list | Node Metrics — SNR/RSSI history and the per-node signal quality reference | Settings — Radio & User — modem presets and their SNR limits | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/signal-meter.html#related-topics",
    
    "relUrl": "/pt-rPT/user/signal-meter.html#related-topics"
  },"4885": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "How the Meshtastic Signal Meter Works",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/signal-meter.html",
    
    "relUrl": "/pl-rPL/user/signal-meter.html"
  },"4886": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/pl-rPL/user/signal-meter.html#rssi-and-snr"
  },"4887": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/pl-rPL/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4888": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | Level | Bars | Criteria | Meaning | . | dobry | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | . | wystarczający | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | . | słaby | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | . | Brak | 1 | more than 7.5 dB below limit | Far below the preset’s floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/pl-rPL/user/signal-meter.html#rating-signal-quality"
  },"4889": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/pl-rPL/user/signal-meter.html#diagnosing-local-interference"
  },"4890": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Where Signal Information Appears",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Traceroute — per-hop signal quality for each relay node | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/signal-meter.html#where-signal-information-appears",
    
    "relUrl": "/pl-rPL/user/signal-meter.html#where-signal-information-appears"
  },"4891": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Related Topics",
    "content": ". | Nodes — where signal bars appear in the node list | Node Metrics — SNR/RSSI history and the per-node signal quality reference | Settings — Radio & User — modem presets and their SNR limits | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/signal-meter.html#related-topics",
    
    "relUrl": "/pl-rPL/user/signal-meter.html#related-topics"
  },"4892": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "How the Meshtastic Signal Meter Works",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/signal-meter.html",
    
    "relUrl": "/zh-rCN/user/signal-meter.html"
  },"4893": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/zh-rCN/user/signal-meter.html#rssi-and-snr"
  },"4894": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/zh-rCN/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4895": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | Level | Bars | Criteria | Meaning | . | 良好 | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | . | 一般 | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | . | 差 | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | . | 无 | 1 | more than 7.5 dB below limit | Far below the preset’s floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/zh-rCN/user/signal-meter.html#rating-signal-quality"
  },"4896": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/zh-rCN/user/signal-meter.html#diagnosing-local-interference"
  },"4897": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Where Signal Information Appears",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Traceroute — per-hop signal quality for each relay node | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/signal-meter.html#where-signal-information-appears",
    
    "relUrl": "/zh-rCN/user/signal-meter.html#where-signal-information-appears"
  },"4898": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Related Topics",
    "content": ". | Nodes — where signal bars appear in the node list | Node Metrics — SNR/RSSI history and the per-node signal quality reference | Settings — Radio & User — modem presets and their SNR limits | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/signal-meter.html#related-topics",
    
    "relUrl": "/zh-rCN/user/signal-meter.html#related-topics"
  },"4899": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "How the Meshtastic Signal Meter Works",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/signal-meter.html",
    
    "relUrl": "/sq-rAL/user/signal-meter.html"
  },"4900": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/sq-rAL/user/signal-meter.html#rssi-and-snr"
  },"4901": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/sq-rAL/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4902": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | Level | Bars | Criteria | Meaning | . | Mirë | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | . | Mesatar | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | . | I Keq | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | . | Asnjë | 1 | more than 7.5 dB below limit | Far below the preset’s floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/sq-rAL/user/signal-meter.html#rating-signal-quality"
  },"4903": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/sq-rAL/user/signal-meter.html#diagnosing-local-interference"
  },"4904": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Where Signal Information Appears",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Traceroute — per-hop signal quality for each relay node | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/signal-meter.html#where-signal-information-appears",
    
    "relUrl": "/sq-rAL/user/signal-meter.html#where-signal-information-appears"
  },"4905": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Related Topics",
    "content": ". | Nodes — where signal bars appear in the node list | Node Metrics — SNR/RSSI history and the per-node signal quality reference | Settings — Radio & User — modem presets and their SNR limits | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/signal-meter.html#related-topics",
    
    "relUrl": "/sq-rAL/user/signal-meter.html#related-topics"
  },"4906": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "How the Meshtastic Signal Meter Works",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/signal-meter.html",
    
    "relUrl": "/zh-rTW/user/signal-meter.html"
  },"4907": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/zh-rTW/user/signal-meter.html#rssi-and-snr"
  },"4908": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/zh-rTW/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4909": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | Level | Bars | Criteria | Meaning | —– | ————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————– | ————————————————————– | ————————————————————————————————— | 良好 | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | 普通 | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | 不良 | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | 無 | 1. Overview Meshtastic is a project that allows you to use inexpensive LoRa radios as a long range, off-grid, decentralized communication platform. These radios, combined with readily available and very affordable microcontrollers like the ESP32, nRF52, and RP2040, create a network that can be used to send text messages, share locations, and more without relying on cellular or WiFi infrastructure. It's perfect for hiking, camping, or any situation where you need to stay connected beyond the reach of traditional networks. 2. Key Components``` . | LoRa Radios: These radios provide the long-range communication capabilities. The RAK Wireless modules are a popular choice. | Microcontrollers: The brains of the operation. ESP32, nRF52, and RP2040 are commonly used due to their low cost and capabilities. | GPS (Optional): For location sharing. Many devices, like the T-Beam, have built-in GPS. | Battery (Optional): For portable use. | Enclosure (Optional): To protect the hardware. 3. **Popular Devices** | T-Beam: A popular board with ESP32, LoRa, and GPS. | Heltec WiFi LoRa 32: Another popular ESP32-based board with LoRa. | LilyGo Boards: LilyGo offers a variety of ESP32 and nRF52 based boards with LoRa. 4. **Features** | Text Messaging: Send and receive text messages over the LoRa network. | Location Sharing: Share your location with other users on the network (requires GPS). | Encryption: Messages can be encrypted for privacy. | Mesh Networking: The network automatically routes messages through other nodes to reach the destination. | Off-Grid Communication: No cellular or WiFi required. | Channel Settings: Customize channel settings for different regions and use cases (Long Fast, Mid Slow, etc.). 5. **Software & Firmware** | Meshtastic Firmware: The core software that runs on the microcontrollers. | Meshtastic Mobile App: For configuring and interacting with the devices. Available on Android and iOS. | CLI (Command Line Interface): For advanced configuration and debugging. | API (Application Programming Interface): For integrating Meshtastic with other applications. 6. **Hardware Setup** | Flashing Firmware: You’ll need to flash the Meshtastic firmware onto your microcontroller. This is typically done using a USB connection and a flashing tool. | Connecting Peripherals: Connect the LoRa radio and any other peripherals (GPS, battery) to the microcontroller. | Antenna: Attach an appropriate antenna to the LoRa radio. 7. **Configuration** | Region Settings: Configure the correct region settings for your location. | Channel Settings: Choose a channel or create a custom channel. | Encryption: Enable encryption for secure communication. | Power Settings: Adjust power settings to optimize battery life. 8. **Technical Details** | LoRa Modulation: Uses LoRa modulation for long-range communication. | Frequency Bands: Operates on various frequency bands depending on the region (e.g., 915 MHz in North America, 868 MHz in Europe). | Microcontroller Interfaces: Uses various interfaces for communication between the microcontroller and peripherals, including GPIO, USB, UART, SPI, and I2C. | BLE (Bluetooth Low Energy): Used for initial configuration and communication with the mobile app. | WiFi: Some devices support WiFi for OTA (Over-The-Air) firmware updates. | MQTT: Supports MQTT for integration with other systems. 9. **Use Cases** | Hiking and Camping: Stay connected with your group in areas without cellular coverage. | Emergency Communication: Provide a backup communication system in case of emergencies. | Disaster Relief: Establish communication networks in areas affected by disasters. | Rural Communication: Connect communities in remote areas. | IoT Applications: Use Meshtastic for various IoT applications that require long-range communication. 10. **Resources** | Meshtastic Website: https://meshtastic.org/ | Meshtastic Documentation: https://meshtastic.org/docs/ | Meshtastic Forums: https://meshtastic.discourse.group/ ```1) 概觀 | . Meshtastic 是一個專案，讓你可以使用便宜的 LoRa 無線電作為長距離、離線、去中心化的通訊平台。這些無線電，結合了容易取得且非常實惠的微控制器，像是 ESP32、nRF52 和 RP2040，創建了一個網路，可以用來傳送簡訊、分享位置等等，而不需要依賴行動網路或 WiFi 基礎設施。它非常適合健行、露營，或任何你需要保持連線，但又超出傳統網路覆蓋範圍的情況。 . 2) 主要組件 . | LoRa 無線電: 提供長距離通訊能力。 RAK Wireless 模組是一個很受歡迎的選擇。 | 微控制器: 運作的大腦。 ESP32、nRF52 和 RP2040 因為它們的低成本和功能而被廣泛使用。 | GPS (可選): 用於位置分享。 許多裝置，像是 T-Beam，都有內建 GPS。 | 電池 (可選): 用於攜帶型使用。 | 外殼 (可選): 保護硬體。 | . 3) 熱門裝置 . | T-Beam: 一個受歡迎的板子，具有 ESP32、LoRa 和 GPS。 | Heltec WiFi LoRa 32: 另一個受歡迎的基於 ESP32 的板子，具有 LoRa。 | LilyGo Boards: LilyGo 提供各種基於 ESP32 和 nRF52 的板子，具有 LoRa。 | . 4) 功能 . | 簡訊傳輸: 透過 LoRa 網路傳送和接收簡訊。 | 位置分享: 與網路上其他使用者分享你的位置 (需要 GPS)。 | 加密: 可以加密訊息以保護隱私。 | 網狀網路: 網路會自動透過其他節點路由訊息，以到達目的地。 | 離線通訊: 不需要行動網路或 WiFi。 | 頻道設定: 客製化不同地區和使用案例的頻道設定 (Long Fast、Mid Slow 等)。 | . 5) 軟體與 Firmware . | Meshtastic Firmware: 在微控制器上執行的核心軟體。 | Meshtastic Mobile App: 用於配置和與裝置互動。 可在 Android 和 iOS 上使用。 | CLI (Command Line Interface): 用於進階配置和除錯。 | API (Application Programming Interface): 用於將 Meshtastic 與其他應用程式整合。 | . 6) 硬體設定 . | 刷入 Firmware: 你需要將 Meshtastic firmware 刷入你的微控制器。 這通常是使用 USB 連線和刷入工具來完成的。 | 連接週邊設備: 將 LoRa 無線電和任何其他週邊設備 (GPS、電池) 連接到微控制器。 | 天線: 將適當的天線連接到 LoRa 無線電。 | . 7) 配置 . | 區域設定: 為你的位置配置正確的區域設定。 | 頻道設定: 選擇一個頻道或創建一個自定義頻道。 | 加密: 啟用加密以進行安全通訊。 | 電源設定: 調整電源設定以優化電池壽命。 | . 8) 技術細節 . | LoRa 調變: 使用 LoRa 調變進行長距離通訊。 | 頻率範圍: 根據地區在不同的頻率範圍上運作 (例如，北美為 915 MHz，歐洲為 868 MHz)。 | 微控制器介面: 使用各種介面在微控制器和週邊設備之間進行通訊，包括 GPIO、USB、UART、SPI 和 I2C。 | BLE (Bluetooth Low Energy): 用於初始配置和與行動應用程式的通訊。 | WiFi: 某些裝置支援 WiFi 用於 OTA (Over-The-Air) firmware 更新。 | MQTT: 支援 MQTT 用於與其他系統整合。 | . 9) 使用案例 . | 健行和露營: 在沒有行動網路覆蓋的地區與你的團隊保持聯繫。 | 緊急通訊: 在緊急情況下提供備份通訊系統。 | 災害救援: 在受災害影響的地區建立通訊網路。 | 農村通訊: 連接偏遠地區的社群。 | IoT 應用: 將 Meshtastic 用於各種需要長距離通訊的 IoT 應用。 | . 10) 資源 . - **Meshtastic Website:** [https://meshtastic.org/](https://meshtastic.org/) - **Meshtastic Documentation:** [https://meshtastic.org/docs/](https://meshtastic.org/docs/) - **Meshtastic Forums:** [https://meshtastic.discourse.group/](https://meshtastic.discourse.group/) | more than 7.5 dB below `limit` | Far below the preset's floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/zh-rTW/user/signal-meter.html#rating-signal-quality"
  },"4910": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/zh-rTW/user/signal-meter.html#diagnosing-local-interference"
  },"4911": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Where Signal Information Appears",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Traceroute — per-hop signal quality for each relay node | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/signal-meter.html#where-signal-information-appears",
    
    "relUrl": "/zh-rTW/user/signal-meter.html#where-signal-information-appears"
  },"4912": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "相關主題",
    "content": ". | Nodes — where signal bars appear in the node list | Node Metrics — SNR/RSSI history and the per-node signal quality reference | Settings — Radio & User — modem presets and their SNR limits | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/signal-meter.html#%E7%9B%B8%E9%97%9C%E4%B8%BB%E9%A1%8C",
    
    "relUrl": "/zh-rTW/user/signal-meter.html#相關主題"
  },"4913": {
    "doc": "Kuidas Meshtastic signaalimõõtur töötab",
    "title": "Kuidas Meshtastic signaalimõõtur töötab",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/signal-meter.html",
    
    "relUrl": "/et-rEE/user/signal-meter.html"
  },"4914": {
    "doc": "Kuidas Meshtastic signaalimõõtur töötab",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/et-rEE/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/et-rEE/user/signal-meter.html#rssi-and-snr"
  },"4915": {
    "doc": "Kuidas Meshtastic signaalimõõtur töötab",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/et-rEE/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/et-rEE/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4916": {
    "doc": "Kuidas Meshtastic signaalimõõtur töötab",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | Level | Bars | Criteria | Tähendus | . | Hea | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | . | Rahuldav | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | . | Halb | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | . | Puudub | 1 | more than 7.5 dB below limit | Far below the preset’s floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/et-rEE/user/signal-meter.html#rating-signal-quality"
  },"4917": {
    "doc": "Kuidas Meshtastic signaalimõõtur töötab",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/et-rEE/user/signal-meter.html#diagnosing-local-interference"
  },"4918": {
    "doc": "Kuidas Meshtastic signaalimõõtur töötab",
    "title": "Where Signal Information Appears",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Traceroute — iga vahendussõlme signaali kvaliteet hüppe kohta | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/signal-meter.html#where-signal-information-appears",
    
    "relUrl": "/et-rEE/user/signal-meter.html#where-signal-information-appears"
  },"4919": {
    "doc": "Kuidas Meshtastic signaalimõõtur töötab",
    "title": "Seotud teemad",
    "content": ". | Nodes — where signal bars appear in the node list | Node Metrics — SNR/RSSI history and the per-node signal quality reference | Seaded — Raadio ja kasutaja — modemi eelseadistused ja nende signaali-müra piirangud | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/signal-meter.html#seotud-teemad",
    
    "relUrl": "/et-rEE/user/signal-meter.html#seotud-teemad"
  },"4920": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "How the Meshtastic Signal Meter Works",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/signal-meter.html",
    
    "relUrl": "/fr-rFR/user/signal-meter.html"
  },"4921": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/fr-rFR/user/signal-meter.html#rssi-and-snr"
  },"4922": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/fr-rFR/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4923": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | Level | Bars | Criteria | Meaning | . | Bon | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | . | Passable | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | . | Mauvais | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | . | Aucun | 1 | more than 7.5 dB below limit | Far below the preset’s floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/fr-rFR/user/signal-meter.html#rating-signal-quality"
  },"4924": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/fr-rFR/user/signal-meter.html#diagnosing-local-interference"
  },"4925": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Where Signal Information Appears",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Traceroute — per-hop signal quality for each relay node | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/signal-meter.html#where-signal-information-appears",
    
    "relUrl": "/fr-rFR/user/signal-meter.html#where-signal-information-appears"
  },"4926": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Related Topics",
    "content": ". | Nodes — where signal bars appear in the node list | Node Metrics — SNR/RSSI history and the per-node signal quality reference | Settings — Radio & User — modem presets and their SNR limits | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/signal-meter.html#related-topics",
    
    "relUrl": "/fr-rFR/user/signal-meter.html#related-topics"
  },"4927": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "How the Meshtastic Signal Meter Works",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/signal-meter.html",
    
    "relUrl": "/tr-rTR/user/signal-meter.html"
  },"4928": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/tr-rTR/user/signal-meter.html#rssi-and-snr"
  },"4929": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/tr-rTR/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4930": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | Level | Bars | Criteria | Meaning | . | İyi | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | . | İdare Eder | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | . | Kötü | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | . | Yok | 1 | more than 7.5 dB below limit | Far below the preset’s floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/tr-rTR/user/signal-meter.html#rating-signal-quality"
  },"4931": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/tr-rTR/user/signal-meter.html#diagnosing-local-interference"
  },"4932": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Where Signal Information Appears",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Traceroute — per-hop signal quality for each relay node | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/signal-meter.html#where-signal-information-appears",
    
    "relUrl": "/tr-rTR/user/signal-meter.html#where-signal-information-appears"
  },"4933": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Related Topics",
    "content": ". | Nodes — where signal bars appear in the node list | Node Metrics — SNR/RSSI history and the per-node signal quality reference | Settings — Radio & User — modem presets and their SNR limits | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/signal-meter.html#related-topics",
    
    "relUrl": "/tr-rTR/user/signal-meter.html#related-topics"
  },"4934": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "How the Meshtastic Signal Meter Works",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/signal-meter.html",
    
    "relUrl": "/el-rGR/user/signal-meter.html"
  },"4935": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/el-rGR/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/el-rGR/user/signal-meter.html#rssi-and-snr"
  },"4936": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/el-rGR/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/el-rGR/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4937": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | Level | Bars | Criteria | Meaning | . | Good | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | . | Fair | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | . | Bad | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | . | None | 1 | more than 7.5 dB below limit | Far below the preset’s floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/el-rGR/user/signal-meter.html#rating-signal-quality"
  },"4938": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/el-rGR/user/signal-meter.html#diagnosing-local-interference"
  },"4939": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Where Signal Information Appears",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Traceroute — per-hop signal quality for each relay node | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/signal-meter.html#where-signal-information-appears",
    
    "relUrl": "/el-rGR/user/signal-meter.html#where-signal-information-appears"
  },"4940": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Related Topics",
    "content": ". | Nodes — where signal bars appear in the node list | Node Metrics — SNR/RSSI history and the per-node signal quality reference | Settings — Radio & User — modem presets and their SNR limits | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/signal-meter.html#related-topics",
    
    "relUrl": "/el-rGR/user/signal-meter.html#related-topics"
  },"4941": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "How the Meshtastic Signal Meter Works",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/signal-meter.html",
    
    "relUrl": "/ro-rRO/user/signal-meter.html"
  },"4942": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/ro-rRO/user/signal-meter.html#rssi-and-snr"
  },"4943": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/ro-rRO/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4944": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | Level | Bars | Criteria | Meaning | . | Bun | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | . | Acceptabil | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | . | Slab | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | . | Niciunul | 1 | more than 7.5 dB below limit | Far below the preset’s floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/ro-rRO/user/signal-meter.html#rating-signal-quality"
  },"4945": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/ro-rRO/user/signal-meter.html#diagnosing-local-interference"
  },"4946": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Where Signal Information Appears",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Traceroute — per-hop signal quality for each relay node | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/signal-meter.html#where-signal-information-appears",
    
    "relUrl": "/ro-rRO/user/signal-meter.html#where-signal-information-appears"
  },"4947": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Related Topics",
    "content": ". | Nodes — where signal bars appear in the node list | Node Metrics — SNR/RSSI history and the per-node signal quality reference | Settings — Radio & User — modem presets and their SNR limits | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/signal-meter.html#related-topics",
    
    "relUrl": "/ro-rRO/user/signal-meter.html#related-topics"
  },"4948": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "How the Meshtastic Signal Meter Works",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/signal-meter.html",
    
    "relUrl": "/iw-rIL/user/signal-meter.html"
  },"4949": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/iw-rIL/user/signal-meter.html#rssi-and-snr"
  },"4950": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/iw-rIL/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4951": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | Level | Bars | Criteria | Meaning | . | Good | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | . | Fair | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | . | Bad | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | . | None | 1 | more than 7.5 dB below limit | Far below the preset’s floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/iw-rIL/user/signal-meter.html#rating-signal-quality"
  },"4952": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/iw-rIL/user/signal-meter.html#diagnosing-local-interference"
  },"4953": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Where Signal Information Appears",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Traceroute — per-hop signal quality for each relay node | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/signal-meter.html#where-signal-information-appears",
    
    "relUrl": "/iw-rIL/user/signal-meter.html#where-signal-information-appears"
  },"4954": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Related Topics",
    "content": ". | Nodes — where signal bars appear in the node list | Node Metrics — SNR/RSSI history and the per-node signal quality reference | Settings — Radio & User — modem presets and their SNR limits | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/signal-meter.html#related-topics",
    
    "relUrl": "/iw-rIL/user/signal-meter.html#related-topics"
  },"4955": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "How the Meshtastic Signal Meter Works",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/signal-meter.html",
    
    "relUrl": "/pt-rBR/user/signal-meter.html"
  },"4956": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/pt-rBR/user/signal-meter.html#rssi-and-snr"
  },"4957": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/pt-rBR/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4958": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | Level | Bars | Criteria | Meaning | . | Bom | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | . | Média | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | . | Ruim | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | . | Nenhum | 1 | more than 7.5 dB below limit | Far below the preset’s floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/pt-rBR/user/signal-meter.html#rating-signal-quality"
  },"4959": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/pt-rBR/user/signal-meter.html#diagnosing-local-interference"
  },"4960": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Where Signal Information Appears",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Traceroute — per-hop signal quality for each relay node | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/signal-meter.html#where-signal-information-appears",
    
    "relUrl": "/pt-rBR/user/signal-meter.html#where-signal-information-appears"
  },"4961": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Related Topics",
    "content": ". | Nodes — where signal bars appear in the node list | Node Metrics — SNR/RSSI history and the per-node signal quality reference | Settings — Radio & User — modem presets and their SNR limits | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/signal-meter.html#related-topics",
    
    "relUrl": "/pt-rBR/user/signal-meter.html#related-topics"
  },"4962": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "How the Meshtastic Signal Meter Works",
    "content": "The Meshtastic signal meter — the bars or status color next to a node — is calculated differently from the bars on a cell phone or Wi-Fi router. This page explains what it measures and why the same reading can mean something different on another preset. ",
    "url": "/Meshtastic-Android/main/en/user/signal-meter.html",
    
    "relUrl": "/en/user/signal-meter.html"
  },"4963": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "RSSI and SNR",
    "content": "Every time the LoRa radio receives a message, it reports two measurements: . | RSSI (Received Signal Strength Indicator) — the raw power hitting the antenna. | SNR (Signal-to-Noise Ratio) — how far the signal stands above the background noise. | . 💡 Tip: Think of RSSI as how loud a friend is talking and SNR as how easily you can pick their voice out of the noise in the room. A friend shouting at a rock concert can be loud (high RSSI) yet unintelligible (bad SNR), while a whisper in a quiet library is faint (low RSSI) yet perfectly clear (great SNR). ",
    "url": "/Meshtastic-Android/main/en/user/signal-meter.html#rssi-and-snr",
    
    "relUrl": "/en/user/signal-meter.html#rssi-and-snr"
  },"4964": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Decoding Below the Noise Floor",
    "content": "Standard radios such as FM or Wi-Fi lose a signal to static once the background noise is louder than it (a negative SNR). LoRa’s spread spectrum modulation lets the radio pull a signal out of the noise even when the noise is louder, so negative SNR values are common and expected in Meshtastic — for example, −10 dB means the signal is 10 decibels weaker than the background noise. Each modem preset has an SNR limit: the lowest SNR at which that preset can still decode a message. Slower presets tolerate a weaker, noisier signal (a more negative limit, longer range); faster presets need a stronger signal (a less negative limit, shorter range). ",
    "url": "/Meshtastic-Android/main/en/user/signal-meter.html#decoding-below-the-noise-floor",
    
    "relUrl": "/en/user/signal-meter.html#decoding-below-the-noise-floor"
  },"4965": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Rating Signal Quality",
    "content": "The app rates signal quality (None, Bad, Fair, or Good) from SNR relative to the active preset’s SNR limit. When RSSI and a noise-floor reading are both available, it also rates the difference between them against that limit and uses the worse rating. Otherwise, it uses SNR alone. Because the rating is relative to the preset, the same SNR rates differently on different presets. An SNR of −16 dB rates Good on Long Fast (SNR limit −17.5 dB) but None on Short Fast (SNR limit −7.5 dB). Let limit be the active preset’s SNR limit: . | Level | Bars | Criteria | Meaning | . | Good | Full | SNR above limit | Comfortably above the demodulation floor — a healthy connection. | . | Fair | 3 | less than 5.5 dB below limit | Decodable, but approaching the floor. | . | Bad | 2 | 5.5 dB to 7.5 dB below limit | At the edge of what the preset can recover. | . | None | 1 | more than 7.5 dB below limit | Far below the preset’s floor; further packets from this node are likely to be lost. | . The icon never goes blank, so count the bars carefully: a single bar means None, not a weak but usable link, and Good is a solid wedge rather than a set of bars. A gray three-bar icon labeled Unknown is a different state again — the packet carried no SNR measurement at all, which is not the same as measuring one and finding it too weak. ℹ️ Note: Traceroute and neighbor-info SNR colors use the active preset’s limits too. RSSI text has separate strength colors: green above −115 dBm, yellow above −120 dBm, orange above −126 dBm, and red at or below −126 dBm. ",
    "url": "/Meshtastic-Android/main/en/user/signal-meter.html#rating-signal-quality",
    
    "relUrl": "/en/user/signal-meter.html#rating-signal-quality"
  },"4966": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Diagnosing Local Interference",
    "content": "A great RSSI paired with a one- or two-bar rating (None or Bad) points to local interference, not distance. A cheap power supply, a noisy computer, or a nearby transmitter can create enough static to drown out an otherwise strong signal. ",
    "url": "/Meshtastic-Android/main/en/user/signal-meter.html#diagnosing-local-interference",
    
    "relUrl": "/en/user/signal-meter.html#diagnosing-local-interference"
  },"4967": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Where Signal Information Appears",
    "content": "In the app, signal data appears in several places: . | Node list — a signal-bars icon, shown only for nodes your radio heard directly. A node reached through a relay shows its hop count instead, because the SNR your radio measured describes the last hop, not the whole path | Node detail — SNR, RSSI, and the quality word in the Details card at the top of the screen | Traceroute — per-hop signal quality for each relay node | Signal Quality — historical SNR and RSSI data in the metrics charts | . ",
    "url": "/Meshtastic-Android/main/en/user/signal-meter.html#where-signal-information-appears",
    
    "relUrl": "/en/user/signal-meter.html#where-signal-information-appears"
  },"4968": {
    "doc": "How the Meshtastic Signal Meter Works",
    "title": "Related Topics",
    "content": ". | Nodes — where signal bars appear in the node list | Node Metrics — SNR/RSSI history and the per-node signal quality reference | Settings — Radio & User — modem presets and their SNR limits | . ",
    "url": "/Meshtastic-Android/main/en/user/signal-meter.html#related-topics",
    
    "relUrl": "/en/user/signal-meter.html#related-topics"
  },"4969": {
    "doc": "TAK Integration",
    "title": "TAK Integration",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/tak.html",
    
    "relUrl": "/sk-rSK/user/tak.html"
  },"4970": {
    "doc": "TAK Integration",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/tak.html#overview",
    
    "relUrl": "/sk-rSK/user/tak.html#overview"
  },"4971": {
    "doc": "TAK Integration",
    "title": "Setup",
    "content": "Prerequisites . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. Configuration . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | Setting | Popis | . | Team Color | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Member Role | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 Tip: Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments. Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. The server binds to localhost only (127.0.0.1:8089) and uses TLS with mutual certificate authentication (mTLS), so it is not reachable from other devices on the network. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK Mesh Channel — selects which Meshtastic channel outgoing TAK traffic is sent on (default: the primary channel, index 0). Incoming TAK traffic is accepted from any channel. Matches the equivalent setting on iOS and in the legacy ATAK plugin. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | Export TAK Data Package — generates a .zip data package that ATAK/iTAK can import to connect to this server. | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/tak.html#setup",
    
    "relUrl": "/sk-rSK/user/tak.html#setup"
  },"4972": {
    "doc": "TAK Integration",
    "title": "TAK Roles",
    "content": "Nodes configured with TAK-related roles behave differently from standard clients: . | Rola | Popis | . | 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. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/tak.html#tak-roles",
    
    "relUrl": "/sk-rSK/user/tak.html#tak-roles"
  },"4973": {
    "doc": "TAK Integration",
    "title": "Wire Format (V1 / V2)",
    "content": "Meshtastic supports two TAK wire formats, chosen automatically based on the connected radio’s firmware — no manual configuration needed: . | Format | Compatibility | Features | . | V1 (Legacy) | Firmware 2.7.x and older | Bare protobuf encoding on port 72. Supports position sharing (PLI) and chat (GeoChat) only — shapes, markers, routes, and other typed CoT events are dropped | . | V2 (Current) | Firmware 2.8.0+ | Compact, zstd-compressed encoding on port 78. Adds shapes, markers, routes, aircraft, casevac, emergency, and task CoT types on top of everything V1 supports | . A node still relays legacy V1 packets from older nodes even while running V2 itself, so mixed-firmware meshes keep working. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/tak.html#wire-format-v1--v2",
    
    "relUrl": "/sk-rSK/user/tak.html#wire-format-v1--v2"
  },"4974": {
    "doc": "TAK Integration",
    "title": "Usage with ATAK",
    "content": "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. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/tak.html#usage-with-atak",
    
    "relUrl": "/sk-rSK/user/tak.html#usage-with-atak"
  },"4975": {
    "doc": "TAK Integration",
    "title": "Troubleshooting",
    "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | Shapes, markers, or routes not bridging | Sending node is on legacy V1 (firmware 2.7.x or older) | Update the sending node’s firmware to 2.8.0+ for V2 wire format | . | CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/tak.html#troubleshooting",
    
    "relUrl": "/sk-rSK/user/tak.html#troubleshooting"
  },"4976": {
    "doc": "TAK Integration",
    "title": "Security Considerations",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/tak.html#security-considerations",
    
    "relUrl": "/sk-rSK/user/tak.html#security-considerations"
  },"4977": {
    "doc": "TAK Integration",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — TAK module configuration | Nodes — TAK and TAK Tracker roles in the node list | Map & Waypoints — node positions on the map | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/tak.html#related-topics",
    
    "relUrl": "/sk-rSK/user/tak.html#related-topics"
  },"4978": {
    "doc": "TAK Integration",
    "title": "TAK Integration",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/tak.html",
    
    "relUrl": "/be-rBY/user/tak.html"
  },"4979": {
    "doc": "TAK Integration",
    "title": "Абзор",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/tak.html#%D0%B0%D0%B1%D0%B7%D0%BE%D1%80",
    
    "relUrl": "/be-rBY/user/tak.html#абзор"
  },"4980": {
    "doc": "TAK Integration",
    "title": "Setup",
    "content": "Prerequisites . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. Конфигурация . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | Setting | Апісанне | . | Team Color | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Member Role | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 Tip: Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments. Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. The server binds to localhost only (127.0.0.1:8089) and uses TLS with mutual certificate authentication (mTLS), so it is not reachable from other devices on the network. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK Mesh Channel — selects which Meshtastic channel outgoing TAK traffic is sent on (default: the primary channel, index 0). Incoming TAK traffic is accepted from any channel. Matches the equivalent setting on iOS and in the legacy ATAK plugin. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | Export TAK Data Package — generates a .zip data package that ATAK/iTAK can import to connect to this server. | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/tak.html#setup",
    
    "relUrl": "/be-rBY/user/tak.html#setup"
  },"4981": {
    "doc": "TAK Integration",
    "title": "TAK Roles",
    "content": "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. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/tak.html#tak-roles",
    
    "relUrl": "/be-rBY/user/tak.html#tak-roles"
  },"4982": {
    "doc": "TAK Integration",
    "title": "Wire Format (V1 / V2)",
    "content": "Meshtastic supports two TAK wire formats, chosen automatically based on the connected radio’s firmware — no manual configuration needed: . | Format | Compatibility | Функцианал | . | V1 (Legacy) | Firmware 2.7.x and older | Bare protobuf encoding on port 72. Supports position sharing (PLI) and chat (GeoChat) only — shapes, markers, routes, and other typed CoT events are dropped | . | V2 (Current) | Firmware 2.8.0+ | Compact, zstd-compressed encoding on port 78. Adds shapes, markers, routes, aircraft, casevac, emergency, and task CoT types on top of everything V1 supports | . A node still relays legacy V1 packets from older nodes even while running V2 itself, so mixed-firmware meshes keep working. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/tak.html#wire-format-v1--v2",
    
    "relUrl": "/be-rBY/user/tak.html#wire-format-v1--v2"
  },"4983": {
    "doc": "TAK Integration",
    "title": "Usage with ATAK",
    "content": "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. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/tak.html#usage-with-atak",
    
    "relUrl": "/be-rBY/user/tak.html#usage-with-atak"
  },"4984": {
    "doc": "TAK Integration",
    "title": "Troubleshooting",
    "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | Shapes, markers, or routes not bridging | Sending node is on legacy V1 (firmware 2.7.x or older) | Update the sending node’s firmware to 2.8.0+ for V2 wire format | . | CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/tak.html#troubleshooting",
    
    "relUrl": "/be-rBY/user/tak.html#troubleshooting"
  },"4985": {
    "doc": "TAK Integration",
    "title": "Security Considerations",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/tak.html#security-considerations",
    
    "relUrl": "/be-rBY/user/tak.html#security-considerations"
  },"4986": {
    "doc": "TAK Integration",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — TAK module configuration | Nodes — TAK and TAK Tracker roles in the node list | Map & Waypoints — node positions on the map | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/tak.html#related-topics",
    
    "relUrl": "/be-rBY/user/tak.html#related-topics"
  },"4987": {
    "doc": "TAK Integration",
    "title": "TAK Integration",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/tak.html",
    
    "relUrl": "/it-rIT/user/tak.html"
  },"4988": {
    "doc": "TAK Integration",
    "title": "Panoramica",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/tak.html#panoramica",
    
    "relUrl": "/it-rIT/user/tak.html#panoramica"
  },"4989": {
    "doc": "TAK Integration",
    "title": "Configurazione",
    "content": "Prerequisiti . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. Configurazione . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | Impostazione | Descrizione | . | Team Color | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Member Role | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 Tip: Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments. Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. The server binds to localhost only (127.0.0.1:8089) and uses TLS with mutual certificate authentication (mTLS), so it is not reachable from other devices on the network. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK Mesh Channel — selects which Meshtastic channel outgoing TAK traffic is sent on (default: the primary channel, index 0). Incoming TAK traffic is accepted from any channel. Matches the equivalent setting on iOS and in the legacy ATAK plugin. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | Export TAK Data Package — generates a .zip data package that ATAK/iTAK can import to connect to this server. | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/tak.html#configurazione",
    
    "relUrl": "/it-rIT/user/tak.html#configurazione"
  },"4990": {
    "doc": "TAK Integration",
    "title": "TAK Roles",
    "content": "Nodes configured with TAK-related roles behave differently from standard clients: . | Ruolo | Descrizione | . | 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. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/tak.html#tak-roles",
    
    "relUrl": "/it-rIT/user/tak.html#tak-roles"
  },"4991": {
    "doc": "TAK Integration",
    "title": "Wire Format (V1 / V2)",
    "content": "Meshtastic supports two TAK wire formats, chosen automatically based on the connected radio’s firmware — no manual configuration needed: . | Format | Compatibility | Caratteristiche | . | V1 (Legacy) | Firmware 2.7.x and older | Bare protobuf encoding on port 72. Supports position sharing (PLI) and chat (GeoChat) only — shapes, markers, routes, and other typed CoT events are dropped | . | V2 (Current) | Firmware 2.8.0+ | Compact, zstd-compressed encoding on port 78. Adds shapes, markers, routes, aircraft, casevac, emergency, and task CoT types on top of everything V1 supports | . A node still relays legacy V1 packets from older nodes even while running V2 itself, so mixed-firmware meshes keep working. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/tak.html#wire-format-v1--v2",
    
    "relUrl": "/it-rIT/user/tak.html#wire-format-v1--v2"
  },"4992": {
    "doc": "TAK Integration",
    "title": "Usage with ATAK",
    "content": "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. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/tak.html#usage-with-atak",
    
    "relUrl": "/it-rIT/user/tak.html#usage-with-atak"
  },"4993": {
    "doc": "TAK Integration",
    "title": "Risoluzione problemi",
    "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | Shapes, markers, or routes not bridging | Sending node is on legacy V1 (firmware 2.7.x or older) | Update the sending node’s firmware to 2.8.0+ for V2 wire format | . | CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/tak.html#risoluzione-problemi",
    
    "relUrl": "/it-rIT/user/tak.html#risoluzione-problemi"
  },"4994": {
    "doc": "TAK Integration",
    "title": "Security Considerations",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/tak.html#security-considerations",
    
    "relUrl": "/it-rIT/user/tak.html#security-considerations"
  },"4995": {
    "doc": "TAK Integration",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — TAK module configuration | Nodes — TAK and TAK Tracker roles in the node list | Map & Waypoints — node positions on the map | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/tak.html#related-topics",
    
    "relUrl": "/it-rIT/user/tak.html#related-topics"
  },"4996": {
    "doc": "TAK Integration",
    "title": "TAK Integration",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/es-rES/user/tak.html",
    
    "relUrl": "/es-rES/user/tak.html"
  },"4997": {
    "doc": "TAK Integration",
    "title": "Visión general",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/tak.html#visi%C3%B3n-general",
    
    "relUrl": "/es-rES/user/tak.html#visión-general"
  },"4998": {
    "doc": "TAK Integration",
    "title": "Setup",
    "content": "Prerequisites . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. Configuración . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | Setting | Descripción | . | Team Color | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Member Role | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 Tip: Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments. Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. The server binds to localhost only (127.0.0.1:8089) and uses TLS with mutual certificate authentication (mTLS), so it is not reachable from other devices on the network. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK Mesh Channel — selects which Meshtastic channel outgoing TAK traffic is sent on (default: the primary channel, index 0). Incoming TAK traffic is accepted from any channel. Matches the equivalent setting on iOS and in the legacy ATAK plugin. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | Export TAK Data Package — generates a .zip data package that ATAK/iTAK can import to connect to this server. | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/tak.html#setup",
    
    "relUrl": "/es-rES/user/tak.html#setup"
  },"4999": {
    "doc": "TAK Integration",
    "title": "TAK Roles",
    "content": "Nodes configured with TAK-related roles behave differently from standard clients: . | Rol | Descripción | . | 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. ",
    "url": "/Meshtastic-Android/main/es-rES/user/tak.html#tak-roles",
    
    "relUrl": "/es-rES/user/tak.html#tak-roles"
  },"5000": {
    "doc": "TAK Integration",
    "title": "Wire Format (V1 / V2)",
    "content": "Meshtastic supports two TAK wire formats, chosen automatically based on the connected radio’s firmware — no manual configuration needed: . | Format | Compatibility | Features | . | V1 (Legacy) | Firmware 2.7.x and older | Bare protobuf encoding on port 72. Supports position sharing (PLI) and chat (GeoChat) only — shapes, markers, routes, and other typed CoT events are dropped | . | V2 (Current) | Firmware 2.8.0+ | Compact, zstd-compressed encoding on port 78. Adds shapes, markers, routes, aircraft, casevac, emergency, and task CoT types on top of everything V1 supports | . A node still relays legacy V1 packets from older nodes even while running V2 itself, so mixed-firmware meshes keep working. ",
    "url": "/Meshtastic-Android/main/es-rES/user/tak.html#wire-format-v1--v2",
    
    "relUrl": "/es-rES/user/tak.html#wire-format-v1--v2"
  },"5001": {
    "doc": "TAK Integration",
    "title": "Usage with ATAK",
    "content": "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. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/es-rES/user/tak.html#usage-with-atak",
    
    "relUrl": "/es-rES/user/tak.html#usage-with-atak"
  },"5002": {
    "doc": "TAK Integration",
    "title": "Troubleshooting",
    "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | Shapes, markers, or routes not bridging | Sending node is on legacy V1 (firmware 2.7.x or older) | Update the sending node’s firmware to 2.8.0+ for V2 wire format | . | CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/tak.html#troubleshooting",
    
    "relUrl": "/es-rES/user/tak.html#troubleshooting"
  },"5003": {
    "doc": "TAK Integration",
    "title": "Security Considerations",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/es-rES/user/tak.html#security-considerations",
    
    "relUrl": "/es-rES/user/tak.html#security-considerations"
  },"5004": {
    "doc": "TAK Integration",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — TAK module configuration | Nodes — TAK and TAK Tracker roles in the node list | Map & Waypoints — node positions on the map | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/tak.html#related-topics",
    
    "relUrl": "/es-rES/user/tak.html#related-topics"
  },"5005": {
    "doc": "TAK Integration",
    "title": "TAK Integration",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/tak.html",
    
    "relUrl": "/sl-rSI/user/tak.html"
  },"5006": {
    "doc": "TAK Integration",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/tak.html#overview",
    
    "relUrl": "/sl-rSI/user/tak.html#overview"
  },"5007": {
    "doc": "TAK Integration",
    "title": "Setup",
    "content": "Prerequisites . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. Configuration . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | Setting | Opis | . | Team Color | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Member Role | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 Tip: Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments. Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. The server binds to localhost only (127.0.0.1:8089) and uses TLS with mutual certificate authentication (mTLS), so it is not reachable from other devices on the network. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK Mesh Channel — selects which Meshtastic channel outgoing TAK traffic is sent on (default: the primary channel, index 0). Incoming TAK traffic is accepted from any channel. Matches the equivalent setting on iOS and in the legacy ATAK plugin. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | Export TAK Data Package — generates a .zip data package that ATAK/iTAK can import to connect to this server. | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/tak.html#setup",
    
    "relUrl": "/sl-rSI/user/tak.html#setup"
  },"5008": {
    "doc": "TAK Integration",
    "title": "TAK Roles",
    "content": "Nodes configured with TAK-related roles behave differently from standard clients: . | Role | Opis | . | 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. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/tak.html#tak-roles",
    
    "relUrl": "/sl-rSI/user/tak.html#tak-roles"
  },"5009": {
    "doc": "TAK Integration",
    "title": "Wire Format (V1 / V2)",
    "content": "Meshtastic supports two TAK wire formats, chosen automatically based on the connected radio’s firmware — no manual configuration needed: . | Format | Compatibility | Features | . | V1 (Legacy) | Firmware 2.7.x and older | Bare protobuf encoding on port 72. Supports position sharing (PLI) and chat (GeoChat) only — shapes, markers, routes, and other typed CoT events are dropped | . | V2 (Current) | Firmware 2.8.0+ | Compact, zstd-compressed encoding on port 78. Adds shapes, markers, routes, aircraft, casevac, emergency, and task CoT types on top of everything V1 supports | . A node still relays legacy V1 packets from older nodes even while running V2 itself, so mixed-firmware meshes keep working. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/tak.html#wire-format-v1--v2",
    
    "relUrl": "/sl-rSI/user/tak.html#wire-format-v1--v2"
  },"5010": {
    "doc": "TAK Integration",
    "title": "Usage with ATAK",
    "content": "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. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/tak.html#usage-with-atak",
    
    "relUrl": "/sl-rSI/user/tak.html#usage-with-atak"
  },"5011": {
    "doc": "TAK Integration",
    "title": "Troubleshooting",
    "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | Shapes, markers, or routes not bridging | Sending node is on legacy V1 (firmware 2.7.x or older) | Update the sending node’s firmware to 2.8.0+ for V2 wire format | . | CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/tak.html#troubleshooting",
    
    "relUrl": "/sl-rSI/user/tak.html#troubleshooting"
  },"5012": {
    "doc": "TAK Integration",
    "title": "Security Considerations",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/tak.html#security-considerations",
    
    "relUrl": "/sl-rSI/user/tak.html#security-considerations"
  },"5013": {
    "doc": "TAK Integration",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — TAK module configuration | Nodes — TAK and TAK Tracker roles in the node list | Map & Waypoints — node positions on the map | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/tak.html#related-topics",
    
    "relUrl": "/sl-rSI/user/tak.html#related-topics"
  },"5014": {
    "doc": "TAK Integration",
    "title": "TAK Integration",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/tak.html",
    
    "relUrl": "/no-rNO/user/tak.html"
  },"5015": {
    "doc": "TAK Integration",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/tak.html#overview",
    
    "relUrl": "/no-rNO/user/tak.html#overview"
  },"5016": {
    "doc": "TAK Integration",
    "title": "Setup",
    "content": "Prerequisites . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. Configuration . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | Setting | Beskrivelse | . | Team Color | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Member Role | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 Tip: Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments. Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. The server binds to localhost only (127.0.0.1:8089) and uses TLS with mutual certificate authentication (mTLS), so it is not reachable from other devices on the network. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK Mesh Channel — selects which Meshtastic channel outgoing TAK traffic is sent on (default: the primary channel, index 0). Incoming TAK traffic is accepted from any channel. Matches the equivalent setting on iOS and in the legacy ATAK plugin. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | Export TAK Data Package — generates a .zip data package that ATAK/iTAK can import to connect to this server. | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/tak.html#setup",
    
    "relUrl": "/no-rNO/user/tak.html#setup"
  },"5017": {
    "doc": "TAK Integration",
    "title": "TAK Roles",
    "content": "Nodes configured with TAK-related roles behave differently from standard clients: . | Role | Beskrivelse | . | 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. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/tak.html#tak-roles",
    
    "relUrl": "/no-rNO/user/tak.html#tak-roles"
  },"5018": {
    "doc": "TAK Integration",
    "title": "Wire Format (V1 / V2)",
    "content": "Meshtastic supports two TAK wire formats, chosen automatically based on the connected radio’s firmware — no manual configuration needed: . | Format | Compatibility | Features | . | V1 (Legacy) | Firmware 2.7.x and older | Bare protobuf encoding on port 72. Supports position sharing (PLI) and chat (GeoChat) only — shapes, markers, routes, and other typed CoT events are dropped | . | V2 (Current) | Firmware 2.8.0+ | Compact, zstd-compressed encoding on port 78. Adds shapes, markers, routes, aircraft, casevac, emergency, and task CoT types on top of everything V1 supports | . A node still relays legacy V1 packets from older nodes even while running V2 itself, so mixed-firmware meshes keep working. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/tak.html#wire-format-v1--v2",
    
    "relUrl": "/no-rNO/user/tak.html#wire-format-v1--v2"
  },"5019": {
    "doc": "TAK Integration",
    "title": "Usage with ATAK",
    "content": "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. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/tak.html#usage-with-atak",
    
    "relUrl": "/no-rNO/user/tak.html#usage-with-atak"
  },"5020": {
    "doc": "TAK Integration",
    "title": "Troubleshooting",
    "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | Shapes, markers, or routes not bridging | Sending node is on legacy V1 (firmware 2.7.x or older) | Update the sending node’s firmware to 2.8.0+ for V2 wire format | . | CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/tak.html#troubleshooting",
    
    "relUrl": "/no-rNO/user/tak.html#troubleshooting"
  },"5021": {
    "doc": "TAK Integration",
    "title": "Security Considerations",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/tak.html#security-considerations",
    
    "relUrl": "/no-rNO/user/tak.html#security-considerations"
  },"5022": {
    "doc": "TAK Integration",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — TAK module configuration | Nodes — TAK and TAK Tracker roles in the node list | Map & Waypoints — node positions on the map | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/tak.html#related-topics",
    
    "relUrl": "/no-rNO/user/tak.html#related-topics"
  },"5023": {
    "doc": "TAK Integration",
    "title": "TAK Integration",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/tak.html",
    
    "relUrl": "/hu-rHU/user/tak.html"
  },"5024": {
    "doc": "TAK Integration",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/tak.html#overview",
    
    "relUrl": "/hu-rHU/user/tak.html#overview"
  },"5025": {
    "doc": "TAK Integration",
    "title": "Setup",
    "content": "Prerequisites . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. Configuration . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | Setting | Leírás | . | Team Color | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Member Role | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 Tip: Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments. Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. The server binds to localhost only (127.0.0.1:8089) and uses TLS with mutual certificate authentication (mTLS), so it is not reachable from other devices on the network. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK Mesh Channel — selects which Meshtastic channel outgoing TAK traffic is sent on (default: the primary channel, index 0). Incoming TAK traffic is accepted from any channel. Matches the equivalent setting on iOS and in the legacy ATAK plugin. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | Export TAK Data Package — generates a .zip data package that ATAK/iTAK can import to connect to this server. | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/tak.html#setup",
    
    "relUrl": "/hu-rHU/user/tak.html#setup"
  },"5026": {
    "doc": "TAK Integration",
    "title": "TAK Roles",
    "content": "Nodes configured with TAK-related roles behave differently from standard clients: . | Szerepkör | Leírás | . | 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. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/tak.html#tak-roles",
    
    "relUrl": "/hu-rHU/user/tak.html#tak-roles"
  },"5027": {
    "doc": "TAK Integration",
    "title": "Wire Format (V1 / V2)",
    "content": "Meshtastic supports two TAK wire formats, chosen automatically based on the connected radio’s firmware — no manual configuration needed: . | Format | Compatibility | Features | . | V1 (Legacy) | Firmware 2.7.x and older | Bare protobuf encoding on port 72. Supports position sharing (PLI) and chat (GeoChat) only — shapes, markers, routes, and other typed CoT events are dropped | . | V2 (Current) | Firmware 2.8.0+ | Compact, zstd-compressed encoding on port 78. Adds shapes, markers, routes, aircraft, casevac, emergency, and task CoT types on top of everything V1 supports | . A node still relays legacy V1 packets from older nodes even while running V2 itself, so mixed-firmware meshes keep working. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/tak.html#wire-format-v1--v2",
    
    "relUrl": "/hu-rHU/user/tak.html#wire-format-v1--v2"
  },"5028": {
    "doc": "TAK Integration",
    "title": "Usage with ATAK",
    "content": "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. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/tak.html#usage-with-atak",
    
    "relUrl": "/hu-rHU/user/tak.html#usage-with-atak"
  },"5029": {
    "doc": "TAK Integration",
    "title": "Troubleshooting",
    "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | Shapes, markers, or routes not bridging | Sending node is on legacy V1 (firmware 2.7.x or older) | Update the sending node’s firmware to 2.8.0+ for V2 wire format | . | CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/tak.html#troubleshooting",
    
    "relUrl": "/hu-rHU/user/tak.html#troubleshooting"
  },"5030": {
    "doc": "TAK Integration",
    "title": "Security Considerations",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/tak.html#security-considerations",
    
    "relUrl": "/hu-rHU/user/tak.html#security-considerations"
  },"5031": {
    "doc": "TAK Integration",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — TAK module configuration | Nodes — TAK and TAK Tracker roles in the node list | Map & Waypoints — node positions on the map | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/tak.html#related-topics",
    
    "relUrl": "/hu-rHU/user/tak.html#related-topics"
  },"5032": {
    "doc": "Интеграция TAK",
    "title": "Интеграция TAK",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/tak.html",
    
    "relUrl": "/ru-rRU/user/tak.html"
  },"5033": {
    "doc": "Интеграция TAK",
    "title": "Обзор",
    "content": "Модуль TAK позволяет нодам Meshtastic: . | Делиться данными о местоположении в формате CoT (Cursor on Target), совместимом с TAK | Отображаться как члены команды на картах TAK | Получать сообщения PLI (информация о местоположении) TAK | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/tak.html#%D0%BE%D0%B1%D0%B7%D0%BE%D1%80",
    
    "relUrl": "/ru-rRU/user/tak.html#обзор"
  },"5034": {
    "doc": "Интеграция TAK",
    "title": "Настройка",
    "content": "Необходимые условия . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. Настройки . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | Настройка | Описание | . | Цвет команды | Цвет твоей команды на карте TAK (например, Синий, Красный, Голубой, Зелёный) | . | Роль участника | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 Совет: Цвета команд/ролей являются стандартными цветами принадлежности в TAK. Coordinate with your TAK team to use consistent team assignments. Локальный TAK-сервер . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. Сервер привязывается только к локальному хосту (127.0.0.1:8089) и использует TLS с взаимной аутентификацией по сертификатам (mTLS), поэтому он недоступен с других устройств в сети. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK Mesh Channel — выбирает, в какой канал Meshtastic отправляется исходящий трафик TAK (по умолчанию: основной канал, индекс 0). Входящий трафик TAK принимается с любого канала. Соответствует аналогичной настройке на iOS и в устаревшем плагине ATAK. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | Экспорт пакета данных TAK — создаёт пакет данных .zip, который ATAK/iTAK может импортировать для подключения к этому серверу. | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/tak.html#%D0%BD%D0%B0%D1%81%D1%82%D1%80%D0%BE%D0%B9%D0%BA%D0%B0",
    
    "relUrl": "/ru-rRU/user/tak.html#настройка"
  },"5035": {
    "doc": "Интеграция TAK",
    "title": "Роли TAK",
    "content": "Ноды, настроенные с ролями, связанными с TAK, ведут себя иначе, чем стандартные клиенты: . | Роль | Описание | . | TAK | Полная совместимость с TAK — отправляет и принимает данные CoT, сообщения чата и обновления PLI. Выполняет функции стандартного клиента и TAK-моста. | . | TAK Tracker | Вывод только координат в формате TAK — автоматически передаёт PLI через равные промежутки времени без участия пользователя. Оптимизирован для автономных маячков местоположения (транспортные средства, оборудование, путевые точки). Не ретранслирует сообщения чата. | . 💡 Совет: Используйте TAK Tracker для устройств, которым требуется только передавать координаты (например, радио, установленное в автомобиле). Используйте TAK для устройств, где пользователи активно участвуют в операциях TAK. Формат CoT (Cursor on Target) . Сообщения TAK используют формат XML Cursor on Target — военный стандарт для обмена данными о ситуационной осведомлённости. Meshtastic преобразует свои внутренние сообщения protobuf в формат CoT при соединении с системами TAK, поэтому ручное преобразование формата не требуется. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/tak.html#%D1%80%D0%BE%D0%BB%D0%B8-tak",
    
    "relUrl": "/ru-rRU/user/tak.html#роли-tak"
  },"5036": {
    "doc": "Интеграция TAK",
    "title": "Формат передачи (V1 / V2)",
    "content": "Meshtastic поддерживает два формата передачи данных TAK, которые выбираются автоматически в зависимости от прошивки подключённого радио — ручная настройка не требуется: . | Формат | Совместимость | Особенности | . | V1 (Устаревший) | Прошивка 2.7.x и старше | Простое кодирование protobuf на порт 72. Поддерживает только передачу местоположения (PLI) и чат (GeoChat) — фигуры, маркеры, маршруты и другие типизированные события CoT отбрасываются | . | V2 (Текущий) | Прошивка 2.8.0 и новее | Компактное кодирование со сжатием zstd на порт 78. Добавляет типы CoT: фигуры, маркеры, маршруты, воздушные суда, эвакуацию, чрезвычайные ситуации и задачи — в дополнение ко всему, что поддерживает V1 | . Нода продолжает ретранслировать устаревшие пакеты V1 от старых нод, даже если сама работает на V2, поэтому смешанные по прошивке mesh-сети продолжают функционировать. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/tak.html#%D1%84%D0%BE%D1%80%D0%BC%D0%B0%D1%82-%D0%BF%D0%B5%D1%80%D0%B5%D0%B4%D0%B0%D1%87%D0%B8-v1--v2",
    
    "relUrl": "/ru-rRU/user/tak.html#формат-передачи-v1--v2"
  },"5037": {
    "doc": "Интеграция TAK",
    "title": "Использование с ATAK",
    "content": "После настройки: . | Ноды Meshtastic отображаются как маркеры на карте ATAK с подписями позывных | Сообщения чата могут передаваться между mesh-сетью и сетями TAK | Обновления местоположения передаются двунаправленно между Meshtastic и TAK | Ноды TAK Tracker автоматически передают PLI — их координаты отображаются на картах ATAK без какой-либо настройки на стороне ATAK | . ℹ️ Note: TAK integration requires specific node roles. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/tak.html#%D0%B8%D1%81%D0%BF%D0%BE%D0%BB%D1%8C%D0%B7%D0%BE%D0%B2%D0%B0%D0%BD%D0%B8%D0%B5-%D1%81-atak",
    
    "relUrl": "/ru-rRU/user/tak.html#использование-с-atak"
  },"5038": {
    "doc": "Интеграция TAK",
    "title": "Устранение неполадок",
    "content": "| Проблема | Причина | Решение | . | Нода не отображается на карте ATAK | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Данные о местоположении устарели | Потерян сигнал GPS или слишком большой интервал | Проверьте состояние GPS; уменьшите интервал передачи координат в настройках Position Config | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | Фигуры, маркеры или маршруты не передаются | Отправляющая нода использует устаревший V1 (прошивка 2.7.x или старше) | Обновите прошивку отправляющей ноды до 2.8.0+ для использования формата передачи V2 | . | Данные CoT не передаются | Несовпадение каналов | Все ноды TAK должны находиться на одном канале с одинаковым шифрованием | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/tak.html#%D1%83%D1%81%D1%82%D1%80%D0%B0%D0%BD%D0%B5%D0%BD%D0%B8%D0%B5-%D0%BD%D0%B5%D0%BF%D0%BE%D0%BB%D0%B0%D0%B4%D0%BE%D0%BA",
    
    "relUrl": "/ru-rRU/user/tak.html#устранение-неполадок"
  },"5039": {
    "doc": "Интеграция TAK",
    "title": "Соображения безопасности",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/tak.html#%D1%81%D0%BE%D0%BE%D0%B1%D1%80%D0%B0%D0%B6%D0%B5%D0%BD%D0%B8%D1%8F-%D0%B1%D0%B5%D0%B7%D0%BE%D0%BF%D0%B0%D1%81%D0%BD%D0%BE%D1%81%D1%82%D0%B8",
    
    "relUrl": "/ru-rRU/user/tak.html#соображения-безопасности"
  },"5040": {
    "doc": "Интеграция TAK",
    "title": "Связанные темы",
    "content": ". | Настройки — Модули и администрирование — конфигурация модуля TAK | Ноды — роли TAK и TAK Tracker в списке нод | Карта и путевые точки — расположение нод на карте | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/tak.html#%D1%81%D0%B2%D1%8F%D0%B7%D0%B0%D0%BD%D0%BD%D1%8B%D0%B5-%D1%82%D0%B5%D0%BC%D1%8B",
    
    "relUrl": "/ru-rRU/user/tak.html#связанные-темы"
  },"5041": {
    "doc": "TAK Integration",
    "title": "TAK Integration",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/tak.html",
    
    "relUrl": "/cs-rCZ/user/tak.html"
  },"5042": {
    "doc": "TAK Integration",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/tak.html#overview",
    
    "relUrl": "/cs-rCZ/user/tak.html#overview"
  },"5043": {
    "doc": "TAK Integration",
    "title": "Setup",
    "content": "Prerequisites . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. Nastavení . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | Nastavení | Popis | . | Team Color | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Member Role | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 Tip: Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments. Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. The server binds to localhost only (127.0.0.1:8089) and uses TLS with mutual certificate authentication (mTLS), so it is not reachable from other devices on the network. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK Mesh Channel — selects which Meshtastic channel outgoing TAK traffic is sent on (default: the primary channel, index 0). Incoming TAK traffic is accepted from any channel. Matches the equivalent setting on iOS and in the legacy ATAK plugin. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | Export TAK Data Package — generates a .zip data package that ATAK/iTAK can import to connect to this server. | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/tak.html#setup",
    
    "relUrl": "/cs-rCZ/user/tak.html#setup"
  },"5044": {
    "doc": "TAK Integration",
    "title": "TAK Roles",
    "content": "Nodes configured with TAK-related roles behave differently from standard clients: . | Role | Popis | . | 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. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/tak.html#tak-roles",
    
    "relUrl": "/cs-rCZ/user/tak.html#tak-roles"
  },"5045": {
    "doc": "TAK Integration",
    "title": "Wire Format (V1 / V2)",
    "content": "Meshtastic supports two TAK wire formats, chosen automatically based on the connected radio’s firmware — no manual configuration needed: . | Format | Compatibility | Features | . | V1 (Legacy) | Firmware 2.7.x and older | Bare protobuf encoding on port 72. Supports position sharing (PLI) and chat (GeoChat) only — shapes, markers, routes, and other typed CoT events are dropped | . | V2 (Current) | Firmware 2.8.0+ | Compact, zstd-compressed encoding on port 78. Adds shapes, markers, routes, aircraft, casevac, emergency, and task CoT types on top of everything V1 supports | . A node still relays legacy V1 packets from older nodes even while running V2 itself, so mixed-firmware meshes keep working. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/tak.html#wire-format-v1--v2",
    
    "relUrl": "/cs-rCZ/user/tak.html#wire-format-v1--v2"
  },"5046": {
    "doc": "TAK Integration",
    "title": "Usage with ATAK",
    "content": "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. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/tak.html#usage-with-atak",
    
    "relUrl": "/cs-rCZ/user/tak.html#usage-with-atak"
  },"5047": {
    "doc": "TAK Integration",
    "title": "Troubleshooting",
    "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | Shapes, markers, or routes not bridging | Sending node is on legacy V1 (firmware 2.7.x or older) | Update the sending node’s firmware to 2.8.0+ for V2 wire format | . | CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/tak.html#troubleshooting",
    
    "relUrl": "/cs-rCZ/user/tak.html#troubleshooting"
  },"5048": {
    "doc": "TAK Integration",
    "title": "Security Considerations",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/tak.html#security-considerations",
    
    "relUrl": "/cs-rCZ/user/tak.html#security-considerations"
  },"5049": {
    "doc": "TAK Integration",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — TAK module configuration | Nodes — TAK and TAK Tracker roles in the node list | Map & Waypoints — node positions on the map | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/tak.html#related-topics",
    
    "relUrl": "/cs-rCZ/user/tak.html#related-topics"
  },"5050": {
    "doc": "TAK Integration",
    "title": "TAK Integration",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/tak.html",
    
    "relUrl": "/bg-rBG/user/tak.html"
  },"5051": {
    "doc": "TAK Integration",
    "title": "Преглед",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/tak.html#%D0%BF%D1%80%D0%B5%D0%B3%D0%BB%D0%B5%D0%B4",
    
    "relUrl": "/bg-rBG/user/tak.html#преглед"
  },"5052": {
    "doc": "TAK Integration",
    "title": "Setup",
    "content": "Prerequisites . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. Конфигурация . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | Настройка | Описание | . | Цвят на екипа | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Роля на члена | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 Tip: Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments. Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. The server binds to localhost only (127.0.0.1:8089) and uses TLS with mutual certificate authentication (mTLS), so it is not reachable from other devices on the network. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK Mesh Channel — selects which Meshtastic channel outgoing TAK traffic is sent on (default: the primary channel, index 0). Incoming TAK traffic is accepted from any channel. Matches the equivalent setting on iOS and in the legacy ATAK plugin. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | Export TAK Data Package — generates a .zip data package that ATAK/iTAK can import to connect to this server. | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/tak.html#setup",
    
    "relUrl": "/bg-rBG/user/tak.html#setup"
  },"5053": {
    "doc": "TAK Integration",
    "title": "TAK Roles",
    "content": "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. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/tak.html#tak-roles",
    
    "relUrl": "/bg-rBG/user/tak.html#tak-roles"
  },"5054": {
    "doc": "TAK Integration",
    "title": "Wire Format (V1 / V2)",
    "content": "Meshtastic supports two TAK wire formats, chosen automatically based on the connected radio’s firmware — no manual configuration needed: . | Format | Съвместимост | Характеристики | . | V1 (Legacy) | Firmware 2.7.x and older | Bare protobuf encoding on port 72. Supports position sharing (PLI) and chat (GeoChat) only — shapes, markers, routes, and other typed CoT events are dropped | . | V2 (Current) | Firmware 2.8.0+ | Compact, zstd-compressed encoding on port 78. Adds shapes, markers, routes, aircraft, casevac, emergency, and task CoT types on top of everything V1 supports | . A node still relays legacy V1 packets from older nodes even while running V2 itself, so mixed-firmware meshes keep working. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/tak.html#wire-format-v1--v2",
    
    "relUrl": "/bg-rBG/user/tak.html#wire-format-v1--v2"
  },"5055": {
    "doc": "TAK Integration",
    "title": "Usage with ATAK",
    "content": "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. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/tak.html#usage-with-atak",
    
    "relUrl": "/bg-rBG/user/tak.html#usage-with-atak"
  },"5056": {
    "doc": "TAK Integration",
    "title": "Отстраняване на неизправности",
    "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | Shapes, markers, or routes not bridging | Sending node is on legacy V1 (firmware 2.7.x or older) | Update the sending node’s firmware to 2.8.0+ for V2 wire format | . | CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/tak.html#%D0%BE%D1%82%D1%81%D1%82%D1%80%D0%B0%D0%BD%D1%8F%D0%B2%D0%B0%D0%BD%D0%B5-%D0%BD%D0%B0-%D0%BD%D0%B5%D0%B8%D0%B7%D0%BF%D1%80%D0%B0%D0%B2%D0%BD%D0%BE%D1%81%D1%82%D0%B8",
    
    "relUrl": "/bg-rBG/user/tak.html#отстраняване-на-неизправности"
  },"5057": {
    "doc": "TAK Integration",
    "title": "Security Considerations",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/tak.html#security-considerations",
    
    "relUrl": "/bg-rBG/user/tak.html#security-considerations"
  },"5058": {
    "doc": "TAK Integration",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — TAK module configuration | Nodes — TAK and TAK Tracker roles in the node list | Map & Waypoints — node positions on the map | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/tak.html#related-topics",
    
    "relUrl": "/bg-rBG/user/tak.html#related-topics"
  },"5059": {
    "doc": "TAK Integration",
    "title": "TAK Integration",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/tak.html",
    
    "relUrl": "/ga-rIE/user/tak.html"
  },"5060": {
    "doc": "TAK Integration",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/tak.html#overview",
    
    "relUrl": "/ga-rIE/user/tak.html#overview"
  },"5061": {
    "doc": "TAK Integration",
    "title": "Setup",
    "content": "Prerequisites . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. Configuration . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | Setting | Cur síos | . | Team Color | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Member Role | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 Tip: Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments. Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. The server binds to localhost only (127.0.0.1:8089) and uses TLS with mutual certificate authentication (mTLS), so it is not reachable from other devices on the network. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK Mesh Channel — selects which Meshtastic channel outgoing TAK traffic is sent on (default: the primary channel, index 0). Incoming TAK traffic is accepted from any channel. Matches the equivalent setting on iOS and in the legacy ATAK plugin. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | Export TAK Data Package — generates a .zip data package that ATAK/iTAK can import to connect to this server. | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/tak.html#setup",
    
    "relUrl": "/ga-rIE/user/tak.html#setup"
  },"5062": {
    "doc": "TAK Integration",
    "title": "TAK Roles",
    "content": "Nodes configured with TAK-related roles behave differently from standard clients: . | Role | Cur síos | . | 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. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/tak.html#tak-roles",
    
    "relUrl": "/ga-rIE/user/tak.html#tak-roles"
  },"5063": {
    "doc": "TAK Integration",
    "title": "Wire Format (V1 / V2)",
    "content": "Meshtastic supports two TAK wire formats, chosen automatically based on the connected radio’s firmware — no manual configuration needed: . | Format | Compatibility | Features | . | V1 (Legacy) | Firmware 2.7.x and older | Bare protobuf encoding on port 72. Supports position sharing (PLI) and chat (GeoChat) only — shapes, markers, routes, and other typed CoT events are dropped | . | V2 (Current) | Firmware 2.8.0+ | Compact, zstd-compressed encoding on port 78. Adds shapes, markers, routes, aircraft, casevac, emergency, and task CoT types on top of everything V1 supports | . A node still relays legacy V1 packets from older nodes even while running V2 itself, so mixed-firmware meshes keep working. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/tak.html#wire-format-v1--v2",
    
    "relUrl": "/ga-rIE/user/tak.html#wire-format-v1--v2"
  },"5064": {
    "doc": "TAK Integration",
    "title": "Usage with ATAK",
    "content": "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. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/tak.html#usage-with-atak",
    
    "relUrl": "/ga-rIE/user/tak.html#usage-with-atak"
  },"5065": {
    "doc": "TAK Integration",
    "title": "Troubleshooting",
    "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | Shapes, markers, or routes not bridging | Sending node is on legacy V1 (firmware 2.7.x or older) | Update the sending node’s firmware to 2.8.0+ for V2 wire format | . | CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/tak.html#troubleshooting",
    
    "relUrl": "/ga-rIE/user/tak.html#troubleshooting"
  },"5066": {
    "doc": "TAK Integration",
    "title": "Security Considerations",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/tak.html#security-considerations",
    
    "relUrl": "/ga-rIE/user/tak.html#security-considerations"
  },"5067": {
    "doc": "TAK Integration",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — TAK module configuration | Nodes — TAK and TAK Tracker roles in the node list | Map & Waypoints — node positions on the map | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/tak.html#related-topics",
    
    "relUrl": "/ga-rIE/user/tak.html#related-topics"
  },"5068": {
    "doc": "TAK Integration",
    "title": "TAK Integration",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/tak.html",
    
    "relUrl": "/fr-rCA/user/tak.html"
  },"5069": {
    "doc": "TAK Integration",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/tak.html#overview",
    
    "relUrl": "/fr-rCA/user/tak.html#overview"
  },"5070": {
    "doc": "TAK Integration",
    "title": "Setup",
    "content": "Prerequisites . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. Configuration . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | Paramètre | Description | . | Couleur de l’équipe | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Rôle Membre | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 Tip: Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments. Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. The server binds to localhost only (127.0.0.1:8089) and uses TLS with mutual certificate authentication (mTLS), so it is not reachable from other devices on the network. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK Mesh Channel — selects which Meshtastic channel outgoing TAK traffic is sent on (default: the primary channel, index 0). Incoming TAK traffic is accepted from any channel. Matches the equivalent setting on iOS and in the legacy ATAK plugin. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | Export TAK Data Package — generates a .zip data package that ATAK/iTAK can import to connect to this server. | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/tak.html#setup",
    
    "relUrl": "/fr-rCA/user/tak.html#setup"
  },"5071": {
    "doc": "TAK Integration",
    "title": "TAK Roles",
    "content": "Nodes configured with TAK-related roles behave differently from standard clients: . | Rôle | Description | . | 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. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/tak.html#tak-roles",
    
    "relUrl": "/fr-rCA/user/tak.html#tak-roles"
  },"5072": {
    "doc": "TAK Integration",
    "title": "Wire Format (V1 / V2)",
    "content": "Meshtastic supports two TAK wire formats, chosen automatically based on the connected radio’s firmware — no manual configuration needed: . | Format | Compatibility | Features | . | V1 (Legacy) | Firmware 2.7.x and older | Bare protobuf encoding on port 72. Supports position sharing (PLI) and chat (GeoChat) only — shapes, markers, routes, and other typed CoT events are dropped | . | V2 (Current) | Firmware 2.8.0+ | Compact, zstd-compressed encoding on port 78. Adds shapes, markers, routes, aircraft, casevac, emergency, and task CoT types on top of everything V1 supports | . A node still relays legacy V1 packets from older nodes even while running V2 itself, so mixed-firmware meshes keep working. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/tak.html#wire-format-v1--v2",
    
    "relUrl": "/fr-rCA/user/tak.html#wire-format-v1--v2"
  },"5073": {
    "doc": "TAK Integration",
    "title": "Usage with ATAK",
    "content": "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. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/tak.html#usage-with-atak",
    
    "relUrl": "/fr-rCA/user/tak.html#usage-with-atak"
  },"5074": {
    "doc": "TAK Integration",
    "title": "Troubleshooting",
    "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | Shapes, markers, or routes not bridging | Sending node is on legacy V1 (firmware 2.7.x or older) | Update the sending node’s firmware to 2.8.0+ for V2 wire format | . | CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/tak.html#troubleshooting",
    
    "relUrl": "/fr-rCA/user/tak.html#troubleshooting"
  },"5075": {
    "doc": "TAK Integration",
    "title": "Security Considerations",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/tak.html#security-considerations",
    
    "relUrl": "/fr-rCA/user/tak.html#security-considerations"
  },"5076": {
    "doc": "TAK Integration",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — TAK module configuration | Nodes — TAK and TAK Tracker roles in the node list | Map & Waypoints — node positions on the map | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/tak.html#related-topics",
    
    "relUrl": "/fr-rCA/user/tak.html#related-topics"
  },"5077": {
    "doc": "TAK Integration",
    "title": "TAK Integration",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/srp/user/tak.html",
    
    "relUrl": "/srp/user/tak.html"
  },"5078": {
    "doc": "TAK Integration",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/srp/user/tak.html#overview",
    
    "relUrl": "/srp/user/tak.html#overview"
  },"5079": {
    "doc": "TAK Integration",
    "title": "Setup",
    "content": "Prerequisites . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. Configuration . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | Setting | Опис | . | Team Color | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Member Role | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 Tip: Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments. Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. The server binds to localhost only (127.0.0.1:8089) and uses TLS with mutual certificate authentication (mTLS), so it is not reachable from other devices on the network. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK Mesh Channel — selects which Meshtastic channel outgoing TAK traffic is sent on (default: the primary channel, index 0). Incoming TAK traffic is accepted from any channel. Matches the equivalent setting on iOS and in the legacy ATAK plugin. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | Export TAK Data Package — generates a .zip data package that ATAK/iTAK can import to connect to this server. | . ",
    "url": "/Meshtastic-Android/main/srp/user/tak.html#setup",
    
    "relUrl": "/srp/user/tak.html#setup"
  },"5080": {
    "doc": "TAK Integration",
    "title": "TAK Roles",
    "content": "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. ",
    "url": "/Meshtastic-Android/main/srp/user/tak.html#tak-roles",
    
    "relUrl": "/srp/user/tak.html#tak-roles"
  },"5081": {
    "doc": "TAK Integration",
    "title": "Wire Format (V1 / V2)",
    "content": "Meshtastic supports two TAK wire formats, chosen automatically based on the connected radio’s firmware — no manual configuration needed: . | Format | Compatibility | Features | . | V1 (Legacy) | Firmware 2.7.x and older | Bare protobuf encoding on port 72. Supports position sharing (PLI) and chat (GeoChat) only — shapes, markers, routes, and other typed CoT events are dropped | . | V2 (Current) | Firmware 2.8.0+ | Compact, zstd-compressed encoding on port 78. Adds shapes, markers, routes, aircraft, casevac, emergency, and task CoT types on top of everything V1 supports | . A node still relays legacy V1 packets from older nodes even while running V2 itself, so mixed-firmware meshes keep working. ",
    "url": "/Meshtastic-Android/main/srp/user/tak.html#wire-format-v1--v2",
    
    "relUrl": "/srp/user/tak.html#wire-format-v1--v2"
  },"5082": {
    "doc": "TAK Integration",
    "title": "Usage with ATAK",
    "content": "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. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/srp/user/tak.html#usage-with-atak",
    
    "relUrl": "/srp/user/tak.html#usage-with-atak"
  },"5083": {
    "doc": "TAK Integration",
    "title": "Troubleshooting",
    "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | Shapes, markers, or routes not bridging | Sending node is on legacy V1 (firmware 2.7.x or older) | Update the sending node’s firmware to 2.8.0+ for V2 wire format | . | CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption | . ",
    "url": "/Meshtastic-Android/main/srp/user/tak.html#troubleshooting",
    
    "relUrl": "/srp/user/tak.html#troubleshooting"
  },"5084": {
    "doc": "TAK Integration",
    "title": "Security Considerations",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/srp/user/tak.html#security-considerations",
    
    "relUrl": "/srp/user/tak.html#security-considerations"
  },"5085": {
    "doc": "TAK Integration",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — TAK module configuration | Nodes — TAK and TAK Tracker roles in the node list | Map & Waypoints — node positions on the map | . ",
    "url": "/Meshtastic-Android/main/srp/user/tak.html#related-topics",
    
    "relUrl": "/srp/user/tak.html#related-topics"
  },"5086": {
    "doc": "TAK Integration",
    "title": "TAK Integration",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/tak.html",
    
    "relUrl": "/ca-rES/user/tak.html"
  },"5087": {
    "doc": "TAK Integration",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/tak.html#overview",
    
    "relUrl": "/ca-rES/user/tak.html#overview"
  },"5088": {
    "doc": "TAK Integration",
    "title": "Setup",
    "content": "Prerequisites . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. Configuration . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | Setting | Descripció | . | Team Color | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Member Role | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 Tip: Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments. Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. The server binds to localhost only (127.0.0.1:8089) and uses TLS with mutual certificate authentication (mTLS), so it is not reachable from other devices on the network. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK Mesh Channel — selects which Meshtastic channel outgoing TAK traffic is sent on (default: the primary channel, index 0). Incoming TAK traffic is accepted from any channel. Matches the equivalent setting on iOS and in the legacy ATAK plugin. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | Export TAK Data Package — generates a .zip data package that ATAK/iTAK can import to connect to this server. | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/tak.html#setup",
    
    "relUrl": "/ca-rES/user/tak.html#setup"
  },"5089": {
    "doc": "TAK Integration",
    "title": "TAK Roles",
    "content": "Nodes configured with TAK-related roles behave differently from standard clients: . | Role | Descripció | . | 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. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/tak.html#tak-roles",
    
    "relUrl": "/ca-rES/user/tak.html#tak-roles"
  },"5090": {
    "doc": "TAK Integration",
    "title": "Wire Format (V1 / V2)",
    "content": "Meshtastic supports two TAK wire formats, chosen automatically based on the connected radio’s firmware — no manual configuration needed: . | Format | Compatibility | Features | . | V1 (Legacy) | Firmware 2.7.x and older | Bare protobuf encoding on port 72. Supports position sharing (PLI) and chat (GeoChat) only — shapes, markers, routes, and other typed CoT events are dropped | . | V2 (Current) | Firmware 2.8.0+ | Compact, zstd-compressed encoding on port 78. Adds shapes, markers, routes, aircraft, casevac, emergency, and task CoT types on top of everything V1 supports | . A node still relays legacy V1 packets from older nodes even while running V2 itself, so mixed-firmware meshes keep working. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/tak.html#wire-format-v1--v2",
    
    "relUrl": "/ca-rES/user/tak.html#wire-format-v1--v2"
  },"5091": {
    "doc": "TAK Integration",
    "title": "Usage with ATAK",
    "content": "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. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/tak.html#usage-with-atak",
    
    "relUrl": "/ca-rES/user/tak.html#usage-with-atak"
  },"5092": {
    "doc": "TAK Integration",
    "title": "Troubleshooting",
    "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | Shapes, markers, or routes not bridging | Sending node is on legacy V1 (firmware 2.7.x or older) | Update the sending node’s firmware to 2.8.0+ for V2 wire format | . | CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/tak.html#troubleshooting",
    
    "relUrl": "/ca-rES/user/tak.html#troubleshooting"
  },"5093": {
    "doc": "TAK Integration",
    "title": "Security Considerations",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/tak.html#security-considerations",
    
    "relUrl": "/ca-rES/user/tak.html#security-considerations"
  },"5094": {
    "doc": "TAK Integration",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — TAK module configuration | Nodes — TAK and TAK Tracker roles in the node list | Map & Waypoints — node positions on the map | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/tak.html#related-topics",
    
    "relUrl": "/ca-rES/user/tak.html#related-topics"
  },"5095": {
    "doc": "TAK Integration",
    "title": "TAK Integration",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/tak.html",
    
    "relUrl": "/ko-rKR/user/tak.html"
  },"5096": {
    "doc": "TAK Integration",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/tak.html#overview",
    
    "relUrl": "/ko-rKR/user/tak.html#overview"
  },"5097": {
    "doc": "TAK Integration",
    "title": "Setup",
    "content": "Prerequisites . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. 설정 . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | Setting | 설명 | . | Team Color | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Member Role | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 Tip: Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments. Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. The server binds to localhost only (127.0.0.1:8089) and uses TLS with mutual certificate authentication (mTLS), so it is not reachable from other devices on the network. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK Mesh Channel — selects which Meshtastic channel outgoing TAK traffic is sent on (default: the primary channel, index 0). Incoming TAK traffic is accepted from any channel. Matches the equivalent setting on iOS and in the legacy ATAK plugin. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | Export TAK Data Package — generates a .zip data package that ATAK/iTAK can import to connect to this server. | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/tak.html#setup",
    
    "relUrl": "/ko-rKR/user/tak.html#setup"
  },"5098": {
    "doc": "TAK Integration",
    "title": "TAK Roles",
    "content": "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. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/tak.html#tak-roles",
    
    "relUrl": "/ko-rKR/user/tak.html#tak-roles"
  },"5099": {
    "doc": "TAK Integration",
    "title": "Wire Format (V1 / V2)",
    "content": "Meshtastic supports two TAK wire formats, chosen automatically based on the connected radio’s firmware — no manual configuration needed: . | Format | Compatibility | Features | . | V1 (Legacy) | Firmware 2.7.x and older | Bare protobuf encoding on port 72. Supports position sharing (PLI) and chat (GeoChat) only — shapes, markers, routes, and other typed CoT events are dropped | . | V2 (Current) | Firmware 2.8.0+ | Compact, zstd-compressed encoding on port 78. Adds shapes, markers, routes, aircraft, casevac, emergency, and task CoT types on top of everything V1 supports | . A node still relays legacy V1 packets from older nodes even while running V2 itself, so mixed-firmware meshes keep working. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/tak.html#wire-format-v1--v2",
    
    "relUrl": "/ko-rKR/user/tak.html#wire-format-v1--v2"
  },"5100": {
    "doc": "TAK Integration",
    "title": "Usage with ATAK",
    "content": "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. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/tak.html#usage-with-atak",
    
    "relUrl": "/ko-rKR/user/tak.html#usage-with-atak"
  },"5101": {
    "doc": "TAK Integration",
    "title": "Troubleshooting",
    "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | Shapes, markers, or routes not bridging | Sending node is on legacy V1 (firmware 2.7.x or older) | Update the sending node’s firmware to 2.8.0+ for V2 wire format | . | CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/tak.html#troubleshooting",
    
    "relUrl": "/ko-rKR/user/tak.html#troubleshooting"
  },"5102": {
    "doc": "TAK Integration",
    "title": "Security Considerations",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/tak.html#security-considerations",
    
    "relUrl": "/ko-rKR/user/tak.html#security-considerations"
  },"5103": {
    "doc": "TAK Integration",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — TAK module configuration | Nodes — TAK and TAK Tracker roles in the node list | Map & Waypoints — node positions on the map | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/tak.html#related-topics",
    
    "relUrl": "/ko-rKR/user/tak.html#related-topics"
  },"5104": {
    "doc": "TAK Integration",
    "title": "TAK Integration",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/tak.html",
    
    "relUrl": "/sv-rSE/user/tak.html"
  },"5105": {
    "doc": "TAK Integration",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/tak.html#overview",
    
    "relUrl": "/sv-rSE/user/tak.html#overview"
  },"5106": {
    "doc": "TAK Integration",
    "title": "Setup",
    "content": "Prerequisites . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. Konfiguration . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | Setting | Beskrivning | . | Lagfärg | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Member Role | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 Tip: Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments. Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. The server binds to localhost only (127.0.0.1:8089) and uses TLS with mutual certificate authentication (mTLS), so it is not reachable from other devices on the network. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK Mesh Channel — selects which Meshtastic channel outgoing TAK traffic is sent on (default: the primary channel, index 0). Incoming TAK traffic is accepted from any channel. Matches the equivalent setting on iOS and in the legacy ATAK plugin. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | Export TAK Data Package — generates a .zip data package that ATAK/iTAK can import to connect to this server. | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/tak.html#setup",
    
    "relUrl": "/sv-rSE/user/tak.html#setup"
  },"5107": {
    "doc": "TAK Integration",
    "title": "TAK Roles",
    "content": "Nodes configured with TAK-related roles behave differently from standard clients: . | Roll | Beskrivning | . | 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. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/tak.html#tak-roles",
    
    "relUrl": "/sv-rSE/user/tak.html#tak-roles"
  },"5108": {
    "doc": "TAK Integration",
    "title": "Wire Format (V1 / V2)",
    "content": "Meshtastic supports two TAK wire formats, chosen automatically based on the connected radio’s firmware — no manual configuration needed: . | Format | Compatibility | Features | . | V1 (Legacy) | Firmware 2.7.x and older | Bare protobuf encoding on port 72. Supports position sharing (PLI) and chat (GeoChat) only — shapes, markers, routes, and other typed CoT events are dropped | . | V2 (Current) | Firmware 2.8.0+ | Compact, zstd-compressed encoding on port 78. Adds shapes, markers, routes, aircraft, casevac, emergency, and task CoT types on top of everything V1 supports | . A node still relays legacy V1 packets from older nodes even while running V2 itself, so mixed-firmware meshes keep working. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/tak.html#wire-format-v1--v2",
    
    "relUrl": "/sv-rSE/user/tak.html#wire-format-v1--v2"
  },"5109": {
    "doc": "TAK Integration",
    "title": "Usage with ATAK",
    "content": "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. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/tak.html#usage-with-atak",
    
    "relUrl": "/sv-rSE/user/tak.html#usage-with-atak"
  },"5110": {
    "doc": "TAK Integration",
    "title": "Felsökning",
    "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | Shapes, markers, or routes not bridging | Sending node is on legacy V1 (firmware 2.7.x or older) | Update the sending node’s firmware to 2.8.0+ for V2 wire format | . | CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/tak.html#fels%C3%B6kning",
    
    "relUrl": "/sv-rSE/user/tak.html#felsökning"
  },"5111": {
    "doc": "TAK Integration",
    "title": "Security Considerations",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/tak.html#security-considerations",
    
    "relUrl": "/sv-rSE/user/tak.html#security-considerations"
  },"5112": {
    "doc": "TAK Integration",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — TAK module configuration | Nodes — TAK and TAK Tracker roles in the node list | Map & Waypoints — node positions on the map | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/tak.html#related-topics",
    
    "relUrl": "/sv-rSE/user/tak.html#related-topics"
  },"5113": {
    "doc": "TAK Integration",
    "title": "TAK Integration",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/tak.html",
    
    "relUrl": "/ht-rHT/user/tak.html"
  },"5114": {
    "doc": "TAK Integration",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/tak.html#overview",
    
    "relUrl": "/ht-rHT/user/tak.html#overview"
  },"5115": {
    "doc": "TAK Integration",
    "title": "Setup",
    "content": "Prerequisites . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. Configuration . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | Setting | Deskripsyon | . | Team Color | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Member Role | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 Tip: Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments. Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. The server binds to localhost only (127.0.0.1:8089) and uses TLS with mutual certificate authentication (mTLS), so it is not reachable from other devices on the network. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK Mesh Channel — selects which Meshtastic channel outgoing TAK traffic is sent on (default: the primary channel, index 0). Incoming TAK traffic is accepted from any channel. Matches the equivalent setting on iOS and in the legacy ATAK plugin. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | Export TAK Data Package — generates a .zip data package that ATAK/iTAK can import to connect to this server. | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/tak.html#setup",
    
    "relUrl": "/ht-rHT/user/tak.html#setup"
  },"5116": {
    "doc": "TAK Integration",
    "title": "TAK Roles",
    "content": "Nodes configured with TAK-related roles behave differently from standard clients: . | Role | Deskripsyon | . | 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. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/tak.html#tak-roles",
    
    "relUrl": "/ht-rHT/user/tak.html#tak-roles"
  },"5117": {
    "doc": "TAK Integration",
    "title": "Wire Format (V1 / V2)",
    "content": "Meshtastic supports two TAK wire formats, chosen automatically based on the connected radio’s firmware — no manual configuration needed: . | Format | Compatibility | Features | . | V1 (Legacy) | Firmware 2.7.x and older | Bare protobuf encoding on port 72. Supports position sharing (PLI) and chat (GeoChat) only — shapes, markers, routes, and other typed CoT events are dropped | . | V2 (Current) | Firmware 2.8.0+ | Compact, zstd-compressed encoding on port 78. Adds shapes, markers, routes, aircraft, casevac, emergency, and task CoT types on top of everything V1 supports | . A node still relays legacy V1 packets from older nodes even while running V2 itself, so mixed-firmware meshes keep working. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/tak.html#wire-format-v1--v2",
    
    "relUrl": "/ht-rHT/user/tak.html#wire-format-v1--v2"
  },"5118": {
    "doc": "TAK Integration",
    "title": "Usage with ATAK",
    "content": "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. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/tak.html#usage-with-atak",
    
    "relUrl": "/ht-rHT/user/tak.html#usage-with-atak"
  },"5119": {
    "doc": "TAK Integration",
    "title": "Troubleshooting",
    "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | Shapes, markers, or routes not bridging | Sending node is on legacy V1 (firmware 2.7.x or older) | Update the sending node’s firmware to 2.8.0+ for V2 wire format | . | CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/tak.html#troubleshooting",
    
    "relUrl": "/ht-rHT/user/tak.html#troubleshooting"
  },"5120": {
    "doc": "TAK Integration",
    "title": "Security Considerations",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/tak.html#security-considerations",
    
    "relUrl": "/ht-rHT/user/tak.html#security-considerations"
  },"5121": {
    "doc": "TAK Integration",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — TAK module configuration | Nodes — TAK and TAK Tracker roles in the node list | Map & Waypoints — node positions on the map | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/tak.html#related-topics",
    
    "relUrl": "/ht-rHT/user/tak.html#related-topics"
  },"5122": {
    "doc": "TAK Integration",
    "title": "TAK Integration",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/tak.html",
    
    "relUrl": "/sr-rLatn/user/tak.html"
  },"5123": {
    "doc": "TAK Integration",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/tak.html#overview",
    
    "relUrl": "/sr-rLatn/user/tak.html#overview"
  },"5124": {
    "doc": "TAK Integration",
    "title": "Setup",
    "content": "Prerequisites . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. Configuration . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | Setting | Опис | . | Team Color | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Member Role | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 Tip: Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments. Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. The server binds to localhost only (127.0.0.1:8089) and uses TLS with mutual certificate authentication (mTLS), so it is not reachable from other devices on the network. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK Mesh Channel — selects which Meshtastic channel outgoing TAK traffic is sent on (default: the primary channel, index 0). Incoming TAK traffic is accepted from any channel. Matches the equivalent setting on iOS and in the legacy ATAK plugin. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | Export TAK Data Package — generates a .zip data package that ATAK/iTAK can import to connect to this server. | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/tak.html#setup",
    
    "relUrl": "/sr-rLatn/user/tak.html#setup"
  },"5125": {
    "doc": "TAK Integration",
    "title": "TAK Roles",
    "content": "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. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/tak.html#tak-roles",
    
    "relUrl": "/sr-rLatn/user/tak.html#tak-roles"
  },"5126": {
    "doc": "TAK Integration",
    "title": "Wire Format (V1 / V2)",
    "content": "Meshtastic supports two TAK wire formats, chosen automatically based on the connected radio’s firmware — no manual configuration needed: . | Format | Compatibility | Features | . | V1 (Legacy) | Firmware 2.7.x and older | Bare protobuf encoding on port 72. Supports position sharing (PLI) and chat (GeoChat) only — shapes, markers, routes, and other typed CoT events are dropped | . | V2 (Current) | Firmware 2.8.0+ | Compact, zstd-compressed encoding on port 78. Adds shapes, markers, routes, aircraft, casevac, emergency, and task CoT types on top of everything V1 supports | . A node still relays legacy V1 packets from older nodes even while running V2 itself, so mixed-firmware meshes keep working. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/tak.html#wire-format-v1--v2",
    
    "relUrl": "/sr-rLatn/user/tak.html#wire-format-v1--v2"
  },"5127": {
    "doc": "TAK Integration",
    "title": "Usage with ATAK",
    "content": "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. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/tak.html#usage-with-atak",
    
    "relUrl": "/sr-rLatn/user/tak.html#usage-with-atak"
  },"5128": {
    "doc": "TAK Integration",
    "title": "Troubleshooting",
    "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | Shapes, markers, or routes not bridging | Sending node is on legacy V1 (firmware 2.7.x or older) | Update the sending node’s firmware to 2.8.0+ for V2 wire format | . | CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/tak.html#troubleshooting",
    
    "relUrl": "/sr-rLatn/user/tak.html#troubleshooting"
  },"5129": {
    "doc": "TAK Integration",
    "title": "Security Considerations",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/tak.html#security-considerations",
    
    "relUrl": "/sr-rLatn/user/tak.html#security-considerations"
  },"5130": {
    "doc": "TAK Integration",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — TAK module configuration | Nodes — TAK and TAK Tracker roles in the node list | Map & Waypoints — node positions on the map | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/tak.html#related-topics",
    
    "relUrl": "/sr-rLatn/user/tak.html#related-topics"
  },"5131": {
    "doc": "TAK Integration",
    "title": "TAK Integration",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/tak.html",
    
    "relUrl": "/nl-rNL/user/tak.html"
  },"5132": {
    "doc": "TAK Integration",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/tak.html#overview",
    
    "relUrl": "/nl-rNL/user/tak.html#overview"
  },"5133": {
    "doc": "TAK Integration",
    "title": "Setup",
    "content": "Prerequisites . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. Configuration . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | Setting | Beschrijving | . | Team Color | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Member Role | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 Tip: Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments. Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. The server binds to localhost only (127.0.0.1:8089) and uses TLS with mutual certificate authentication (mTLS), so it is not reachable from other devices on the network. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK Mesh Channel — selects which Meshtastic channel outgoing TAK traffic is sent on (default: the primary channel, index 0). Incoming TAK traffic is accepted from any channel. Matches the equivalent setting on iOS and in the legacy ATAK plugin. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | Export TAK Data Package — generates a .zip data package that ATAK/iTAK can import to connect to this server. | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/tak.html#setup",
    
    "relUrl": "/nl-rNL/user/tak.html#setup"
  },"5134": {
    "doc": "TAK Integration",
    "title": "TAK Roles",
    "content": "Nodes configured with TAK-related roles behave differently from standard clients: . | Functie | Beschrijving | . | 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. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/tak.html#tak-roles",
    
    "relUrl": "/nl-rNL/user/tak.html#tak-roles"
  },"5135": {
    "doc": "TAK Integration",
    "title": "Wire Format (V1 / V2)",
    "content": "Meshtastic supports two TAK wire formats, chosen automatically based on the connected radio’s firmware — no manual configuration needed: . | Format | Compatibility | Features | . | V1 (Legacy) | Firmware 2.7.x and older | Bare protobuf encoding on port 72. Supports position sharing (PLI) and chat (GeoChat) only — shapes, markers, routes, and other typed CoT events are dropped | . | V2 (Current) | Firmware 2.8.0+ | Compact, zstd-compressed encoding on port 78. Adds shapes, markers, routes, aircraft, casevac, emergency, and task CoT types on top of everything V1 supports | . A node still relays legacy V1 packets from older nodes even while running V2 itself, so mixed-firmware meshes keep working. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/tak.html#wire-format-v1--v2",
    
    "relUrl": "/nl-rNL/user/tak.html#wire-format-v1--v2"
  },"5136": {
    "doc": "TAK Integration",
    "title": "Usage with ATAK",
    "content": "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. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/tak.html#usage-with-atak",
    
    "relUrl": "/nl-rNL/user/tak.html#usage-with-atak"
  },"5137": {
    "doc": "TAK Integration",
    "title": "Troubleshooting",
    "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | Shapes, markers, or routes not bridging | Sending node is on legacy V1 (firmware 2.7.x or older) | Update the sending node’s firmware to 2.8.0+ for V2 wire format | . | CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/tak.html#troubleshooting",
    
    "relUrl": "/nl-rNL/user/tak.html#troubleshooting"
  },"5138": {
    "doc": "TAK Integration",
    "title": "Security Considerations",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/tak.html#security-considerations",
    
    "relUrl": "/nl-rNL/user/tak.html#security-considerations"
  },"5139": {
    "doc": "TAK Integration",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — TAK module configuration | Nodes — TAK and TAK Tracker roles in the node list | Map & Waypoints — node positions on the map | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/tak.html#related-topics",
    
    "relUrl": "/nl-rNL/user/tak.html#related-topics"
  },"5140": {
    "doc": "TAK Integration",
    "title": "TAK Integration",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/tak.html",
    
    "relUrl": "/uk-rUA/user/tak.html"
  },"5141": {
    "doc": "TAK Integration",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/tak.html#overview",
    
    "relUrl": "/uk-rUA/user/tak.html#overview"
  },"5142": {
    "doc": "TAK Integration",
    "title": "Setup",
    "content": "Prerequisites . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. Налаштування . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | Setting | Опис | . | Team Color | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Member Role | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 Tip: Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments. Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. The server binds to localhost only (127.0.0.1:8089) and uses TLS with mutual certificate authentication (mTLS), so it is not reachable from other devices on the network. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK Mesh Channel — selects which Meshtastic channel outgoing TAK traffic is sent on (default: the primary channel, index 0). Incoming TAK traffic is accepted from any channel. Matches the equivalent setting on iOS and in the legacy ATAK plugin. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | Export TAK Data Package — generates a .zip data package that ATAK/iTAK can import to connect to this server. | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/tak.html#setup",
    
    "relUrl": "/uk-rUA/user/tak.html#setup"
  },"5143": {
    "doc": "TAK Integration",
    "title": "TAK Roles",
    "content": "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. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/tak.html#tak-roles",
    
    "relUrl": "/uk-rUA/user/tak.html#tak-roles"
  },"5144": {
    "doc": "TAK Integration",
    "title": "Wire Format (V1 / V2)",
    "content": "Meshtastic supports two TAK wire formats, chosen automatically based on the connected radio’s firmware — no manual configuration needed: . | Format | Compatibility | Features | . | V1 (Legacy) | Firmware 2.7.x and older | Bare protobuf encoding on port 72. Supports position sharing (PLI) and chat (GeoChat) only — shapes, markers, routes, and other typed CoT events are dropped | . | V2 (Current) | Firmware 2.8.0+ | Compact, zstd-compressed encoding on port 78. Adds shapes, markers, routes, aircraft, casevac, emergency, and task CoT types on top of everything V1 supports | . A node still relays legacy V1 packets from older nodes even while running V2 itself, so mixed-firmware meshes keep working. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/tak.html#wire-format-v1--v2",
    
    "relUrl": "/uk-rUA/user/tak.html#wire-format-v1--v2"
  },"5145": {
    "doc": "TAK Integration",
    "title": "Usage with ATAK",
    "content": "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. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/tak.html#usage-with-atak",
    
    "relUrl": "/uk-rUA/user/tak.html#usage-with-atak"
  },"5146": {
    "doc": "TAK Integration",
    "title": "Troubleshooting",
    "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | Shapes, markers, or routes not bridging | Sending node is on legacy V1 (firmware 2.7.x or older) | Update the sending node’s firmware to 2.8.0+ for V2 wire format | . | CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/tak.html#troubleshooting",
    
    "relUrl": "/uk-rUA/user/tak.html#troubleshooting"
  },"5147": {
    "doc": "TAK Integration",
    "title": "Security Considerations",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/tak.html#security-considerations",
    
    "relUrl": "/uk-rUA/user/tak.html#security-considerations"
  },"5148": {
    "doc": "TAK Integration",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — TAK module configuration | Nodes — TAK and TAK Tracker roles in the node list | Map & Waypoints — node positions on the map | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/tak.html#related-topics",
    
    "relUrl": "/uk-rUA/user/tak.html#related-topics"
  },"5149": {
    "doc": "TAK-integraatio",
    "title": "TAK-integraatio",
    "content": "Meshtastic integroituu Team Awareness Kit (TAK) -ekosysteemiin, mikä mahdollistaa yhteentoimivuuden Meshtastic-radioiden ja TAK-sovellusten, kuten ATAKin ja WinTAKin, välillä. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/tak.html",
    
    "relUrl": "/fi-rFI/user/tak.html"
  },"5150": {
    "doc": "TAK-integraatio",
    "title": "Yleiskatsaus",
    "content": "TAK-moduuli mahdollistaa Meshtastic-radioille: . | Sijaintidatan jakamisen TAK-yhteensopivassa CoT (Cursor on Target) -muodossa | Näkyä tiimin jäseninä TAK-karttanäkymissä | Vastaanottaa TAK PLI (Position Location Information) -viestejä | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/tak.html#yleiskatsaus",
    
    "relUrl": "/fi-rFI/user/tak.html#yleiskatsaus"
  },"5151": {
    "doc": "TAK-integraatio",
    "title": "Asetukset",
    "content": "Edellytykset . | Asennettuna ATAK (Android Team Awareness Kit), iTAK tai WinTAK | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Varoitus: Vanha Meshtastic ATAK Plugin ei enää kuulu tähän kokonaisuuteen eikä toimi. Yhteentoimivuus toteutetaan sovelluksen sisäisen paikallisen AIDL-rajapinnan kautta, joka poistettiin sovelluksesta 2.8.0. Mesh-palvelu toimii nyt vain sovelluksen sisäisenä. Älä asenna sitä. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. Asetukset . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Radiosi lähettää tämän tunnuksen, joka näkyy TAK-kartoilla. | Asetus | Kuvaus | . | Tiimin väri | TAK-kartan tiimiväri (esim. sininen, punainen, syaani, vihreä) | . | Jäsenen rooli | Toiminnallinen roolisi kyseisessä ryhmässä (Team Member, Team Lead, HQ, Medic, RTO jne.) | . TAK-kutsutunnuksesi ei ole erillinen asetus — se muodostetaan automaattisesti Meshtastic-radiosi nimestä. 💡 Vinkki: Tiimi- ja roolivärit ovat TAK-järjestelmän standardeja ryhmävärikoodauksia. Sovi TAK-ryhmäsi kanssa yhtenäisistä ryhmämäärityksistä. Paikallinen TAK-palvelin . Sovellus voi myös käyttää paikallista TAK-palvelinta, jolloin samalla puhelimella oleva ATAK tai iTAK voi muodostaa siihen yhteyden suoraan ilman etä-TAK-palvelinta. Palvelin kuuntelee vain paikallisia yhteyksiä (127.0.0.1:8089) ja käyttää TLS:ää molemminpuolisella varmenteiden todentamisella. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Ota paikallinen TAK-palvelin käyttöön — käynnistää vain loopback-yhteyttä käyttävän mTLS-palvelimen portissa 8089 samalla puhelimella olevien ATAK- ja iTAK-yhteyksien käyttöön. | TAK-mesh-kanava – valitsee, mitä Meshtastic-kanavaa käytetään lähtevään TAK-liikenteeseen (oletuksena ensisijainen kanava, indeksi 0) Saapuva TAK-liikenne hyväksytään miltä tahansa kanavalta. Vastaa iOS:n ja vanhan ATAK-liitännäisen vastaavaa asetusta. | Mesh to CoT Converter — oletusarvoisesti pois käytöstä, ja näkyy palvelinkytkimen alla. Kun palvelin on käynnissä, se luo CoT-yhteystiedon jokaisesta radiosolmujen tietokannan radiosta, jolloin tavalliset Meshtastic-radiot näkyvät ATAK-kartalla yhteystietoina. Tämä korvaa vanhan lisäosan näkyvyyden — ilman tätä näkyvät vain TAK-roolin radiot. | Vie TAK-tietopaketti — luo .zip-tietopaketin, jonka ATAK/iTAK voi tuoda muodostaakseen yhteyden tähän palvelimeen. | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/tak.html#asetukset",
    
    "relUrl": "/fi-rFI/user/tak.html#asetukset"
  },"5152": {
    "doc": "TAK-integraatio",
    "title": "TAK-roolit",
    "content": "TAK-rooleilla määritetyt radiot käyttäytyvät eri tavalla kuin tavalliset client-laitteet: . | Rooli | Kuvaus | . | TAK | Täysi TAK-yhteentoimivuus — lähettää ja vastaanottaa CoT-dataa, chat-viestejä ja PLI-päivityksiä. Toimii tavallisen clientin lisäksi TAK-siltana. | . | TAK Tracker | Vain sijaintitietoihin perustuva TAK-lähtö — lähettää automaattisesti PLI-dataa säännöllisin väliajoin ilman käyttäjän toimintaa. Optimoitu valvomattomiin sijaintilähettimiin (ajoneuvot, laitteet ja reittipisteet). Ei välitä chat-viestejä. | . 💡 Vinkki: Käytä TAK Tracker -tilaa laitteille, joiden tarvitsee vain lähettää sijainti (esim. ajoneuvoon asennettu radio). Käytä TAK-tilaa laitteille, joissa käyttäjät osallistuvat aktiivisesti TAK-toimintaan. CoT (Cursor on Target) -muoto . TAK-viestit käyttävät Cursor on Target XML -muotoa — sotilaskäytössä olevaa standardia tilannetiedon jakamiseen. Meshtastic muuntaa sisäiset protobuf-viestinsä CoT-muotoon silloin, kun se välittää dataa TAK-järjestelmiin, joten manuaalista muunnosta ei tarvita. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/tak.html#tak-roolit",
    
    "relUrl": "/fi-rFI/user/tak.html#tak-roolit"
  },"5153": {
    "doc": "TAK-integraatio",
    "title": "Wire Format (V1 / V2)",
    "content": "Meshtastic tukee kahta TAK-siirtomuotoa, jotka valitaan automaattisesti yhdistetyn radion laiteohjelmiston perusteella — manuaalisia asetuksia ei tarvita: . | Muoto | Yhteensopivuus | Ominaisuudet | . | V1 (vanha versio) | Laiteohjelmisto 2.7.x ja vanhemmat | Raaka protobuf-koodaus portissa 72. Tukee vain sijainnin jakamista (PLI) ja keskusteluja (GeoChat) — muodot, merkinnät, reitit ja muut tyypitetyt CoT-tapahtumat jätetään välittämättä | . | V2 (nykyinen) | Laiteohjelmisto 2.8.0+ | Pakkausmuoto käyttää zstd-pakkausta portissa 78. Tukee V1:n ominaisuuksien lisäksi myös muotoja, merkintöjä, reittejä, ilma-aluksia, lääkintäevakuointeja (CASEVAC), hätätilanteita ja tehtävätyyppisiä CoT-tapahtumia | . Radio välittää edelleen vanhojen radioiden V1-paketteja myös käyttäessään itse V2:ta, joten eri laiteohjelmistoversioita käyttävät mesh-verkot toimivat keskenään. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/tak.html#wire-format-v1--v2",
    
    "relUrl": "/fi-rFI/user/tak.html#wire-format-v1--v2"
  },"5154": {
    "doc": "TAK-integraatio",
    "title": "Käyttö ATAK:n kanssa",
    "content": "Kun asetukset on määritetty: . | Meshtastic-radiot näkyvät ATAK-kartalla merkkeinä kutsutunnuksineen | Viestit voivat välittyä mesh-verkon ja TAK-verkon välillä | Sijaintipäivitykset kulkevat kaksisuuntaisesti Meshtasticin ja TAK-järjestelmän välillä | TAK Tracker -radiot lähettävät PLI-sijaintia automaattisesti — niiden sijainti näkyy ATAK-kartoilla ilman erillistä ATAK-asetusta | . ℹ️ Huomautus: TAK-integraatio edellyttää tiettyjä radiorooleja. Tavalliset Client-roolin radiot eivät osallistu automaattisesti TAK-toimintoihin — mutta kun Mesh to CoT Converter on käytössä, ne näkyvät silti ATAK-kartalla yhteystietoina. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/tak.html#k%C3%A4ytt%C3%B6-atakn-kanssa",
    
    "relUrl": "/fi-rFI/user/tak.html#käyttö-atakn-kanssa"
  },"5155": {
    "doc": "TAK-integraatio",
    "title": "Vianetsintä",
    "content": "| Ongelma | Syy | Ratkaisu | . | Radio ei näy ATAK-kartalla | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Sijaintipäivitykset ovat vanhentuneita | GPS-signaali katkennut tai lähetysväli liian pitkä | Tarkista GPS-tila; lyhennä sijaintilähetyksen väliä kohdassa Sijainnin asetukset | . | ATAK näyttää tilan “Ei yhteyttä” | Paikallinen TAK-palvelin ei ole käytössä tai ATAK on yhdistetty muualle | Varmista, että Ota paikallinen TAK-palvelin käyttöön on käytössä ja että ATAK muodostaa yhteyden osoitteeseen 127.0.0.1:8089 — tuo viety datapaketti uudelleen, jos et ole varma | . | Muotoja, merkintöjä tai reittejä ei välitetä | Lähettävä radio käyttää vanhaa V1-protokollaa (laiteohjelmisto 2.7.x tai vanhempi) | Päivitä lähettävän radion laiteohjelmisto versioon 2.8.0 tai uudempaan, jotta V2-siirtomuoto on käytettävissä | . | CoT-data ei kulje | Kanava ei täsmää | Kaikkien TAK-laitteiden täytyy olla samalla kanavalla ja yhteensopivalla salauksella | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/tak.html#vianetsint%C3%A4",
    
    "relUrl": "/fi-rFI/user/tak.html#vianetsintä"
  },"5156": {
    "doc": "TAK-integraatio",
    "title": "Tietoturvahuomiot",
    "content": "🔒 Tietosuoja: TAK-tiedot sisältävät sijaintisi ja kutsutunnuksesi. TAK-moduuli käyttää samaa kanavasalausta kuin muutkin Meshtastic-viestit — arkaluonteisissa ympäristöissä käytä kanavaa, jonka avain ei ole oletusarvoinen. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/tak.html#tietoturvahuomiot",
    
    "relUrl": "/fi-rFI/user/tak.html#tietoturvahuomiot"
  },"5157": {
    "doc": "TAK-integraatio",
    "title": "Aiheeseen liittyvät aiheet",
    "content": ". | Asetukset — Moduulit ja ylläpito — TAK-moduulin asetukset | Radiot — TAK- ja TAK Tracker -roolit radiolistassa | Kartta ja reittipisteet — radioiden sijainnit kartalla | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/tak.html#aiheeseen-liittyv%C3%A4t-aiheet",
    
    "relUrl": "/fi-rFI/user/tak.html#aiheeseen-liittyvät-aiheet"
  },"5158": {
    "doc": "TAK Integration",
    "title": "TAK Integration",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/tak.html",
    
    "relUrl": "/is-rIS/user/tak.html"
  },"5159": {
    "doc": "TAK Integration",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/tak.html#overview",
    
    "relUrl": "/is-rIS/user/tak.html#overview"
  },"5160": {
    "doc": "TAK Integration",
    "title": "Setup",
    "content": "Prerequisites . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. Configuration . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | Setting | Lýsing | . | Team Color | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Member Role | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 Tip: Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments. Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. The server binds to localhost only (127.0.0.1:8089) and uses TLS with mutual certificate authentication (mTLS), so it is not reachable from other devices on the network. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK Mesh Channel — selects which Meshtastic channel outgoing TAK traffic is sent on (default: the primary channel, index 0). Incoming TAK traffic is accepted from any channel. Matches the equivalent setting on iOS and in the legacy ATAK plugin. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | Export TAK Data Package — generates a .zip data package that ATAK/iTAK can import to connect to this server. | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/tak.html#setup",
    
    "relUrl": "/is-rIS/user/tak.html#setup"
  },"5161": {
    "doc": "TAK Integration",
    "title": "TAK Roles",
    "content": "Nodes configured with TAK-related roles behave differently from standard clients: . | Role | Lýsing | . | 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. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/tak.html#tak-roles",
    
    "relUrl": "/is-rIS/user/tak.html#tak-roles"
  },"5162": {
    "doc": "TAK Integration",
    "title": "Wire Format (V1 / V2)",
    "content": "Meshtastic supports two TAK wire formats, chosen automatically based on the connected radio’s firmware — no manual configuration needed: . | Format | Compatibility | Features | . | V1 (Legacy) | Firmware 2.7.x and older | Bare protobuf encoding on port 72. Supports position sharing (PLI) and chat (GeoChat) only — shapes, markers, routes, and other typed CoT events are dropped | . | V2 (Current) | Firmware 2.8.0+ | Compact, zstd-compressed encoding on port 78. Adds shapes, markers, routes, aircraft, casevac, emergency, and task CoT types on top of everything V1 supports | . A node still relays legacy V1 packets from older nodes even while running V2 itself, so mixed-firmware meshes keep working. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/tak.html#wire-format-v1--v2",
    
    "relUrl": "/is-rIS/user/tak.html#wire-format-v1--v2"
  },"5163": {
    "doc": "TAK Integration",
    "title": "Usage with ATAK",
    "content": "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. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/tak.html#usage-with-atak",
    
    "relUrl": "/is-rIS/user/tak.html#usage-with-atak"
  },"5164": {
    "doc": "TAK Integration",
    "title": "Troubleshooting",
    "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | Shapes, markers, or routes not bridging | Sending node is on legacy V1 (firmware 2.7.x or older) | Update the sending node’s firmware to 2.8.0+ for V2 wire format | . | CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/tak.html#troubleshooting",
    
    "relUrl": "/is-rIS/user/tak.html#troubleshooting"
  },"5165": {
    "doc": "TAK Integration",
    "title": "Security Considerations",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/tak.html#security-considerations",
    
    "relUrl": "/is-rIS/user/tak.html#security-considerations"
  },"5166": {
    "doc": "TAK Integration",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — TAK module configuration | Nodes — TAK and TAK Tracker roles in the node list | Map & Waypoints — node positions on the map | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/tak.html#related-topics",
    
    "relUrl": "/is-rIS/user/tak.html#related-topics"
  },"5167": {
    "doc": "TAK Integration",
    "title": "TAK Integration",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/tak.html",
    
    "relUrl": "/lt-rLT/user/tak.html"
  },"5168": {
    "doc": "TAK Integration",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/tak.html#overview",
    
    "relUrl": "/lt-rLT/user/tak.html#overview"
  },"5169": {
    "doc": "TAK Integration",
    "title": "Setup",
    "content": "Prerequisites . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. Configuration . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | Setting | Aprašymas | . | Team Color | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Member Role | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 Tip: Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments. Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. The server binds to localhost only (127.0.0.1:8089) and uses TLS with mutual certificate authentication (mTLS), so it is not reachable from other devices on the network. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK Mesh Channel — selects which Meshtastic channel outgoing TAK traffic is sent on (default: the primary channel, index 0). Incoming TAK traffic is accepted from any channel. Matches the equivalent setting on iOS and in the legacy ATAK plugin. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | Export TAK Data Package — generates a .zip data package that ATAK/iTAK can import to connect to this server. | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/tak.html#setup",
    
    "relUrl": "/lt-rLT/user/tak.html#setup"
  },"5170": {
    "doc": "TAK Integration",
    "title": "TAK Roles",
    "content": "Nodes configured with TAK-related roles behave differently from standard clients: . | Role | Aprašymas | . | 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. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/tak.html#tak-roles",
    
    "relUrl": "/lt-rLT/user/tak.html#tak-roles"
  },"5171": {
    "doc": "TAK Integration",
    "title": "Wire Format (V1 / V2)",
    "content": "Meshtastic supports two TAK wire formats, chosen automatically based on the connected radio’s firmware — no manual configuration needed: . | Format | Compatibility | Features | . | V1 (Legacy) | Firmware 2.7.x and older | Bare protobuf encoding on port 72. Supports position sharing (PLI) and chat (GeoChat) only — shapes, markers, routes, and other typed CoT events are dropped | . | V2 (Current) | Firmware 2.8.0+ | Compact, zstd-compressed encoding on port 78. Adds shapes, markers, routes, aircraft, casevac, emergency, and task CoT types on top of everything V1 supports | . A node still relays legacy V1 packets from older nodes even while running V2 itself, so mixed-firmware meshes keep working. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/tak.html#wire-format-v1--v2",
    
    "relUrl": "/lt-rLT/user/tak.html#wire-format-v1--v2"
  },"5172": {
    "doc": "TAK Integration",
    "title": "Usage with ATAK",
    "content": "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. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/tak.html#usage-with-atak",
    
    "relUrl": "/lt-rLT/user/tak.html#usage-with-atak"
  },"5173": {
    "doc": "TAK Integration",
    "title": "Troubleshooting",
    "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | Shapes, markers, or routes not bridging | Sending node is on legacy V1 (firmware 2.7.x or older) | Update the sending node’s firmware to 2.8.0+ for V2 wire format | . | CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/tak.html#troubleshooting",
    
    "relUrl": "/lt-rLT/user/tak.html#troubleshooting"
  },"5174": {
    "doc": "TAK Integration",
    "title": "Security Considerations",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/tak.html#security-considerations",
    
    "relUrl": "/lt-rLT/user/tak.html#security-considerations"
  },"5175": {
    "doc": "TAK Integration",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — TAK module configuration | Nodes — TAK and TAK Tracker roles in the node list | Map & Waypoints — node positions on the map | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/tak.html#related-topics",
    
    "relUrl": "/lt-rLT/user/tak.html#related-topics"
  },"5176": {
    "doc": "TAK Integration",
    "title": "TAK Integration",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/tak.html",
    
    "relUrl": "/gl-rES/user/tak.html"
  },"5177": {
    "doc": "TAK Integration",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/tak.html#overview",
    
    "relUrl": "/gl-rES/user/tak.html#overview"
  },"5178": {
    "doc": "TAK Integration",
    "title": "Setup",
    "content": "Prerequisites . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. Configuration . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | Setting | Descrición | . | Team Color | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Member Role | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 Tip: Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments. Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. The server binds to localhost only (127.0.0.1:8089) and uses TLS with mutual certificate authentication (mTLS), so it is not reachable from other devices on the network. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK Mesh Channel — selects which Meshtastic channel outgoing TAK traffic is sent on (default: the primary channel, index 0). Incoming TAK traffic is accepted from any channel. Matches the equivalent setting on iOS and in the legacy ATAK plugin. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | Export TAK Data Package — generates a .zip data package that ATAK/iTAK can import to connect to this server. | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/tak.html#setup",
    
    "relUrl": "/gl-rES/user/tak.html#setup"
  },"5179": {
    "doc": "TAK Integration",
    "title": "TAK Roles",
    "content": "Nodes configured with TAK-related roles behave differently from standard clients: . | Role | Descrición | . | 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. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/tak.html#tak-roles",
    
    "relUrl": "/gl-rES/user/tak.html#tak-roles"
  },"5180": {
    "doc": "TAK Integration",
    "title": "Wire Format (V1 / V2)",
    "content": "Meshtastic supports two TAK wire formats, chosen automatically based on the connected radio’s firmware — no manual configuration needed: . | Format | Compatibility | Features | . | V1 (Legacy) | Firmware 2.7.x and older | Bare protobuf encoding on port 72. Supports position sharing (PLI) and chat (GeoChat) only — shapes, markers, routes, and other typed CoT events are dropped | . | V2 (Current) | Firmware 2.8.0+ | Compact, zstd-compressed encoding on port 78. Adds shapes, markers, routes, aircraft, casevac, emergency, and task CoT types on top of everything V1 supports | . A node still relays legacy V1 packets from older nodes even while running V2 itself, so mixed-firmware meshes keep working. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/tak.html#wire-format-v1--v2",
    
    "relUrl": "/gl-rES/user/tak.html#wire-format-v1--v2"
  },"5181": {
    "doc": "TAK Integration",
    "title": "Usage with ATAK",
    "content": "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. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/tak.html#usage-with-atak",
    
    "relUrl": "/gl-rES/user/tak.html#usage-with-atak"
  },"5182": {
    "doc": "TAK Integration",
    "title": "Troubleshooting",
    "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | Shapes, markers, or routes not bridging | Sending node is on legacy V1 (firmware 2.7.x or older) | Update the sending node’s firmware to 2.8.0+ for V2 wire format | . | CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/tak.html#troubleshooting",
    
    "relUrl": "/gl-rES/user/tak.html#troubleshooting"
  },"5183": {
    "doc": "TAK Integration",
    "title": "Security Considerations",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/tak.html#security-considerations",
    
    "relUrl": "/gl-rES/user/tak.html#security-considerations"
  },"5184": {
    "doc": "TAK Integration",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — TAK module configuration | Nodes — TAK and TAK Tracker roles in the node list | Map & Waypoints — node positions on the map | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/tak.html#related-topics",
    
    "relUrl": "/gl-rES/user/tak.html#related-topics"
  },"5185": {
    "doc": "TAK 連携",
    "title": "TAK 連携",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/tak.html",
    
    "relUrl": "/ja-rJP/user/tak.html"
  },"5186": {
    "doc": "TAK 連携",
    "title": "概要",
    "content": "TAK モジュールを使うと、Meshtastic のノードは次のことができます： . | TAK 互換の CoT（Cursor on Target）形式で位置データを共有する | TAK のマップ表示上にチームメンバーとして表示される | TAK の PLI（位置情報）メッセージを受信する | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/tak.html#%E6%A6%82%E8%A6%81",
    
    "relUrl": "/ja-rJP/user/tak.html#概要"
  },"5187": {
    "doc": "TAK 連携",
    "title": "セットアップ",
    "content": "前提条件 . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. 設定 . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | 設定項目 | 説明 | . | チームカラー | TAK のマップ上でのチームの色（例：ブルー、レッド、シアン、グリーン） | . | メンバーロール | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 ヒント： チーム／役割の色は、TAK の標準的な所属色です。 Coordinate with your TAK team to use consistent team assignments. ローカル TAK サーバー . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. サーバーは localhost のみ（127.0.0.1:8089）にバインドし、相互証明書認証（mTLS）による TLS を使用するため、ネットワーク上の他のデバイスからは到達できません。 . Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK Mesh Channel — selects which Meshtastic channel outgoing TAK traffic is sent on (default: the primary channel, index 0). Incoming TAK traffic is accepted from any channel. Matches the equivalent setting on iOS and in the legacy ATAK plugin. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | TAK データパッケージをエクスポート：ATAK／iTAK がこのサーバーに接続するためにインポートできる .zip データパッケージを生成します。 | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/tak.html#%E3%82%BB%E3%83%83%E3%83%88%E3%82%A2%E3%83%83%E3%83%97",
    
    "relUrl": "/ja-rJP/user/tak.html#セットアップ"
  },"5188": {
    "doc": "TAK 連携",
    "title": "TAK の役割",
    "content": "TAK 関連の役割を設定したノードは、標準のクライアントとは動作が異なります： . | 役割 | 説明 | . | TAK | 完全な TAK 相互運用。CoT データ、チャットメッセージ、PLI 更新を送受信します。標準のクライアントとして機能し、さらに TAK ブリッジも兼ねます。 | . | TAK Tracker | 位置情報のみの TAK 出力。ユーザーの操作なしに、一定間隔で自動的に PLI をブロードキャストします。無人の位置ビーコン（車両、機材、ウェイポイント）に最適化されています。チャットメッセージは中継しません。 | . 💡 ヒント： 位置の報告だけが必要なデバイス（例：車両に取り付けた無線機）には TAK Tracker を使用します。ユーザーが TAK の運用に積極的に参加するデバイスには TAK を使用します。 . CoT（Cursor on Target）形式 . TAK のメッセージは Cursor on Target の XML 形式を使用します。これは状況認識データを共有するための軍事標準です。 Meshtastic は、TAK システムに橋渡しする際に内部の protobuf メッセージを CoT 形式に変換するため、手動での形式変換は必要ありません。 . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/tak.html#tak-%E3%81%AE%E5%BD%B9%E5%89%B2",
    
    "relUrl": "/ja-rJP/user/tak.html#tak-の役割"
  },"5189": {
    "doc": "TAK 連携",
    "title": "ワイヤ形式（V1／V2）",
    "content": "Meshtastic は 2 つの TAK ワイヤ形式に対応しており、接続中の無線機のファームウェアに基づいて自動的に選択されます。手動での設定は必要ありません： . | 形式 | 互換性 | 機能 | . | V1（レガシー） | ファームウェア 2.7.x 以前 | ポート 72 での素の protobuf エンコード。位置共有（PLI）とチャット（GeoChat）のみに対応。図形、マーカー、ルート、その他の型付き CoT イベントは破棄されます | . | V2（現行） | ファームウェア 2.8.0 以降 | ポート 78 でのコンパクトな zstd 圧縮エンコード。 V1 が対応するすべてに加えて、図形、マーカー、ルート、航空機、casevac、緊急、タスクの CoT タイプを追加します | . ノードは V2 を実行していても、古いノードからのレガシーな V1 パケットを引き続き中継するため、ファームウェアが混在したメッシュでも動作し続けます。 . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/tak.html#%E3%83%AF%E3%82%A4%E3%83%A4%E5%BD%A2%E5%BC%8Fv1v2",
    
    "relUrl": "/ja-rJP/user/tak.html#ワイヤ形式v1v2"
  },"5190": {
    "doc": "TAK 連携",
    "title": "ATAK での使用",
    "content": "設定が完了すると： . | Meshtastic のノードが、コールサインのラベル付きで ATAK のマップにマーカーとして表示されます | チャットメッセージを、メッシュと TAK ネットワークの間で橋渡しできます | 位置の更新が、Meshtastic と TAK の間で双方向に流れます | TAK Tracker のノードは自動的に PLI をブロードキャストします。ATAK 側の設定なしで、その位置が ATAK のマップに表示されます | . ℹ️ Note: TAK integration requires specific node roles. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/tak.html#atak-%E3%81%A7%E3%81%AE%E4%BD%BF%E7%94%A8",
    
    "relUrl": "/ja-rJP/user/tak.html#atak-での使用"
  },"5191": {
    "doc": "TAK 連携",
    "title": "トラブルシューティング",
    "content": "| 問題 | 原因 | 解決策 | . | ノードが ATAK のマップに表示されない | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | 位置の更新が古い | GPS 測位が失われた、または間隔が長すぎる | GPS の状態を確認し、位置情報設定で位置のブロードキャスト間隔を短くする | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | 図形、マーカー、ルートが橋渡しされない | 送信側のノードがレガシーな V1（ファームウェア 2.7.x 以前）である | V2 ワイヤ形式にするため、送信側のノードのファームウェアを 2.8.0 以降に更新する | . | CoT データが流れない | チャンネルの不一致 | すべての TAK ノードが、暗号化が一致した同じチャンネル上にある必要がある | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/tak.html#%E3%83%88%E3%83%A9%E3%83%96%E3%83%AB%E3%82%B7%E3%83%A5%E3%83%BC%E3%83%86%E3%82%A3%E3%83%B3%E3%82%B0",
    
    "relUrl": "/ja-rJP/user/tak.html#トラブルシューティング"
  },"5192": {
    "doc": "TAK 連携",
    "title": "セキュリティに関する注意",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/tak.html#%E3%82%BB%E3%82%AD%E3%83%A5%E3%83%AA%E3%83%86%E3%82%A3%E3%81%AB%E9%96%A2%E3%81%99%E3%82%8B%E6%B3%A8%E6%84%8F",
    
    "relUrl": "/ja-rJP/user/tak.html#セキュリティに関する注意"
  },"5193": {
    "doc": "TAK 連携",
    "title": "関連トピック",
    "content": ". | 設定：モジュールと管理：TAK モジュールの設定 | ノード：ノードリストの TAK と TAK Tracker の役割 | マップとウェイポイント：マップ上のノードの位置 | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/tak.html#%E9%96%A2%E9%80%A3%E3%83%88%E3%83%94%E3%83%83%E3%82%AF",
    
    "relUrl": "/ja-rJP/user/tak.html#関連トピック"
  },"5194": {
    "doc": "TAK Integration",
    "title": "TAK Integration",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/tak.html",
    
    "relUrl": "/de-rDE/user/tak.html"
  },"5195": {
    "doc": "TAK Integration",
    "title": "Übersicht",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/tak.html#%C3%BCbersicht",
    
    "relUrl": "/de-rDE/user/tak.html#übersicht"
  },"5196": {
    "doc": "TAK Integration",
    "title": "Einstellungen",
    "content": "Voraussetzungen . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. Einstellungen . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | Einstellung | Beschreibung | . | Teamfarbe | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Mitgliedsrolle | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 Tip: Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments. Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. The server binds to localhost only (127.0.0.1:8089) and uses TLS with mutual certificate authentication (mTLS), so it is not reachable from other devices on the network. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK Mesh Channel — selects which Meshtastic channel outgoing TAK traffic is sent on (default: the primary channel, index 0). Incoming TAK traffic is accepted from any channel. Matches the equivalent setting on iOS and in the legacy ATAK plugin. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | Export TAK Data Package — generates a .zip data package that ATAK/iTAK can import to connect to this server. | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/tak.html#einstellungen",
    
    "relUrl": "/de-rDE/user/tak.html#einstellungen"
  },"5197": {
    "doc": "TAK Integration",
    "title": "TAK Roles",
    "content": "Nodes configured with TAK-related roles behave differently from standard clients: . | Rolle | Beschreibung | . | 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. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/tak.html#tak-roles",
    
    "relUrl": "/de-rDE/user/tak.html#tak-roles"
  },"5198": {
    "doc": "TAK Integration",
    "title": "Wire Format (V1 / V2)",
    "content": "Meshtastic supports two TAK wire formats, chosen automatically based on the connected radio’s firmware — no manual configuration needed: . | Format | Kompatibilität | Merkmale | . | V1 (Legacy) | Firmware 2.7.x and older | Bare protobuf encoding on port 72. Supports position sharing (PLI) and chat (GeoChat) only — shapes, markers, routes, and other typed CoT events are dropped | . | V2 (Current) | Firmware 2.8.0+ | Compact, zstd-compressed encoding on port 78. Adds shapes, markers, routes, aircraft, casevac, emergency, and task CoT types on top of everything V1 supports | . A node still relays legacy V1 packets from older nodes even while running V2 itself, so mixed-firmware meshes keep working. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/tak.html#wire-format-v1--v2",
    
    "relUrl": "/de-rDE/user/tak.html#wire-format-v1--v2"
  },"5199": {
    "doc": "TAK Integration",
    "title": "Usage with ATAK",
    "content": "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. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/tak.html#usage-with-atak",
    
    "relUrl": "/de-rDE/user/tak.html#usage-with-atak"
  },"5200": {
    "doc": "TAK Integration",
    "title": "Fehlerbehebung",
    "content": "| Problem | Ursache | Solution | . | Node doesn’t appear on ATAK map | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | Shapes, markers, or routes not bridging | Sending node is on legacy V1 (firmware 2.7.x or older) | Update the sending node’s firmware to 2.8.0+ for V2 wire format | . | CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/tak.html#fehlerbehebung",
    
    "relUrl": "/de-rDE/user/tak.html#fehlerbehebung"
  },"5201": {
    "doc": "TAK Integration",
    "title": "Security Considerations",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/tak.html#security-considerations",
    
    "relUrl": "/de-rDE/user/tak.html#security-considerations"
  },"5202": {
    "doc": "TAK Integration",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — TAK module configuration | Nodes — TAK and TAK Tracker roles in the node list | Map & Waypoints — node positions on the map | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/tak.html#related-topics",
    
    "relUrl": "/de-rDE/user/tak.html#related-topics"
  },"5203": {
    "doc": "TAK Integration",
    "title": "TAK Integration",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/tak.html",
    
    "relUrl": "/ar-rSA/user/tak.html"
  },"5204": {
    "doc": "TAK Integration",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/tak.html#overview",
    
    "relUrl": "/ar-rSA/user/tak.html#overview"
  },"5205": {
    "doc": "TAK Integration",
    "title": "Setup",
    "content": "Prerequisites . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. Configuration . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | Setting | الوصف | . | Team Color | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Member Role | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 Tip: Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments. Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. The server binds to localhost only (127.0.0.1:8089) and uses TLS with mutual certificate authentication (mTLS), so it is not reachable from other devices on the network. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK Mesh Channel — selects which Meshtastic channel outgoing TAK traffic is sent on (default: the primary channel, index 0). Incoming TAK traffic is accepted from any channel. Matches the equivalent setting on iOS and in the legacy ATAK plugin. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | Export TAK Data Package — generates a .zip data package that ATAK/iTAK can import to connect to this server. | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/tak.html#setup",
    
    "relUrl": "/ar-rSA/user/tak.html#setup"
  },"5206": {
    "doc": "TAK Integration",
    "title": "TAK Roles",
    "content": "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. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/tak.html#tak-roles",
    
    "relUrl": "/ar-rSA/user/tak.html#tak-roles"
  },"5207": {
    "doc": "TAK Integration",
    "title": "Wire Format (V1 / V2)",
    "content": "Meshtastic supports two TAK wire formats, chosen automatically based on the connected radio’s firmware — no manual configuration needed: . | Format | Compatibility | Features | . | V1 (Legacy) | Firmware 2.7.x and older | Bare protobuf encoding on port 72. Supports position sharing (PLI) and chat (GeoChat) only — shapes, markers, routes, and other typed CoT events are dropped | . | V2 (Current) | Firmware 2.8.0+ | Compact, zstd-compressed encoding on port 78. Adds shapes, markers, routes, aircraft, casevac, emergency, and task CoT types on top of everything V1 supports | . A node still relays legacy V1 packets from older nodes even while running V2 itself, so mixed-firmware meshes keep working. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/tak.html#wire-format-v1--v2",
    
    "relUrl": "/ar-rSA/user/tak.html#wire-format-v1--v2"
  },"5208": {
    "doc": "TAK Integration",
    "title": "Usage with ATAK",
    "content": "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. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/tak.html#usage-with-atak",
    
    "relUrl": "/ar-rSA/user/tak.html#usage-with-atak"
  },"5209": {
    "doc": "TAK Integration",
    "title": "Troubleshooting",
    "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | Shapes, markers, or routes not bridging | Sending node is on legacy V1 (firmware 2.7.x or older) | Update the sending node’s firmware to 2.8.0+ for V2 wire format | . | CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/tak.html#troubleshooting",
    
    "relUrl": "/ar-rSA/user/tak.html#troubleshooting"
  },"5210": {
    "doc": "TAK Integration",
    "title": "Security Considerations",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/tak.html#security-considerations",
    
    "relUrl": "/ar-rSA/user/tak.html#security-considerations"
  },"5211": {
    "doc": "TAK Integration",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — TAK module configuration | Nodes — TAK and TAK Tracker roles in the node list | Map & Waypoints — node positions on the map | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/tak.html#related-topics",
    
    "relUrl": "/ar-rSA/user/tak.html#related-topics"
  },"5212": {
    "doc": "TAK Integration",
    "title": "TAK Integration",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/tak.html",
    
    "relUrl": "/hr-rHR/user/tak.html"
  },"5213": {
    "doc": "TAK Integration",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/tak.html#overview",
    
    "relUrl": "/hr-rHR/user/tak.html#overview"
  },"5214": {
    "doc": "TAK Integration",
    "title": "Setup",
    "content": "Prerequisites . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. Configuration . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | Setting | Opis | . | Team Color | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Member Role | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 Tip: Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments. Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. The server binds to localhost only (127.0.0.1:8089) and uses TLS with mutual certificate authentication (mTLS), so it is not reachable from other devices on the network. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK Mesh Channel — selects which Meshtastic channel outgoing TAK traffic is sent on (default: the primary channel, index 0). Incoming TAK traffic is accepted from any channel. Matches the equivalent setting on iOS and in the legacy ATAK plugin. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | Export TAK Data Package — generates a .zip data package that ATAK/iTAK can import to connect to this server. | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/tak.html#setup",
    
    "relUrl": "/hr-rHR/user/tak.html#setup"
  },"5215": {
    "doc": "TAK Integration",
    "title": "TAK Roles",
    "content": "Nodes configured with TAK-related roles behave differently from standard clients: . | Role | Opis | . | 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. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/tak.html#tak-roles",
    
    "relUrl": "/hr-rHR/user/tak.html#tak-roles"
  },"5216": {
    "doc": "TAK Integration",
    "title": "Wire Format (V1 / V2)",
    "content": "Meshtastic supports two TAK wire formats, chosen automatically based on the connected radio’s firmware — no manual configuration needed: . | Format | Compatibility | Features | . | V1 (Legacy) | Firmware 2.7.x and older | Bare protobuf encoding on port 72. Supports position sharing (PLI) and chat (GeoChat) only — shapes, markers, routes, and other typed CoT events are dropped | . | V2 (Current) | Firmware 2.8.0+ | Compact, zstd-compressed encoding on port 78. Adds shapes, markers, routes, aircraft, casevac, emergency, and task CoT types on top of everything V1 supports | . A node still relays legacy V1 packets from older nodes even while running V2 itself, so mixed-firmware meshes keep working. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/tak.html#wire-format-v1--v2",
    
    "relUrl": "/hr-rHR/user/tak.html#wire-format-v1--v2"
  },"5217": {
    "doc": "TAK Integration",
    "title": "Usage with ATAK",
    "content": "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. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/tak.html#usage-with-atak",
    
    "relUrl": "/hr-rHR/user/tak.html#usage-with-atak"
  },"5218": {
    "doc": "TAK Integration",
    "title": "Troubleshooting",
    "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | Shapes, markers, or routes not bridging | Sending node is on legacy V1 (firmware 2.7.x or older) | Update the sending node’s firmware to 2.8.0+ for V2 wire format | . | CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/tak.html#troubleshooting",
    
    "relUrl": "/hr-rHR/user/tak.html#troubleshooting"
  },"5219": {
    "doc": "TAK Integration",
    "title": "Security Considerations",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/tak.html#security-considerations",
    
    "relUrl": "/hr-rHR/user/tak.html#security-considerations"
  },"5220": {
    "doc": "TAK Integration",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — TAK module configuration | Nodes — TAK and TAK Tracker roles in the node list | Map & Waypoints — node positions on the map | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/tak.html#related-topics",
    
    "relUrl": "/hr-rHR/user/tak.html#related-topics"
  },"5221": {
    "doc": "TAK Integration",
    "title": "TAK Integration",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/tak.html",
    
    "relUrl": "/pt-rPT/user/tak.html"
  },"5222": {
    "doc": "TAK Integration",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/tak.html#overview",
    
    "relUrl": "/pt-rPT/user/tak.html#overview"
  },"5223": {
    "doc": "TAK Integration",
    "title": "Setup",
    "content": "Prerequisites . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. Configuração . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | Setting | Descrição | . | Team Color | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Member Role | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 Tip: Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments. Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. The server binds to localhost only (127.0.0.1:8089) and uses TLS with mutual certificate authentication (mTLS), so it is not reachable from other devices on the network. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK Mesh Channel — selects which Meshtastic channel outgoing TAK traffic is sent on (default: the primary channel, index 0). Incoming TAK traffic is accepted from any channel. Matches the equivalent setting on iOS and in the legacy ATAK plugin. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | Export TAK Data Package — generates a .zip data package that ATAK/iTAK can import to connect to this server. | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/tak.html#setup",
    
    "relUrl": "/pt-rPT/user/tak.html#setup"
  },"5224": {
    "doc": "TAK Integration",
    "title": "TAK Roles",
    "content": "Nodes configured with TAK-related roles behave differently from standard clients: . | Papel | Descrição | . | 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. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/tak.html#tak-roles",
    
    "relUrl": "/pt-rPT/user/tak.html#tak-roles"
  },"5225": {
    "doc": "TAK Integration",
    "title": "Wire Format (V1 / V2)",
    "content": "Meshtastic supports two TAK wire formats, chosen automatically based on the connected radio’s firmware — no manual configuration needed: . | Format | Compatibility | Features | . | V1 (Legacy) | Firmware 2.7.x and older | Bare protobuf encoding on port 72. Supports position sharing (PLI) and chat (GeoChat) only — shapes, markers, routes, and other typed CoT events are dropped | . | V2 (Current) | Firmware 2.8.0+ | Compact, zstd-compressed encoding on port 78. Adds shapes, markers, routes, aircraft, casevac, emergency, and task CoT types on top of everything V1 supports | . A node still relays legacy V1 packets from older nodes even while running V2 itself, so mixed-firmware meshes keep working. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/tak.html#wire-format-v1--v2",
    
    "relUrl": "/pt-rPT/user/tak.html#wire-format-v1--v2"
  },"5226": {
    "doc": "TAK Integration",
    "title": "Usage with ATAK",
    "content": "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. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/tak.html#usage-with-atak",
    
    "relUrl": "/pt-rPT/user/tak.html#usage-with-atak"
  },"5227": {
    "doc": "TAK Integration",
    "title": "Troubleshooting",
    "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | Shapes, markers, or routes not bridging | Sending node is on legacy V1 (firmware 2.7.x or older) | Update the sending node’s firmware to 2.8.0+ for V2 wire format | . | CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/tak.html#troubleshooting",
    
    "relUrl": "/pt-rPT/user/tak.html#troubleshooting"
  },"5228": {
    "doc": "TAK Integration",
    "title": "Security Considerations",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/tak.html#security-considerations",
    
    "relUrl": "/pt-rPT/user/tak.html#security-considerations"
  },"5229": {
    "doc": "TAK Integration",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — TAK module configuration | Nodes — TAK and TAK Tracker roles in the node list | Map & Waypoints — node positions on the map | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/tak.html#related-topics",
    
    "relUrl": "/pt-rPT/user/tak.html#related-topics"
  },"5230": {
    "doc": "TAK Integration",
    "title": "TAK Integration",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/tak.html",
    
    "relUrl": "/pl-rPL/user/tak.html"
  },"5231": {
    "doc": "TAK Integration",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/tak.html#overview",
    
    "relUrl": "/pl-rPL/user/tak.html#overview"
  },"5232": {
    "doc": "TAK Integration",
    "title": "Setup",
    "content": "Prerequisites . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. Konfiguracja . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | Setting | Opis | . | Team Color | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Member Role | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 Tip: Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments. Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. The server binds to localhost only (127.0.0.1:8089) and uses TLS with mutual certificate authentication (mTLS), so it is not reachable from other devices on the network. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK Mesh Channel — selects which Meshtastic channel outgoing TAK traffic is sent on (default: the primary channel, index 0). Incoming TAK traffic is accepted from any channel. Matches the equivalent setting on iOS and in the legacy ATAK plugin. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | Export TAK Data Package — generates a .zip data package that ATAK/iTAK can import to connect to this server. | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/tak.html#setup",
    
    "relUrl": "/pl-rPL/user/tak.html#setup"
  },"5233": {
    "doc": "TAK Integration",
    "title": "TAK Roles",
    "content": "Nodes configured with TAK-related roles behave differently from standard clients: . | Rola | Opis | . | 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. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/tak.html#tak-roles",
    
    "relUrl": "/pl-rPL/user/tak.html#tak-roles"
  },"5234": {
    "doc": "TAK Integration",
    "title": "Wire Format (V1 / V2)",
    "content": "Meshtastic supports two TAK wire formats, chosen automatically based on the connected radio’s firmware — no manual configuration needed: . | Format | Compatibility | Features | . | V1 (Legacy) | Firmware 2.7.x and older | Bare protobuf encoding on port 72. Supports position sharing (PLI) and chat (GeoChat) only — shapes, markers, routes, and other typed CoT events are dropped | . | V2 (Current) | Firmware 2.8.0+ | Compact, zstd-compressed encoding on port 78. Adds shapes, markers, routes, aircraft, casevac, emergency, and task CoT types on top of everything V1 supports | . A node still relays legacy V1 packets from older nodes even while running V2 itself, so mixed-firmware meshes keep working. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/tak.html#wire-format-v1--v2",
    
    "relUrl": "/pl-rPL/user/tak.html#wire-format-v1--v2"
  },"5235": {
    "doc": "TAK Integration",
    "title": "Usage with ATAK",
    "content": "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. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/tak.html#usage-with-atak",
    
    "relUrl": "/pl-rPL/user/tak.html#usage-with-atak"
  },"5236": {
    "doc": "TAK Integration",
    "title": "Troubleshooting",
    "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | Shapes, markers, or routes not bridging | Sending node is on legacy V1 (firmware 2.7.x or older) | Update the sending node’s firmware to 2.8.0+ for V2 wire format | . | CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/tak.html#troubleshooting",
    
    "relUrl": "/pl-rPL/user/tak.html#troubleshooting"
  },"5237": {
    "doc": "TAK Integration",
    "title": "Security Considerations",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/tak.html#security-considerations",
    
    "relUrl": "/pl-rPL/user/tak.html#security-considerations"
  },"5238": {
    "doc": "TAK Integration",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — TAK module configuration | Nodes — TAK and TAK Tracker roles in the node list | Map & Waypoints — node positions on the map | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/tak.html#related-topics",
    
    "relUrl": "/pl-rPL/user/tak.html#related-topics"
  },"5239": {
    "doc": "TAK Integration",
    "title": "TAK Integration",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/tak.html",
    
    "relUrl": "/zh-rCN/user/tak.html"
  },"5240": {
    "doc": "TAK Integration",
    "title": "总览",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/tak.html#%E6%80%BB%E8%A7%88",
    
    "relUrl": "/zh-rCN/user/tak.html#总览"
  },"5241": {
    "doc": "TAK Integration",
    "title": "Setup",
    "content": "前置条件 . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. Configuration . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | Setting | 说明 | . | 队伍颜色 | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | 成员角色 | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 Tip: Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments. Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. The server binds to localhost only (127.0.0.1:8089) and uses TLS with mutual certificate authentication (mTLS), so it is not reachable from other devices on the network. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK Mesh Channel — selects which Meshtastic channel outgoing TAK traffic is sent on (default: the primary channel, index 0). Incoming TAK traffic is accepted from any channel. Matches the equivalent setting on iOS and in the legacy ATAK plugin. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | Export TAK Data Package — generates a .zip data package that ATAK/iTAK can import to connect to this server. | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/tak.html#setup",
    
    "relUrl": "/zh-rCN/user/tak.html#setup"
  },"5242": {
    "doc": "TAK Integration",
    "title": "TAK Roles",
    "content": "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. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/tak.html#tak-roles",
    
    "relUrl": "/zh-rCN/user/tak.html#tak-roles"
  },"5243": {
    "doc": "TAK Integration",
    "title": "Wire Format (V1 / V2)",
    "content": "Meshtastic supports two TAK wire formats, chosen automatically based on the connected radio’s firmware — no manual configuration needed: . | Format | Compatibility | 特性 | . | V1 (Legacy) | Firmware 2.7.x and older | Bare protobuf encoding on port 72. Supports position sharing (PLI) and chat (GeoChat) only — shapes, markers, routes, and other typed CoT events are dropped | . | V2 (Current) | Firmware 2.8.0+ | Compact, zstd-compressed encoding on port 78. Adds shapes, markers, routes, aircraft, casevac, emergency, and task CoT types on top of everything V1 supports | . A node still relays legacy V1 packets from older nodes even while running V2 itself, so mixed-firmware meshes keep working. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/tak.html#wire-format-v1--v2",
    
    "relUrl": "/zh-rCN/user/tak.html#wire-format-v1--v2"
  },"5244": {
    "doc": "TAK Integration",
    "title": "Usage with ATAK",
    "content": "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. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/tak.html#usage-with-atak",
    
    "relUrl": "/zh-rCN/user/tak.html#usage-with-atak"
  },"5245": {
    "doc": "TAK Integration",
    "title": "问题排查",
    "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | Shapes, markers, or routes not bridging | Sending node is on legacy V1 (firmware 2.7.x or older) | Update the sending node’s firmware to 2.8.0+ for V2 wire format | . | CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/tak.html#%E9%97%AE%E9%A2%98%E6%8E%92%E6%9F%A5",
    
    "relUrl": "/zh-rCN/user/tak.html#问题排查"
  },"5246": {
    "doc": "TAK Integration",
    "title": "Security Considerations",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/tak.html#security-considerations",
    
    "relUrl": "/zh-rCN/user/tak.html#security-considerations"
  },"5247": {
    "doc": "TAK Integration",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — TAK module configuration | Nodes — TAK and TAK Tracker roles in the node list | Map & Waypoints — node positions on the map | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/tak.html#related-topics",
    
    "relUrl": "/zh-rCN/user/tak.html#related-topics"
  },"5248": {
    "doc": "TAK Integration",
    "title": "TAK Integration",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/tak.html",
    
    "relUrl": "/sq-rAL/user/tak.html"
  },"5249": {
    "doc": "TAK Integration",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/tak.html#overview",
    
    "relUrl": "/sq-rAL/user/tak.html#overview"
  },"5250": {
    "doc": "TAK Integration",
    "title": "Setup",
    "content": "Prerequisites . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. Configuration . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | Setting | Përshkrimi | . | Team Color | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Member Role | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 Tip: Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments. Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. The server binds to localhost only (127.0.0.1:8089) and uses TLS with mutual certificate authentication (mTLS), so it is not reachable from other devices on the network. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK Mesh Channel — selects which Meshtastic channel outgoing TAK traffic is sent on (default: the primary channel, index 0). Incoming TAK traffic is accepted from any channel. Matches the equivalent setting on iOS and in the legacy ATAK plugin. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | Export TAK Data Package — generates a .zip data package that ATAK/iTAK can import to connect to this server. | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/tak.html#setup",
    
    "relUrl": "/sq-rAL/user/tak.html#setup"
  },"5251": {
    "doc": "TAK Integration",
    "title": "TAK Roles",
    "content": "Nodes configured with TAK-related roles behave differently from standard clients: . | Role | Përshkrimi | . | 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. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/tak.html#tak-roles",
    
    "relUrl": "/sq-rAL/user/tak.html#tak-roles"
  },"5252": {
    "doc": "TAK Integration",
    "title": "Wire Format (V1 / V2)",
    "content": "Meshtastic supports two TAK wire formats, chosen automatically based on the connected radio’s firmware — no manual configuration needed: . | Format | Compatibility | Features | . | V1 (Legacy) | Firmware 2.7.x and older | Bare protobuf encoding on port 72. Supports position sharing (PLI) and chat (GeoChat) only — shapes, markers, routes, and other typed CoT events are dropped | . | V2 (Current) | Firmware 2.8.0+ | Compact, zstd-compressed encoding on port 78. Adds shapes, markers, routes, aircraft, casevac, emergency, and task CoT types on top of everything V1 supports | . A node still relays legacy V1 packets from older nodes even while running V2 itself, so mixed-firmware meshes keep working. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/tak.html#wire-format-v1--v2",
    
    "relUrl": "/sq-rAL/user/tak.html#wire-format-v1--v2"
  },"5253": {
    "doc": "TAK Integration",
    "title": "Usage with ATAK",
    "content": "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. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/tak.html#usage-with-atak",
    
    "relUrl": "/sq-rAL/user/tak.html#usage-with-atak"
  },"5254": {
    "doc": "TAK Integration",
    "title": "Troubleshooting",
    "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | Shapes, markers, or routes not bridging | Sending node is on legacy V1 (firmware 2.7.x or older) | Update the sending node’s firmware to 2.8.0+ for V2 wire format | . | CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/tak.html#troubleshooting",
    
    "relUrl": "/sq-rAL/user/tak.html#troubleshooting"
  },"5255": {
    "doc": "TAK Integration",
    "title": "Security Considerations",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/tak.html#security-considerations",
    
    "relUrl": "/sq-rAL/user/tak.html#security-considerations"
  },"5256": {
    "doc": "TAK Integration",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — TAK module configuration | Nodes — TAK and TAK Tracker roles in the node list | Map & Waypoints — node positions on the map | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/tak.html#related-topics",
    
    "relUrl": "/sq-rAL/user/tak.html#related-topics"
  },"5257": {
    "doc": "TAK Integration",
    "title": "TAK Integration",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/tak.html",
    
    "relUrl": "/zh-rTW/user/tak.html"
  },"5258": {
    "doc": "TAK Integration",
    "title": "概觀",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/tak.html#%E6%A6%82%E8%A7%80",
    
    "relUrl": "/zh-rTW/user/tak.html#概觀"
  },"5259": {
    "doc": "TAK Integration",
    "title": "設定",
    "content": "先決條件 . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. 設定 . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | 設定 | 描述說明 | . | 隊伍顏色 | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | 隊員角色 | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 Tip: Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments. Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. The server binds to localhost only (127.0.0.1:8089) and uses TLS with mutual certificate authentication (mTLS), so it is not reachable from other devices on the network. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK Mesh Channel — selects which Meshtastic channel outgoing TAK traffic is sent on (default: the primary channel, index 0). Incoming TAK traffic is accepted from any channel. Matches the equivalent setting on iOS and in the legacy ATAK plugin. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | Export TAK Data Package — generates a .zip data package that ATAK/iTAK can import to connect to this server. | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/tak.html#%E8%A8%AD%E5%AE%9A",
    
    "relUrl": "/zh-rTW/user/tak.html#設定"
  },"5260": {
    "doc": "TAK Integration",
    "title": "TAK Roles",
    "content": "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. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/tak.html#tak-roles",
    
    "relUrl": "/zh-rTW/user/tak.html#tak-roles"
  },"5261": {
    "doc": "TAK Integration",
    "title": "Wire Format (V1 / V2)",
    "content": "Meshtastic supports two TAK wire formats, chosen automatically based on the connected radio’s firmware — no manual configuration needed: . | Format | 相容性 | 特色 | . | V1 (Legacy) | Firmware 2.7.x and older | Bare protobuf encoding on port 72. Supports position sharing (PLI) and chat (GeoChat) only — shapes, markers, routes, and other typed CoT events are dropped | . | V2 (Current) | Firmware 2.8.0+ | Compact, zstd-compressed encoding on port 78. Adds shapes, markers, routes, aircraft, casevac, emergency, and task CoT types on top of everything V1 supports | . A node still relays legacy V1 packets from older nodes even while running V2 itself, so mixed-firmware meshes keep working. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/tak.html#wire-format-v1--v2",
    
    "relUrl": "/zh-rTW/user/tak.html#wire-format-v1--v2"
  },"5262": {
    "doc": "TAK Integration",
    "title": "Usage with ATAK",
    "content": "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. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/tak.html#usage-with-atak",
    
    "relUrl": "/zh-rTW/user/tak.html#usage-with-atak"
  },"5263": {
    "doc": "TAK Integration",
    "title": "故障排除",
    "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | Shapes, markers, or routes not bridging | Sending node is on legacy V1 (firmware 2.7.x or older) | Update the sending node’s firmware to 2.8.0+ for V2 wire format | . | CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/tak.html#%E6%95%85%E9%9A%9C%E6%8E%92%E9%99%A4",
    
    "relUrl": "/zh-rTW/user/tak.html#故障排除"
  },"5264": {
    "doc": "TAK Integration",
    "title": "Security Considerations",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/tak.html#security-considerations",
    
    "relUrl": "/zh-rTW/user/tak.html#security-considerations"
  },"5265": {
    "doc": "TAK Integration",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — TAK module configuration | Nodes — TAK and TAK Tracker roles in the node list | Map & Waypoints — node positions on the map | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/tak.html#related-topics",
    
    "relUrl": "/zh-rTW/user/tak.html#related-topics"
  },"5266": {
    "doc": "TAK integratsioon",
    "title": "TAK integratsioon",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/tak.html",
    
    "relUrl": "/et-rEE/user/tak.html"
  },"5267": {
    "doc": "TAK integratsioon",
    "title": "Ülevaade",
    "content": "TAK moodul võimaldab Meshtastic sõlmedel: . | Jaga asukohaandmeid TAK ühilduvas CoT (Cursor on Target) vormingus | Kuvatakse meeskonnaliikmetena TAK kaardil | TAK PLI (asukohateabe) sõnumite vastuvõtmine | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/tak.html#%C3%BClevaade",
    
    "relUrl": "/et-rEE/user/tak.html#ülevaade"
  },"5268": {
    "doc": "TAK integratsioon",
    "title": "Seadistamine",
    "content": "Prerequisites . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. Sätted . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | Seadistamine | Kirjeldus | . | Meeskonna värv | Sinu meeskonna värv TAK kaardil (nt sinine, punane, tsüaansinine, roheline) | . | Liikme roll | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 Vihje: Meeskonna/rolli värvid on TAK standardsed kuuluvusvärvid. Coordinate with your TAK team to use consistent team assignments. Lokaalne TAK server . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. Server seostub ainult localhostiga (127.0.0.1:8089) ja kasutab TLS-i vastastikuse sertifikaadi autentimisega (mTLS), seega pole see võrgus olevatest seadmetest kättesaadav. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK kärgvõrgu kanal — valib, millisel Meshtastic kanalil väljaminev TAK liiklus saadetakse (vaikimisi: peamine kanal, indeks 0). Sissetulevat TAK liiklust võetakse vastu igalt kanalilt. Vastab iOS-i ja pärand-ATAK-i pistikprogrammi samaväärsele sättele. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | Ekspordi TAK andmepakett — genereerib .zip-andmepaketi, mille ATAK/iTAK saab selle serveriga ühenduse loomiseks importida. | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/tak.html#seadistamine",
    
    "relUrl": "/et-rEE/user/tak.html#seadistamine"
  },"5269": {
    "doc": "TAK integratsioon",
    "title": "TAK rollid",
    "content": "TAKiga seotud rollidega seadistatud sõlmed käituvad tavalistest klientidest erinevalt: . | Roll | Kirjeldus | . | TAK | Täielik TAK koostalitlusvõime – saadab ja võtab vastu CoT andmeid, vestlussõnumeid ja PLI-uuendusi. Toimib tavalise kliendi ja TAK sillana. | . | TAK jälgimisseade | Ainult asukohapõhine TAK väljund – levitab PLI automaatselt regulaarsete intervallidega ilma kasutaja sekkumiseta. Optimeeritud järelevalveta asukohamajakate (sõidukid, seadmed, teekonnapunktid) jaoks. Ei vahenda vestlussõnumeid. | . 💡 Vihje: Kasuta TAK jälgimisseadet seadmete puhul, mis peavad edastama ainult asukohta (nt sõidukisse paigaldatud raadio). Kasutage TAK seadmete puhul, mille kasutajad osalevad aktiivselt TAK toimingutes. CoT (Cursor on Target) vorming . TAK- õnumid kasutavad kursori sihtmärgil XML-vormingut – see on sõjaline standard olukorrateadlikkuse andmete jagamiseks. Meshtastic teisendab oma sisemised protobuf-sõnumid TAK-süsteemidega ühendamisel CoT-vormingusse, seega pole käsitsi vormingu teisendamist vaja. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/tak.html#tak-rollid",
    
    "relUrl": "/et-rEE/user/tak.html#tak-rollid"
  },"5270": {
    "doc": "TAK integratsioon",
    "title": "Sõnumivorming (V1 / V2)",
    "content": "Meshtastic toetab kahte TAK sõnumivormingut, mis valitakse ühendatud raadio püsivara põhjal automaatselt – käsitsi konfigureerimist pole vaja: . | Vorming | Compatibility | Omadused | . | V1 (pärandversioon) | Püsivara 2.7.x ja vanem | Bare protobuf encoding on port 72. Toetab ainult asukoha jagamist (PLI) ja vestlust (GeoChat) – kujundid, markerid, marsruudid ja muud tüüpi CoT-sündmused eemaldatakse | . | V2 (praegune) | Püsivara 2.8.0+ | Compact, zstd-compressed encoding on port 78. Lisab lisaks kõigele, mida V1 toetab, kujundeid, markereid, marsruute, õhusõidukeid, tsiviillennukeid, hädaolukordi ja ülesannete CoT tüüpe | . Sõlm edastab pärand sõlmedelt pärit V1 pakette isegi V2 kasutamise ajal, seega sega-püsivaraga võrgud töötavad edasi. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/tak.html#s%C3%B5numivorming-v1--v2",
    
    "relUrl": "/et-rEE/user/tak.html#sõnumivorming-v1--v2"
  },"5271": {
    "doc": "TAK integratsioon",
    "title": "Kasutamine koos ATAKiga",
    "content": "Kui on seadistatud: . | Meshtastic sõlmed ilmuvad ATAK kaardil markeritena koos kutsungi nimega | Vestlussõnumid võivad ühendada kärgvõrgu ja TAK võrke | Asukohavärskendused liiguvad Meshtasticu ja TAKi vahel kahesuunaliselt | TAK jälgimisseadme sõlmed levitavad PLId automaatselt – nende asukohad kuvatakse ATAK kaartidel ilma ATAK poolse konfita | . ℹ️ Note: TAK integration requires specific node roles. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/tak.html#kasutamine-koos-atakiga",
    
    "relUrl": "/et-rEE/user/tak.html#kasutamine-koos-atakiga"
  },"5272": {
    "doc": "TAK integratsioon",
    "title": "Veaotsing",
    "content": "| Probleem | Põhjus | Lahendus | . | Sõlme ei kuvata ATAK kaardile | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Asukohavärskendused on aegunud | GPS asukoht kadunud või intervall liiga pikk | Kontrolli GPSi olekut; vähenda asukoha konfis asukoha levitamise intervalli | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | Shapes, markers, or routes not bridging | Saatja sõlm kasutab pärandversiooni V1 (püsivara 2.7.x või vanem) | Värskenda saatva sõlme püsivara versioonile 2.8.0+ sõnumivormingu V2 jaoks | . | CoT andmed ei liigu | Kanali mittevastavus | Kõik TAK-sõlmed peavad olema samal kanalil ja sama krüpteeringuga | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/tak.html#veaotsing",
    
    "relUrl": "/et-rEE/user/tak.html#veaotsing"
  },"5273": {
    "doc": "TAK integratsioon",
    "title": "Security Considerations",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/tak.html#security-considerations",
    
    "relUrl": "/et-rEE/user/tak.html#security-considerations"
  },"5274": {
    "doc": "TAK integratsioon",
    "title": "Seotud teemad",
    "content": ". | Seaded — moodulid ja admin — TAK mooduli konf | Sõlmed — TAK ja TAK jälgimisseade rollid sõlmede loendis | Kaart ja teekonnapunktid — sõlmede asukohad kaardil | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/tak.html#seotud-teemad",
    
    "relUrl": "/et-rEE/user/tak.html#seotud-teemad"
  },"5275": {
    "doc": "TAK Integration",
    "title": "TAK Integration",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/tak.html",
    
    "relUrl": "/fr-rFR/user/tak.html"
  },"5276": {
    "doc": "TAK Integration",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/tak.html#overview",
    
    "relUrl": "/fr-rFR/user/tak.html#overview"
  },"5277": {
    "doc": "TAK Integration",
    "title": "Setup",
    "content": "Prerequisites . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. Configuration . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | Paramètre | Description | . | Couleur de l’équipe | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Rôle Membre | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 Tip: Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments. Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. The server binds to localhost only (127.0.0.1:8089) and uses TLS with mutual certificate authentication (mTLS), so it is not reachable from other devices on the network. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK Mesh Channel — selects which Meshtastic channel outgoing TAK traffic is sent on (default: the primary channel, index 0). Incoming TAK traffic is accepted from any channel. Matches the equivalent setting on iOS and in the legacy ATAK plugin. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | Export TAK Data Package — generates a .zip data package that ATAK/iTAK can import to connect to this server. | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/tak.html#setup",
    
    "relUrl": "/fr-rFR/user/tak.html#setup"
  },"5278": {
    "doc": "TAK Integration",
    "title": "TAK Roles",
    "content": "Nodes configured with TAK-related roles behave differently from standard clients: . | Rôle | Description | . | 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. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/tak.html#tak-roles",
    
    "relUrl": "/fr-rFR/user/tak.html#tak-roles"
  },"5279": {
    "doc": "TAK Integration",
    "title": "Wire Format (V1 / V2)",
    "content": "Meshtastic supports two TAK wire formats, chosen automatically based on the connected radio’s firmware — no manual configuration needed: . | Format | Compatibility | Features | . | V1 (Legacy) | Firmware 2.7.x and older | Bare protobuf encoding on port 72. Supports position sharing (PLI) and chat (GeoChat) only — shapes, markers, routes, and other typed CoT events are dropped | . | V2 (Current) | Firmware 2.8.0+ | Compact, zstd-compressed encoding on port 78. Adds shapes, markers, routes, aircraft, casevac, emergency, and task CoT types on top of everything V1 supports | . A node still relays legacy V1 packets from older nodes even while running V2 itself, so mixed-firmware meshes keep working. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/tak.html#wire-format-v1--v2",
    
    "relUrl": "/fr-rFR/user/tak.html#wire-format-v1--v2"
  },"5280": {
    "doc": "TAK Integration",
    "title": "Usage with ATAK",
    "content": "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. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/tak.html#usage-with-atak",
    
    "relUrl": "/fr-rFR/user/tak.html#usage-with-atak"
  },"5281": {
    "doc": "TAK Integration",
    "title": "Troubleshooting",
    "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | Shapes, markers, or routes not bridging | Sending node is on legacy V1 (firmware 2.7.x or older) | Update the sending node’s firmware to 2.8.0+ for V2 wire format | . | CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/tak.html#troubleshooting",
    
    "relUrl": "/fr-rFR/user/tak.html#troubleshooting"
  },"5282": {
    "doc": "TAK Integration",
    "title": "Security Considerations",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/tak.html#security-considerations",
    
    "relUrl": "/fr-rFR/user/tak.html#security-considerations"
  },"5283": {
    "doc": "TAK Integration",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — TAK module configuration | Nodes — TAK and TAK Tracker roles in the node list | Map & Waypoints — node positions on the map | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/tak.html#related-topics",
    
    "relUrl": "/fr-rFR/user/tak.html#related-topics"
  },"5284": {
    "doc": "TAK Integration",
    "title": "TAK Integration",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/tak.html",
    
    "relUrl": "/tr-rTR/user/tak.html"
  },"5285": {
    "doc": "TAK Integration",
    "title": "Genel Bakış",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/tak.html#genel-bak%C4%B1%C5%9F",
    
    "relUrl": "/tr-rTR/user/tak.html#genel-bakış"
  },"5286": {
    "doc": "TAK Integration",
    "title": "Setup",
    "content": "Prerequisites . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. Yapılandırma . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | Setting | Açıklaması | . | Team Color | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Member Role | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 Tip: Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments. Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. The server binds to localhost only (127.0.0.1:8089) and uses TLS with mutual certificate authentication (mTLS), so it is not reachable from other devices on the network. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK Mesh Channel — selects which Meshtastic channel outgoing TAK traffic is sent on (default: the primary channel, index 0). Incoming TAK traffic is accepted from any channel. Matches the equivalent setting on iOS and in the legacy ATAK plugin. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | Export TAK Data Package — generates a .zip data package that ATAK/iTAK can import to connect to this server. | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/tak.html#setup",
    
    "relUrl": "/tr-rTR/user/tak.html#setup"
  },"5287": {
    "doc": "TAK Integration",
    "title": "TAK Roles",
    "content": "Nodes configured with TAK-related roles behave differently from standard clients: . | Rol | Açıklaması | . | 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. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/tak.html#tak-roles",
    
    "relUrl": "/tr-rTR/user/tak.html#tak-roles"
  },"5288": {
    "doc": "TAK Integration",
    "title": "Wire Format (V1 / V2)",
    "content": "Meshtastic supports two TAK wire formats, chosen automatically based on the connected radio’s firmware — no manual configuration needed: . | Format | Compatibility | Özellikler | . | V1 (Legacy) | Firmware 2.7.x and older | Bare protobuf encoding on port 72. Supports position sharing (PLI) and chat (GeoChat) only — shapes, markers, routes, and other typed CoT events are dropped | . | V2 (Current) | Firmware 2.8.0+ | Compact, zstd-compressed encoding on port 78. Adds shapes, markers, routes, aircraft, casevac, emergency, and task CoT types on top of everything V1 supports | . A node still relays legacy V1 packets from older nodes even while running V2 itself, so mixed-firmware meshes keep working. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/tak.html#wire-format-v1--v2",
    
    "relUrl": "/tr-rTR/user/tak.html#wire-format-v1--v2"
  },"5289": {
    "doc": "TAK Integration",
    "title": "Usage with ATAK",
    "content": "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. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/tak.html#usage-with-atak",
    
    "relUrl": "/tr-rTR/user/tak.html#usage-with-atak"
  },"5290": {
    "doc": "TAK Integration",
    "title": "Troubleshooting",
    "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | Shapes, markers, or routes not bridging | Sending node is on legacy V1 (firmware 2.7.x or older) | Update the sending node’s firmware to 2.8.0+ for V2 wire format | . | CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/tak.html#troubleshooting",
    
    "relUrl": "/tr-rTR/user/tak.html#troubleshooting"
  },"5291": {
    "doc": "TAK Integration",
    "title": "Security Considerations",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/tak.html#security-considerations",
    
    "relUrl": "/tr-rTR/user/tak.html#security-considerations"
  },"5292": {
    "doc": "TAK Integration",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — TAK module configuration | Nodes — TAK and TAK Tracker roles in the node list | Map & Waypoints — node positions on the map | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/tak.html#related-topics",
    
    "relUrl": "/tr-rTR/user/tak.html#related-topics"
  },"5293": {
    "doc": "TAK Integration",
    "title": "TAK Integration",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/tak.html",
    
    "relUrl": "/el-rGR/user/tak.html"
  },"5294": {
    "doc": "TAK Integration",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/tak.html#overview",
    
    "relUrl": "/el-rGR/user/tak.html#overview"
  },"5295": {
    "doc": "TAK Integration",
    "title": "Setup",
    "content": "Prerequisites . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. Configuration . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | Setting | Περιγραφή | . | Team Color | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Member Role | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 Tip: Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments. Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. The server binds to localhost only (127.0.0.1:8089) and uses TLS with mutual certificate authentication (mTLS), so it is not reachable from other devices on the network. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK Mesh Channel — selects which Meshtastic channel outgoing TAK traffic is sent on (default: the primary channel, index 0). Incoming TAK traffic is accepted from any channel. Matches the equivalent setting on iOS and in the legacy ATAK plugin. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | Export TAK Data Package — generates a .zip data package that ATAK/iTAK can import to connect to this server. | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/tak.html#setup",
    
    "relUrl": "/el-rGR/user/tak.html#setup"
  },"5296": {
    "doc": "TAK Integration",
    "title": "TAK Roles",
    "content": "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. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/tak.html#tak-roles",
    
    "relUrl": "/el-rGR/user/tak.html#tak-roles"
  },"5297": {
    "doc": "TAK Integration",
    "title": "Wire Format (V1 / V2)",
    "content": "Meshtastic supports two TAK wire formats, chosen automatically based on the connected radio’s firmware — no manual configuration needed: . | Format | Compatibility | Features | . | V1 (Legacy) | Firmware 2.7.x and older | Bare protobuf encoding on port 72. Supports position sharing (PLI) and chat (GeoChat) only — shapes, markers, routes, and other typed CoT events are dropped | . | V2 (Current) | Firmware 2.8.0+ | Compact, zstd-compressed encoding on port 78. Adds shapes, markers, routes, aircraft, casevac, emergency, and task CoT types on top of everything V1 supports | . A node still relays legacy V1 packets from older nodes even while running V2 itself, so mixed-firmware meshes keep working. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/tak.html#wire-format-v1--v2",
    
    "relUrl": "/el-rGR/user/tak.html#wire-format-v1--v2"
  },"5298": {
    "doc": "TAK Integration",
    "title": "Usage with ATAK",
    "content": "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. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/tak.html#usage-with-atak",
    
    "relUrl": "/el-rGR/user/tak.html#usage-with-atak"
  },"5299": {
    "doc": "TAK Integration",
    "title": "Troubleshooting",
    "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | Shapes, markers, or routes not bridging | Sending node is on legacy V1 (firmware 2.7.x or older) | Update the sending node’s firmware to 2.8.0+ for V2 wire format | . | CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/tak.html#troubleshooting",
    
    "relUrl": "/el-rGR/user/tak.html#troubleshooting"
  },"5300": {
    "doc": "TAK Integration",
    "title": "Security Considerations",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/tak.html#security-considerations",
    
    "relUrl": "/el-rGR/user/tak.html#security-considerations"
  },"5301": {
    "doc": "TAK Integration",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — TAK module configuration | Nodes — TAK and TAK Tracker roles in the node list | Map & Waypoints — node positions on the map | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/tak.html#related-topics",
    
    "relUrl": "/el-rGR/user/tak.html#related-topics"
  },"5302": {
    "doc": "TAK Integration",
    "title": "TAK Integration",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/tak.html",
    
    "relUrl": "/ro-rRO/user/tak.html"
  },"5303": {
    "doc": "TAK Integration",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/tak.html#overview",
    
    "relUrl": "/ro-rRO/user/tak.html#overview"
  },"5304": {
    "doc": "TAK Integration",
    "title": "Setup",
    "content": "Prerequisites . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. Configuration . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | Setting | Descriere | . | Culoarea echipei | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Rolul membrului | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 Tip: Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments. Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. The server binds to localhost only (127.0.0.1:8089) and uses TLS with mutual certificate authentication (mTLS), so it is not reachable from other devices on the network. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK Mesh Channel — selects which Meshtastic channel outgoing TAK traffic is sent on (default: the primary channel, index 0). Incoming TAK traffic is accepted from any channel. Matches the equivalent setting on iOS and in the legacy ATAK plugin. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | Export TAK Data Package — generates a .zip data package that ATAK/iTAK can import to connect to this server. | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/tak.html#setup",
    
    "relUrl": "/ro-rRO/user/tak.html#setup"
  },"5305": {
    "doc": "TAK Integration",
    "title": "TAK Roles",
    "content": "Nodes configured with TAK-related roles behave differently from standard clients: . | Role | Descriere | . | 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. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/tak.html#tak-roles",
    
    "relUrl": "/ro-rRO/user/tak.html#tak-roles"
  },"5306": {
    "doc": "TAK Integration",
    "title": "Wire Format (V1 / V2)",
    "content": "Meshtastic supports two TAK wire formats, chosen automatically based on the connected radio’s firmware — no manual configuration needed: . | Format | Compatibility | Features | . | V1 (Legacy) | Firmware 2.7.x and older | Bare protobuf encoding on port 72. Supports position sharing (PLI) and chat (GeoChat) only — shapes, markers, routes, and other typed CoT events are dropped | . | V2 (Current) | Firmware 2.8.0+ | Compact, zstd-compressed encoding on port 78. Adds shapes, markers, routes, aircraft, casevac, emergency, and task CoT types on top of everything V1 supports | . A node still relays legacy V1 packets from older nodes even while running V2 itself, so mixed-firmware meshes keep working. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/tak.html#wire-format-v1--v2",
    
    "relUrl": "/ro-rRO/user/tak.html#wire-format-v1--v2"
  },"5307": {
    "doc": "TAK Integration",
    "title": "Usage with ATAK",
    "content": "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. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/tak.html#usage-with-atak",
    
    "relUrl": "/ro-rRO/user/tak.html#usage-with-atak"
  },"5308": {
    "doc": "TAK Integration",
    "title": "Troubleshooting",
    "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | Shapes, markers, or routes not bridging | Sending node is on legacy V1 (firmware 2.7.x or older) | Update the sending node’s firmware to 2.8.0+ for V2 wire format | . | CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/tak.html#troubleshooting",
    
    "relUrl": "/ro-rRO/user/tak.html#troubleshooting"
  },"5309": {
    "doc": "TAK Integration",
    "title": "Security Considerations",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/tak.html#security-considerations",
    
    "relUrl": "/ro-rRO/user/tak.html#security-considerations"
  },"5310": {
    "doc": "TAK Integration",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — TAK module configuration | Nodes — TAK and TAK Tracker roles in the node list | Map & Waypoints — node positions on the map | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/tak.html#related-topics",
    
    "relUrl": "/ro-rRO/user/tak.html#related-topics"
  },"5311": {
    "doc": "TAK Integration",
    "title": "TAK Integration",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/tak.html",
    
    "relUrl": "/iw-rIL/user/tak.html"
  },"5312": {
    "doc": "TAK Integration",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/tak.html#overview",
    
    "relUrl": "/iw-rIL/user/tak.html#overview"
  },"5313": {
    "doc": "TAK Integration",
    "title": "Setup",
    "content": "Prerequisites . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. Configuration . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | Setting | תיאור | . | Team Color | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Member Role | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 Tip: Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments. Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. The server binds to localhost only (127.0.0.1:8089) and uses TLS with mutual certificate authentication (mTLS), so it is not reachable from other devices on the network. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK Mesh Channel — selects which Meshtastic channel outgoing TAK traffic is sent on (default: the primary channel, index 0). Incoming TAK traffic is accepted from any channel. Matches the equivalent setting on iOS and in the legacy ATAK plugin. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | Export TAK Data Package — generates a .zip data package that ATAK/iTAK can import to connect to this server. | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/tak.html#setup",
    
    "relUrl": "/iw-rIL/user/tak.html#setup"
  },"5314": {
    "doc": "TAK Integration",
    "title": "TAK Roles",
    "content": "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. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/tak.html#tak-roles",
    
    "relUrl": "/iw-rIL/user/tak.html#tak-roles"
  },"5315": {
    "doc": "TAK Integration",
    "title": "Wire Format (V1 / V2)",
    "content": "Meshtastic supports two TAK wire formats, chosen automatically based on the connected radio’s firmware — no manual configuration needed: . | Format | Compatibility | Features | . | V1 (Legacy) | Firmware 2.7.x and older | Bare protobuf encoding on port 72. Supports position sharing (PLI) and chat (GeoChat) only — shapes, markers, routes, and other typed CoT events are dropped | . | V2 (Current) | Firmware 2.8.0+ | Compact, zstd-compressed encoding on port 78. Adds shapes, markers, routes, aircraft, casevac, emergency, and task CoT types on top of everything V1 supports | . A node still relays legacy V1 packets from older nodes even while running V2 itself, so mixed-firmware meshes keep working. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/tak.html#wire-format-v1--v2",
    
    "relUrl": "/iw-rIL/user/tak.html#wire-format-v1--v2"
  },"5316": {
    "doc": "TAK Integration",
    "title": "Usage with ATAK",
    "content": "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. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/tak.html#usage-with-atak",
    
    "relUrl": "/iw-rIL/user/tak.html#usage-with-atak"
  },"5317": {
    "doc": "TAK Integration",
    "title": "Troubleshooting",
    "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | Shapes, markers, or routes not bridging | Sending node is on legacy V1 (firmware 2.7.x or older) | Update the sending node’s firmware to 2.8.0+ for V2 wire format | . | CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/tak.html#troubleshooting",
    
    "relUrl": "/iw-rIL/user/tak.html#troubleshooting"
  },"5318": {
    "doc": "TAK Integration",
    "title": "Security Considerations",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/tak.html#security-considerations",
    
    "relUrl": "/iw-rIL/user/tak.html#security-considerations"
  },"5319": {
    "doc": "TAK Integration",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — TAK module configuration | Nodes — TAK and TAK Tracker roles in the node list | Map & Waypoints — node positions on the map | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/tak.html#related-topics",
    
    "relUrl": "/iw-rIL/user/tak.html#related-topics"
  },"5320": {
    "doc": "TAK Integration",
    "title": "TAK Integration",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/tak.html",
    
    "relUrl": "/pt-rBR/user/tak.html"
  },"5321": {
    "doc": "TAK Integration",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/tak.html#overview",
    
    "relUrl": "/pt-rBR/user/tak.html#overview"
  },"5322": {
    "doc": "TAK Integration",
    "title": "Setup",
    "content": "Prerequisites . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. Configuration . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | Setting | Descrição | . | Team Color | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Member Role | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 Tip: Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments. Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. The server binds to localhost only (127.0.0.1:8089) and uses TLS with mutual certificate authentication (mTLS), so it is not reachable from other devices on the network. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK Mesh Channel — selects which Meshtastic channel outgoing TAK traffic is sent on (default: the primary channel, index 0). Incoming TAK traffic is accepted from any channel. Matches the equivalent setting on iOS and in the legacy ATAK plugin. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | Export TAK Data Package — generates a .zip data package that ATAK/iTAK can import to connect to this server. | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/tak.html#setup",
    
    "relUrl": "/pt-rBR/user/tak.html#setup"
  },"5323": {
    "doc": "TAK Integration",
    "title": "TAK Roles",
    "content": "Nodes configured with TAK-related roles behave differently from standard clients: . | Função | Descrição | . | 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. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/tak.html#tak-roles",
    
    "relUrl": "/pt-rBR/user/tak.html#tak-roles"
  },"5324": {
    "doc": "TAK Integration",
    "title": "Wire Format (V1 / V2)",
    "content": "Meshtastic supports two TAK wire formats, chosen automatically based on the connected radio’s firmware — no manual configuration needed: . | Format | Compatibility | Features | . | V1 (Legacy) | Firmware 2.7.x and older | Bare protobuf encoding on port 72. Supports position sharing (PLI) and chat (GeoChat) only — shapes, markers, routes, and other typed CoT events are dropped | . | V2 (Current) | Firmware 2.8.0+ | Compact, zstd-compressed encoding on port 78. Adds shapes, markers, routes, aircraft, casevac, emergency, and task CoT types on top of everything V1 supports | . A node still relays legacy V1 packets from older nodes even while running V2 itself, so mixed-firmware meshes keep working. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/tak.html#wire-format-v1--v2",
    
    "relUrl": "/pt-rBR/user/tak.html#wire-format-v1--v2"
  },"5325": {
    "doc": "TAK Integration",
    "title": "Usage with ATAK",
    "content": "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. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/tak.html#usage-with-atak",
    
    "relUrl": "/pt-rBR/user/tak.html#usage-with-atak"
  },"5326": {
    "doc": "TAK Integration",
    "title": "Troubleshooting",
    "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | Shapes, markers, or routes not bridging | Sending node is on legacy V1 (firmware 2.7.x or older) | Update the sending node’s firmware to 2.8.0+ for V2 wire format | . | CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/tak.html#troubleshooting",
    
    "relUrl": "/pt-rBR/user/tak.html#troubleshooting"
  },"5327": {
    "doc": "TAK Integration",
    "title": "Security Considerations",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/tak.html#security-considerations",
    
    "relUrl": "/pt-rBR/user/tak.html#security-considerations"
  },"5328": {
    "doc": "TAK Integration",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — TAK module configuration | Nodes — TAK and TAK Tracker roles in the node list | Map & Waypoints — node positions on the map | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/tak.html#related-topics",
    
    "relUrl": "/pt-rBR/user/tak.html#related-topics"
  },"5329": {
    "doc": "TAK Integration",
    "title": "TAK Integration",
    "content": "Meshtastic integrates with the Team Awareness Kit (TAK) ecosystem, enabling interoperability between Meshtastic radios and TAK applications like ATAK and WinTAK. ",
    "url": "/Meshtastic-Android/main/en/user/tak.html",
    
    "relUrl": "/en/user/tak.html"
  },"5330": {
    "doc": "TAK Integration",
    "title": "Overview",
    "content": "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 | . ",
    "url": "/Meshtastic-Android/main/en/user/tak.html#overview",
    
    "relUrl": "/en/user/tak.html#overview"
  },"5331": {
    "doc": "TAK Integration",
    "title": "Setup",
    "content": "Prerequisites . | ATAK (Android Team Awareness Kit), iTAK, or WinTAK installed | Your node’s Device Role (Device configuration) set to TAK or TAK Tracker — this is what makes the TAK module appear in Module configuration at all | Firmware 2.8.0 or newer on the radio. Earlier firmware accepts a TAK config write and never stores it, so the app hides the TAK module entry below that version even when the role is set correctly. See Firmware Updates | . ⚠️ Warning: The old Meshtastic ATAK Plugin is no longer part of this path and cannot work. It bridged through the cross-process AIDL API, which was removed in app 2.8.0; the mesh service is now in-process only. Do not install it. Interop today runs over the app’s own local TAK server plus the Mesh to CoT Converter, both described in the following sections, with stock ATAK/iTAK/WinTAK. Configuration . Navigate to Settings → Module configuration → TAK. The module’s own settings are your TAK identity — there is no separate enable switch here, because the Device Role setting in Device configuration is what turns TAK on. Your node broadcasts this identity, which appears on TAK maps. | Setting | Description | . | Team Color | Your team color on the TAK map (e.g., Blue, Red, Cyan, Green) | . | Member Role | Your operational role within that team (Team Member, Team Lead, HQ, Medic, RTO, etc.) | . Your TAK callsign isn’t a separate setting — it’s derived automatically from your Meshtastic node name. 💡 Tip: Team/role colors are the standard TAK affiliation colors. Coordinate with your TAK team to use consistent team assignments. Local TAK Server . The app can also run a local TAK server so ATAK/iTAK on the same phone can connect directly, without a remote TAK server. The server binds to localhost only (127.0.0.1:8089) and uses TLS with mutual certificate authentication (mTLS), so it is not reachable from other devices on the network. Open Settings → Advanced → TAK Server. These are app settings stored on this phone, which is why they sit next to Firmware Update and Debug Panel rather than under the TAK module config — and why they need neither a TAK role nor firmware 2.8.0: . | Enable Local TAK Server — starts the loopback-only mTLS server on port 8089 for ATAK/iTAK connections from the same phone. | TAK Mesh Channel — selects which Meshtastic channel outgoing TAK traffic is sent on (default: the primary channel, index 0). Incoming TAK traffic is accepted from any channel. Matches the equivalent setting on iOS and in the legacy ATAK plugin. | Mesh to CoT Converter — off by default, and shown under the server toggle. With the server running, this synthesizes a CoT contact for every node in your node database, so ordinary Meshtastic nodes appear on the ATAK map as contacts. This is what replaced the old plugin’s node visibility — without it, only TAK-role nodes show up. | Export TAK Data Package — generates a .zip data package that ATAK/iTAK can import to connect to this server. | . ",
    "url": "/Meshtastic-Android/main/en/user/tak.html#setup",
    
    "relUrl": "/en/user/tak.html#setup"
  },"5332": {
    "doc": "TAK Integration",
    "title": "TAK Roles",
    "content": "Nodes configured with TAK-related roles behave differently from standard clients: . | Role | Description | . | 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. ",
    "url": "/Meshtastic-Android/main/en/user/tak.html#tak-roles",
    
    "relUrl": "/en/user/tak.html#tak-roles"
  },"5333": {
    "doc": "TAK Integration",
    "title": "Wire Format (V1 / V2)",
    "content": "Meshtastic supports two TAK wire formats, chosen automatically based on the connected radio’s firmware — no manual configuration needed: . | Format | Compatibility | Features | . | V1 (Legacy) | Firmware 2.7.x and older | Bare protobuf encoding on port 72. Supports position sharing (PLI) and chat (GeoChat) only — shapes, markers, routes, and other typed CoT events are dropped | . | V2 (Current) | Firmware 2.8.0+ | Compact, zstd-compressed encoding on port 78. Adds shapes, markers, routes, aircraft, casevac, emergency, and task CoT types on top of everything V1 supports | . A node still relays legacy V1 packets from older nodes even while running V2 itself, so mixed-firmware meshes keep working. ",
    "url": "/Meshtastic-Android/main/en/user/tak.html#wire-format-v1--v2",
    
    "relUrl": "/en/user/tak.html#wire-format-v1--v2"
  },"5334": {
    "doc": "TAK Integration",
    "title": "Usage with ATAK",
    "content": "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. Standard client nodes don’t automatically participate in TAK operations — though with Mesh to CoT Converter enabled they still appear on the ATAK map as contacts. ",
    "url": "/Meshtastic-Android/main/en/user/tak.html#usage-with-atak",
    
    "relUrl": "/en/user/tak.html#usage-with-atak"
  },"5335": {
    "doc": "TAK Integration",
    "title": "Troubleshooting",
    "content": "| Problem | Cause | Solution | . | Node doesn’t appear on ATAK map | Wrong Device Role setting, or Mesh to CoT Converter off | Set the node’s Device Role to TAK or TAK Tracker. For ordinary (non-TAK-role) nodes to appear, also enable Mesh to CoT Converter under Settings → Advanced → TAK Server | . | Position updates are stale | GPS fix lost or interval too long | Check GPS status; reduce position broadcast interval in Position Config | . | ATAK shows “disconnected” | The local TAK server is off, or ATAK is pointed elsewhere | Check Enable Local TAK Server is on, and that ATAK is connecting to 127.0.0.1:8089 — re-import the exported data package if unsure | . | Shapes, markers, or routes not bridging | Sending node is on legacy V1 (firmware 2.7.x or older) | Update the sending node’s firmware to 2.8.0+ for V2 wire format | . | CoT data not flowing | Channel mismatch | All TAK nodes must be on the same channel with matching encryption | . ",
    "url": "/Meshtastic-Android/main/en/user/tak.html#troubleshooting",
    
    "relUrl": "/en/user/tak.html#troubleshooting"
  },"5336": {
    "doc": "TAK Integration",
    "title": "Security Considerations",
    "content": "🔒 Privacy: TAK data shares your position and callsign information. The TAK module respects the same channel encryption as other Meshtastic messages — in sensitive environments, use a channel with a non-default key. ",
    "url": "/Meshtastic-Android/main/en/user/tak.html#security-considerations",
    
    "relUrl": "/en/user/tak.html#security-considerations"
  },"5337": {
    "doc": "TAK Integration",
    "title": "Related Topics",
    "content": ". | Settings — Modules & Admin — TAK module configuration | Nodes — TAK and TAK Tracker roles in the node list | Map & Waypoints — node positions on the map | . ",
    "url": "/Meshtastic-Android/main/en/user/tak.html#related-topics",
    
    "relUrl": "/en/user/tak.html#related-topics"
  },"5338": {
    "doc": "Test Builds & Obtainium",
    "title": "Test Builds & Obtainium",
    "content": "Obtainium installs and auto-updates Android apps straight from their GitHub releases — no Play Store account, no testing-track invite. This page sets it up for Meshtastic and shows how to follow the open beta, closed beta, or snapshot channels. Builds from GitHub are signed with the project’s release key (CN=Kevin Hester, O=Geeksville Industries), not Google Play’s — if you already have Meshtastic installed from the Play Store, Android refuses to update over it. Switching between the fdroid and google flavors is fine: both flavors in a given release carry the same release key, so Obtainium can move you from one to the other in place (verified by installing the google APK over an installed fdroid build). Only the origin of a build (Play vs GitHub) determines whether the signatures clash. ⚠️ Warning: Uninstalling the Play Store version of Meshtastic clears the app’s data — message history and settings on this phone are lost. Uninstall it before installing via Obtainium, then stay on Obtainium for updates. ",
    "url": "/Meshtastic-Android/main/en/developer/test-builds.html#test-builds--obtainium",
    
    "relUrl": "/en/developer/test-builds.html#test-builds--obtainium"
  },"5339": {
    "doc": "Test Builds & Obtainium",
    "title": "Which channels can Obtainium reach?",
    "content": "Meshtastic for Android promotes builds up a ladder: closed → open → production. Each maps to a Google Play track, and the GitHub release is published (un-drafted) when a build is promoted to closed or higher. | Channel | Play track | On GitHub | Obtainium can install it? | . | stable | Production | published, marked Latest | ✅ Yes | . | open beta | Beta (Open) | published prerelease, tag vX.Y.Z-open.N | ✅ Yes | . | closed beta | Alpha (Closed) | published prerelease, tag vX.Y.Z-closed.N | ✅ Yes | . | snapshot | — (not on Play) | rolling prerelease, tag snapshot | ✅ Yes | . Each promotion cuts its own tag, and older ones stay published — a whole run of vX.Y.Z-open.N tags accumulates during a version cycle, each still installable with APKs attached. So a channel gathers releases rather than moving a single one forward, and the channel configs in One-Tap Setup pick the newest release whose title matches the channel. Which release each channel currently resolves to is deliberately not listed on this page: it is archived per release tag and bundled into the app, so a live version number here would be frozen at build time and wrong within weeks. The project README carries the current state, refreshed automatically. A channel can legitimately be empty — most often -closed, early in a cycle before any build has been cut to it. The number of published fdroid ABI splits has changed across releases, which is why the filter matches every split. Snapshot is different: it’s an automated debug build of the latest commit on main, rebuilt and re-published under the single moving snapshot tag on every push. It never goes to Play. Because debug builds use a .debug application-ID suffix (com.geeksville.mesh.fdroid.debug / com.geeksville.mesh.google.debug) and the debug signing key, a snapshot installs as its own separate app — it sits alongside a Play/stable/beta install, so the uninstall-first warning earlier on this page does not apply to it. ",
    "url": "/Meshtastic-Android/main/en/developer/test-builds.html#which-channels-can-obtainium-reach",
    
    "relUrl": "/en/developer/test-builds.html#which-channels-can-obtainium-reach"
  },"5340": {
    "doc": "Test Builds & Obtainium",
    "title": "One-tap setup",
    "content": "Tap a link in the following table on the phone that has Obtainium installed. Every setting from the rest of this page is already baked into it — pick the channel you want and the flavor you want (which flavor?). | Channel | google flavor | fdroid flavor | . | Stable | Add | Add | . | Open beta | Add | Add | . | Closed beta | Add | Add | . | Bleeding edge (newest promoted test build) | Add | Add | . | Snapshot (latest commit on main) | Add | Add | . Prefer a file? Import one of these via Import/Export → Obtainium import. Pick the one matching the flavor you want for the release build; each also sets up both snapshot flavors, which can coexist: . | meshtastic-obtainium-export-google.json — google stable + both snapshots | meshtastic-obtainium-export-fdroid.json — fdroid stable + both snapshots | . How many entries can you have at once? . Obtainium keys apps by application ID, so the rule follows from ours: . |   | Application ID | Can coexist? | . | Release builds — stable, open, closed, bleeding edge, either flavor | com.geeksville.mesh | No — pick exactly one | . | Snapshot, google | com.geeksville.mesh.google.debug | Yes | . | Snapshot, fdroid | com.geeksville.mesh.fdroid.debug | Yes | . At most one release entry plus the two snapshot entries. Tapping a second release link switches that single entry to the new channel or flavor instead of adding one, and importing both files in turn leaves you with whichever flavor’s release entry came last. The snapshots are unaffected either way. To set things up by hand instead, follow the rest of this page. ",
    "url": "/Meshtastic-Android/main/en/developer/test-builds.html#one-tap-setup",
    
    "relUrl": "/en/developer/test-builds.html#one-tap-setup"
  },"5341": {
    "doc": "Test Builds & Obtainium",
    "title": "Manual setup",
    "content": ". | Install Obtainium (GitHub releases or F-Droid / IzzyOnDroid). | Tap Add App. | App Source URL: https://github.com/meshtastic/Meshtastic-Android | Set the options for the channel you want — see Stable, Open beta, Closed beta, Bleeding edge, or Snapshot. | Tap Add, then Install. | . Stable . | Include prereleases: off | (optional, stricter) Verify the ‘latest’ tag: on | Filter APKs by regular expression: see Picking the APK | . Open beta . | Include prereleases: on | Filter release titles by regular expression: -open | Filter APKs by regular expression: see Picking the APK | . Closed beta . | Include prereleases: on | Filter release titles by regular expression: -closed | Filter APKs by regular expression: see Picking the APK | . Bleeding edge (newest promoted test build, any channel) . | Include prereleases: on | Filter release titles by regular expression: -(closed|open) | Filter APKs by regular expression: see Picking the APK | . Obtainium installs the newest promoted prerelease — whatever is currently in open or closed. The title filter is required to skip the always-newer snapshot prerelease; without it Obtainium would follow snapshot instead. Snapshot (latest commit on main) . | Include prereleases: on | Filter release titles by regular expression: ^Snapshot | Use the latest asset date as the release date: on | Version detection: off, with Release date as version on | Filter APKs by regular expression: debug-signed names, see the following table | . Follows main directly — updates on every push. These are debug builds (.debug package, debug key), so they install as a separate app and won’t disturb a stable/beta install. The snapshot tag never changes, so there is no version string to compare — date-based pseudo-versioning is what makes updates detectable. The APKs are named …-debug-<versionCode>.apk (not -release.apk), so use debug-suffixed filters: . | You want | Regex | . | google flavor, most phones (arm64) | google-arm64-v8a-debug-\\d+\\.apk | . | fdroid flavor, most phones (arm64) | fdroid-arm64-v8a-debug-\\d+\\.apk | . | fdroid flavor, one-size-fits-all | fdroid-universal-debug-\\d+\\.apk | . Snapshot releases attach only the debug APKs — no .aab or desktop installers. ℹ️ Note: Local debug builds and CI snapshots are update-compatible: the repo checks in a shared debug keystore (config/debug.keystore) that both sign with, so Obtainium can update over your own debug install. INSTALL_FAILED_UPDATE_INCOMPATIBLE means the installed build predates the shared keystore (or was signed with another machine’s default key) — uninstall that one build and reinstall. Two more things about release selection apply to every channel described earlier, not just snapshot: . Leave “Fallback to older releases” ON. It is not a channel-strictness setting, and turning it off breaks every channel config here. Obtainium’s release loop breaks out after the first candidate when fallback is off, so a title filter never gets to skip past non-matching releases. A config pinned to -open or ^Snapshot then fails with “Could not find a suitable release” when a newer production release sits at the head of the list. The title filter is what pins the channel; fallback is what lets Obtainium walk down to the newest release that matches it. ℹ️ Note: If your channel filter still finds nothing, that channel has no published release — common early in a version cycle. Check the project README for what is live, or use the Bleeding edge form to follow whichever of open/closed is newest. ",
    "url": "/Meshtastic-Android/main/en/developer/test-builds.html#manual-setup",
    
    "relUrl": "/en/developer/test-builds.html#manual-setup"
  },"5342": {
    "doc": "Test Builds & Obtainium",
    "title": "Picking the APK",
    "content": "Each release attaches the google flavor APK, several fdroid flavor APKs, plus an .aab (not installable) and the desktop installers. Obtainium ignores non-APK assets on its own, but the two flavors share the com.geeksville.mesh package name, so exactly one must be pinned with Filter APKs by regular expression: . | You want | Regex | . | Recommended for testing — google flavor | google-release\\.apk | . | fdroid flavor, most phones (arm64) | fdroid-arm64-v8a-release\\.apk | . | fdroid flavor, one-size-fits-all | fdroid-universal-release\\.apk | . | fdroid flavor, let Obtainium pick the ABI | fdroid-.*-release\\.apk with Auto-select by architecture on | . Use the google flavor while testing. It ships Firebase Crashlytics and Datadog RUM, so the crashes and errors you hit get reported back to the team — which is the whole point of a test phase. It also has Google push (FCM) and Google Maps. Pick an fdroid flavor only if you’d rather not send that telemetry. You can change your mind later: both flavors share the release key, so Obtainium updates across the flavor boundary without an uninstall. Expect the google flavor to show its analytics-consent screen the first time it starts. ",
    "url": "/Meshtastic-Android/main/en/developer/test-builds.html#picking-the-apk",
    
    "relUrl": "/en/developer/test-builds.html#picking-the-apk"
  },"5343": {
    "doc": "Test Builds & Obtainium",
    "title": "Version detection turns itself off — that’s expected",
    "content": "Release tags read vX.Y.Z, while our installed versionName reads X.Y.Z (versionCode) <flavor>. Obtainium tries to reconcile the two against a list of standard version formats, all of which are fully anchored — none of them tolerates the spaces and parentheses in our versionName. So on the first update check Obtainium logs Could not reconcile version formats for: com.geeksville.mesh, sets Version detection to off for the app, and records the release tag as the installed version. This is harmless and you should not try to fix it. With detection off, Obtainium compares the release tag it last installed against the newest tag, so updates are still detected and installed normally. What you lose is only the ability to notice a version installed outside Obtainium. In particular, do not set “Trim the version string” to \\d+\\.\\d+\\.\\d+ hoping to fix it. That setting only rewrites the version parsed from the release; the unparseable side is the installed versionName, which it never touches — so reconciliation fails exactly as before. It also adds a failure mode: if the regex ever matches nothing (a tag without a three-part version), the update check fails outright with a “no version found” error instead of degrading quietly. Snapshot is a separate case: its tag is the literal string snapshot and never changes, so tag comparison can’t work either. Those configs use date-based pseudo-versioning (Release date as version plus Use the latest asset date as the release date) instead. ",
    "url": "/Meshtastic-Android/main/en/developer/test-builds.html#version-detection-turns-itself-off--thats-expected",
    
    "relUrl": "/en/developer/test-builds.html#version-detection-turns-itself-off--thats-expected"
  },"5344": {
    "doc": "Test Builds & Obtainium",
    "title": "The config format",
    "content": "An Obtainium app configuration is a flat JSON object. Four keys are required — id (Android package name), url (the GitHub repo, which is what selects the source), author, and name. Everything else goes in additionalSettings, a JSON string nested inside the JSON, so its quotes and backslashes are escaped one extra level. Any key you omit takes its default. The same object travels in three shapes: . | Shape | Format | Used for | . | Import/export file | {\"apps\":[…],\"settings\":null} | Import/Export → Obtainium import | . | Deep link | obtainium://app/<percent-encoded JSON> | one-tap add with settings baked in | . | Config-site entry | {\"configs\":[…],\"icon\",\"categories\",\"description\"} | PRs to apps.obtainium.imranr.dev | . obtainium://add/<url> only prefills the Add-App page; obtainium://app/… is what carries settings. Wrapping a link as https://apps.obtainium.imranr.dev/redirect.html?r=obtainium://app/… keeps it clickable where a custom scheme wouldn’t linkify. Obtainium keys apps by package name, so the two stable flavors cannot coexist as separate entries — the config-site submission expresses them as alternate configs with an altLabel each. See obtainium/README.md for the full key reference and the submission checklist. ",
    "url": "/Meshtastic-Android/main/en/developer/test-builds.html#the-config-format",
    
    "relUrl": "/en/developer/test-builds.html#the-config-format"
  },"5345": {
    "doc": "Test Builds & Obtainium",
    "title": "Notes",
    "content": ". | Play Protect may interrupt the install with “App scan recommended — Play Protect hasn’t seen this app before,” offering Scan app or Don’t install app. Scan app uploads the APK to Google. Declining cancels the install, so on a phone with Play Services you’ll need to allow the scan, or install with adb install instead. This showed up for a debug-signed snapshot but not for a release-signed build. | Obtainium’s first launch shows two full-screen dialogs (a welcome note and a Play-certification note). They swallow an incoming obtainium:// link, so dismiss them before using a one-tap link. | Track without installing: turn on Track-only to get update notifications without Obtainium downloading anything. | Snapshot filenames carry the versionCode so that a moving tag, which reuses the same release and asset URLs forever, still produces a distinguishable asset on every build. | . ",
    "url": "/Meshtastic-Android/main/en/developer/test-builds.html#notes",
    
    "relUrl": "/en/developer/test-builds.html#notes"
  },"5346": {
    "doc": "Test Builds & Obtainium",
    "title": "Test Builds & Obtainium",
    "content": " ",
    "url": "/Meshtastic-Android/main/en/developer/test-builds.html",
    
    "relUrl": "/en/developer/test-builds.html"
  },"5347": {
    "doc": "Testing",
    "title": "Testing",
    "content": "Testing strategy and practices for the Meshtastic KMP project. ",
    "url": "/Meshtastic-Android/main/en/developer/testing.html",
    
    "relUrl": "/en/developer/testing.html"
  },"5348": {
    "doc": "Testing",
    "title": "Test categories",
    "content": "KMP unit tests (commonTest) . Shared tests that run on all platforms: ./gradlew allTests . | Business logic tests | Data model validation | Search/ranking algorithm tests | Route serialization tests | . Android host tests . Android-specific tests that run on JVM: ./gradlew test . | ViewModel tests | Repository tests with Room fakes | Android-specific integration tests | . Compose UI tests . Compose Multiplatform UI test framework: . @Test fun myScreenTest() = runComposeUiTest { setContent { MyScreen() } onNodeWithText(\"Expected\").assertIsDisplayed() } . Located in commonTest or jvmTest source sets. Screenshot tests . Uses Android Gradle Plugin’s native (layoutlib) screenshot testing framework, split across two modules: . | \u00000\u0000 — the visual-regression gate. CI runs validateDebugScreenshotTest on it; reframing one of these baselines is a real diff to review. Holds atomic, dual-purpose components. | \u00000\u0000 — generate-only, not validated in CI. Holds doc-framed compositions whose framing is tuned for the docs site, so reframing a doc image never churns the regression gate. | ./gradlew :screenshot-tests:updateDebugScreenshotTest # record regression goldens ./gradlew :screenshot-tests:validateDebugScreenshotTest # compare against goldens (CI gate) ./gradlew :docs-screenshots:updateDebugScreenshotTest # record doc-framed composition images ./gradlew :screenshot-tests:copyDocsScreenshots # copy doc images from BOTH modules into docs/assets . Rendering is host-deterministic here (layoutlib): a local update produces references byte-identical to CI, so locally-recorded goldens pass validate. See docs/assets/screenshots/README.md for which module a new screenshot belongs in. Marketing screenshots . The store-listing screenshots (Play, F-Droid, IzzyOnDroid, and the desktop app’s Flathub listing) are generated too, by a third module: \u00000\u0000 is a plain JVM program, not a test. It renders the app’s own commonMain screens offscreen with Compose Desktop’s ImageComposeScene over one sample mesh and captures the real MapLibre map (basemap plus the app’s node chips) through maplibre-compose’s MapSnapshotter. Every shot is the raw screen, as Play’s listing rules require - no device frame, no caption banner - at one size per form factor. It has no tests, so ./gradlew test never touches it, and CI never runs it. The one command: ./gradlew :marketing-screenshots:updateMarketingScreenshots . That writes 1_messages.png … 5_channels.png into five folders under fastlane/metadata/android/en-US/images/, and meshtastic-desktop-01-nodes.png … meshtastic-desktop-05-settings.png into the Flathub folder, reproducibly - the screens are byte-identical between runs; a wide map can differ by a few antialiased label-edge pixels, see below: . | Folder | Size | Window | Uploaded by | . | phoneScreenshots/ | 1080×1920 @2.5x | 432×768 dp, compact: bottom navigation bar | fastlane supply | . | sevenInchScreenshots/ | 1080×1920 @1.8x | 600×1067 dp, medium: navigation rail, one pane | fastlane supply | . | tenInchScreenshots/ | 2560×1440 @2x | 1280×720 dp, expanded: rail, list beside detail | fastlane supply | . | chromebookScreenshots/ | 1920×1080 @1x | expanded | hand, in Play Console | . | xrScreenshots/ | 1920×1200 @1x (8:5) | expanded | hand, in Play Console | . | desktopApp/packaging/linux/screenshots/ | 1280×800 @1x (16:10) | expanded: rail, list beside detail | Flathub, through metainfo.xml | . The screens are composed in the app’s own adaptive shell (NavigationSuiteScaffold, ListDetailPaneScaffold, AdaptiveTwoPane) with the same window-class calculations the app uses, so the form factors are data - a size, a density, a shot list and an output folder in FormFactor.kt - and every layout difference between them is the app’s own. Neither fastlane supply nor the Play Developer API has a Chromebook or XR slot, so those two folders are ignored by supply and F-Droid and uploaded by hand. The desktop set lists nodes, messages, map, connections and settings, the five <screenshot> entries in desktopApp/packaging/linux/org.meshtastic.MeshtasticDesktop.metainfo.xml, whose <image> URLs are raw.githubusercontent.com links pinned to a commit: regenerating it is two commits, first the PNGs (with the generator and doc changes that produced them), then the metainfo pointing its URLs at that first commit’s full SHA, because the URLs can’t name a commit that contains them. After the PR squash-merges, re-pin them to the merge commit: a squash leaves the branch commits out of main, and a deleted branch leaves the SHA they named unreferenced and eventually collectable, which would blank the Flathub listing. The basemap is the app’s default Liberty style, labels included. MapLibre packs glyphs into an atlas in tile-arrival order, so on the wide layouts a label’s antialiased edge can land one level off between generations - a dozen pixels, invisible; the generator captures from fresh runtimes until two agree and warns if they never do, and a regenerated wide map may not cmp the previous one. Commit whichever run produced it. Locales: -PmarketingLocales=en-US,de-DE renders each locale in turn after switching the JVM default locale, the same switch the desktop app makes, so the app’s strings, numbers and dates follow. Only en-US goes into fastlane/ - everything there is read straight from git by F-Droid and IzzyOnDroid - and every other locale lands in marketing-screenshots/build/marketing-screenshots/<locale>/images/ in the same layout, ready for a later supply run, with the desktop set beside it in <locale>/desktop/. The sample prose (the thread, the conversation previews, the framed variant’s captions) is in marketing-screenshots/src/main/composeResources/values/strings.xml, which crowdin.yml’s first rule already globs like every other composeResources strings file, so a translated conversation needs no configuration change; until Crowdin fills a locale’s values-xx/strings.xml, that locale’s chat text stays English while the UI around it is translated. -PmarketingFramed=true also writes the framed 1242×2484 phone variants - bezel, drawn status bar and a caption banner - under marketing-screenshots/build/marketing-screenshots/framed/<locale>/, for the website and social posts. They never go into fastlane/. The map needs a Vulkan loader the JVM can find. On a stock Ubuntu nothing is required; in a Nix dev shell, which replaces LD_LIBRARY_PATH on entry, pass -PmarketingLibraryPath=/usr/lib/x86_64-linux-gnu (the system loader plus the GPU’s ICD). No display is needed or used. Baseline Profile / startup performance . The :baselineprofile module (#5735) generates a Baseline Profile for :androidApp, AOT-compiling the hot startup paths so ART doesn’t pay the JIT cost on first launch. It targets the google flavor (the variant most users run). The Macrobenchmark generator (BaselineProfileGenerator) and the before/after benchmark (StartupBenchmark) live in baselineprofile/src/main/kotlin/org/meshtastic/baselineprofile/. Both run on a device/emulator: ./gradlew :androidApp:generateGoogleReleaseBaselineProfile # Generate the profile (commit the output) ./gradlew :androidApp:benchmarkGoogleReleaseBaselineProfile # Quantify the cold-start win . The generated profile is merged into androidApp/src/googleRelease/generated/baselineProfiles/ and packaged into release builds via androidx.profileinstaller. ℹ️ Note: The journey covers cold start only (launch → first frame), because CI has no paired node. Post-connection screens (node list, map, message thread) aren’t yet AOT-compiled. Extending the journey past cold start needs a fake transport or a connected node wired into the harness. ",
    "url": "/Meshtastic-Android/main/en/developer/testing.html#test-categories",
    
    "relUrl": "/en/developer/testing.html#test-categories"
  },"5349": {
    "doc": "Testing",
    "title": "Test organization",
    "content": "feature/my-feature/src/ ├── commonTest/kotlin/org/meshtastic/feature/myfeature/ │ ├── MyBusinessLogicTest.kt │ └── MyModelTest.kt └── jvmTest/kotlin/org/meshtastic/feature/myfeature/ └── MyDesktopSpecificTest.kt . ",
    "url": "/Meshtastic-Android/main/en/developer/testing.html#test-organization",
    
    "relUrl": "/en/developer/testing.html#test-organization"
  },"5350": {
    "doc": "Testing",
    "title": "Testing guidelines",
    "content": "DO . | Write tests in commonTest when possible (runs everywhere) | Test business logic independently from UI | Use fakes/stubs instead of mocks where practical | Test edge cases: empty states, error states, boundary values | Test deep link routing in DeepLinkRouterTest | Keep tests fast — no network, no disk I/O in unit tests | . DON’T . | Don’t test framework behavior (Compose internals, Room queries) | Don’t create tests that depend on other feature modules | Don’t use Thread.sleep — use coroutine test dispatchers | Don’t rely on test execution order | . ",
    "url": "/Meshtastic-Android/main/en/developer/testing.html#testing-guidelines",
    
    "relUrl": "/en/developer/testing.html#testing-guidelines"
  },"5351": {
    "doc": "Testing",
    "title": "Running tests",
    "content": "# All KMP tests ./gradlew allTests # Specific module ./gradlew :feature:docs:allTests # Code quality ./gradlew spotlessCheck detekt # Full verification ./gradlew spotlessCheck detekt kmpSmokeCompile test allTests . ",
    "url": "/Meshtastic-Android/main/en/developer/testing.html#running-tests",
    
    "relUrl": "/en/developer/testing.html#running-tests"
  },"5352": {
    "doc": "Testing",
    "title": "CI integration",
    "content": "Tests run automatically on: . | Pull request creation/update | Push to main | Pre-release validation | . Single-runner jobs in reusable-check.yml run on ubuntu-26.04 with JDK 25 and Gradle caching. Two jobs use a matrix: test-shards splits into shard-core, shard-feature and shard-app, and build-desktop runs across macOS, Windows and Linux, still pinned to ubuntu-24.04/-arm. Flatpak verification is its own workflow, not a job here. The ARM (ubuntu-26.04-arm) and container-backed ubuntu-slim runners carry the lightweight utility workflows — see .skills/testing-ci/SKILL.md for the four-tier rule, which still quotes the older labels. ",
    "url": "/Meshtastic-Android/main/en/developer/testing.html#ci-integration",
    
    "relUrl": "/en/developer/testing.html#ci-integration"
  },"5353": {
    "doc": "Translate the App",
    "title": "Translate the App",
    "content": "The app and its in-app docs are translated on Crowdin — this page shows how to contribute. The app uses Crowdin to manage community translations for both the user interface and in-app documentation. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/translate.html",
    
    "relUrl": "/sk-rSK/user/translate.html"
  },"5354": {
    "doc": "Translate the App",
    "title": "What Gets Translated",
    "content": "| Resource | Source Location | Notes | . | UI strings | core/resources/src/commonMain/composeResources/values/strings.xml | Buttons, labels, messages, and all user-visible text | . | User Guide pages | docs/en/user/*.md | In-app documentation shown in Help & Documentation | . | Fastlane metadata | fastlane/metadata/android/en-US/ | Google Play listing title, description, and changelogs | . ℹ️ Note: Developer Guide pages are English-only. Code-focused documentation targeting contributors is not translated. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/translate.html#what-gets-translated",
    
    "relUrl": "/sk-rSK/user/translate.html#what-gets-translated"
  },"5355": {
    "doc": "Translate the App",
    "title": "How to Contribute",
    "content": ". | Visit the Crowdin project. Open the Meshtastic Android Crowdin project and sign in or create a free account. | Choose your language. Select an existing language or request a new one by opening a GitHub issue. | Translate strings. Crowdin shows the English source on the left and your translation on the right. Translate each string and save. | Review context. Many strings include screenshots or context comments — check these to understand where the text appears in the app. A scheduled job pulls approved translations from Crowdin and opens a pull request; they ship once a maintainer merges it and a new build goes out. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/translate.html#how-to-contribute",
    
    "relUrl": "/sk-rSK/user/translate.html#how-to-contribute"
  },"5356": {
    "doc": "Translate the App",
    "title": "Adding a New Language",
    "content": "If your language is not yet listed on Crowdin: . | Open an issue on GitHub requesting the new locale. | A maintainer will add the language to Crowdin and configure crowdin.yml. | Once added, you can begin translating immediately. | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/translate.html#adding-a-new-language",
    
    "relUrl": "/sk-rSK/user/translate.html#adding-a-new-language"
  },"5357": {
    "doc": "Translate the App",
    "title": "How Translations Are Organized",
    "content": "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/ ├── en/user/ ← English source (default) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← French (France) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← German (Germany) │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. The app automatically selects the correct locale based on your phone’s Language & Region settings. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/translate.html#how-translations-are-organized",
    
    "relUrl": "/sk-rSK/user/translate.html#how-translations-are-organized"
  },"5358": {
    "doc": "Translate the App",
    "title": "Translation Guidelines",
    "content": ". | 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 phone’s language and open the app to see how translations look in context. | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/translate.html#translation-guidelines",
    
    "relUrl": "/sk-rSK/user/translate.html#translation-guidelines"
  },"5359": {
    "doc": "Translate the App",
    "title": "Questions?",
    "content": "If you have questions about a specific string’s context or need help getting started, open a discussion on the Meshtastic GitHub Discussions page. Thank you for helping expand the reach of Meshtastic. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/translate.html#questions",
    
    "relUrl": "/sk-rSK/user/translate.html#questions"
  },"5360": {
    "doc": "Translate the App",
    "title": "Related Topics",
    "content": ". | Units & Locale — how the app picks number, date, and unit formats for your region | Help & Documentation — the in-app docs browser these pages are published to | Onboarding — where a new user first meets the translated strings | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/translate.html#related-topics",
    
    "relUrl": "/sk-rSK/user/translate.html#related-topics"
  },"5361": {
    "doc": "Translate the App",
    "title": "Translate the App",
    "content": "The app and its in-app docs are translated on Crowdin — this page shows how to contribute. The app uses Crowdin to manage community translations for both the user interface and in-app documentation. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/translate.html",
    
    "relUrl": "/be-rBY/user/translate.html"
  },"5362": {
    "doc": "Translate the App",
    "title": "What Gets Translated",
    "content": "| Resource | Source Location | Notes | . | UI strings | core/resources/src/commonMain/composeResources/values/strings.xml | Buttons, labels, messages, and all user-visible text | . | User Guide pages | docs/en/user/*.md | In-app documentation shown in Help & Documentation | . | Fastlane metadata | fastlane/metadata/android/en-US/ | Google Play listing title, description, and changelogs | . ℹ️ Note: Developer Guide pages are English-only. Code-focused documentation targeting contributors is not translated. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/translate.html#what-gets-translated",
    
    "relUrl": "/be-rBY/user/translate.html#what-gets-translated"
  },"5363": {
    "doc": "Translate the App",
    "title": "How to Contribute",
    "content": ". | Visit the Crowdin project. Open the Meshtastic Android Crowdin project and sign in or create a free account. | Choose your language. Select an existing language or request a new one by opening a GitHub issue. | Translate strings. Crowdin shows the English source on the left and your translation on the right. Translate each string and save. | Review context. Many strings include screenshots or context comments — check these to understand where the text appears in the app. A scheduled job pulls approved translations from Crowdin and opens a pull request; they ship once a maintainer merges it and a new build goes out. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/translate.html#how-to-contribute",
    
    "relUrl": "/be-rBY/user/translate.html#how-to-contribute"
  },"5364": {
    "doc": "Translate the App",
    "title": "Adding a New Language",
    "content": "If your language is not yet listed on Crowdin: . | Open an issue on GitHub requesting the new locale. | A maintainer will add the language to Crowdin and configure crowdin.yml. | Once added, you can begin translating immediately. | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/translate.html#adding-a-new-language",
    
    "relUrl": "/be-rBY/user/translate.html#adding-a-new-language"
  },"5365": {
    "doc": "Translate the App",
    "title": "How Translations Are Organized",
    "content": "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/ ├── en/user/ ← English source (default) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← French (France) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← German (Germany) │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. The app automatically selects the correct locale based on your phone’s Language & Region settings. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/translate.html#how-translations-are-organized",
    
    "relUrl": "/be-rBY/user/translate.html#how-translations-are-organized"
  },"5366": {
    "doc": "Translate the App",
    "title": "Translation Guidelines",
    "content": ". | 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 phone’s language and open the app to see how translations look in context. | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/translate.html#translation-guidelines",
    
    "relUrl": "/be-rBY/user/translate.html#translation-guidelines"
  },"5367": {
    "doc": "Translate the App",
    "title": "Questions?",
    "content": "If you have questions about a specific string’s context or need help getting started, open a discussion on the Meshtastic GitHub Discussions page. Thank you for helping expand the reach of Meshtastic. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/translate.html#questions",
    
    "relUrl": "/be-rBY/user/translate.html#questions"
  },"5368": {
    "doc": "Translate the App",
    "title": "Related Topics",
    "content": ". | Units & Locale — how the app picks number, date, and unit formats for your region | Help & Documentation — the in-app docs browser these pages are published to | Onboarding — where a new user first meets the translated strings | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/translate.html#related-topics",
    
    "relUrl": "/be-rBY/user/translate.html#related-topics"
  },"5369": {
    "doc": "Translate the App",
    "title": "Translate the App",
    "content": "The app and its in-app docs are translated on Crowdin — this page shows how to contribute. The app uses Crowdin to manage community translations for both the user interface and in-app documentation. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/translate.html",
    
    "relUrl": "/it-rIT/user/translate.html"
  },"5370": {
    "doc": "Translate the App",
    "title": "What Gets Translated",
    "content": "| Resource | Source Location | Note | . | UI strings | core/resources/src/commonMain/composeResources/values/strings.xml | Buttons, labels, messages, and all user-visible text | . | User Guide pages | docs/en/user/*.md | In-app documentation shown in Help & Documentation | . | Fastlane metadata | fastlane/metadata/android/en-US/ | Google Play listing title, description, and changelogs | . ℹ️ Note: Developer Guide pages are English-only. Code-focused documentation targeting contributors is not translated. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/translate.html#what-gets-translated",
    
    "relUrl": "/it-rIT/user/translate.html#what-gets-translated"
  },"5371": {
    "doc": "Translate the App",
    "title": "How to Contribute",
    "content": ". | Visit the Crowdin project. Open the Meshtastic Android Crowdin project and sign in or create a free account. | Choose your language. Select an existing language or request a new one by opening a GitHub issue. | Translate strings. Crowdin shows the English source on the left and your translation on the right. Translate each string and save. | Review context. Many strings include screenshots or context comments — check these to understand where the text appears in the app. A scheduled job pulls approved translations from Crowdin and opens a pull request; they ship once a maintainer merges it and a new build goes out. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/translate.html#how-to-contribute",
    
    "relUrl": "/it-rIT/user/translate.html#how-to-contribute"
  },"5372": {
    "doc": "Translate the App",
    "title": "Adding a New Language",
    "content": "If your language is not yet listed on Crowdin: . | Open an issue on GitHub requesting the new locale. | A maintainer will add the language to Crowdin and configure crowdin.yml. | Once added, you can begin translating immediately. | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/translate.html#adding-a-new-language",
    
    "relUrl": "/it-rIT/user/translate.html#adding-a-new-language"
  },"5373": {
    "doc": "Translate the App",
    "title": "How Translations Are Organized",
    "content": "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/ ├── en/user/ ← English source (default) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← French (France) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← German (Germany) │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. The app automatically selects the correct locale based on your phone’s Language & Region settings. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/translate.html#how-translations-are-organized",
    
    "relUrl": "/it-rIT/user/translate.html#how-translations-are-organized"
  },"5374": {
    "doc": "Translate the App",
    "title": "Translation Guidelines",
    "content": ". | 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 phone’s language and open the app to see how translations look in context. | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/translate.html#translation-guidelines",
    
    "relUrl": "/it-rIT/user/translate.html#translation-guidelines"
  },"5375": {
    "doc": "Translate the App",
    "title": "Questions?",
    "content": "If you have questions about a specific string’s context or need help getting started, open a discussion on the Meshtastic GitHub Discussions page. Thank you for helping expand the reach of Meshtastic. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/translate.html#questions",
    
    "relUrl": "/it-rIT/user/translate.html#questions"
  },"5376": {
    "doc": "Translate the App",
    "title": "Related Topics",
    "content": ". | Units & Locale — how the app picks number, date, and unit formats for your region | Help & Documentation — the in-app docs browser these pages are published to | Onboarding — where a new user first meets the translated strings | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/translate.html#related-topics",
    
    "relUrl": "/it-rIT/user/translate.html#related-topics"
  },"5377": {
    "doc": "Translate the App",
    "title": "Translate the App",
    "content": "The app and its in-app docs are translated on Crowdin — this page shows how to contribute. The app uses Crowdin to manage community translations for both the user interface and in-app documentation. ",
    "url": "/Meshtastic-Android/main/es-rES/user/translate.html",
    
    "relUrl": "/es-rES/user/translate.html"
  },"5378": {
    "doc": "Translate the App",
    "title": "What Gets Translated",
    "content": "| Resource | Source Location | Notas | . | UI strings | core/resources/src/commonMain/composeResources/values/strings.xml | Buttons, labels, messages, and all user-visible text | . | User Guide pages | docs/en/user/*.md | In-app documentation shown in Help & Documentation | . | Fastlane metadata | fastlane/metadata/android/en-US/ | Google Play listing title, description, and changelogs | . ℹ️ Note: Developer Guide pages are English-only. Code-focused documentation targeting contributors is not translated. ",
    "url": "/Meshtastic-Android/main/es-rES/user/translate.html#what-gets-translated",
    
    "relUrl": "/es-rES/user/translate.html#what-gets-translated"
  },"5379": {
    "doc": "Translate the App",
    "title": "How to Contribute",
    "content": ". | Visit the Crowdin project. Open the Meshtastic Android Crowdin project and sign in or create a free account. | Choose your language. Select an existing language or request a new one by opening a GitHub issue. | Translate strings. Crowdin shows the English source on the left and your translation on the right. Translate each string and save. | Review context. Many strings include screenshots or context comments — check these to understand where the text appears in the app. A scheduled job pulls approved translations from Crowdin and opens a pull request; they ship once a maintainer merges it and a new build goes out. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/es-rES/user/translate.html#how-to-contribute",
    
    "relUrl": "/es-rES/user/translate.html#how-to-contribute"
  },"5380": {
    "doc": "Translate the App",
    "title": "Adding a New Language",
    "content": "If your language is not yet listed on Crowdin: . | Open an issue on GitHub requesting the new locale. | A maintainer will add the language to Crowdin and configure crowdin.yml. | Once added, you can begin translating immediately. | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/translate.html#adding-a-new-language",
    
    "relUrl": "/es-rES/user/translate.html#adding-a-new-language"
  },"5381": {
    "doc": "Translate the App",
    "title": "How Translations Are Organized",
    "content": "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/ ├── en/user/ ← English source (default) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← French (France) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← German (Germany) │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. The app automatically selects the correct locale based on your phone’s Language & Region settings. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/es-rES/user/translate.html#how-translations-are-organized",
    
    "relUrl": "/es-rES/user/translate.html#how-translations-are-organized"
  },"5382": {
    "doc": "Translate the App",
    "title": "Translation Guidelines",
    "content": ". | 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 phone’s language and open the app to see how translations look in context. | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/translate.html#translation-guidelines",
    
    "relUrl": "/es-rES/user/translate.html#translation-guidelines"
  },"5383": {
    "doc": "Translate the App",
    "title": "Questions?",
    "content": "If you have questions about a specific string’s context or need help getting started, open a discussion on the Meshtastic GitHub Discussions page. Thank you for helping expand the reach of Meshtastic. ",
    "url": "/Meshtastic-Android/main/es-rES/user/translate.html#questions",
    
    "relUrl": "/es-rES/user/translate.html#questions"
  },"5384": {
    "doc": "Translate the App",
    "title": "Related Topics",
    "content": ". | Units & Locale — how the app picks number, date, and unit formats for your region | Help & Documentation — the in-app docs browser these pages are published to | Onboarding — where a new user first meets the translated strings | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/translate.html#related-topics",
    
    "relUrl": "/es-rES/user/translate.html#related-topics"
  },"5385": {
    "doc": "Translate the App",
    "title": "Translate the App",
    "content": "The app and its in-app docs are translated on Crowdin — this page shows how to contribute. The app uses Crowdin to manage community translations for both the user interface and in-app documentation. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/translate.html",
    
    "relUrl": "/sl-rSI/user/translate.html"
  },"5386": {
    "doc": "Translate the App",
    "title": "What Gets Translated",
    "content": "| Resource | Source Location | Notes | . | UI strings | core/resources/src/commonMain/composeResources/values/strings.xml | Buttons, labels, messages, and all user-visible text | . | User Guide pages | docs/en/user/*.md | In-app documentation shown in Help & Documentation | . | Fastlane metadata | fastlane/metadata/android/en-US/ | Google Play listing title, description, and changelogs | . ℹ️ Note: Developer Guide pages are English-only. Code-focused documentation targeting contributors is not translated. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/translate.html#what-gets-translated",
    
    "relUrl": "/sl-rSI/user/translate.html#what-gets-translated"
  },"5387": {
    "doc": "Translate the App",
    "title": "How to Contribute",
    "content": ". | Visit the Crowdin project. Open the Meshtastic Android Crowdin project and sign in or create a free account. | Choose your language. Select an existing language or request a new one by opening a GitHub issue. | Translate strings. Crowdin shows the English source on the left and your translation on the right. Translate each string and save. | Review context. Many strings include screenshots or context comments — check these to understand where the text appears in the app. A scheduled job pulls approved translations from Crowdin and opens a pull request; they ship once a maintainer merges it and a new build goes out. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/translate.html#how-to-contribute",
    
    "relUrl": "/sl-rSI/user/translate.html#how-to-contribute"
  },"5388": {
    "doc": "Translate the App",
    "title": "Adding a New Language",
    "content": "If your language is not yet listed on Crowdin: . | Open an issue on GitHub requesting the new locale. | A maintainer will add the language to Crowdin and configure crowdin.yml. | Once added, you can begin translating immediately. | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/translate.html#adding-a-new-language",
    
    "relUrl": "/sl-rSI/user/translate.html#adding-a-new-language"
  },"5389": {
    "doc": "Translate the App",
    "title": "How Translations Are Organized",
    "content": "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/ ├── en/user/ ← English source (default) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← French (France) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← German (Germany) │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. The app automatically selects the correct locale based on your phone’s Language & Region settings. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/translate.html#how-translations-are-organized",
    
    "relUrl": "/sl-rSI/user/translate.html#how-translations-are-organized"
  },"5390": {
    "doc": "Translate the App",
    "title": "Translation Guidelines",
    "content": ". | 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 phone’s language and open the app to see how translations look in context. | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/translate.html#translation-guidelines",
    
    "relUrl": "/sl-rSI/user/translate.html#translation-guidelines"
  },"5391": {
    "doc": "Translate the App",
    "title": "Questions?",
    "content": "If you have questions about a specific string’s context or need help getting started, open a discussion on the Meshtastic GitHub Discussions page. Thank you for helping expand the reach of Meshtastic. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/translate.html#questions",
    
    "relUrl": "/sl-rSI/user/translate.html#questions"
  },"5392": {
    "doc": "Translate the App",
    "title": "Related Topics",
    "content": ". | Units & Locale — how the app picks number, date, and unit formats for your region | Help & Documentation — the in-app docs browser these pages are published to | Onboarding — where a new user first meets the translated strings | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/translate.html#related-topics",
    
    "relUrl": "/sl-rSI/user/translate.html#related-topics"
  },"5393": {
    "doc": "Translate the App",
    "title": "Translate the App",
    "content": "The app and its in-app docs are translated on Crowdin — this page shows how to contribute. The app uses Crowdin to manage community translations for both the user interface and in-app documentation. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/translate.html",
    
    "relUrl": "/no-rNO/user/translate.html"
  },"5394": {
    "doc": "Translate the App",
    "title": "What Gets Translated",
    "content": "| Resource | Source Location | Notes | . | UI strings | core/resources/src/commonMain/composeResources/values/strings.xml | Buttons, labels, messages, and all user-visible text | . | User Guide pages | docs/en/user/*.md | In-app documentation shown in Help & Documentation | . | Fastlane metadata | fastlane/metadata/android/en-US/ | Google Play listing title, description, and changelogs | . ℹ️ Note: Developer Guide pages are English-only. Code-focused documentation targeting contributors is not translated. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/translate.html#what-gets-translated",
    
    "relUrl": "/no-rNO/user/translate.html#what-gets-translated"
  },"5395": {
    "doc": "Translate the App",
    "title": "How to Contribute",
    "content": ". | Visit the Crowdin project. Open the Meshtastic Android Crowdin project and sign in or create a free account. | Choose your language. Select an existing language or request a new one by opening a GitHub issue. | Translate strings. Crowdin shows the English source on the left and your translation on the right. Translate each string and save. | Review context. Many strings include screenshots or context comments — check these to understand where the text appears in the app. A scheduled job pulls approved translations from Crowdin and opens a pull request; they ship once a maintainer merges it and a new build goes out. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/translate.html#how-to-contribute",
    
    "relUrl": "/no-rNO/user/translate.html#how-to-contribute"
  },"5396": {
    "doc": "Translate the App",
    "title": "Adding a New Language",
    "content": "If your language is not yet listed on Crowdin: . | Open an issue on GitHub requesting the new locale. | A maintainer will add the language to Crowdin and configure crowdin.yml. | Once added, you can begin translating immediately. | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/translate.html#adding-a-new-language",
    
    "relUrl": "/no-rNO/user/translate.html#adding-a-new-language"
  },"5397": {
    "doc": "Translate the App",
    "title": "How Translations Are Organized",
    "content": "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/ ├── en/user/ ← English source (default) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← French (France) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← German (Germany) │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. The app automatically selects the correct locale based on your phone’s Language & Region settings. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/translate.html#how-translations-are-organized",
    
    "relUrl": "/no-rNO/user/translate.html#how-translations-are-organized"
  },"5398": {
    "doc": "Translate the App",
    "title": "Translation Guidelines",
    "content": ". | 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 phone’s language and open the app to see how translations look in context. | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/translate.html#translation-guidelines",
    
    "relUrl": "/no-rNO/user/translate.html#translation-guidelines"
  },"5399": {
    "doc": "Translate the App",
    "title": "Questions?",
    "content": "If you have questions about a specific string’s context or need help getting started, open a discussion on the Meshtastic GitHub Discussions page. Thank you for helping expand the reach of Meshtastic. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/translate.html#questions",
    
    "relUrl": "/no-rNO/user/translate.html#questions"
  },"5400": {
    "doc": "Translate the App",
    "title": "Related Topics",
    "content": ". | Units & Locale — how the app picks number, date, and unit formats for your region | Help & Documentation — the in-app docs browser these pages are published to | Onboarding — where a new user first meets the translated strings | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/translate.html#related-topics",
    
    "relUrl": "/no-rNO/user/translate.html#related-topics"
  },"5401": {
    "doc": "Translate the App",
    "title": "Translate the App",
    "content": "The app and its in-app docs are translated on Crowdin — this page shows how to contribute. The app uses Crowdin to manage community translations for both the user interface and in-app documentation. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/translate.html",
    
    "relUrl": "/hu-rHU/user/translate.html"
  },"5402": {
    "doc": "Translate the App",
    "title": "What Gets Translated",
    "content": "| Resource | Source Location | Jegyzetek | . | UI strings | core/resources/src/commonMain/composeResources/values/strings.xml | Buttons, labels, messages, and all user-visible text | . | User Guide pages | docs/en/user/*.md | In-app documentation shown in Help & Documentation | . | Fastlane metadata | fastlane/metadata/android/en-US/ | Google Play listing title, description, and changelogs | . ℹ️ Note: Developer Guide pages are English-only. Code-focused documentation targeting contributors is not translated. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/translate.html#what-gets-translated",
    
    "relUrl": "/hu-rHU/user/translate.html#what-gets-translated"
  },"5403": {
    "doc": "Translate the App",
    "title": "How to Contribute",
    "content": ". | Visit the Crowdin project. Open the Meshtastic Android Crowdin project and sign in or create a free account. | Choose your language. Select an existing language or request a new one by opening a GitHub issue. | Translate strings. Crowdin shows the English source on the left and your translation on the right. Translate each string and save. | Review context. Many strings include screenshots or context comments — check these to understand where the text appears in the app. A scheduled job pulls approved translations from Crowdin and opens a pull request; they ship once a maintainer merges it and a new build goes out. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/translate.html#how-to-contribute",
    
    "relUrl": "/hu-rHU/user/translate.html#how-to-contribute"
  },"5404": {
    "doc": "Translate the App",
    "title": "Adding a New Language",
    "content": "If your language is not yet listed on Crowdin: . | Open an issue on GitHub requesting the new locale. | A maintainer will add the language to Crowdin and configure crowdin.yml. | Once added, you can begin translating immediately. | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/translate.html#adding-a-new-language",
    
    "relUrl": "/hu-rHU/user/translate.html#adding-a-new-language"
  },"5405": {
    "doc": "Translate the App",
    "title": "How Translations Are Organized",
    "content": "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/ ├── en/user/ ← English source (default) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← French (France) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← German (Germany) │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. The app automatically selects the correct locale based on your phone’s Language & Region settings. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/translate.html#how-translations-are-organized",
    
    "relUrl": "/hu-rHU/user/translate.html#how-translations-are-organized"
  },"5406": {
    "doc": "Translate the App",
    "title": "Translation Guidelines",
    "content": ". | 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 phone’s language and open the app to see how translations look in context. | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/translate.html#translation-guidelines",
    
    "relUrl": "/hu-rHU/user/translate.html#translation-guidelines"
  },"5407": {
    "doc": "Translate the App",
    "title": "Questions?",
    "content": "If you have questions about a specific string’s context or need help getting started, open a discussion on the Meshtastic GitHub Discussions page. Thank you for helping expand the reach of Meshtastic. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/translate.html#questions",
    
    "relUrl": "/hu-rHU/user/translate.html#questions"
  },"5408": {
    "doc": "Translate the App",
    "title": "Related Topics",
    "content": ". | Units & Locale — how the app picks number, date, and unit formats for your region | Help & Documentation — the in-app docs browser these pages are published to | Onboarding — where a new user first meets the translated strings | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/translate.html#related-topics",
    
    "relUrl": "/hu-rHU/user/translate.html#related-topics"
  },"5409": {
    "doc": "Перевод приложения",
    "title": "Перевод приложения",
    "content": "Приложение и его встроенные документы переведены на Crowdin — на этой странице показано, как внести свой вклад. Приложение использует Crowdin для управления переводами сообщества как для пользовательского интерфейса, так и для документации в приложении. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/translate.html",
    
    "relUrl": "/ru-rRU/user/translate.html"
  },"5410": {
    "doc": "Перевод приложения",
    "title": "Что переводится",
    "content": "| Ресурс | Исходное местоположение | Заметки | . | Строки интерфейса | core/resources/src/commonMain/composeResources/values/strings.xml | Кнопки, ярлыки, сообщения и весь видимый пользователю текст | . | Страницы руководства пользователя | docs/en/user/*.md | Встроенная документация, отображаемая в разделе «Справка и документация» | . | Метаданные Fastlane | fastlane/metadata/android/en-US/ | Название, описание и журналы изменений в Google Play | . ℹ️ Примечание: Страницы Руководства разработчика только на английском. Документация, ориентированная на код и для участников, не переводится. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/translate.html#%D1%87%D1%82%D0%BE-%D0%BF%D0%B5%D1%80%D0%B5%D0%B2%D0%BE%D0%B4%D0%B8%D1%82%D1%81%D1%8F",
    
    "relUrl": "/ru-rRU/user/translate.html#что-переводится"
  },"5411": {
    "doc": "Перевод приложения",
    "title": "Как внести вклад",
    "content": ". | Посетите проект Crowdin. Откройте проект Meshtastic Android на Crowdin и войдите в систему или создайте бесплатный аккаунт. | Выберите свой язык. Выберите существующий язык или запросите новый, открыв GitHub issue. | Переводите строки. Crowdin показывает английский исходный текст слева и ваш перевод справа. Переведите каждую строку и сохраните. | Проверьте контекст. Многие строки содержат скриншоты или комментарии о контексте — проверьте их, чтобы понять, где данный текст появляется в приложении. Запланированная задача выгружает одобренные переводы из Crowdin и открывает пулл-реквест; они публикуются, как только мейнтейнер его смержит и выйдет новая сборка. | . 💡 Совет: Сохраняйте переводы краткими. Строки интерфейса часто появляются на кнопках, фишках или узких колонках. Если перевод значительно длиннее английского оригинала, рассмотрите возможность сокращения, чтобы смысл оставался понятным. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/translate.html#%D0%BA%D0%B0%D0%BA-%D0%B2%D0%BD%D0%B5%D1%81%D1%82%D0%B8-%D0%B2%D0%BA%D0%BB%D0%B0%D0%B4",
    
    "relUrl": "/ru-rRU/user/translate.html#как-внести-вклад"
  },"5412": {
    "doc": "Перевод приложения",
    "title": "Добавление нового языка",
    "content": "Если твоего языка еще нет в списке на Crowdin: . | Открой задачу на GitHub для запроса нового языка. | Поддерживающий добавит язык в Crowdin и настроит crowdin.yml. | После добавления вы можете начать переводить сразу. | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/translate.html#%D0%B4%D0%BE%D0%B1%D0%B0%D0%B2%D0%BB%D0%B5%D0%BD%D0%B8%D0%B5-%D0%BD%D0%BE%D0%B2%D0%BE%D0%B3%D0%BE-%D1%8F%D0%B7%D1%8B%D0%BA%D0%B0",
    
    "relUrl": "/ru-rRU/user/translate.html#добавление-нового-языка"
  },"5413": {
    "doc": "Перевод приложения",
    "title": "Как организованы переводы",
    "content": "Приложение для Android использует Compose Multiplatform resources для всех строк, видимых пользователю: . core/resources/src/commonMain/composeResources/ ├── values/ ← English (default) │ └── strings.xml ├── values-de/ ← German │ └── strings.xml ├── values-fr/ ← French │ └── strings.xml └── ... Встроенная документация следует аналогичной схеме в папке docs/: . docs/ ├── en/user/ ← English source (default) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← French (France) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← German (Germany) │ └── ... └── ... Папки с локалями документации используют локальные квалификаторы Android: либо {lang}, либо {lang}-r{REGION} (например, fr, fr-rFR, de-rDE, ja-rJP). Папки values-* для строк приложения используют просто коды языков (values-fr, values-de, values-ja), потому что crowdin.yml пишет строки с %two_letters_code%, а страницы документации — с %android_code%. Эти два набора не совпадают один к одному. Приложение автоматически выбирает правильный язык и регион на основе настроек вашего телефона Язык и регион. Страница, пришедшая из Crowdin, в приложении под своим заголовком отмечена как Переведено сообществом. Если на странице ещё нет перевода на твой язык в Crowdin, сборка для Android с помощью Google автоматически переводит исходник с английского и помечает его как Автоперевод; сборки для F-Droid и десктопа показывают английскую страницу. Твой перевод в Crowdin заменяет машинный, как только он появляется. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/translate.html#%D0%BA%D0%B0%D0%BA-%D0%BE%D1%80%D0%B3%D0%B0%D0%BD%D0%B8%D0%B7%D0%BE%D0%B2%D0%B0%D0%BD%D1%8B-%D0%BF%D0%B5%D1%80%D0%B5%D0%B2%D0%BE%D0%B4%D1%8B",
    
    "relUrl": "/ru-rRU/user/translate.html#как-организованы-переводы"
  },"5414": {
    "doc": "Перевод приложения",
    "title": "Руководство по переводу",
    "content": ". | Не переводите технические термины, такие как “LoRa”, “MQTT”, “BLE”, “TAK”, “SNR” или “RSSI” — они универсальны. | Сохраняйте заполнители без изменений. Строки, такие как %1$s или %d, заполняются во время выполнения. Не удаляйте и не меняйте их порядок, если только грамматика вашего языка не требует этого. | Согласуйте тон. Приложение использует дружелюбный, прямой стиль общения. Избегайте чрезмерно официального языка. | Проверь, если возможно. Поменяй язык на телефоне и открой приложение, чтобы увидеть, как выглядят переводы в контексте. | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/translate.html#%D1%80%D1%83%D0%BA%D0%BE%D0%B2%D0%BE%D0%B4%D1%81%D1%82%D0%B2%D0%BE-%D0%BF%D0%BE-%D0%BF%D0%B5%D1%80%D0%B5%D0%B2%D0%BE%D0%B4%D1%83",
    
    "relUrl": "/ru-rRU/user/translate.html#руководство-по-переводу"
  },"5415": {
    "doc": "Перевод приложения",
    "title": "Вопросы?",
    "content": "Если у тебя есть вопросы о контексте конкретной строки или нужна помощь для начала работы, создайте обсуждение на странице Meshtastic GitHub Discussions. Спасибо, что помогаешь расширять охват Meshtastic. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/translate.html#%D0%B2%D0%BE%D0%BF%D1%80%D0%BE%D1%81%D1%8B",
    
    "relUrl": "/ru-rRU/user/translate.html#вопросы"
  },"5416": {
    "doc": "Перевод приложения",
    "title": "Связанные темы",
    "content": ". | Единицы и локаль — как приложение выбирает форматы чисел, дат и единиц для твоего региона | Справка и документация — встроенный браузер документации, куда публикуются эти страницы | Onboarding — это момент, когда новый пользователь впервые сталкивается с переведёнными строками | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/translate.html#%D1%81%D0%B2%D1%8F%D0%B7%D0%B0%D0%BD%D0%BD%D1%8B%D0%B5-%D1%82%D0%B5%D0%BC%D1%8B",
    
    "relUrl": "/ru-rRU/user/translate.html#связанные-темы"
  },"5417": {
    "doc": "Překlad aplikace",
    "title": "Překlad aplikace",
    "content": "Aplikace a její dokumentace v aplikaci se překládají na Crowdin – tato stránka ukazuje, jak přispívat k překladům. Aplikace používá Crowdin ke správě komunitních překladů uživatelského rozhraní i dokumentace přímo v aplikaci. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/translate.html",
    
    "relUrl": "/cs-rCZ/user/translate.html"
  },"5418": {
    "doc": "Překlad aplikace",
    "title": "Co se překládá",
    "content": "| Zdroj | Umístění zdroje | Poznámka | . | UI řetězce | core/resources/src/commonMain/composeResources/values/strings.xml | Tlačítka, popisky, zprávy a veškerý text zobrazený uživateli | . | Stránky uživatelské příručky | docs/en/user/*.md | Dokumentace v aplikaci zobrazená v části Nápověda a dokumentace | . | Fastlane metadata | fastlane/metadata/android/en-US/ | Google Play listing title, description, and changelogs | . ℹ️ Poznámka: Stránky Vývojářské příručky jsou pouze v angličtině. Dokumentace zaměřená na kód pro přispěvatele se nepřekládá. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/translate.html#co-se-p%C5%99ekl%C3%A1d%C3%A1",
    
    "relUrl": "/cs-rCZ/user/translate.html#co-se-překládá"
  },"5419": {
    "doc": "Překlad aplikace",
    "title": "Jak přispět",
    "content": ". | Navštivte projekt na Crowdinu. Otevřete Meshtastic Android Crowdin project a přihlaste se nebo si zdarma vytvořte účet. | Vyberte svůj jazyk. Vyberte některý z dostupných jazyků nebo požádejte o přidání nového jazyka založením GitHub problému. | Přeložte řetězce. Crowdin zobrazuje vlevo anglický zdrojový text a vpravo váš překlad. Přeložte každý řetězec a uložte ho. | Zkontrolujte kontext. Mnoho řetězců obsahuje snímky obrazovky nebo poznámky ke kontextu – podívejte se na ně, abyste zjistili, kde se text v aplikaci zobrazuje. Naplánovaná úloha stáhne schválené překlady z Crowdin a vytvoří pull request. Překlady se dostanou do aplikace, jakmile jej správce sloučí a vyjde nová verze. | . 💡 Tip: Překlady udržujte krátké. UI řetězce se často zobrazují na tlačítkách, štítcích nebo v úzkých sloupcích. Pokud je překlad výrazně delší než anglický originál, zvažte jeho zkrácení, pokud zůstane význam jasný. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/translate.html#jak-p%C5%99isp%C4%9Bt",
    
    "relUrl": "/cs-rCZ/user/translate.html#jak-přispět"
  },"5420": {
    "doc": "Překlad aplikace",
    "title": "Přidání nového jazyka",
    "content": "Pokud váš jazyk ještě není na Crowdinu uveden: . | Otevřete problém na GitHub s žádostí o přidání nového jazyka. | Správce přidá jazyk do Crowdinu a nastaví crowdin.yml. | Jakmile bude přidán, můžete začít překládat. | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/translate.html#p%C5%99id%C3%A1n%C3%AD-nov%C3%A9ho-jazyka",
    
    "relUrl": "/cs-rCZ/user/translate.html#přidání-nového-jazyka"
  },"5421": {
    "doc": "Překlad aplikace",
    "title": "Jak jsou překlady uspořádány",
    "content": "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/ ├── en/user/ ← English source (default) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← French (France) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← German (Germany) │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. The app automatically selects the correct locale based on your phone’s Language & Region settings. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/translate.html#jak-jsou-p%C5%99eklady-uspo%C5%99%C3%A1d%C3%A1ny",
    
    "relUrl": "/cs-rCZ/user/translate.html#jak-jsou-překlady-uspořádány"
  },"5422": {
    "doc": "Překlad aplikace",
    "title": "Pokyny pro překlad",
    "content": ". | Technické výrazy jako „LoRa“, „MQTT“, „BLE“, „TAK“, „SNR“ nebo „RSSI“ nepřekládejte – jsou univerzální. | **Zástupné symboly ponechte beze změny. ** Řetězce jako %1$s nebo %dse doplňují za běhu aplikace. Neodstraňujte je ani neměňte jejich pořadí, pokud to nevyžaduje gramatika vašeho jazyka. | Dodržujte tón komunikace. Aplikace používá přátelský a přímý styl. Vyhněte se příliš formálnímu jazyku. | Pokud můžete, překlad otestujte. Přepněte jazyk telefonu a otevřete aplikaci, abyste viděli, jak překlady vypadají v kontextu. | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/translate.html#pokyny-pro-p%C5%99eklad",
    
    "relUrl": "/cs-rCZ/user/translate.html#pokyny-pro-překlad"
  },"5423": {
    "doc": "Překlad aplikace",
    "title": "Máte dotazy?",
    "content": "Pokud máte dotazy ke kontextu konkrétního řetězce nebo potřebujete pomoct se začátky, založte diskuzi na stránce Meshtastic GitHub Discussions. Děkujeme, že pomáháte rozšiřovat Meshtastic. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/translate.html#m%C3%A1te-dotazy",
    
    "relUrl": "/cs-rCZ/user/translate.html#máte-dotazy"
  },"5424": {
    "doc": "Překlad aplikace",
    "title": "Související témata",
    "content": ". | Units & Locale — how the app picks number, date, and unit formats for your region | Help & Documentation — the in-app docs browser these pages are published to | Onboarding — where a new user first meets the translated strings | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/translate.html#souvisej%C3%ADc%C3%AD-t%C3%A9mata",
    
    "relUrl": "/cs-rCZ/user/translate.html#související-témata"
  },"5425": {
    "doc": "Преведете приложението",
    "title": "Преведете приложението",
    "content": "Приложението и придружаващата го документация се превеждат в Crowdin – на тази страница е обяснено как да се включите. Приложението използва Crowdin за управление на преводите, извършвани от общността, както за потребителския интерфейс, така и за документацията в самото приложение. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/translate.html",
    
    "relUrl": "/bg-rBG/user/translate.html"
  },"5426": {
    "doc": "Преведете приложението",
    "title": "What Gets Translated",
    "content": "| Resource | Source Location | Бележки | . | UI strings | core/resources/src/commonMain/composeResources/values/strings.xml | Buttons, labels, messages, and all user-visible text | . | User Guide pages | docs/en/user/*.md | In-app documentation shown in Help & Documentation | . | Fastlane metadata | fastlane/metadata/android/en-US/ | Google Play listing title, description, and changelogs | . ℹ️ Note: Developer Guide pages are English-only. Code-focused documentation targeting contributors is not translated. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/translate.html#what-gets-translated",
    
    "relUrl": "/bg-rBG/user/translate.html#what-gets-translated"
  },"5427": {
    "doc": "Преведете приложението",
    "title": "Как да допринесете",
    "content": ". | Visit the Crowdin project. Open the Meshtastic Android Crowdin project and sign in or create a free account. | Choose your language. Select an existing language or request a new one by opening a GitHub issue. | Translate strings. Crowdin shows the English source on the left and your translation on the right. Translate each string and save. | Review context. Many strings include screenshots or context comments — check these to understand where the text appears in the app. A scheduled job pulls approved translations from Crowdin and opens a pull request; they ship once a maintainer merges it and a new build goes out. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/translate.html#%D0%BA%D0%B0%D0%BA-%D0%B4%D0%B0-%D0%B4%D0%BE%D0%BF%D1%80%D0%B8%D0%BD%D0%B5%D1%81%D0%B5%D1%82%D0%B5",
    
    "relUrl": "/bg-rBG/user/translate.html#как-да-допринесете"
  },"5428": {
    "doc": "Преведете приложението",
    "title": "Добавяне на нов език",
    "content": "Ако езикът ви все още не е включен в списъка в Crowdin: . | Отворете проблем в GitHub, като поискате новия език. | Поддържащият ще добави езика в Crowdin и ще конфигурира crowdin.yml. | След като бъде добавен, можете да започнете да превеждате веднага. | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/translate.html#%D0%B4%D0%BE%D0%B1%D0%B0%D0%B2%D1%8F%D0%BD%D0%B5-%D0%BD%D0%B0-%D0%BD%D0%BE%D0%B2-%D0%B5%D0%B7%D0%B8%D0%BA",
    
    "relUrl": "/bg-rBG/user/translate.html#добавяне-на-нов-език"
  },"5429": {
    "doc": "Преведете приложението",
    "title": "Как са организирани преводите",
    "content": "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/ ├── en/user/ ← English source (default) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← French (France) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← German (Germany) │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. The app automatically selects the correct locale based on your phone’s Language & Region settings. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/translate.html#%D0%BA%D0%B0%D0%BA-%D1%81%D0%B0-%D0%BE%D1%80%D0%B3%D0%B0%D0%BD%D0%B8%D0%B7%D0%B8%D1%80%D0%B0%D0%BD%D0%B8-%D0%BF%D1%80%D0%B5%D0%B2%D0%BE%D0%B4%D0%B8%D1%82%D0%B5",
    
    "relUrl": "/bg-rBG/user/translate.html#как-са-организирани-преводите"
  },"5430": {
    "doc": "Преведете приложението",
    "title": "Translation Guidelines",
    "content": ". | 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 phone’s language and open the app to see how translations look in context. | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/translate.html#translation-guidelines",
    
    "relUrl": "/bg-rBG/user/translate.html#translation-guidelines"
  },"5431": {
    "doc": "Преведете приложението",
    "title": "Въпроси?",
    "content": "If you have questions about a specific string’s context or need help getting started, open a discussion on the Meshtastic GitHub Discussions page. Thank you for helping expand the reach of Meshtastic. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/translate.html#%D0%B2%D1%8A%D0%BF%D1%80%D0%BE%D1%81%D0%B8",
    
    "relUrl": "/bg-rBG/user/translate.html#въпроси"
  },"5432": {
    "doc": "Преведете приложението",
    "title": "Свързани теми",
    "content": ". | Units & Locale — how the app picks number, date, and unit formats for your region | Help & Documentation — the in-app docs browser these pages are published to | Onboarding — where a new user first meets the translated strings | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/translate.html#%D1%81%D0%B2%D1%8A%D1%80%D0%B7%D0%B0%D0%BD%D0%B8-%D1%82%D0%B5%D0%BC%D0%B8",
    
    "relUrl": "/bg-rBG/user/translate.html#свързани-теми"
  },"5433": {
    "doc": "Translate the App",
    "title": "Translate the App",
    "content": "The app and its in-app docs are translated on Crowdin — this page shows how to contribute. The app uses Crowdin to manage community translations for both the user interface and in-app documentation. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/translate.html",
    
    "relUrl": "/ga-rIE/user/translate.html"
  },"5434": {
    "doc": "Translate the App",
    "title": "What Gets Translated",
    "content": "| Resource | Source Location | Notes | . | UI strings | core/resources/src/commonMain/composeResources/values/strings.xml | Buttons, labels, messages, and all user-visible text | . | User Guide pages | docs/en/user/*.md | In-app documentation shown in Help & Documentation | . | Fastlane metadata | fastlane/metadata/android/en-US/ | Google Play listing title, description, and changelogs | . ℹ️ Note: Developer Guide pages are English-only. Code-focused documentation targeting contributors is not translated. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/translate.html#what-gets-translated",
    
    "relUrl": "/ga-rIE/user/translate.html#what-gets-translated"
  },"5435": {
    "doc": "Translate the App",
    "title": "How to Contribute",
    "content": ". | Visit the Crowdin project. Open the Meshtastic Android Crowdin project and sign in or create a free account. | Choose your language. Select an existing language or request a new one by opening a GitHub issue. | Translate strings. Crowdin shows the English source on the left and your translation on the right. Translate each string and save. | Review context. Many strings include screenshots or context comments — check these to understand where the text appears in the app. A scheduled job pulls approved translations from Crowdin and opens a pull request; they ship once a maintainer merges it and a new build goes out. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/translate.html#how-to-contribute",
    
    "relUrl": "/ga-rIE/user/translate.html#how-to-contribute"
  },"5436": {
    "doc": "Translate the App",
    "title": "Adding a New Language",
    "content": "If your language is not yet listed on Crowdin: . | Open an issue on GitHub requesting the new locale. | A maintainer will add the language to Crowdin and configure crowdin.yml. | Once added, you can begin translating immediately. | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/translate.html#adding-a-new-language",
    
    "relUrl": "/ga-rIE/user/translate.html#adding-a-new-language"
  },"5437": {
    "doc": "Translate the App",
    "title": "How Translations Are Organized",
    "content": "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/ ├── en/user/ ← English source (default) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← French (France) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← German (Germany) │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. The app automatically selects the correct locale based on your phone’s Language & Region settings. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/translate.html#how-translations-are-organized",
    
    "relUrl": "/ga-rIE/user/translate.html#how-translations-are-organized"
  },"5438": {
    "doc": "Translate the App",
    "title": "Translation Guidelines",
    "content": ". | 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 phone’s language and open the app to see how translations look in context. | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/translate.html#translation-guidelines",
    
    "relUrl": "/ga-rIE/user/translate.html#translation-guidelines"
  },"5439": {
    "doc": "Translate the App",
    "title": "Questions?",
    "content": "If you have questions about a specific string’s context or need help getting started, open a discussion on the Meshtastic GitHub Discussions page. Thank you for helping expand the reach of Meshtastic. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/translate.html#questions",
    
    "relUrl": "/ga-rIE/user/translate.html#questions"
  },"5440": {
    "doc": "Translate the App",
    "title": "Related Topics",
    "content": ". | Units & Locale — how the app picks number, date, and unit formats for your region | Help & Documentation — the in-app docs browser these pages are published to | Onboarding — where a new user first meets the translated strings | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/translate.html#related-topics",
    
    "relUrl": "/ga-rIE/user/translate.html#related-topics"
  },"5441": {
    "doc": "Translate the App",
    "title": "Translate the App",
    "content": "The app and its in-app docs are translated on Crowdin — this page shows how to contribute. The app uses Crowdin to manage community translations for both the user interface and in-app documentation. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/translate.html",
    
    "relUrl": "/fr-rCA/user/translate.html"
  },"5442": {
    "doc": "Translate the App",
    "title": "Ce qui est traduit",
    "content": "| Ressource | Emplacement de la source | Notes | . | Chaînes UI | core/resources/src/commonMain/composeResources/values/strings.xml | Boutons, étiquettes, messages et tout texte visible par l’utilisateur | . | Pages du Guide de l’utilisateur | docs/en/user/*.md | Documentation dans l’application affichée dans Aide et Documentation | . | Métadonnées Fastlane | fastlane/metadata/android/fr-FR/ | Google Play listing title, description, and changelogs | . ℹ️ Note: Developer Guide pages are English-only. Code-focused documentation targeting contributors is not translated. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/translate.html#ce-qui-est-traduit",
    
    "relUrl": "/fr-rCA/user/translate.html#ce-qui-est-traduit"
  },"5443": {
    "doc": "Translate the App",
    "title": "Comment contribuer",
    "content": ". | Visitez le projet Crowdin. Ouvrez le projet Meshtastic Android Crowdin et connectez-vous ou créez un compte gratuit. | Choisissez votre langue. Sélectionnez une langue existante ou demandez-en une nouvelle en ouvrant un problème GitHub. | Traductions Crowdin montre la source anglaise à gauche et votre traduction à droite. Traduisez chaque portion et sauvegardez. | Vérifier le contexte. De nombreuses portions incluent des captures d’écran ou des commentaires de contexte — cochez celles-ci pour comprendre où le texte apparaît dans l’application. A scheduled job pulls approved translations from Crowdin and opens a pull request; they ship once a maintainer merges it and a new build goes out. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. Si une traduction est considérablement plus longue que l’original anglais, pensez à abréger en conservant la signification claire. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/translate.html#comment-contribuer",
    
    "relUrl": "/fr-rCA/user/translate.html#comment-contribuer"
  },"5444": {
    "doc": "Translate the App",
    "title": "Ajouter une nouvelle langue",
    "content": "Si votre langue n’est pas encore listée sur Crowdin : . | Ouvrir un ticket sur GitHub demandant la nouvelle langue. | Un responsable ajoutera la langue à Crowdin et configurera crowdin.yml. | Une fois ajouté, vous pouvez commencer à traduire immédiatement. | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/translate.html#ajouter-une-nouvelle-langue",
    
    "relUrl": "/fr-rCA/user/translate.html#ajouter-une-nouvelle-langue"
  },"5445": {
    "doc": "Translate the App",
    "title": "Comment sont organisées les traductions",
    "content": "L’application Android utilise des Ressources Multiplateforme pour tous les textes visibles par l’utilisateur: . core/resources/src/commonMain/composeResources/ ├── values/ ← English (default) │ └── strings.xml ├── values-de/ ← German │ └── strings.xml ├── values-fr/ ← French │ └── strings.xml └── ... La documentation dans l’application suit un modèle similaire dans docs/: . docs/ ├── en/user/ ← English source (default) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← French (France) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← German (Germany) │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. The app automatically selects the correct locale based on your phone’s Language & Region settings. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/translate.html#comment-sont-organis%C3%A9es-les-traductions",
    
    "relUrl": "/fr-rCA/user/translate.html#comment-sont-organisées-les-traductions"
  },"5446": {
    "doc": "Translate the App",
    "title": "Directives de Traduction",
    "content": ". | Ne traduisez pas des termes techniques tels que “LoRa”, “MQTT”, “BLE”, “TAK”, “SNR”, ou “RSSI” — ce sont des termes universels. | Garder les espaces réservés intact. Les chaînes comme %1$s ou %d sont remplies au moment de l’exécution. Ne les supprimez ni ne les réordonnez pas à moins que la grammaire de votre langue ne l’exige. | Respectez le ton L’application utilise un ton amical Évitez des formulations trop formelles | Test if possible. Switch your phone’s language and open the app to see how translations look in context. | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/translate.html#directives-de-traduction",
    
    "relUrl": "/fr-rCA/user/translate.html#directives-de-traduction"
  },"5447": {
    "doc": "Translate the App",
    "title": "Des questions ?",
    "content": "If you have questions about a specific string’s context or need help getting started, open a discussion on the Meshtastic GitHub Discussions page. Thank you for helping expand the reach of Meshtastic. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/translate.html#des-questions",
    
    "relUrl": "/fr-rCA/user/translate.html#des-questions"
  },"5448": {
    "doc": "Translate the App",
    "title": "Related Topics",
    "content": ". | Units & Locale — how the app picks number, date, and unit formats for your region | Help & Documentation — the in-app docs browser these pages are published to | Onboarding — where a new user first meets the translated strings | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/translate.html#related-topics",
    
    "relUrl": "/fr-rCA/user/translate.html#related-topics"
  },"5449": {
    "doc": "Translate the App",
    "title": "Translate the App",
    "content": "The app and its in-app docs are translated on Crowdin — this page shows how to contribute. The app uses Crowdin to manage community translations for both the user interface and in-app documentation. ",
    "url": "/Meshtastic-Android/main/srp/user/translate.html",
    
    "relUrl": "/srp/user/translate.html"
  },"5450": {
    "doc": "Translate the App",
    "title": "What Gets Translated",
    "content": "| Resource | Source Location | Белешке | . | UI strings | core/resources/src/commonMain/composeResources/values/strings.xml | Buttons, labels, messages, and all user-visible text | . | User Guide pages | docs/en/user/*.md | In-app documentation shown in Help & Documentation | . | Fastlane metadata | fastlane/metadata/android/en-US/ | Google Play listing title, description, and changelogs | . ℹ️ Note: Developer Guide pages are English-only. Code-focused documentation targeting contributors is not translated. ",
    "url": "/Meshtastic-Android/main/srp/user/translate.html#what-gets-translated",
    
    "relUrl": "/srp/user/translate.html#what-gets-translated"
  },"5451": {
    "doc": "Translate the App",
    "title": "How to Contribute",
    "content": ". | Visit the Crowdin project. Open the Meshtastic Android Crowdin project and sign in or create a free account. | Choose your language. Select an existing language or request a new one by opening a GitHub issue. | Translate strings. Crowdin shows the English source on the left and your translation on the right. Translate each string and save. | Review context. Many strings include screenshots or context comments — check these to understand where the text appears in the app. A scheduled job pulls approved translations from Crowdin and opens a pull request; they ship once a maintainer merges it and a new build goes out. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/srp/user/translate.html#how-to-contribute",
    
    "relUrl": "/srp/user/translate.html#how-to-contribute"
  },"5452": {
    "doc": "Translate the App",
    "title": "Adding a New Language",
    "content": "If your language is not yet listed on Crowdin: . | Open an issue on GitHub requesting the new locale. | A maintainer will add the language to Crowdin and configure crowdin.yml. | Once added, you can begin translating immediately. | . ",
    "url": "/Meshtastic-Android/main/srp/user/translate.html#adding-a-new-language",
    
    "relUrl": "/srp/user/translate.html#adding-a-new-language"
  },"5453": {
    "doc": "Translate the App",
    "title": "How Translations Are Organized",
    "content": "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/ ├── en/user/ ← English source (default) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← French (France) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← German (Germany) │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. The app automatically selects the correct locale based on your phone’s Language & Region settings. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/srp/user/translate.html#how-translations-are-organized",
    
    "relUrl": "/srp/user/translate.html#how-translations-are-organized"
  },"5454": {
    "doc": "Translate the App",
    "title": "Translation Guidelines",
    "content": ". | 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 phone’s language and open the app to see how translations look in context. | . ",
    "url": "/Meshtastic-Android/main/srp/user/translate.html#translation-guidelines",
    
    "relUrl": "/srp/user/translate.html#translation-guidelines"
  },"5455": {
    "doc": "Translate the App",
    "title": "Questions?",
    "content": "If you have questions about a specific string’s context or need help getting started, open a discussion on the Meshtastic GitHub Discussions page. Thank you for helping expand the reach of Meshtastic. ",
    "url": "/Meshtastic-Android/main/srp/user/translate.html#questions",
    
    "relUrl": "/srp/user/translate.html#questions"
  },"5456": {
    "doc": "Translate the App",
    "title": "Related Topics",
    "content": ". | Units & Locale — how the app picks number, date, and unit formats for your region | Help & Documentation — the in-app docs browser these pages are published to | Onboarding — where a new user first meets the translated strings | . ",
    "url": "/Meshtastic-Android/main/srp/user/translate.html#related-topics",
    
    "relUrl": "/srp/user/translate.html#related-topics"
  },"5457": {
    "doc": "Translate the App",
    "title": "Translate the App",
    "content": "The app and its in-app docs are translated on Crowdin — this page shows how to contribute. The app uses Crowdin to manage community translations for both the user interface and in-app documentation. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/translate.html",
    
    "relUrl": "/ca-rES/user/translate.html"
  },"5458": {
    "doc": "Translate the App",
    "title": "What Gets Translated",
    "content": "| Resource | Source Location | Notes | . | UI strings | core/resources/src/commonMain/composeResources/values/strings.xml | Buttons, labels, messages, and all user-visible text | . | User Guide pages | docs/en/user/*.md | In-app documentation shown in Help & Documentation | . | Fastlane metadata | fastlane/metadata/android/en-US/ | Google Play listing title, description, and changelogs | . ℹ️ Note: Developer Guide pages are English-only. Code-focused documentation targeting contributors is not translated. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/translate.html#what-gets-translated",
    
    "relUrl": "/ca-rES/user/translate.html#what-gets-translated"
  },"5459": {
    "doc": "Translate the App",
    "title": "How to Contribute",
    "content": ". | Visit the Crowdin project. Open the Meshtastic Android Crowdin project and sign in or create a free account. | Choose your language. Select an existing language or request a new one by opening a GitHub issue. | Translate strings. Crowdin shows the English source on the left and your translation on the right. Translate each string and save. | Review context. Many strings include screenshots or context comments — check these to understand where the text appears in the app. A scheduled job pulls approved translations from Crowdin and opens a pull request; they ship once a maintainer merges it and a new build goes out. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/translate.html#how-to-contribute",
    
    "relUrl": "/ca-rES/user/translate.html#how-to-contribute"
  },"5460": {
    "doc": "Translate the App",
    "title": "Adding a New Language",
    "content": "If your language is not yet listed on Crowdin: . | Open an issue on GitHub requesting the new locale. | A maintainer will add the language to Crowdin and configure crowdin.yml. | Once added, you can begin translating immediately. | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/translate.html#adding-a-new-language",
    
    "relUrl": "/ca-rES/user/translate.html#adding-a-new-language"
  },"5461": {
    "doc": "Translate the App",
    "title": "How Translations Are Organized",
    "content": "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/ ├── en/user/ ← English source (default) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← French (France) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← German (Germany) │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. The app automatically selects the correct locale based on your phone’s Language & Region settings. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/translate.html#how-translations-are-organized",
    
    "relUrl": "/ca-rES/user/translate.html#how-translations-are-organized"
  },"5462": {
    "doc": "Translate the App",
    "title": "Translation Guidelines",
    "content": ". | 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 phone’s language and open the app to see how translations look in context. | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/translate.html#translation-guidelines",
    
    "relUrl": "/ca-rES/user/translate.html#translation-guidelines"
  },"5463": {
    "doc": "Translate the App",
    "title": "Questions?",
    "content": "If you have questions about a specific string’s context or need help getting started, open a discussion on the Meshtastic GitHub Discussions page. Thank you for helping expand the reach of Meshtastic. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/translate.html#questions",
    
    "relUrl": "/ca-rES/user/translate.html#questions"
  },"5464": {
    "doc": "Translate the App",
    "title": "Related Topics",
    "content": ". | Units & Locale — how the app picks number, date, and unit formats for your region | Help & Documentation — the in-app docs browser these pages are published to | Onboarding — where a new user first meets the translated strings | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/translate.html#related-topics",
    
    "relUrl": "/ca-rES/user/translate.html#related-topics"
  },"5465": {
    "doc": "Translate the App",
    "title": "Translate the App",
    "content": "The app and its in-app docs are translated on Crowdin — this page shows how to contribute. The app uses Crowdin to manage community translations for both the user interface and in-app documentation. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/translate.html",
    
    "relUrl": "/ko-rKR/user/translate.html"
  },"5466": {
    "doc": "Translate the App",
    "title": "What Gets Translated",
    "content": "| Resource | Source Location | Notes | . | UI strings | core/resources/src/commonMain/composeResources/values/strings.xml | Buttons, labels, messages, and all user-visible text | . | User Guide pages | docs/en/user/*.md | In-app documentation shown in Help & Documentation | . | Fastlane metadata | fastlane/metadata/android/en-US/ | Google Play listing title, description, and changelogs | . ℹ️ Note: Developer Guide pages are English-only. Code-focused documentation targeting contributors is not translated. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/translate.html#what-gets-translated",
    
    "relUrl": "/ko-rKR/user/translate.html#what-gets-translated"
  },"5467": {
    "doc": "Translate the App",
    "title": "How to Contribute",
    "content": ". | Visit the Crowdin project. Open the Meshtastic Android Crowdin project and sign in or create a free account. | Choose your language. Select an existing language or request a new one by opening a GitHub issue. | Translate strings. Crowdin shows the English source on the left and your translation on the right. Translate each string and save. | Review context. Many strings include screenshots or context comments — check these to understand where the text appears in the app. A scheduled job pulls approved translations from Crowdin and opens a pull request; they ship once a maintainer merges it and a new build goes out. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/translate.html#how-to-contribute",
    
    "relUrl": "/ko-rKR/user/translate.html#how-to-contribute"
  },"5468": {
    "doc": "Translate the App",
    "title": "Adding a New Language",
    "content": "If your language is not yet listed on Crowdin: . | Open an issue on GitHub requesting the new locale. | A maintainer will add the language to Crowdin and configure crowdin.yml. | Once added, you can begin translating immediately. | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/translate.html#adding-a-new-language",
    
    "relUrl": "/ko-rKR/user/translate.html#adding-a-new-language"
  },"5469": {
    "doc": "Translate the App",
    "title": "How Translations Are Organized",
    "content": "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/ ├── en/user/ ← English source (default) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← French (France) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← German (Germany) │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. The app automatically selects the correct locale based on your phone’s Language & Region settings. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/translate.html#how-translations-are-organized",
    
    "relUrl": "/ko-rKR/user/translate.html#how-translations-are-organized"
  },"5470": {
    "doc": "Translate the App",
    "title": "Translation Guidelines",
    "content": ". | 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 phone’s language and open the app to see how translations look in context. | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/translate.html#translation-guidelines",
    
    "relUrl": "/ko-rKR/user/translate.html#translation-guidelines"
  },"5471": {
    "doc": "Translate the App",
    "title": "Questions?",
    "content": "If you have questions about a specific string’s context or need help getting started, open a discussion on the Meshtastic GitHub Discussions page. Thank you for helping expand the reach of Meshtastic. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/translate.html#questions",
    
    "relUrl": "/ko-rKR/user/translate.html#questions"
  },"5472": {
    "doc": "Translate the App",
    "title": "Related Topics",
    "content": ". | Units & Locale — how the app picks number, date, and unit formats for your region | Help & Documentation — the in-app docs browser these pages are published to | Onboarding — where a new user first meets the translated strings | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/translate.html#related-topics",
    
    "relUrl": "/ko-rKR/user/translate.html#related-topics"
  },"5473": {
    "doc": "Translate the App",
    "title": "Translate the App",
    "content": "The app and its in-app docs are translated on Crowdin — this page shows how to contribute. The app uses Crowdin to manage community translations for both the user interface and in-app documentation. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/translate.html",
    
    "relUrl": "/sv-rSE/user/translate.html"
  },"5474": {
    "doc": "Translate the App",
    "title": "What Gets Translated",
    "content": "| Resource | Source Location | Anteckningar | . | UI strings | core/resources/src/commonMain/composeResources/values/strings.xml | Buttons, labels, messages, and all user-visible text | . | User Guide pages | docs/en/user/*.md | In-app documentation shown in Help & Documentation | . | Fastlane metadata | fastlane/metadata/android/en-US/ | Google Play listing title, description, and changelogs | . ℹ️ Note: Developer Guide pages are English-only. Code-focused documentation targeting contributors is not translated. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/translate.html#what-gets-translated",
    
    "relUrl": "/sv-rSE/user/translate.html#what-gets-translated"
  },"5475": {
    "doc": "Translate the App",
    "title": "How to Contribute",
    "content": ". | Visit the Crowdin project. Open the Meshtastic Android Crowdin project and sign in or create a free account. | Choose your language. Select an existing language or request a new one by opening a GitHub issue. | Translate strings. Crowdin shows the English source on the left and your translation on the right. Translate each string and save. | Review context. Many strings include screenshots or context comments — check these to understand where the text appears in the app. A scheduled job pulls approved translations from Crowdin and opens a pull request; they ship once a maintainer merges it and a new build goes out. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/translate.html#how-to-contribute",
    
    "relUrl": "/sv-rSE/user/translate.html#how-to-contribute"
  },"5476": {
    "doc": "Translate the App",
    "title": "Adding a New Language",
    "content": "If your language is not yet listed on Crowdin: . | Open an issue on GitHub requesting the new locale. | A maintainer will add the language to Crowdin and configure crowdin.yml. | Once added, you can begin translating immediately. | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/translate.html#adding-a-new-language",
    
    "relUrl": "/sv-rSE/user/translate.html#adding-a-new-language"
  },"5477": {
    "doc": "Translate the App",
    "title": "How Translations Are Organized",
    "content": "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/ ├── en/user/ ← English source (default) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← French (France) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← German (Germany) │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. The app automatically selects the correct locale based on your phone’s Language & Region settings. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/translate.html#how-translations-are-organized",
    
    "relUrl": "/sv-rSE/user/translate.html#how-translations-are-organized"
  },"5478": {
    "doc": "Translate the App",
    "title": "Translation Guidelines",
    "content": ". | 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 phone’s language and open the app to see how translations look in context. | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/translate.html#translation-guidelines",
    
    "relUrl": "/sv-rSE/user/translate.html#translation-guidelines"
  },"5479": {
    "doc": "Translate the App",
    "title": "Questions?",
    "content": "If you have questions about a specific string’s context or need help getting started, open a discussion on the Meshtastic GitHub Discussions page. Thank you for helping expand the reach of Meshtastic. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/translate.html#questions",
    
    "relUrl": "/sv-rSE/user/translate.html#questions"
  },"5480": {
    "doc": "Translate the App",
    "title": "Related Topics",
    "content": ". | Units & Locale — how the app picks number, date, and unit formats for your region | Help & Documentation — the in-app docs browser these pages are published to | Onboarding — where a new user first meets the translated strings | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/translate.html#related-topics",
    
    "relUrl": "/sv-rSE/user/translate.html#related-topics"
  },"5481": {
    "doc": "Translate the App",
    "title": "Translate the App",
    "content": "The app and its in-app docs are translated on Crowdin — this page shows how to contribute. The app uses Crowdin to manage community translations for both the user interface and in-app documentation. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/translate.html",
    
    "relUrl": "/ht-rHT/user/translate.html"
  },"5482": {
    "doc": "Translate the App",
    "title": "What Gets Translated",
    "content": "| Resource | Source Location | Notes | . | UI strings | core/resources/src/commonMain/composeResources/values/strings.xml | Buttons, labels, messages, and all user-visible text | . | User Guide pages | docs/en/user/*.md | In-app documentation shown in Help & Documentation | . | Fastlane metadata | fastlane/metadata/android/en-US/ | Google Play listing title, description, and changelogs | . ℹ️ Note: Developer Guide pages are English-only. Code-focused documentation targeting contributors is not translated. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/translate.html#what-gets-translated",
    
    "relUrl": "/ht-rHT/user/translate.html#what-gets-translated"
  },"5483": {
    "doc": "Translate the App",
    "title": "How to Contribute",
    "content": ". | Visit the Crowdin project. Open the Meshtastic Android Crowdin project and sign in or create a free account. | Choose your language. Select an existing language or request a new one by opening a GitHub issue. | Translate strings. Crowdin shows the English source on the left and your translation on the right. Translate each string and save. | Review context. Many strings include screenshots or context comments — check these to understand where the text appears in the app. A scheduled job pulls approved translations from Crowdin and opens a pull request; they ship once a maintainer merges it and a new build goes out. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/translate.html#how-to-contribute",
    
    "relUrl": "/ht-rHT/user/translate.html#how-to-contribute"
  },"5484": {
    "doc": "Translate the App",
    "title": "Adding a New Language",
    "content": "If your language is not yet listed on Crowdin: . | Open an issue on GitHub requesting the new locale. | A maintainer will add the language to Crowdin and configure crowdin.yml. | Once added, you can begin translating immediately. | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/translate.html#adding-a-new-language",
    
    "relUrl": "/ht-rHT/user/translate.html#adding-a-new-language"
  },"5485": {
    "doc": "Translate the App",
    "title": "How Translations Are Organized",
    "content": "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/ ├── en/user/ ← English source (default) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← French (France) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← German (Germany) │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. The app automatically selects the correct locale based on your phone’s Language & Region settings. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/translate.html#how-translations-are-organized",
    
    "relUrl": "/ht-rHT/user/translate.html#how-translations-are-organized"
  },"5486": {
    "doc": "Translate the App",
    "title": "Translation Guidelines",
    "content": ". | 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 phone’s language and open the app to see how translations look in context. | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/translate.html#translation-guidelines",
    
    "relUrl": "/ht-rHT/user/translate.html#translation-guidelines"
  },"5487": {
    "doc": "Translate the App",
    "title": "Questions?",
    "content": "If you have questions about a specific string’s context or need help getting started, open a discussion on the Meshtastic GitHub Discussions page. Thank you for helping expand the reach of Meshtastic. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/translate.html#questions",
    
    "relUrl": "/ht-rHT/user/translate.html#questions"
  },"5488": {
    "doc": "Translate the App",
    "title": "Related Topics",
    "content": ". | Units & Locale — how the app picks number, date, and unit formats for your region | Help & Documentation — the in-app docs browser these pages are published to | Onboarding — where a new user first meets the translated strings | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/translate.html#related-topics",
    
    "relUrl": "/ht-rHT/user/translate.html#related-topics"
  },"5489": {
    "doc": "Translate the App",
    "title": "Translate the App",
    "content": "The app and its in-app docs are translated on Crowdin — this page shows how to contribute. The app uses Crowdin to manage community translations for both the user interface and in-app documentation. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/translate.html",
    
    "relUrl": "/sr-rLatn/user/translate.html"
  },"5490": {
    "doc": "Translate the App",
    "title": "What Gets Translated",
    "content": "| Resource | Source Location | Белешке | . | UI strings | core/resources/src/commonMain/composeResources/values/strings.xml | Buttons, labels, messages, and all user-visible text | . | User Guide pages | docs/en/user/*.md | In-app documentation shown in Help & Documentation | . | Fastlane metadata | fastlane/metadata/android/en-US/ | Google Play listing title, description, and changelogs | . ℹ️ Note: Developer Guide pages are English-only. Code-focused documentation targeting contributors is not translated. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/translate.html#what-gets-translated",
    
    "relUrl": "/sr-rLatn/user/translate.html#what-gets-translated"
  },"5491": {
    "doc": "Translate the App",
    "title": "How to Contribute",
    "content": ". | Visit the Crowdin project. Open the Meshtastic Android Crowdin project and sign in or create a free account. | Choose your language. Select an existing language or request a new one by opening a GitHub issue. | Translate strings. Crowdin shows the English source on the left and your translation on the right. Translate each string and save. | Review context. Many strings include screenshots or context comments — check these to understand where the text appears in the app. A scheduled job pulls approved translations from Crowdin and opens a pull request; they ship once a maintainer merges it and a new build goes out. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/translate.html#how-to-contribute",
    
    "relUrl": "/sr-rLatn/user/translate.html#how-to-contribute"
  },"5492": {
    "doc": "Translate the App",
    "title": "Adding a New Language",
    "content": "If your language is not yet listed on Crowdin: . | Open an issue on GitHub requesting the new locale. | A maintainer will add the language to Crowdin and configure crowdin.yml. | Once added, you can begin translating immediately. | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/translate.html#adding-a-new-language",
    
    "relUrl": "/sr-rLatn/user/translate.html#adding-a-new-language"
  },"5493": {
    "doc": "Translate the App",
    "title": "How Translations Are Organized",
    "content": "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/ ├── en/user/ ← English source (default) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← French (France) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← German (Germany) │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. The app automatically selects the correct locale based on your phone’s Language & Region settings. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/translate.html#how-translations-are-organized",
    
    "relUrl": "/sr-rLatn/user/translate.html#how-translations-are-organized"
  },"5494": {
    "doc": "Translate the App",
    "title": "Translation Guidelines",
    "content": ". | 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 phone’s language and open the app to see how translations look in context. | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/translate.html#translation-guidelines",
    
    "relUrl": "/sr-rLatn/user/translate.html#translation-guidelines"
  },"5495": {
    "doc": "Translate the App",
    "title": "Questions?",
    "content": "If you have questions about a specific string’s context or need help getting started, open a discussion on the Meshtastic GitHub Discussions page. Thank you for helping expand the reach of Meshtastic. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/translate.html#questions",
    
    "relUrl": "/sr-rLatn/user/translate.html#questions"
  },"5496": {
    "doc": "Translate the App",
    "title": "Related Topics",
    "content": ". | Units & Locale — how the app picks number, date, and unit formats for your region | Help & Documentation — the in-app docs browser these pages are published to | Onboarding — where a new user first meets the translated strings | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/translate.html#related-topics",
    
    "relUrl": "/sr-rLatn/user/translate.html#related-topics"
  },"5497": {
    "doc": "Translate the App",
    "title": "Translate the App",
    "content": "The app and its in-app docs are translated on Crowdin — this page shows how to contribute. The app uses Crowdin to manage community translations for both the user interface and in-app documentation. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/translate.html",
    
    "relUrl": "/nl-rNL/user/translate.html"
  },"5498": {
    "doc": "Translate the App",
    "title": "What Gets Translated",
    "content": "| Resource | Source Location | Notes | . | UI strings | core/resources/src/commonMain/composeResources/values/strings.xml | Buttons, labels, messages, and all user-visible text | . | User Guide pages | docs/en/user/*.md | In-app documentation shown in Help & Documentation | . | Fastlane metadata | fastlane/metadata/android/en-US/ | Google Play listing title, description, and changelogs | . ℹ️ Note: Developer Guide pages are English-only. Code-focused documentation targeting contributors is not translated. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/translate.html#what-gets-translated",
    
    "relUrl": "/nl-rNL/user/translate.html#what-gets-translated"
  },"5499": {
    "doc": "Translate the App",
    "title": "How to Contribute",
    "content": ". | Visit the Crowdin project. Open the Meshtastic Android Crowdin project and sign in or create a free account. | Choose your language. Select an existing language or request a new one by opening a GitHub issue. | Translate strings. Crowdin shows the English source on the left and your translation on the right. Translate each string and save. | Review context. Many strings include screenshots or context comments — check these to understand where the text appears in the app. A scheduled job pulls approved translations from Crowdin and opens a pull request; they ship once a maintainer merges it and a new build goes out. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/translate.html#how-to-contribute",
    
    "relUrl": "/nl-rNL/user/translate.html#how-to-contribute"
  },"5500": {
    "doc": "Translate the App",
    "title": "Adding a New Language",
    "content": "If your language is not yet listed on Crowdin: . | Open an issue on GitHub requesting the new locale. | A maintainer will add the language to Crowdin and configure crowdin.yml. | Once added, you can begin translating immediately. | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/translate.html#adding-a-new-language",
    
    "relUrl": "/nl-rNL/user/translate.html#adding-a-new-language"
  },"5501": {
    "doc": "Translate the App",
    "title": "How Translations Are Organized",
    "content": "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/ ├── en/user/ ← English source (default) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← French (France) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← German (Germany) │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. The app automatically selects the correct locale based on your phone’s Language & Region settings. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/translate.html#how-translations-are-organized",
    
    "relUrl": "/nl-rNL/user/translate.html#how-translations-are-organized"
  },"5502": {
    "doc": "Translate the App",
    "title": "Translation Guidelines",
    "content": ". | 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 phone’s language and open the app to see how translations look in context. | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/translate.html#translation-guidelines",
    
    "relUrl": "/nl-rNL/user/translate.html#translation-guidelines"
  },"5503": {
    "doc": "Translate the App",
    "title": "Questions?",
    "content": "If you have questions about a specific string’s context or need help getting started, open a discussion on the Meshtastic GitHub Discussions page. Thank you for helping expand the reach of Meshtastic. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/translate.html#questions",
    
    "relUrl": "/nl-rNL/user/translate.html#questions"
  },"5504": {
    "doc": "Translate the App",
    "title": "Related Topics",
    "content": ". | Units & Locale — how the app picks number, date, and unit formats for your region | Help & Documentation — the in-app docs browser these pages are published to | Onboarding — where a new user first meets the translated strings | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/translate.html#related-topics",
    
    "relUrl": "/nl-rNL/user/translate.html#related-topics"
  },"5505": {
    "doc": "Translate the App",
    "title": "Translate the App",
    "content": "The app and its in-app docs are translated on Crowdin — this page shows how to contribute. The app uses Crowdin to manage community translations for both the user interface and in-app documentation. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/translate.html",
    
    "relUrl": "/uk-rUA/user/translate.html"
  },"5506": {
    "doc": "Translate the App",
    "title": "What Gets Translated",
    "content": "| Resource | Source Location | Нотатки | . | UI strings | core/resources/src/commonMain/composeResources/values/strings.xml | Buttons, labels, messages, and all user-visible text | . | User Guide pages | docs/en/user/*.md | In-app documentation shown in Help & Documentation | . | Fastlane metadata | fastlane/metadata/android/en-US/ | Google Play listing title, description, and changelogs | . ℹ️ Note: Developer Guide pages are English-only. Code-focused documentation targeting contributors is not translated. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/translate.html#what-gets-translated",
    
    "relUrl": "/uk-rUA/user/translate.html#what-gets-translated"
  },"5507": {
    "doc": "Translate the App",
    "title": "How to Contribute",
    "content": ". | Visit the Crowdin project. Open the Meshtastic Android Crowdin project and sign in or create a free account. | Choose your language. Select an existing language or request a new one by opening a GitHub issue. | Translate strings. Crowdin shows the English source on the left and your translation on the right. Translate each string and save. | Review context. Many strings include screenshots or context comments — check these to understand where the text appears in the app. A scheduled job pulls approved translations from Crowdin and opens a pull request; they ship once a maintainer merges it and a new build goes out. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/translate.html#how-to-contribute",
    
    "relUrl": "/uk-rUA/user/translate.html#how-to-contribute"
  },"5508": {
    "doc": "Translate the App",
    "title": "Adding a New Language",
    "content": "If your language is not yet listed on Crowdin: . | Open an issue on GitHub requesting the new locale. | A maintainer will add the language to Crowdin and configure crowdin.yml. | Once added, you can begin translating immediately. | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/translate.html#adding-a-new-language",
    
    "relUrl": "/uk-rUA/user/translate.html#adding-a-new-language"
  },"5509": {
    "doc": "Translate the App",
    "title": "How Translations Are Organized",
    "content": "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/ ├── en/user/ ← English source (default) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← French (France) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← German (Germany) │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. The app automatically selects the correct locale based on your phone’s Language & Region settings. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/translate.html#how-translations-are-organized",
    
    "relUrl": "/uk-rUA/user/translate.html#how-translations-are-organized"
  },"5510": {
    "doc": "Translate the App",
    "title": "Translation Guidelines",
    "content": ". | 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 phone’s language and open the app to see how translations look in context. | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/translate.html#translation-guidelines",
    
    "relUrl": "/uk-rUA/user/translate.html#translation-guidelines"
  },"5511": {
    "doc": "Translate the App",
    "title": "Questions?",
    "content": "If you have questions about a specific string’s context or need help getting started, open a discussion on the Meshtastic GitHub Discussions page. Thank you for helping expand the reach of Meshtastic. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/translate.html#questions",
    
    "relUrl": "/uk-rUA/user/translate.html#questions"
  },"5512": {
    "doc": "Translate the App",
    "title": "Related Topics",
    "content": ". | Units & Locale — how the app picks number, date, and unit formats for your region | Help & Documentation — the in-app docs browser these pages are published to | Onboarding — where a new user first meets the translated strings | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/translate.html#related-topics",
    
    "relUrl": "/uk-rUA/user/translate.html#related-topics"
  },"5513": {
    "doc": "Käännä sovellus",
    "title": "Käännä sovellus",
    "content": "Sovellus ja sen sisäinen dokumentaatio käännetään Crowdinissa – tällä sivulla kerrotaan, miten voit osallistua. Sovellus käyttää Crowdinia yhteisökäännösten hallintaan sekä käyttöliittymän sovelluksen sisäisten dokumentaatioiden hallintaan. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/translate.html",
    
    "relUrl": "/fi-rFI/user/translate.html"
  },"5514": {
    "doc": "Käännä sovellus",
    "title": "Mitä käännetään",
    "content": "| Resurssi | Lähteen sijainti | Viestit | . | UI-tekstit | core/resources/src/commonMain/composeResources/values/strings.xml | Painikkeet, otsikot, viestit ja kaikki käyttäjälle näkyvä teksti | . | Käyttöoppaan sivut | docs/en/user/*.md | Sovelluksen sisäinen dokumentaatio Ohjeet ja dokumentaatio -osiossa | . | Fastlane-metatiedot | fastlane/metadata/android/en-US/ | Google Play listing title, description, and changelogs | . ℹ️ Huomautus: Developer Guide -sivut ovat saatavilla vain englanniksi. Koodiin keskittyvää dokumentaatiota, joka on suunnattu kehitystyöhön osallistuville, ei käännetä. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/translate.html#mit%C3%A4-k%C3%A4%C3%A4nnet%C3%A4%C3%A4n",
    
    "relUrl": "/fi-rFI/user/translate.html#mitä-käännetään"
  },"5515": {
    "doc": "Käännä sovellus",
    "title": "Kuinka voi osallistua",
    "content": ". | Avaa Meshtastic Android Crowdin -projekti (https://crowdin.com/project/meshtastic-android) ja kirjaudu sisään tai luo ilmainen tili. | Valitse kielesi. Valitse olemassa oleva kieli tai pyydä uutta avaamalla GitHub-issue. | Käännä merkkijonot. Crowdin näyttää englanninkielisen lähteen vasemmalla ja käännöksesi oikealla. Käännä jokainen merkkijono ja tallenna. | Tarkista konteksti. Monet merkkijonot sisältävät kuvakaappauksia tai kontekstikommentteja — tarkista nämä ymmärtääksesi, missä teksti näkyy sovelluksessa. A scheduled job pulls approved translations from Crowdin and opens a pull request; they ship once a maintainer merges it and a new build goes out. | . 💡 Vinkki: Pidä käännökset lyhyinä. Käyttöliittymän tekstit näkyvät usein painikkeissa, tunnisteissa tai kapeissa sarakkeissa. Jos käännös on huomattavasti pidempi kuin englanninkielinen alkuperäinen, harkitse tiivistämistä niin, että merkitys säilyy selkeänä. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/translate.html#kuinka-voi-osallistua",
    
    "relUrl": "/fi-rFI/user/translate.html#kuinka-voi-osallistua"
  },"5516": {
    "doc": "Käännä sovellus",
    "title": "Uuden kielen lisääminen",
    "content": "Jos kieltäsi ei ole vielä listattu Crowdinissa: . | Avaa GitHub-issue (https://github.com/meshtastic/Meshtastic-Android/issues/new) ja pyydä uutta kielialuetta. | Ylläpitäjä lisää kielen Crowdin-projektiin ja määrittää crowdin.yml-asetukset. | Kun kieli on lisätty, voit aloittaa kääntämisen heti. | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/translate.html#uuden-kielen-lis%C3%A4%C3%A4minen",
    
    "relUrl": "/fi-rFI/user/translate.html#uuden-kielen-lisääminen"
  },"5517": {
    "doc": "Käännä sovellus",
    "title": "Kuinka käännökset on järjestetty",
    "content": "Android-sovellus käyttää Compose Multiplatform -resursseja kaikille käyttäjälle näkyville teksteille: . core/resources/src/commonMain/composeResources/ ├── values/ ← English (default) │ └── strings.xml ├── values-de/ ← German │ └── strings.xml ├── values-fr/ ← French │ └── strings.xml └── ... Sovelluksen sisäinen dokumentaatio noudattaa samaa rakennetta docs/ -hakemistossa: . docs/ ├── en/user/ ← English source (default) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← French (France) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← German (Germany) │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. Sovellus valitsee oikean alueasetuksen automaattisesti puhelimesi Kieli ja alue -asetusten perusteella. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/translate.html#kuinka-k%C3%A4%C3%A4nn%C3%B6kset-on-j%C3%A4rjestetty",
    
    "relUrl": "/fi-rFI/user/translate.html#kuinka-käännökset-on-järjestetty"
  },"5518": {
    "doc": "Käännä sovellus",
    "title": "Käännösohjeet",
    "content": ". | Älä käännä teknisiä termejä kuten “LoRa”, “MQTT”, “BLE”, “TAK”, “SNR” tai “RSSI” — nämä ovat yleisiä. | Pidä paikkamerkit ennallaan. Merkkijonot kuten %1$s tai %d täytetään ajon aikana. Älä poista tai muuta niiden järjestystä, ellei kielesi kielioppi sitä vaadi. | Säilytä sävy. Sovellus käyttää ystävällistä ja suoraa tyyliä. Vältä liian muodollista kieltä. | Testaa mahdollisuuksien mukaan. Vaihda puhelimesi kieli ja avaa sovellus nähdäksesi, miltä käännökset näyttävät käytännössä. | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/translate.html#k%C3%A4%C3%A4nn%C3%B6sohjeet",
    
    "relUrl": "/fi-rFI/user/translate.html#käännösohjeet"
  },"5519": {
    "doc": "Käännä sovellus",
    "title": "Kysyttävää?",
    "content": "Jos sinulla on kysyttävää tietyn merkkijonon asiayhteydestä tai tarvitset apua alkuun pääsemisessä, avaa keskustelu Meshtastic GitHub Discussions -sivulla. Kiitos, että autat laajentamaan Meshtasticin tavoittavuutta. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/translate.html#kysytt%C3%A4v%C3%A4%C3%A4",
    
    "relUrl": "/fi-rFI/user/translate.html#kysyttävää"
  },"5520": {
    "doc": "Käännä sovellus",
    "title": "Aiheeseen liittyvät aiheet",
    "content": ". | Yksiköt ja alue – miten sovellus valitsee alueellesi sopivat lukujen, päivämäärien ja yksiköiden muodot | Ohje ja dokumentaatio – sovelluksen sisäinen dokumentaatio, johon nämä sivut julkaistaan | Käyttöönotto – missä uusi käyttäjä kohtaa ensimmäisenä käännetyt tekstit | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/translate.html#aiheeseen-liittyv%C3%A4t-aiheet",
    
    "relUrl": "/fi-rFI/user/translate.html#aiheeseen-liittyvät-aiheet"
  },"5521": {
    "doc": "Translate the App",
    "title": "Translate the App",
    "content": "The app and its in-app docs are translated on Crowdin — this page shows how to contribute. The app uses Crowdin to manage community translations for both the user interface and in-app documentation. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/translate.html",
    
    "relUrl": "/is-rIS/user/translate.html"
  },"5522": {
    "doc": "Translate the App",
    "title": "What Gets Translated",
    "content": "| Resource | Source Location | Notes | . | UI strings | core/resources/src/commonMain/composeResources/values/strings.xml | Buttons, labels, messages, and all user-visible text | . | User Guide pages | docs/en/user/*.md | In-app documentation shown in Help & Documentation | . | Fastlane metadata | fastlane/metadata/android/en-US/ | Google Play listing title, description, and changelogs | . ℹ️ Note: Developer Guide pages are English-only. Code-focused documentation targeting contributors is not translated. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/translate.html#what-gets-translated",
    
    "relUrl": "/is-rIS/user/translate.html#what-gets-translated"
  },"5523": {
    "doc": "Translate the App",
    "title": "How to Contribute",
    "content": ". | Visit the Crowdin project. Open the Meshtastic Android Crowdin project and sign in or create a free account. | Choose your language. Select an existing language or request a new one by opening a GitHub issue. | Translate strings. Crowdin shows the English source on the left and your translation on the right. Translate each string and save. | Review context. Many strings include screenshots or context comments — check these to understand where the text appears in the app. A scheduled job pulls approved translations from Crowdin and opens a pull request; they ship once a maintainer merges it and a new build goes out. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/translate.html#how-to-contribute",
    
    "relUrl": "/is-rIS/user/translate.html#how-to-contribute"
  },"5524": {
    "doc": "Translate the App",
    "title": "Adding a New Language",
    "content": "If your language is not yet listed on Crowdin: . | Open an issue on GitHub requesting the new locale. | A maintainer will add the language to Crowdin and configure crowdin.yml. | Once added, you can begin translating immediately. | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/translate.html#adding-a-new-language",
    
    "relUrl": "/is-rIS/user/translate.html#adding-a-new-language"
  },"5525": {
    "doc": "Translate the App",
    "title": "How Translations Are Organized",
    "content": "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/ ├── en/user/ ← English source (default) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← French (France) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← German (Germany) │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. The app automatically selects the correct locale based on your phone’s Language & Region settings. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/translate.html#how-translations-are-organized",
    
    "relUrl": "/is-rIS/user/translate.html#how-translations-are-organized"
  },"5526": {
    "doc": "Translate the App",
    "title": "Translation Guidelines",
    "content": ". | 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 phone’s language and open the app to see how translations look in context. | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/translate.html#translation-guidelines",
    
    "relUrl": "/is-rIS/user/translate.html#translation-guidelines"
  },"5527": {
    "doc": "Translate the App",
    "title": "Questions?",
    "content": "If you have questions about a specific string’s context or need help getting started, open a discussion on the Meshtastic GitHub Discussions page. Thank you for helping expand the reach of Meshtastic. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/translate.html#questions",
    
    "relUrl": "/is-rIS/user/translate.html#questions"
  },"5528": {
    "doc": "Translate the App",
    "title": "Related Topics",
    "content": ". | Units & Locale — how the app picks number, date, and unit formats for your region | Help & Documentation — the in-app docs browser these pages are published to | Onboarding — where a new user first meets the translated strings | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/translate.html#related-topics",
    
    "relUrl": "/is-rIS/user/translate.html#related-topics"
  },"5529": {
    "doc": "Translate the App",
    "title": "Translate the App",
    "content": "The app and its in-app docs are translated on Crowdin — this page shows how to contribute. The app uses Crowdin to manage community translations for both the user interface and in-app documentation. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/translate.html",
    
    "relUrl": "/lt-rLT/user/translate.html"
  },"5530": {
    "doc": "Translate the App",
    "title": "What Gets Translated",
    "content": "| Resource | Source Location | Notes | . | UI strings | core/resources/src/commonMain/composeResources/values/strings.xml | Buttons, labels, messages, and all user-visible text | . | User Guide pages | docs/en/user/*.md | In-app documentation shown in Help & Documentation | . | Fastlane metadata | fastlane/metadata/android/en-US/ | Google Play listing title, description, and changelogs | . ℹ️ Note: Developer Guide pages are English-only. Code-focused documentation targeting contributors is not translated. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/translate.html#what-gets-translated",
    
    "relUrl": "/lt-rLT/user/translate.html#what-gets-translated"
  },"5531": {
    "doc": "Translate the App",
    "title": "How to Contribute",
    "content": ". | Visit the Crowdin project. Open the Meshtastic Android Crowdin project and sign in or create a free account. | Choose your language. Select an existing language or request a new one by opening a GitHub issue. | Translate strings. Crowdin shows the English source on the left and your translation on the right. Translate each string and save. | Review context. Many strings include screenshots or context comments — check these to understand where the text appears in the app. A scheduled job pulls approved translations from Crowdin and opens a pull request; they ship once a maintainer merges it and a new build goes out. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/translate.html#how-to-contribute",
    
    "relUrl": "/lt-rLT/user/translate.html#how-to-contribute"
  },"5532": {
    "doc": "Translate the App",
    "title": "Adding a New Language",
    "content": "If your language is not yet listed on Crowdin: . | Open an issue on GitHub requesting the new locale. | A maintainer will add the language to Crowdin and configure crowdin.yml. | Once added, you can begin translating immediately. | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/translate.html#adding-a-new-language",
    
    "relUrl": "/lt-rLT/user/translate.html#adding-a-new-language"
  },"5533": {
    "doc": "Translate the App",
    "title": "How Translations Are Organized",
    "content": "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/ ├── en/user/ ← English source (default) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← French (France) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← German (Germany) │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. The app automatically selects the correct locale based on your phone’s Language & Region settings. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/translate.html#how-translations-are-organized",
    
    "relUrl": "/lt-rLT/user/translate.html#how-translations-are-organized"
  },"5534": {
    "doc": "Translate the App",
    "title": "Translation Guidelines",
    "content": ". | 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 phone’s language and open the app to see how translations look in context. | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/translate.html#translation-guidelines",
    
    "relUrl": "/lt-rLT/user/translate.html#translation-guidelines"
  },"5535": {
    "doc": "Translate the App",
    "title": "Questions?",
    "content": "If you have questions about a specific string’s context or need help getting started, open a discussion on the Meshtastic GitHub Discussions page. Thank you for helping expand the reach of Meshtastic. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/translate.html#questions",
    
    "relUrl": "/lt-rLT/user/translate.html#questions"
  },"5536": {
    "doc": "Translate the App",
    "title": "Related Topics",
    "content": ". | Units & Locale — how the app picks number, date, and unit formats for your region | Help & Documentation — the in-app docs browser these pages are published to | Onboarding — where a new user first meets the translated strings | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/translate.html#related-topics",
    
    "relUrl": "/lt-rLT/user/translate.html#related-topics"
  },"5537": {
    "doc": "Translate the App",
    "title": "Translate the App",
    "content": "The app and its in-app docs are translated on Crowdin — this page shows how to contribute. The app uses Crowdin to manage community translations for both the user interface and in-app documentation. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/translate.html",
    
    "relUrl": "/gl-rES/user/translate.html"
  },"5538": {
    "doc": "Translate the App",
    "title": "What Gets Translated",
    "content": "| Resource | Source Location | Notes | . | UI strings | core/resources/src/commonMain/composeResources/values/strings.xml | Buttons, labels, messages, and all user-visible text | . | User Guide pages | docs/en/user/*.md | In-app documentation shown in Help & Documentation | . | Fastlane metadata | fastlane/metadata/android/en-US/ | Google Play listing title, description, and changelogs | . ℹ️ Note: Developer Guide pages are English-only. Code-focused documentation targeting contributors is not translated. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/translate.html#what-gets-translated",
    
    "relUrl": "/gl-rES/user/translate.html#what-gets-translated"
  },"5539": {
    "doc": "Translate the App",
    "title": "How to Contribute",
    "content": ". | Visit the Crowdin project. Open the Meshtastic Android Crowdin project and sign in or create a free account. | Choose your language. Select an existing language or request a new one by opening a GitHub issue. | Translate strings. Crowdin shows the English source on the left and your translation on the right. Translate each string and save. | Review context. Many strings include screenshots or context comments — check these to understand where the text appears in the app. A scheduled job pulls approved translations from Crowdin and opens a pull request; they ship once a maintainer merges it and a new build goes out. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/translate.html#how-to-contribute",
    
    "relUrl": "/gl-rES/user/translate.html#how-to-contribute"
  },"5540": {
    "doc": "Translate the App",
    "title": "Adding a New Language",
    "content": "If your language is not yet listed on Crowdin: . | Open an issue on GitHub requesting the new locale. | A maintainer will add the language to Crowdin and configure crowdin.yml. | Once added, you can begin translating immediately. | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/translate.html#adding-a-new-language",
    
    "relUrl": "/gl-rES/user/translate.html#adding-a-new-language"
  },"5541": {
    "doc": "Translate the App",
    "title": "How Translations Are Organized",
    "content": "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/ ├── en/user/ ← English source (default) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← French (France) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← German (Germany) │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. The app automatically selects the correct locale based on your phone’s Language & Region settings. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/translate.html#how-translations-are-organized",
    
    "relUrl": "/gl-rES/user/translate.html#how-translations-are-organized"
  },"5542": {
    "doc": "Translate the App",
    "title": "Translation Guidelines",
    "content": ". | 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 phone’s language and open the app to see how translations look in context. | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/translate.html#translation-guidelines",
    
    "relUrl": "/gl-rES/user/translate.html#translation-guidelines"
  },"5543": {
    "doc": "Translate the App",
    "title": "Questions?",
    "content": "If you have questions about a specific string’s context or need help getting started, open a discussion on the Meshtastic GitHub Discussions page. Thank you for helping expand the reach of Meshtastic. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/translate.html#questions",
    
    "relUrl": "/gl-rES/user/translate.html#questions"
  },"5544": {
    "doc": "Translate the App",
    "title": "Related Topics",
    "content": ". | Units & Locale — how the app picks number, date, and unit formats for your region | Help & Documentation — the in-app docs browser these pages are published to | Onboarding — where a new user first meets the translated strings | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/translate.html#related-topics",
    
    "relUrl": "/gl-rES/user/translate.html#related-topics"
  },"5545": {
    "doc": "アプリを翻訳する",
    "title": "アプリを翻訳する",
    "content": "The app and its in-app docs are translated on Crowdin — this page shows how to contribute. アプリは、ユーザーインターフェースとアプリ内ドキュメントの両方のコミュニティ翻訳を管理するために Crowdin を使用しています。 . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/translate.html",
    
    "relUrl": "/ja-rJP/user/translate.html"
  },"5546": {
    "doc": "アプリを翻訳する",
    "title": "翻訳される対象",
    "content": "| リソース | ソースの場所 | 備考 | . | UI 文字列 | core/resources/src/commonMain/composeResources/values/strings.xml | ボタン、ラベル、メッセージ、およびユーザーに表示されるすべてのテキスト | . | ユーザーガイドのページ | docs/en/user/*.md | 「ヘルプとドキュメント」に表示されるアプリ内ドキュメント | . | Fastlane メタデータ | fastlane/metadata/android/en-US/ | Google Play listing title, description, and changelogs | . ℹ️ Note: Developer Guide pages are English-only. コントリビューター向けの、コード中心のドキュメントは翻訳されません。 . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/translate.html#%E7%BF%BB%E8%A8%B3%E3%81%95%E3%82%8C%E3%82%8B%E5%AF%BE%E8%B1%A1",
    
    "relUrl": "/ja-rJP/user/translate.html#翻訳される対象"
  },"5547": {
    "doc": "アプリを翻訳する",
    "title": "貢献する方法",
    "content": ". | Crowdin プロジェクトにアクセスします。 Meshtastic Android の Crowdin プロジェクト を開き、サインインするか、無料アカウントを作成します。 | 言語を選びます。 既存の言語を選択するか、GitHub の issue を作成して新しい言語をリクエストします。 | 文字列を翻訳します。 Crowdin では、左側に英語の原文、右側に自分の翻訳が表示されます。各文字列を翻訳して保存します。 | コンテキストを確認します。 多くの文字列には、スクリーンショットやコンテキストのコメントが含まれています。これらを確認して、テキストがアプリのどこに表示されるかを把握してください。 A scheduled job pulls approved translations from Crowdin and opens a pull request; they ship once a maintainer merges it and a new build goes out. | . 💡 ヒント： 翻訳は短くしてください。 UI 文字列は、ボタン、チップ、狭い列に表示されることがよくあります。翻訳が英語の原文よりも大幅に長くなる場合は、意味が明確なままになる範囲で短縮することを検討してください。 . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/translate.html#%E8%B2%A2%E7%8C%AE%E3%81%99%E3%82%8B%E6%96%B9%E6%B3%95",
    
    "relUrl": "/ja-rJP/user/translate.html#貢献する方法"
  },"5548": {
    "doc": "アプリを翻訳する",
    "title": "新しい言語を追加する",
    "content": "自分の言語がまだ Crowdin に掲載されていない場合： . | GitHub で issue を作成し、新しいロケールをリクエストします。 | メンテナーが Crowdin にその言語を追加し、crowdin.yml を設定します。 | 追加されたら、すぐに翻訳を始められます。 | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/translate.html#%E6%96%B0%E3%81%97%E3%81%84%E8%A8%80%E8%AA%9E%E3%82%92%E8%BF%BD%E5%8A%A0%E3%81%99%E3%82%8B",
    
    "relUrl": "/ja-rJP/user/translate.html#新しい言語を追加する"
  },"5549": {
    "doc": "アプリを翻訳する",
    "title": "翻訳の構成",
    "content": "Android アプリは、ユーザーに表示されるすべての文字列に Compose Multiplatform リソースを使用しています： . core/resources/src/commonMain/composeResources/ ├── values/ ← 英語（デフォルト） │ └── strings.xml ├── values-de/ ← ドイツ語 │ └── strings.xml ├── values-fr/ ← フランス語 │ └── strings.xml └── ... アプリ内ドキュメントも、docs/ の下で同様のパターンに従います： . docs/ ├── en/user/ ← 英語ソース（デフォルト） │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← フランス語（フランス） │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← ドイツ語（ドイツ） │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. The app automatically selects the correct locale based on your phone’s Language & Region settings. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/translate.html#%E7%BF%BB%E8%A8%B3%E3%81%AE%E6%A7%8B%E6%88%90",
    
    "relUrl": "/ja-rJP/user/translate.html#翻訳の構成"
  },"5550": {
    "doc": "アプリを翻訳する",
    "title": "翻訳ガイドライン",
    "content": ". | 「LoRa」「MQTT」「BLE」「TAK」「SNR」「RSSI」などの技術用語は翻訳しないでください。これらは共通です。 | プレースホルダーはそのまま保ちます。 %1$s や %d のような文字列は、実行時に値が埋め込まれます。自分の言語の文法上必要な場合を除き、削除したり並び替えたりしないでください。 | トーンを合わせます。 アプリは、親しみやすく率直な語り口を使っています。過度に堅い言葉は避けてください。 | Test if possible. Switch your phone’s language and open the app to see how translations look in context. | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/translate.html#%E7%BF%BB%E8%A8%B3%E3%82%AC%E3%82%A4%E3%83%89%E3%83%A9%E3%82%A4%E3%83%B3",
    
    "relUrl": "/ja-rJP/user/translate.html#翻訳ガイドライン"
  },"5551": {
    "doc": "アプリを翻訳する",
    "title": "質問がありますか？",
    "content": "特定の文字列のコンテキストについて質問がある場合や、始め方について助けが必要な場合は、Meshtastic GitHub Discussions のページでディスカッションを作成してください。 . Thank you for helping expand the reach of Meshtastic. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/translate.html#%E8%B3%AA%E5%95%8F%E3%81%8C%E3%81%82%E3%82%8A%E3%81%BE%E3%81%99%E3%81%8B",
    
    "relUrl": "/ja-rJP/user/translate.html#質問がありますか"
  },"5552": {
    "doc": "アプリを翻訳する",
    "title": "関連トピック",
    "content": ". | Units & Locale — how the app picks number, date, and unit formats for your region | Help & Documentation — the in-app docs browser these pages are published to | Onboarding — where a new user first meets the translated strings | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/translate.html#%E9%96%A2%E9%80%A3%E3%83%88%E3%83%94%E3%83%83%E3%82%AF",
    
    "relUrl": "/ja-rJP/user/translate.html#関連トピック"
  },"5553": {
    "doc": "Translate the App",
    "title": "Translate the App",
    "content": "The app and its in-app docs are translated on Crowdin — this page shows how to contribute. The app uses Crowdin to manage community translations for both the user interface and in-app documentation. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/translate.html",
    
    "relUrl": "/de-rDE/user/translate.html"
  },"5554": {
    "doc": "Translate the App",
    "title": "What Gets Translated",
    "content": "| Resource | Source Location | Knoten | . | UI strings | core/resources/src/commonMain/composeResources/values/strings.xml | Buttons, labels, messages, and all user-visible text | . | User Guide pages | docs/en/user/*.md | In-app documentation shown in Help & Documentation | . | Fastlane metadata | fastlane/metadata/android/en-US/ | Google Play listing title, description, and changelogs | . ℹ️ Note: Developer Guide pages are English-only. Code-focused documentation targeting contributors is not translated. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/translate.html#what-gets-translated",
    
    "relUrl": "/de-rDE/user/translate.html#what-gets-translated"
  },"5555": {
    "doc": "Translate the App",
    "title": "Wie man beitragen kann",
    "content": ". | Visit the Crowdin project. Open the Meshtastic Android Crowdin project and sign in or create a free account. | Choose your language. Select an existing language or request a new one by opening a GitHub issue. | Translate strings. Crowdin shows the English source on the left and your translation on the right. Translate each string and save. | Review context. Many strings include screenshots or context comments — check these to understand where the text appears in the app. A scheduled job pulls approved translations from Crowdin and opens a pull request; they ship once a maintainer merges it and a new build goes out. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/translate.html#wie-man-beitragen-kann",
    
    "relUrl": "/de-rDE/user/translate.html#wie-man-beitragen-kann"
  },"5556": {
    "doc": "Translate the App",
    "title": "Adding a New Language",
    "content": "If your language is not yet listed on Crowdin: . | Open an issue on GitHub requesting the new locale. | A maintainer will add the language to Crowdin and configure crowdin.yml. | Once added, you can begin translating immediately. | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/translate.html#adding-a-new-language",
    
    "relUrl": "/de-rDE/user/translate.html#adding-a-new-language"
  },"5557": {
    "doc": "Translate the App",
    "title": "How Translations Are Organized",
    "content": "The Android app uses Compose Multiplatform resources for all user-visible strings: . core/resources/src/commonMain/composeResources/ ├── values/ ← Englisch (Standard) │ └── strings.xml ├── values-de/ ← Deutsch │ └── strings.xml ├── values-fr/ ← Französisch │ └── strings.xml └── ... In-app documentation follows a similar pattern under docs/: . docs/ ├── en/user/ ← Englisch (Standard) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← Französisch (Frankreich) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← Deustch (Deutschland) │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. The app automatically selects the correct locale based on your phone’s Language & Region settings. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/translate.html#how-translations-are-organized",
    
    "relUrl": "/de-rDE/user/translate.html#how-translations-are-organized"
  },"5558": {
    "doc": "Translate the App",
    "title": "Translation Guidelines",
    "content": ". | 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 phone’s language and open the app to see how translations look in context. | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/translate.html#translation-guidelines",
    
    "relUrl": "/de-rDE/user/translate.html#translation-guidelines"
  },"5559": {
    "doc": "Translate the App",
    "title": "Questions?",
    "content": "If you have questions about a specific string’s context or need help getting started, open a discussion on the Meshtastic GitHub Discussions page. Thank you for helping expand the reach of Meshtastic. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/translate.html#questions",
    
    "relUrl": "/de-rDE/user/translate.html#questions"
  },"5560": {
    "doc": "Translate the App",
    "title": "Verwandte Themen",
    "content": ". | Units & Locale — how the app picks number, date, and unit formats for your region | Help & Documentation — the in-app docs browser these pages are published to | Onboarding — where a new user first meets the translated strings | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/translate.html#verwandte-themen",
    
    "relUrl": "/de-rDE/user/translate.html#verwandte-themen"
  },"5561": {
    "doc": "Translate the App",
    "title": "Translate the App",
    "content": "The app and its in-app docs are translated on Crowdin — this page shows how to contribute. The app uses Crowdin to manage community translations for both the user interface and in-app documentation. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/translate.html",
    
    "relUrl": "/ar-rSA/user/translate.html"
  },"5562": {
    "doc": "Translate the App",
    "title": "What Gets Translated",
    "content": "| Resource | Source Location | Notes | . | UI strings | core/resources/src/commonMain/composeResources/values/strings.xml | Buttons, labels, messages, and all user-visible text | . | User Guide pages | docs/en/user/*.md | In-app documentation shown in Help & Documentation | . | Fastlane metadata | fastlane/metadata/android/en-US/ | Google Play listing title, description, and changelogs | . ℹ️ Note: Developer Guide pages are English-only. Code-focused documentation targeting contributors is not translated. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/translate.html#what-gets-translated",
    
    "relUrl": "/ar-rSA/user/translate.html#what-gets-translated"
  },"5563": {
    "doc": "Translate the App",
    "title": "How to Contribute",
    "content": ". | Visit the Crowdin project. Open the Meshtastic Android Crowdin project and sign in or create a free account. | Choose your language. Select an existing language or request a new one by opening a GitHub issue. | Translate strings. Crowdin shows the English source on the left and your translation on the right. Translate each string and save. | Review context. Many strings include screenshots or context comments — check these to understand where the text appears in the app. A scheduled job pulls approved translations from Crowdin and opens a pull request; they ship once a maintainer merges it and a new build goes out. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/translate.html#how-to-contribute",
    
    "relUrl": "/ar-rSA/user/translate.html#how-to-contribute"
  },"5564": {
    "doc": "Translate the App",
    "title": "Adding a New Language",
    "content": "If your language is not yet listed on Crowdin: . | Open an issue on GitHub requesting the new locale. | A maintainer will add the language to Crowdin and configure crowdin.yml. | Once added, you can begin translating immediately. | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/translate.html#adding-a-new-language",
    
    "relUrl": "/ar-rSA/user/translate.html#adding-a-new-language"
  },"5565": {
    "doc": "Translate the App",
    "title": "How Translations Are Organized",
    "content": "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/ ├── en/user/ ← English source (default) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← French (France) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← German (Germany) │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. The app automatically selects the correct locale based on your phone’s Language & Region settings. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/translate.html#how-translations-are-organized",
    
    "relUrl": "/ar-rSA/user/translate.html#how-translations-are-organized"
  },"5566": {
    "doc": "Translate the App",
    "title": "Translation Guidelines",
    "content": ". | 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 phone’s language and open the app to see how translations look in context. | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/translate.html#translation-guidelines",
    
    "relUrl": "/ar-rSA/user/translate.html#translation-guidelines"
  },"5567": {
    "doc": "Translate the App",
    "title": "Questions?",
    "content": "If you have questions about a specific string’s context or need help getting started, open a discussion on the Meshtastic GitHub Discussions page. Thank you for helping expand the reach of Meshtastic. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/translate.html#questions",
    
    "relUrl": "/ar-rSA/user/translate.html#questions"
  },"5568": {
    "doc": "Translate the App",
    "title": "Related Topics",
    "content": ". | Units & Locale — how the app picks number, date, and unit formats for your region | Help & Documentation — the in-app docs browser these pages are published to | Onboarding — where a new user first meets the translated strings | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/translate.html#related-topics",
    
    "relUrl": "/ar-rSA/user/translate.html#related-topics"
  },"5569": {
    "doc": "Translate the App",
    "title": "Translate the App",
    "content": "The app and its in-app docs are translated on Crowdin — this page shows how to contribute. The app uses Crowdin to manage community translations for both the user interface and in-app documentation. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/translate.html",
    
    "relUrl": "/hr-rHR/user/translate.html"
  },"5570": {
    "doc": "Translate the App",
    "title": "What Gets Translated",
    "content": "| Resource | Source Location | Notes | . | UI strings | core/resources/src/commonMain/composeResources/values/strings.xml | Buttons, labels, messages, and all user-visible text | . | User Guide pages | docs/en/user/*.md | In-app documentation shown in Help & Documentation | . | Fastlane metadata | fastlane/metadata/android/en-US/ | Google Play listing title, description, and changelogs | . ℹ️ Note: Developer Guide pages are English-only. Code-focused documentation targeting contributors is not translated. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/translate.html#what-gets-translated",
    
    "relUrl": "/hr-rHR/user/translate.html#what-gets-translated"
  },"5571": {
    "doc": "Translate the App",
    "title": "How to Contribute",
    "content": ". | Visit the Crowdin project. Open the Meshtastic Android Crowdin project and sign in or create a free account. | Choose your language. Select an existing language or request a new one by opening a GitHub issue. | Translate strings. Crowdin shows the English source on the left and your translation on the right. Translate each string and save. | Review context. Many strings include screenshots or context comments — check these to understand where the text appears in the app. A scheduled job pulls approved translations from Crowdin and opens a pull request; they ship once a maintainer merges it and a new build goes out. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/translate.html#how-to-contribute",
    
    "relUrl": "/hr-rHR/user/translate.html#how-to-contribute"
  },"5572": {
    "doc": "Translate the App",
    "title": "Adding a New Language",
    "content": "If your language is not yet listed on Crowdin: . | Open an issue on GitHub requesting the new locale. | A maintainer will add the language to Crowdin and configure crowdin.yml. | Once added, you can begin translating immediately. | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/translate.html#adding-a-new-language",
    
    "relUrl": "/hr-rHR/user/translate.html#adding-a-new-language"
  },"5573": {
    "doc": "Translate the App",
    "title": "How Translations Are Organized",
    "content": "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/ ├── en/user/ ← English source (default) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← French (France) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← German (Germany) │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. The app automatically selects the correct locale based on your phone’s Language & Region settings. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/translate.html#how-translations-are-organized",
    
    "relUrl": "/hr-rHR/user/translate.html#how-translations-are-organized"
  },"5574": {
    "doc": "Translate the App",
    "title": "Translation Guidelines",
    "content": ". | 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 phone’s language and open the app to see how translations look in context. | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/translate.html#translation-guidelines",
    
    "relUrl": "/hr-rHR/user/translate.html#translation-guidelines"
  },"5575": {
    "doc": "Translate the App",
    "title": "Questions?",
    "content": "If you have questions about a specific string’s context or need help getting started, open a discussion on the Meshtastic GitHub Discussions page. Thank you for helping expand the reach of Meshtastic. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/translate.html#questions",
    
    "relUrl": "/hr-rHR/user/translate.html#questions"
  },"5576": {
    "doc": "Translate the App",
    "title": "Related Topics",
    "content": ". | Units & Locale — how the app picks number, date, and unit formats for your region | Help & Documentation — the in-app docs browser these pages are published to | Onboarding — where a new user first meets the translated strings | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/translate.html#related-topics",
    
    "relUrl": "/hr-rHR/user/translate.html#related-topics"
  },"5577": {
    "doc": "Translate the App",
    "title": "Translate the App",
    "content": "The app and its in-app docs are translated on Crowdin — this page shows how to contribute. The app uses Crowdin to manage community translations for both the user interface and in-app documentation. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/translate.html",
    
    "relUrl": "/pt-rPT/user/translate.html"
  },"5578": {
    "doc": "Translate the App",
    "title": "What Gets Translated",
    "content": "| Resource | Source Location | Notes | . | UI strings | core/resources/src/commonMain/composeResources/values/strings.xml | Buttons, labels, messages, and all user-visible text | . | User Guide pages | docs/en/user/*.md | In-app documentation shown in Help & Documentation | . | Fastlane metadata | fastlane/metadata/android/en-US/ | Google Play listing title, description, and changelogs | . ℹ️ Note: Developer Guide pages are English-only. Code-focused documentation targeting contributors is not translated. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/translate.html#what-gets-translated",
    
    "relUrl": "/pt-rPT/user/translate.html#what-gets-translated"
  },"5579": {
    "doc": "Translate the App",
    "title": "How to Contribute",
    "content": ". | Visit the Crowdin project. Open the Meshtastic Android Crowdin project and sign in or create a free account. | Choose your language. Select an existing language or request a new one by opening a GitHub issue. | Translate strings. Crowdin shows the English source on the left and your translation on the right. Translate each string and save. | Review context. Many strings include screenshots or context comments — check these to understand where the text appears in the app. A scheduled job pulls approved translations from Crowdin and opens a pull request; they ship once a maintainer merges it and a new build goes out. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/translate.html#how-to-contribute",
    
    "relUrl": "/pt-rPT/user/translate.html#how-to-contribute"
  },"5580": {
    "doc": "Translate the App",
    "title": "Adding a New Language",
    "content": "If your language is not yet listed on Crowdin: . | Open an issue on GitHub requesting the new locale. | A maintainer will add the language to Crowdin and configure crowdin.yml. | Once added, you can begin translating immediately. | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/translate.html#adding-a-new-language",
    
    "relUrl": "/pt-rPT/user/translate.html#adding-a-new-language"
  },"5581": {
    "doc": "Translate the App",
    "title": "How Translations Are Organized",
    "content": "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/ ├── en/user/ ← English source (default) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← French (France) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← German (Germany) │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. The app automatically selects the correct locale based on your phone’s Language & Region settings. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/translate.html#how-translations-are-organized",
    
    "relUrl": "/pt-rPT/user/translate.html#how-translations-are-organized"
  },"5582": {
    "doc": "Translate the App",
    "title": "Translation Guidelines",
    "content": ". | 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 phone’s language and open the app to see how translations look in context. | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/translate.html#translation-guidelines",
    
    "relUrl": "/pt-rPT/user/translate.html#translation-guidelines"
  },"5583": {
    "doc": "Translate the App",
    "title": "Questions?",
    "content": "If you have questions about a specific string’s context or need help getting started, open a discussion on the Meshtastic GitHub Discussions page. Thank you for helping expand the reach of Meshtastic. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/translate.html#questions",
    
    "relUrl": "/pt-rPT/user/translate.html#questions"
  },"5584": {
    "doc": "Translate the App",
    "title": "Related Topics",
    "content": ". | Units & Locale — how the app picks number, date, and unit formats for your region | Help & Documentation — the in-app docs browser these pages are published to | Onboarding — where a new user first meets the translated strings | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/translate.html#related-topics",
    
    "relUrl": "/pt-rPT/user/translate.html#related-topics"
  },"5585": {
    "doc": "Translate the App",
    "title": "Translate the App",
    "content": "The app and its in-app docs are translated on Crowdin — this page shows how to contribute. The app uses Crowdin to manage community translations for both the user interface and in-app documentation. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/translate.html",
    
    "relUrl": "/pl-rPL/user/translate.html"
  },"5586": {
    "doc": "Translate the App",
    "title": "What Gets Translated",
    "content": "| Resource | Source Location | Notatki | . | UI strings | core/resources/src/commonMain/composeResources/values/strings.xml | Buttons, labels, messages, and all user-visible text | . | User Guide pages | docs/en/user/*.md | In-app documentation shown in Help & Documentation | . | Fastlane metadata | fastlane/metadata/android/en-US/ | Google Play listing title, description, and changelogs | . ℹ️ Note: Developer Guide pages are English-only. Code-focused documentation targeting contributors is not translated. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/translate.html#what-gets-translated",
    
    "relUrl": "/pl-rPL/user/translate.html#what-gets-translated"
  },"5587": {
    "doc": "Translate the App",
    "title": "How to Contribute",
    "content": ". | Visit the Crowdin project. Open the Meshtastic Android Crowdin project and sign in or create a free account. | Choose your language. Select an existing language or request a new one by opening a GitHub issue. | Translate strings. Crowdin shows the English source on the left and your translation on the right. Translate each string and save. | Review context. Many strings include screenshots or context comments — check these to understand where the text appears in the app. A scheduled job pulls approved translations from Crowdin and opens a pull request; they ship once a maintainer merges it and a new build goes out. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/translate.html#how-to-contribute",
    
    "relUrl": "/pl-rPL/user/translate.html#how-to-contribute"
  },"5588": {
    "doc": "Translate the App",
    "title": "Adding a New Language",
    "content": "If your language is not yet listed on Crowdin: . | Open an issue on GitHub requesting the new locale. | A maintainer will add the language to Crowdin and configure crowdin.yml. | Once added, you can begin translating immediately. | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/translate.html#adding-a-new-language",
    
    "relUrl": "/pl-rPL/user/translate.html#adding-a-new-language"
  },"5589": {
    "doc": "Translate the App",
    "title": "How Translations Are Organized",
    "content": "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/ ├── en/user/ ← English source (default) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← French (France) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← German (Germany) │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. The app automatically selects the correct locale based on your phone’s Language & Region settings. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/translate.html#how-translations-are-organized",
    
    "relUrl": "/pl-rPL/user/translate.html#how-translations-are-organized"
  },"5590": {
    "doc": "Translate the App",
    "title": "Translation Guidelines",
    "content": ". | 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 phone’s language and open the app to see how translations look in context. | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/translate.html#translation-guidelines",
    
    "relUrl": "/pl-rPL/user/translate.html#translation-guidelines"
  },"5591": {
    "doc": "Translate the App",
    "title": "Questions?",
    "content": "If you have questions about a specific string’s context or need help getting started, open a discussion on the Meshtastic GitHub Discussions page. Thank you for helping expand the reach of Meshtastic. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/translate.html#questions",
    
    "relUrl": "/pl-rPL/user/translate.html#questions"
  },"5592": {
    "doc": "Translate the App",
    "title": "Related Topics",
    "content": ". | Units & Locale — how the app picks number, date, and unit formats for your region | Help & Documentation — the in-app docs browser these pages are published to | Onboarding — where a new user first meets the translated strings | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/translate.html#related-topics",
    
    "relUrl": "/pl-rPL/user/translate.html#related-topics"
  },"5593": {
    "doc": "Translate the App",
    "title": "Translate the App",
    "content": "The app and its in-app docs are translated on Crowdin — this page shows how to contribute. The app uses Crowdin to manage community translations for both the user interface and in-app documentation. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/translate.html",
    
    "relUrl": "/zh-rCN/user/translate.html"
  },"5594": {
    "doc": "Translate the App",
    "title": "What Gets Translated",
    "content": "| Resource | Source Location | 注 | . | UI strings | core/resources/src/commonMain/composeResources/values/strings.xml | Buttons, labels, messages, and all user-visible text | . | User Guide pages | docs/en/user/*.md | In-app documentation shown in Help & Documentation | . | Fastlane metadata | fastlane/metadata/android/en-US/ | Google Play listing title, description, and changelogs | . ℹ️ Note: Developer Guide pages are English-only. Code-focused documentation targeting contributors is not translated. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/translate.html#what-gets-translated",
    
    "relUrl": "/zh-rCN/user/translate.html#what-gets-translated"
  },"5595": {
    "doc": "Translate the App",
    "title": "How to Contribute",
    "content": ". | Visit the Crowdin project. Open the Meshtastic Android Crowdin project and sign in or create a free account. | Choose your language. Select an existing language or request a new one by opening a GitHub issue. | Translate strings. Crowdin shows the English source on the left and your translation on the right. Translate each string and save. | Review context. Many strings include screenshots or context comments — check these to understand where the text appears in the app. A scheduled job pulls approved translations from Crowdin and opens a pull request; they ship once a maintainer merges it and a new build goes out. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/translate.html#how-to-contribute",
    
    "relUrl": "/zh-rCN/user/translate.html#how-to-contribute"
  },"5596": {
    "doc": "Translate the App",
    "title": "Adding a New Language",
    "content": "If your language is not yet listed on Crowdin: . | Open an issue on GitHub requesting the new locale. | A maintainer will add the language to Crowdin and configure crowdin.yml. | Once added, you can begin translating immediately. | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/translate.html#adding-a-new-language",
    
    "relUrl": "/zh-rCN/user/translate.html#adding-a-new-language"
  },"5597": {
    "doc": "Translate the App",
    "title": "How Translations Are Organized",
    "content": "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/ ├── en/user/ ← English source (default) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← French (France) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← German (Germany) │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. The app automatically selects the correct locale based on your phone’s Language & Region settings. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/translate.html#how-translations-are-organized",
    
    "relUrl": "/zh-rCN/user/translate.html#how-translations-are-organized"
  },"5598": {
    "doc": "Translate the App",
    "title": "Translation Guidelines",
    "content": ". | 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 phone’s language and open the app to see how translations look in context. | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/translate.html#translation-guidelines",
    
    "relUrl": "/zh-rCN/user/translate.html#translation-guidelines"
  },"5599": {
    "doc": "Translate the App",
    "title": "Questions?",
    "content": "If you have questions about a specific string’s context or need help getting started, open a discussion on the Meshtastic GitHub Discussions page. Thank you for helping expand the reach of Meshtastic. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/translate.html#questions",
    
    "relUrl": "/zh-rCN/user/translate.html#questions"
  },"5600": {
    "doc": "Translate the App",
    "title": "Related Topics",
    "content": ". | Units & Locale — how the app picks number, date, and unit formats for your region | Help & Documentation — the in-app docs browser these pages are published to | Onboarding — where a new user first meets the translated strings | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/translate.html#related-topics",
    
    "relUrl": "/zh-rCN/user/translate.html#related-topics"
  },"5601": {
    "doc": "Translate the App",
    "title": "Translate the App",
    "content": "The app and its in-app docs are translated on Crowdin — this page shows how to contribute. The app uses Crowdin to manage community translations for both the user interface and in-app documentation. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/translate.html",
    
    "relUrl": "/sq-rAL/user/translate.html"
  },"5602": {
    "doc": "Translate the App",
    "title": "What Gets Translated",
    "content": "| Resource | Source Location | Notes | . | UI strings | core/resources/src/commonMain/composeResources/values/strings.xml | Buttons, labels, messages, and all user-visible text | . | User Guide pages | docs/en/user/*.md | In-app documentation shown in Help & Documentation | . | Fastlane metadata | fastlane/metadata/android/en-US/ | Google Play listing title, description, and changelogs | . ℹ️ Note: Developer Guide pages are English-only. Code-focused documentation targeting contributors is not translated. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/translate.html#what-gets-translated",
    
    "relUrl": "/sq-rAL/user/translate.html#what-gets-translated"
  },"5603": {
    "doc": "Translate the App",
    "title": "How to Contribute",
    "content": ". | Visit the Crowdin project. Open the Meshtastic Android Crowdin project and sign in or create a free account. | Choose your language. Select an existing language or request a new one by opening a GitHub issue. | Translate strings. Crowdin shows the English source on the left and your translation on the right. Translate each string and save. | Review context. Many strings include screenshots or context comments — check these to understand where the text appears in the app. A scheduled job pulls approved translations from Crowdin and opens a pull request; they ship once a maintainer merges it and a new build goes out. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/translate.html#how-to-contribute",
    
    "relUrl": "/sq-rAL/user/translate.html#how-to-contribute"
  },"5604": {
    "doc": "Translate the App",
    "title": "Adding a New Language",
    "content": "If your language is not yet listed on Crowdin: . | Open an issue on GitHub requesting the new locale. | A maintainer will add the language to Crowdin and configure crowdin.yml. | Once added, you can begin translating immediately. | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/translate.html#adding-a-new-language",
    
    "relUrl": "/sq-rAL/user/translate.html#adding-a-new-language"
  },"5605": {
    "doc": "Translate the App",
    "title": "How Translations Are Organized",
    "content": "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/ ├── en/user/ ← English source (default) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← French (France) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← German (Germany) │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. The app automatically selects the correct locale based on your phone’s Language & Region settings. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/translate.html#how-translations-are-organized",
    
    "relUrl": "/sq-rAL/user/translate.html#how-translations-are-organized"
  },"5606": {
    "doc": "Translate the App",
    "title": "Translation Guidelines",
    "content": ". | 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 phone’s language and open the app to see how translations look in context. | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/translate.html#translation-guidelines",
    
    "relUrl": "/sq-rAL/user/translate.html#translation-guidelines"
  },"5607": {
    "doc": "Translate the App",
    "title": "Questions?",
    "content": "If you have questions about a specific string’s context or need help getting started, open a discussion on the Meshtastic GitHub Discussions page. Thank you for helping expand the reach of Meshtastic. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/translate.html#questions",
    
    "relUrl": "/sq-rAL/user/translate.html#questions"
  },"5608": {
    "doc": "Translate the App",
    "title": "Related Topics",
    "content": ". | Units & Locale — how the app picks number, date, and unit formats for your region | Help & Documentation — the in-app docs browser these pages are published to | Onboarding — where a new user first meets the translated strings | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/translate.html#related-topics",
    
    "relUrl": "/sq-rAL/user/translate.html#related-topics"
  },"5609": {
    "doc": "Translate the App",
    "title": "Translate the App",
    "content": "The app and its in-app docs are translated on Crowdin — this page shows how to contribute. The app uses Crowdin to manage community translations for both the user interface and in-app documentation. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/translate.html",
    
    "relUrl": "/zh-rTW/user/translate.html"
  },"5610": {
    "doc": "Translate the App",
    "title": "What Gets Translated",
    "content": "| Resource | Source Location | 備註 | . | UI strings | core/resources/src/commonMain/composeResources/values/strings.xml | Buttons, labels, messages, and all user-visible text | . | User Guide pages | docs/en/user/*.md | In-app documentation shown in Help & Documentation | . | Fastlane metadata | fastlane/metadata/android/en-US/ | Google Play listing title, description, and changelogs | . ℹ️ Note: Developer Guide pages are English-only. Code-focused documentation targeting contributors is not translated. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/translate.html#what-gets-translated",
    
    "relUrl": "/zh-rTW/user/translate.html#what-gets-translated"
  },"5611": {
    "doc": "Translate the App",
    "title": "如何貢獻",
    "content": ". | Visit the Crowdin project. Open the Meshtastic Android Crowdin project and sign in or create a free account. | Choose your language. Select an existing language or request a new one by opening a GitHub issue. | Translate strings. Crowdin shows the English source on the left and your translation on the right. Translate each string and save. | Review context. Many strings include screenshots or context comments — check these to understand where the text appears in the app. A scheduled job pulls approved translations from Crowdin and opens a pull request; they ship once a maintainer merges it and a new build goes out. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/translate.html#%E5%A6%82%E4%BD%95%E8%B2%A2%E7%8D%BB",
    
    "relUrl": "/zh-rTW/user/translate.html#如何貢獻"
  },"5612": {
    "doc": "Translate the App",
    "title": "Adding a New Language",
    "content": "If your language is not yet listed on Crowdin: . | Open an issue on GitHub requesting the new locale. | A maintainer will add the language to Crowdin and configure crowdin.yml. | Once added, you can begin translating immediately. | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/translate.html#adding-a-new-language",
    
    "relUrl": "/zh-rTW/user/translate.html#adding-a-new-language"
  },"5613": {
    "doc": "Translate the App",
    "title": "How Translations Are Organized",
    "content": "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/ ├── en/user/ ← English source (default) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← French (France) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← German (Germany) │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. The app automatically selects the correct locale based on your phone’s Language & Region settings. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/translate.html#how-translations-are-organized",
    
    "relUrl": "/zh-rTW/user/translate.html#how-translations-are-organized"
  },"5614": {
    "doc": "Translate the App",
    "title": "Translation Guidelines",
    "content": ". | 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 phone’s language and open the app to see how translations look in context. | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/translate.html#translation-guidelines",
    
    "relUrl": "/zh-rTW/user/translate.html#translation-guidelines"
  },"5615": {
    "doc": "Translate the App",
    "title": "Questions?",
    "content": "If you have questions about a specific string’s context or need help getting started, open a discussion on the Meshtastic GitHub Discussions page. Thank you for helping expand the reach of Meshtastic. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/translate.html#questions",
    
    "relUrl": "/zh-rTW/user/translate.html#questions"
  },"5616": {
    "doc": "Translate the App",
    "title": "相關主題",
    "content": ". | Units & Locale — how the app picks number, date, and unit formats for your region | Help & Documentation — the in-app docs browser these pages are published to | Onboarding — where a new user first meets the translated strings | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/translate.html#%E7%9B%B8%E9%97%9C%E4%B8%BB%E9%A1%8C",
    
    "relUrl": "/zh-rTW/user/translate.html#相關主題"
  },"5617": {
    "doc": "Tõlgi rakendus",
    "title": "Tõlgi rakendus",
    "content": "The app and its in-app docs are translated on Crowdin — this page shows how to contribute. Rakendus kasutab nii kasutajaliidese kui ka rakendusesisese dokumentatsiooni kogukonna tõlgete haldamiseks Crowdinit. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/translate.html",
    
    "relUrl": "/et-rEE/user/translate.html"
  },"5618": {
    "doc": "Tõlgi rakendus",
    "title": "Mida tõlgitakse",
    "content": "| Resource | Allika asukoht | Sõnumid | . | UI strings | core/resources/src/commonMain/composeResources/values/strings.xml | Nupud, sildid, sõnumid ja kogu kasutajale nähtav tekst | . | Kasutusjuhendi lehed | docs/en/user/*.md | Rakendusesisene dokumentatsioon kuvatakse jaotises Abi ja dokumentatsioon | . | Fastlane metadata | fastlane/metadata/android/en-US/ | Google Play listing title, description, and changelogs | . ℹ️ Note: Developer Guide pages are English-only. Kaastöölistele suunatud koodikeskset dokumentatsiooni ei tõlgita. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/translate.html#mida-t%C3%B5lgitakse",
    
    "relUrl": "/et-rEE/user/translate.html#mida-tõlgitakse"
  },"5619": {
    "doc": "Tõlgi rakendus",
    "title": "How to Contribute",
    "content": ". | Külasta Crowdini projekti. Ava Meshtastic Android Crowdini projekt ja logi sisse või loo tasuta konto. | Vali keel. Vali olemasolev keel või taotle uut, avades GitHubi probleemi. | Tõlgi stringe. Crowdin kuvab ingliskeelse allika vasakul ja sinu tõlke paremal. Tõlki iga string ja salvesta. | Review context. Many strings include screenshots or context comments — check these to understand where the text appears in the app. A scheduled job pulls approved translations from Crowdin and opens a pull request; they ship once a maintainer merges it and a new build goes out. | . 💡 **Vihje.” Hoia tõlked lühikesed. UI strings often appear in buttons, chips, or narrow columns. Kui tõlge on oluliselt pikem kui ingliskeelne originaal, kaaluge lühendamist kohtades, kus tähendus jääb selgeks. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/translate.html#how-to-contribute",
    
    "relUrl": "/et-rEE/user/translate.html#how-to-contribute"
  },"5620": {
    "doc": "Tõlgi rakendus",
    "title": "Lisa uus keel",
    "content": "Kui teie keelt Crowdinis veel pole: . | Ava probleem GitHubis ja taotle uut lokaati. | Hooldaja lisab keele Crowdinile ja seadistab faili crowdin.yml. | Pärast lisamist saad kohe tõlkima hakata. | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/translate.html#lisa-uus-keel",
    
    "relUrl": "/et-rEE/user/translate.html#lisa-uus-keel"
  },"5621": {
    "doc": "Tõlgi rakendus",
    "title": "How Translations Are Organized",
    "content": "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 └── ... Rakendusesisene dokumentatsioon järgib sarnast mustrit jaotises docs/: . docs/ ├── en/user/ ← English source (default) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← French (France) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← German (Germany) │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. The app automatically selects the correct locale based on your phone’s Language & Region settings. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/translate.html#how-translations-are-organized",
    
    "relUrl": "/et-rEE/user/translate.html#how-translations-are-organized"
  },"5622": {
    "doc": "Tõlgi rakendus",
    "title": "Translation Guidelines",
    "content": ". | Ära tõlgi tehnilisi termineid nagu “LoRa”, “MQTT”, “BLE”, “TAK”, “SNR”, or “RSSI” — need on universaalsed. | Jäta kohatäited puutumata. Stringid nagu %1$s või %d täidetakse käitusajal. 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 phone’s language and open the app to see how translations look in context. | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/translate.html#translation-guidelines",
    
    "relUrl": "/et-rEE/user/translate.html#translation-guidelines"
  },"5623": {
    "doc": "Tõlgi rakendus",
    "title": "Küsimusi?",
    "content": "Kui on küsimusi konkreetse stringi konteksti kohta või vajad abi alustamiseks, ava arutelu lehel Meshtastic GitHub Discussions. Thank you for helping expand the reach of Meshtastic. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/translate.html#k%C3%BCsimusi",
    
    "relUrl": "/et-rEE/user/translate.html#küsimusi"
  },"5624": {
    "doc": "Tõlgi rakendus",
    "title": "Seotud teemad",
    "content": ". | Units & Locale — how the app picks number, date, and unit formats for your region | Help & Documentation — the in-app docs browser these pages are published to | Onboarding — where a new user first meets the translated strings | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/translate.html#seotud-teemad",
    
    "relUrl": "/et-rEE/user/translate.html#seotud-teemad"
  },"5625": {
    "doc": "Translate the App",
    "title": "Translate the App",
    "content": "The app and its in-app docs are translated on Crowdin — this page shows how to contribute. The app uses Crowdin to manage community translations for both the user interface and in-app documentation. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/translate.html",
    
    "relUrl": "/fr-rFR/user/translate.html"
  },"5626": {
    "doc": "Translate the App",
    "title": "Ce qui est traduit",
    "content": "| Ressource | Emplacement de la source | Notes | . | Chaînes UI | core/resources/src/commonMain/composeResources/values/strings.xml | Boutons, étiquettes, messages et tout texte visible par l’utilisateur | . | Pages du Guide de l’utilisateur | docs/en/user/*.md | Documentation dans l’application affichée dans Aide et Documentation | . | Métadonnées Fastlane | fastlane/metadata/android/fr-FR/ | Google Play listing title, description, and changelogs | . ℹ️ Note: Developer Guide pages are English-only. Code-focused documentation targeting contributors is not translated. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/translate.html#ce-qui-est-traduit",
    
    "relUrl": "/fr-rFR/user/translate.html#ce-qui-est-traduit"
  },"5627": {
    "doc": "Translate the App",
    "title": "Comment contribuer",
    "content": ". | Visitez le projet Crowdin. Ouvrez le projet Meshtastic Android Crowdin et connectez-vous ou créez un compte gratuit. | Choisissez votre langue. Sélectionnez une langue existante ou demandez-en une nouvelle en ouvrant un problème GitHub. | Traductions Crowdin montre la source anglaise à gauche et votre traduction à droite. Traduisez chaque portion et sauvegardez. | Vérifier le contexte. De nombreuses portions incluent des captures d’écran ou des commentaires de contexte — cochez celles-ci pour comprendre où le texte apparaît dans l’application. A scheduled job pulls approved translations from Crowdin and opens a pull request; they ship once a maintainer merges it and a new build goes out. | . 💡 Tip: Keep translations short. UI strings often appear in buttons, chips, or narrow columns. Si une traduction est considérablement plus longue que l’original anglais, pensez à abréger en conservant la signification claire. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/translate.html#comment-contribuer",
    
    "relUrl": "/fr-rFR/user/translate.html#comment-contribuer"
  },"5628": {
    "doc": "Translate the App",
    "title": "Ajouter une nouvelle langue",
    "content": "Si votre langue n’est pas encore listée sur Crowdin : . | Ouvrir un ticket sur GitHub demandant la nouvelle langue. | Un responsable ajoutera la langue à Crowdin et configurera crowdin.yml. | Une fois ajouté, vous pouvez commencer à traduire immédiatement. | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/translate.html#ajouter-une-nouvelle-langue",
    
    "relUrl": "/fr-rFR/user/translate.html#ajouter-une-nouvelle-langue"
  },"5629": {
    "doc": "Translate the App",
    "title": "Comment sont organisées les traductions",
    "content": "L’application Android utilise des Ressources Multiplateforme pour tous les textes visibles par l’utilisateur: . core/resources/src/commonMain/composeResources/ ├── values/ ← English (default) │ └── strings.xml ├── values-de/ ← German │ └── strings.xml ├── values-fr/ ← French │ └── strings.xml └── ... La documentation dans l’application suit un modèle similaire dans docs/: . docs/ ├── en/user/ ← English source (default) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← French (France) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← German (Germany) │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. The app automatically selects the correct locale based on your phone’s Language & Region settings. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/translate.html#comment-sont-organis%C3%A9es-les-traductions",
    
    "relUrl": "/fr-rFR/user/translate.html#comment-sont-organisées-les-traductions"
  },"5630": {
    "doc": "Translate the App",
    "title": "Directives de Traduction",
    "content": ". | Ne traduisez pas des termes techniques tels que “LoRa”, “MQTT”, “BLE”, “TAK”, “SNR”, ou “RSSI” — ce sont des termes universels. | Garder les espaces réservés intact. Les chaînes comme %1$s ou %d sont remplies au moment de l’exécution. Ne les supprimez ni ne les réordonnez pas à moins que la grammaire de votre langue ne l’exige. | Respectez le ton L’application utilise un ton amical Évitez des formulations trop formelles | Test if possible. Switch your phone’s language and open the app to see how translations look in context. | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/translate.html#directives-de-traduction",
    
    "relUrl": "/fr-rFR/user/translate.html#directives-de-traduction"
  },"5631": {
    "doc": "Translate the App",
    "title": "Des questions ?",
    "content": "If you have questions about a specific string’s context or need help getting started, open a discussion on the Meshtastic GitHub Discussions page. Thank you for helping expand the reach of Meshtastic. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/translate.html#des-questions",
    
    "relUrl": "/fr-rFR/user/translate.html#des-questions"
  },"5632": {
    "doc": "Translate the App",
    "title": "Related Topics",
    "content": ". | Units & Locale — how the app picks number, date, and unit formats for your region | Help & Documentation — the in-app docs browser these pages are published to | Onboarding — where a new user first meets the translated strings | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/translate.html#related-topics",
    
    "relUrl": "/fr-rFR/user/translate.html#related-topics"
  },"5633": {
    "doc": "Translate the App",
    "title": "Translate the App",
    "content": "The app and its in-app docs are translated on Crowdin — this page shows how to contribute. The app uses Crowdin to manage community translations for both the user interface and in-app documentation. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/translate.html",
    
    "relUrl": "/tr-rTR/user/translate.html"
  },"5634": {
    "doc": "Translate the App",
    "title": "What Gets Translated",
    "content": "| Resource | Source Location | Notes | . | UI strings | core/resources/src/commonMain/composeResources/values/strings.xml | Buttons, labels, messages, and all user-visible text | . | User Guide pages | docs/en/user/*.md | In-app documentation shown in Help & Documentation | . | Fastlane metadata | fastlane/metadata/android/en-US/ | Google Play listing title, description, and changelogs | . ℹ️ Note: Developer Guide pages are English-only. Code-focused documentation targeting contributors is not translated. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/translate.html#what-gets-translated",
    
    "relUrl": "/tr-rTR/user/translate.html#what-gets-translated"
  },"5635": {
    "doc": "Translate the App",
    "title": "Nasıl Katkıda Bulunulur",
    "content": ". | Visit the Crowdin project. Open the Meshtastic Android Crowdin project and sign in or create a free account. | Choose your language. Select an existing language or request a new one by opening a GitHub issue. | Translate strings. Crowdin shows the English source on the left and your translation on the right. Translate each string and save. | Review context. Many strings include screenshots or context comments — check these to understand where the text appears in the app. A scheduled job pulls approved translations from Crowdin and opens a pull request; they ship once a maintainer merges it and a new build goes out. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/translate.html#nas%C4%B1l-katk%C4%B1da-bulunulur",
    
    "relUrl": "/tr-rTR/user/translate.html#nasıl-katkıda-bulunulur"
  },"5636": {
    "doc": "Translate the App",
    "title": "Adding a New Language",
    "content": "If your language is not yet listed on Crowdin: . | Open an issue on GitHub requesting the new locale. | A maintainer will add the language to Crowdin and configure crowdin.yml. | Once added, you can begin translating immediately. | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/translate.html#adding-a-new-language",
    
    "relUrl": "/tr-rTR/user/translate.html#adding-a-new-language"
  },"5637": {
    "doc": "Translate the App",
    "title": "How Translations Are Organized",
    "content": "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/ ├── en/user/ ← English source (default) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← French (France) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← German (Germany) │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. The app automatically selects the correct locale based on your phone’s Language & Region settings. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/translate.html#how-translations-are-organized",
    
    "relUrl": "/tr-rTR/user/translate.html#how-translations-are-organized"
  },"5638": {
    "doc": "Translate the App",
    "title": "Translation Guidelines",
    "content": ". | 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 phone’s language and open the app to see how translations look in context. | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/translate.html#translation-guidelines",
    
    "relUrl": "/tr-rTR/user/translate.html#translation-guidelines"
  },"5639": {
    "doc": "Translate the App",
    "title": "Questions?",
    "content": "If you have questions about a specific string’s context or need help getting started, open a discussion on the Meshtastic GitHub Discussions page. Thank you for helping expand the reach of Meshtastic. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/translate.html#questions",
    
    "relUrl": "/tr-rTR/user/translate.html#questions"
  },"5640": {
    "doc": "Translate the App",
    "title": "Related Topics",
    "content": ". | Units & Locale — how the app picks number, date, and unit formats for your region | Help & Documentation — the in-app docs browser these pages are published to | Onboarding — where a new user first meets the translated strings | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/translate.html#related-topics",
    
    "relUrl": "/tr-rTR/user/translate.html#related-topics"
  },"5641": {
    "doc": "Translate the App",
    "title": "Translate the App",
    "content": "The app and its in-app docs are translated on Crowdin — this page shows how to contribute. The app uses Crowdin to manage community translations for both the user interface and in-app documentation. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/translate.html",
    
    "relUrl": "/el-rGR/user/translate.html"
  },"5642": {
    "doc": "Translate the App",
    "title": "What Gets Translated",
    "content": "| Resource | Source Location | Notes | . | UI strings | core/resources/src/commonMain/composeResources/values/strings.xml | Buttons, labels, messages, and all user-visible text | . | User Guide pages | docs/en/user/*.md | In-app documentation shown in Help & Documentation | . | Fastlane metadata | fastlane/metadata/android/en-US/ | Google Play listing title, description, and changelogs | . ℹ️ Note: Developer Guide pages are English-only. Code-focused documentation targeting contributors is not translated. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/translate.html#what-gets-translated",
    
    "relUrl": "/el-rGR/user/translate.html#what-gets-translated"
  },"5643": {
    "doc": "Translate the App",
    "title": "How to Contribute",
    "content": ". | Visit the Crowdin project. Open the Meshtastic Android Crowdin project and sign in or create a free account. | Choose your language. Select an existing language or request a new one by opening a GitHub issue. | Translate strings. Crowdin shows the English source on the left and your translation on the right. Translate each string and save. | Review context. Many strings include screenshots or context comments — check these to understand where the text appears in the app. A scheduled job pulls approved translations from Crowdin and opens a pull request; they ship once a maintainer merges it and a new build goes out. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/translate.html#how-to-contribute",
    
    "relUrl": "/el-rGR/user/translate.html#how-to-contribute"
  },"5644": {
    "doc": "Translate the App",
    "title": "Adding a New Language",
    "content": "If your language is not yet listed on Crowdin: . | Open an issue on GitHub requesting the new locale. | A maintainer will add the language to Crowdin and configure crowdin.yml. | Once added, you can begin translating immediately. | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/translate.html#adding-a-new-language",
    
    "relUrl": "/el-rGR/user/translate.html#adding-a-new-language"
  },"5645": {
    "doc": "Translate the App",
    "title": "How Translations Are Organized",
    "content": "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/ ├── en/user/ ← English source (default) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← French (France) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← German (Germany) │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. The app automatically selects the correct locale based on your phone’s Language & Region settings. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/translate.html#how-translations-are-organized",
    
    "relUrl": "/el-rGR/user/translate.html#how-translations-are-organized"
  },"5646": {
    "doc": "Translate the App",
    "title": "Translation Guidelines",
    "content": ". | 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 phone’s language and open the app to see how translations look in context. | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/translate.html#translation-guidelines",
    
    "relUrl": "/el-rGR/user/translate.html#translation-guidelines"
  },"5647": {
    "doc": "Translate the App",
    "title": "Questions?",
    "content": "If you have questions about a specific string’s context or need help getting started, open a discussion on the Meshtastic GitHub Discussions page. Thank you for helping expand the reach of Meshtastic. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/translate.html#questions",
    
    "relUrl": "/el-rGR/user/translate.html#questions"
  },"5648": {
    "doc": "Translate the App",
    "title": "Related Topics",
    "content": ". | Units & Locale — how the app picks number, date, and unit formats for your region | Help & Documentation — the in-app docs browser these pages are published to | Onboarding — where a new user first meets the translated strings | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/translate.html#related-topics",
    
    "relUrl": "/el-rGR/user/translate.html#related-topics"
  },"5649": {
    "doc": "Translate the App",
    "title": "Translate the App",
    "content": "The app and its in-app docs are translated on Crowdin — this page shows how to contribute. The app uses Crowdin to manage community translations for both the user interface and in-app documentation. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/translate.html",
    
    "relUrl": "/ro-rRO/user/translate.html"
  },"5650": {
    "doc": "Translate the App",
    "title": "What Gets Translated",
    "content": "| Resource | Source Location | Notițe | . | UI strings | core/resources/src/commonMain/composeResources/values/strings.xml | Buttons, labels, messages, and all user-visible text | . | User Guide pages | docs/en/user/*.md | In-app documentation shown in Help & Documentation | . | Fastlane metadata | fastlane/metadata/android/en-US/ | Google Play listing title, description, and changelogs | . ℹ️ Note: Developer Guide pages are English-only. Code-focused documentation targeting contributors is not translated. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/translate.html#what-gets-translated",
    
    "relUrl": "/ro-rRO/user/translate.html#what-gets-translated"
  },"5651": {
    "doc": "Translate the App",
    "title": "How to Contribute",
    "content": ". | Visit the Crowdin project. Open the Meshtastic Android Crowdin project and sign in or create a free account. | Choose your language. Select an existing language or request a new one by opening a GitHub issue. | Translate strings. Crowdin shows the English source on the left and your translation on the right. Translate each string and save. | Review context. Many strings include screenshots or context comments — check these to understand where the text appears in the app. A scheduled job pulls approved translations from Crowdin and opens a pull request; they ship once a maintainer merges it and a new build goes out. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/translate.html#how-to-contribute",
    
    "relUrl": "/ro-rRO/user/translate.html#how-to-contribute"
  },"5652": {
    "doc": "Translate the App",
    "title": "Adding a New Language",
    "content": "If your language is not yet listed on Crowdin: . | Open an issue on GitHub requesting the new locale. | A maintainer will add the language to Crowdin and configure crowdin.yml. | Once added, you can begin translating immediately. | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/translate.html#adding-a-new-language",
    
    "relUrl": "/ro-rRO/user/translate.html#adding-a-new-language"
  },"5653": {
    "doc": "Translate the App",
    "title": "How Translations Are Organized",
    "content": "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/ ├── en/user/ ← English source (default) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← French (France) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← German (Germany) │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. The app automatically selects the correct locale based on your phone’s Language & Region settings. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/translate.html#how-translations-are-organized",
    
    "relUrl": "/ro-rRO/user/translate.html#how-translations-are-organized"
  },"5654": {
    "doc": "Translate the App",
    "title": "Translation Guidelines",
    "content": ". | 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 phone’s language and open the app to see how translations look in context. | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/translate.html#translation-guidelines",
    
    "relUrl": "/ro-rRO/user/translate.html#translation-guidelines"
  },"5655": {
    "doc": "Translate the App",
    "title": "Questions?",
    "content": "If you have questions about a specific string’s context or need help getting started, open a discussion on the Meshtastic GitHub Discussions page. Thank you for helping expand the reach of Meshtastic. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/translate.html#questions",
    
    "relUrl": "/ro-rRO/user/translate.html#questions"
  },"5656": {
    "doc": "Translate the App",
    "title": "Related Topics",
    "content": ". | Units & Locale — how the app picks number, date, and unit formats for your region | Help & Documentation — the in-app docs browser these pages are published to | Onboarding — where a new user first meets the translated strings | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/translate.html#related-topics",
    
    "relUrl": "/ro-rRO/user/translate.html#related-topics"
  },"5657": {
    "doc": "Translate the App",
    "title": "Translate the App",
    "content": "The app and its in-app docs are translated on Crowdin — this page shows how to contribute. The app uses Crowdin to manage community translations for both the user interface and in-app documentation. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/translate.html",
    
    "relUrl": "/iw-rIL/user/translate.html"
  },"5658": {
    "doc": "Translate the App",
    "title": "What Gets Translated",
    "content": "| Resource | Source Location | Notes | . | UI strings | core/resources/src/commonMain/composeResources/values/strings.xml | Buttons, labels, messages, and all user-visible text | . | User Guide pages | docs/en/user/*.md | In-app documentation shown in Help & Documentation | . | Fastlane metadata | fastlane/metadata/android/en-US/ | Google Play listing title, description, and changelogs | . ℹ️ Note: Developer Guide pages are English-only. Code-focused documentation targeting contributors is not translated. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/translate.html#what-gets-translated",
    
    "relUrl": "/iw-rIL/user/translate.html#what-gets-translated"
  },"5659": {
    "doc": "Translate the App",
    "title": "How to Contribute",
    "content": ". | Visit the Crowdin project. Open the Meshtastic Android Crowdin project and sign in or create a free account. | Choose your language. Select an existing language or request a new one by opening a GitHub issue. | Translate strings. Crowdin shows the English source on the left and your translation on the right. Translate each string and save. | Review context. Many strings include screenshots or context comments — check these to understand where the text appears in the app. A scheduled job pulls approved translations from Crowdin and opens a pull request; they ship once a maintainer merges it and a new build goes out. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/translate.html#how-to-contribute",
    
    "relUrl": "/iw-rIL/user/translate.html#how-to-contribute"
  },"5660": {
    "doc": "Translate the App",
    "title": "Adding a New Language",
    "content": "If your language is not yet listed on Crowdin: . | Open an issue on GitHub requesting the new locale. | A maintainer will add the language to Crowdin and configure crowdin.yml. | Once added, you can begin translating immediately. | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/translate.html#adding-a-new-language",
    
    "relUrl": "/iw-rIL/user/translate.html#adding-a-new-language"
  },"5661": {
    "doc": "Translate the App",
    "title": "How Translations Are Organized",
    "content": "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/ ├── en/user/ ← English source (default) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← French (France) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← German (Germany) │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. The app automatically selects the correct locale based on your phone’s Language & Region settings. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/translate.html#how-translations-are-organized",
    
    "relUrl": "/iw-rIL/user/translate.html#how-translations-are-organized"
  },"5662": {
    "doc": "Translate the App",
    "title": "Translation Guidelines",
    "content": ". | 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 phone’s language and open the app to see how translations look in context. | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/translate.html#translation-guidelines",
    
    "relUrl": "/iw-rIL/user/translate.html#translation-guidelines"
  },"5663": {
    "doc": "Translate the App",
    "title": "Questions?",
    "content": "If you have questions about a specific string’s context or need help getting started, open a discussion on the Meshtastic GitHub Discussions page. Thank you for helping expand the reach of Meshtastic. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/translate.html#questions",
    
    "relUrl": "/iw-rIL/user/translate.html#questions"
  },"5664": {
    "doc": "Translate the App",
    "title": "Related Topics",
    "content": ". | Units & Locale — how the app picks number, date, and unit formats for your region | Help & Documentation — the in-app docs browser these pages are published to | Onboarding — where a new user first meets the translated strings | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/translate.html#related-topics",
    
    "relUrl": "/iw-rIL/user/translate.html#related-topics"
  },"5665": {
    "doc": "Translate the App",
    "title": "Translate the App",
    "content": "The app and its in-app docs are translated on Crowdin — this page shows how to contribute. The app uses Crowdin to manage community translations for both the user interface and in-app documentation. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/translate.html",
    
    "relUrl": "/pt-rBR/user/translate.html"
  },"5666": {
    "doc": "Translate the App",
    "title": "What Gets Translated",
    "content": "| Resource | Source Location | Notes | . | UI strings | core/resources/src/commonMain/composeResources/values/strings.xml | Buttons, labels, messages, and all user-visible text | . | User Guide pages | docs/en/user/*.md | In-app documentation shown in Help & Documentation | . | Fastlane metadata | fastlane/metadata/android/en-US/ | Google Play listing title, description, and changelogs | . ℹ️ Note: Developer Guide pages are English-only. Code-focused documentation targeting contributors is not translated. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/translate.html#what-gets-translated",
    
    "relUrl": "/pt-rBR/user/translate.html#what-gets-translated"
  },"5667": {
    "doc": "Translate the App",
    "title": "How to Contribute",
    "content": ". | Visit the Crowdin project. Open the Meshtastic Android Crowdin project and sign in or create a free account. | Choose your language. Select an existing language or request a new one by opening a GitHub issue. | Translate strings. Crowdin shows the English source on the left and your translation on the right. Translate each string and save. | Review context. Many strings include screenshots or context comments — check these to understand where the text appears in the app. A scheduled job pulls approved translations from Crowdin and opens a pull request; they ship once a maintainer merges it and a new build goes out. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/translate.html#how-to-contribute",
    
    "relUrl": "/pt-rBR/user/translate.html#how-to-contribute"
  },"5668": {
    "doc": "Translate the App",
    "title": "Adding a New Language",
    "content": "If your language is not yet listed on Crowdin: . | Open an issue on GitHub requesting the new locale. | A maintainer will add the language to Crowdin and configure crowdin.yml. | Once added, you can begin translating immediately. | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/translate.html#adding-a-new-language",
    
    "relUrl": "/pt-rBR/user/translate.html#adding-a-new-language"
  },"5669": {
    "doc": "Translate the App",
    "title": "How Translations Are Organized",
    "content": "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/ ├── en/user/ ← English source (default) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← French (France) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← German (Germany) │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. The app automatically selects the correct locale based on your phone’s Language & Region settings. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/translate.html#how-translations-are-organized",
    
    "relUrl": "/pt-rBR/user/translate.html#how-translations-are-organized"
  },"5670": {
    "doc": "Translate the App",
    "title": "Translation Guidelines",
    "content": ". | 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 phone’s language and open the app to see how translations look in context. | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/translate.html#translation-guidelines",
    
    "relUrl": "/pt-rBR/user/translate.html#translation-guidelines"
  },"5671": {
    "doc": "Translate the App",
    "title": "Questions?",
    "content": "If you have questions about a specific string’s context or need help getting started, open a discussion on the Meshtastic GitHub Discussions page. Thank you for helping expand the reach of Meshtastic. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/translate.html#questions",
    
    "relUrl": "/pt-rBR/user/translate.html#questions"
  },"5672": {
    "doc": "Translate the App",
    "title": "Related Topics",
    "content": ". | Units & Locale — how the app picks number, date, and unit formats for your region | Help & Documentation — the in-app docs browser these pages are published to | Onboarding — where a new user first meets the translated strings | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/translate.html#related-topics",
    
    "relUrl": "/pt-rBR/user/translate.html#related-topics"
  },"5673": {
    "doc": "Translate the App",
    "title": "Translate the App",
    "content": "The app and its in-app docs are translated on Crowdin — this page shows how to contribute. The app uses Crowdin to manage community translations for both the user interface and in-app documentation. ",
    "url": "/Meshtastic-Android/main/en/user/translate.html",
    
    "relUrl": "/en/user/translate.html"
  },"5674": {
    "doc": "Translate the App",
    "title": "What Gets Translated",
    "content": "| Resource | Source Location | Notes | . | UI strings | core/resources/src/commonMain/composeResources/values/strings.xml | Buttons, labels, messages, and all user-visible text | . | User Guide pages | docs/en/user/*.md | In-app documentation shown in Help & Documentation | . | Fastlane metadata | fastlane/metadata/android/en-US/ | Google Play listing title, description, and changelogs | . ℹ️ Note: Developer Guide pages are English-only. Code-focused documentation targeting contributors is not translated. ",
    "url": "/Meshtastic-Android/main/en/user/translate.html#what-gets-translated",
    
    "relUrl": "/en/user/translate.html#what-gets-translated"
  },"5675": {
    "doc": "Translate the App",
    "title": "How to Contribute",
    "content": ". | Visit the Crowdin project. Open the Meshtastic Android Crowdin project and sign in or create a free account. | Choose your language. Select an existing language or request a new one by opening a GitHub issue. | Translate strings. Crowdin shows the English source on the left and your translation on the right. Translate each string and save. | Review context. Many strings include screenshots or context comments — check these to understand where the text appears in the app. A scheduled job pulls approved translations from Crowdin and opens a pull request; they ship once a maintainer merges it and a new build goes out. | . 💡 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. ",
    "url": "/Meshtastic-Android/main/en/user/translate.html#how-to-contribute",
    
    "relUrl": "/en/user/translate.html#how-to-contribute"
  },"5676": {
    "doc": "Translate the App",
    "title": "Adding a New Language",
    "content": "If your language is not yet listed on Crowdin: . | Open an issue on GitHub requesting the new locale. | A maintainer will add the language to Crowdin and configure crowdin.yml. | Once added, you can begin translating immediately. | . ",
    "url": "/Meshtastic-Android/main/en/user/translate.html#adding-a-new-language",
    
    "relUrl": "/en/user/translate.html#adding-a-new-language"
  },"5677": {
    "doc": "Translate the App",
    "title": "How Translations Are Organized",
    "content": "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/ ├── en/user/ ← English source (default) │ ├── onboarding.md │ └── ... ├── fr-rFR/user/ ← French (France) │ ├── onboarding.md │ └── ... ├── de-rDE/user/ ← German (Germany) │ └── ... └── ... Doc locale folders use Android locale qualifiers, either {lang} or {lang}-r{REGION} (for example fr, fr-rFR, de-rDE, ja-rJP). The values-* folders for app strings use bare language codes instead (values-fr, values-de, values-ja), because crowdin.yml writes strings with %two_letters_code% and doc pages with %android_code%. The two sets do not line up one-to-one. The app automatically selects the correct locale based on your phone’s Language & Region settings. A page that came from Crowdin is labeled Community translated under its title in the app. If a page has no Crowdin translation for your language yet, the Google-flavor Android build machine-translates the English source on the fly and labels it Auto-translated instead; F-Droid and desktop builds show the English page. Your Crowdin translation replaces the machine one as soon as it lands. ",
    "url": "/Meshtastic-Android/main/en/user/translate.html#how-translations-are-organized",
    
    "relUrl": "/en/user/translate.html#how-translations-are-organized"
  },"5678": {
    "doc": "Translate the App",
    "title": "Translation Guidelines",
    "content": ". | 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 phone’s language and open the app to see how translations look in context. | . ",
    "url": "/Meshtastic-Android/main/en/user/translate.html#translation-guidelines",
    
    "relUrl": "/en/user/translate.html#translation-guidelines"
  },"5679": {
    "doc": "Translate the App",
    "title": "Questions?",
    "content": "If you have questions about a specific string’s context or need help getting started, open a discussion on the Meshtastic GitHub Discussions page. Thank you for helping expand the reach of Meshtastic. ",
    "url": "/Meshtastic-Android/main/en/user/translate.html#questions",
    
    "relUrl": "/en/user/translate.html#questions"
  },"5680": {
    "doc": "Translate the App",
    "title": "Related Topics",
    "content": ". | Units & Locale — how the app picks number, date, and unit formats for your region | Help & Documentation — the in-app docs browser these pages are published to | Onboarding — where a new user first meets the translated strings | . ",
    "url": "/Meshtastic-Android/main/en/user/translate.html#related-topics",
    
    "relUrl": "/en/user/translate.html#related-topics"
  },"5681": {
    "doc": "Transport",
    "title": "Transport",
    "content": "The app talks to the radio over three transports — BLE, USB serial, and TCP — behind one abstraction. ",
    "url": "/Meshtastic-Android/main/en/developer/transport.html",
    
    "relUrl": "/en/developer/transport.html"
  },"5682": {
    "doc": "Transport",
    "title": "Transport Abstraction",
    "content": "The transport layer is abstracted through interfaces defined in core:repository (RadioTransport, RadioTransportFactory, RadioInterfaceService). Each transport’s concrete implementation lives in core:network: BleRadioTransport (BLE), TcpRadioTransport (TCP), and SerialRadioTransport (Android USB serial), alongside MockRadioTransport and ReplayRadioTransport for development. core:ble supplies the lower-level BLE connection primitives (scanning, GATT, Kable wiring) that BleRadioTransport builds on — it does not implement RadioTransport itself. This lets the app work identically regardless of the underlying connection type. App ← RadioController → Transport (BLE | Serial | TCP) . ",
    "url": "/Meshtastic-Android/main/en/developer/transport.html#transport-abstraction",
    
    "relUrl": "/en/developer/transport.html#transport-abstraction"
  },"5683": {
    "doc": "Transport",
    "title": "Bluetooth Low Energy (BLE)",
    "content": "Module: core:network (the BleRadioTransport implementation) built on core:ble (BLE connection primitives) Platforms: Android, Desktop (JVM via Kable); code compiles for iOS, but no iOS app ships . The primary transport for mobile devices and also available on desktop: . | Service discovery for Meshtastic GATT services | Characteristic-based read/write for protobuf packets | Connection state management and automatic reconnection | MTU negotiation for optimal packet sizes | . Where the Code Lives . | BleRadioTransport (core:network) — the RadioTransport implementation for BLE | core:ble — BLE scanning, connection, and GATT operations (BleScanner, BluetoothRepository, KableBleConnection), which BleRadioTransport consumes | Platform-specific implementations in androidMain and jvmMain (Kable) | . ",
    "url": "/Meshtastic-Android/main/en/developer/transport.html#bluetooth-low-energy-ble",
    
    "relUrl": "/en/developer/transport.html#bluetooth-low-energy-ble"
  },"5684": {
    "doc": "Transport",
    "title": "USB Serial",
    "content": "Module: core:network Platforms: Android (OTG), Desktop . Serial communication over USB: . | Uses usb-serial-for-android library on Android | Direct serial port access on Desktop (JVM) | Probe table for supported USB vendor/product IDs | Automatic detection when USB device is connected | . Where the Code Lives . | SerialRadioTransport (core:network, androidMain) — the Android RadioTransport implementation | SerialTransport (core:network, jvmMain) — the shared serial-port transport Desktop builds on | DesktopRadioTransportFactory (desktopApp) — wires Desktop’s jSerialComm-based serial connection | . ",
    "url": "/Meshtastic-Android/main/en/developer/transport.html#usb-serial",
    
    "relUrl": "/en/developer/transport.html#usb-serial"
  },"5685": {
    "doc": "Transport",
    "title": "TCP/IP",
    "content": "Module: core:network Platforms: Android, Desktop (iOS: code compiles, but there’s no iOS app target or RadioTransportFactory — see Transport Factory) . Network-based transport for Wi-Fi-enabled radios: . | TCP socket connection to radio’s IP address | Default port: 4403 | Used for development with simulated radios | Available when BLE/USB is impractical | . ",
    "url": "/Meshtastic-Android/main/en/developer/transport.html#tcpip",
    
    "relUrl": "/en/developer/transport.html#tcpip"
  },"5686": {
    "doc": "Transport",
    "title": "Transport Factory",
    "content": "The RadioTransportFactory interface abstracts transport creation: . interface RadioTransportFactory { val supportedDeviceTypes: List<DeviceType> /** Whether the virtual demo transports (`m` mock / `r` replay) may be offered right now. */ val mockTransportEnabled: StateFlow<Boolean> /** Whether this build ships a packet capture to replay, rather than degrading to plain mock. */ val isReplayTransportAvailable: Boolean fun createTransport(address: String, service: RadioInterfaceService): RadioTransport fun isAddressValid(address: String?): Boolean fun toInterfaceAddress(interfaceId: InterfaceId, rest: String): String } . mockTransportEnabled is a flow, not a one-shot check: the Android Demo Mode gesture (five taps on the Settings app-version row) unlocks the demo transports mid-session, and the device list has to notice. Every consumer must read that one flow — the visibility path and the isAddressValid admission path have to agree, or the demo entry appears and then refuses to connect. Platform-specific implementations: . | Android: Supports BLE + USB + TCP | Desktop: Supports BLE (Kable) + USB + TCP | iOS: Code compiles for BLE and TCP, but no RadioTransportFactory implementation exists and no iOS app ships | . ",
    "url": "/Meshtastic-Android/main/en/developer/transport.html#transport-factory",
    
    "relUrl": "/en/developer/transport.html#transport-factory"
  },"5687": {
    "doc": "Transport",
    "title": "Connection Lifecycle",
    "content": ". | Discovery — Scan for available radios (BLE scan / USB detect / manual TCP) | Connection — Establish link to selected radio | Handshake — Exchange node info and configuration | Active — Normal message exchange | Disconnection — Clean teardown or error recovery | . ",
    "url": "/Meshtastic-Android/main/en/developer/transport.html#connection-lifecycle",
    
    "relUrl": "/en/developer/transport.html#connection-lifecycle"
  },"5688": {
    "doc": "Transport",
    "title": "Adding a New Transport",
    "content": ". | Implement RadioTransport interface | Register in platform-specific RadioTransportFactory | Add connection UI in feature:connections | Update DI bindings for the platform | . ",
    "url": "/Meshtastic-Android/main/en/developer/transport.html#adding-a-new-transport",
    
    "relUrl": "/en/developer/transport.html#adding-a-new-transport"
  },"5689": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/units-and-locale.html#units-measurement--locale",
    
    "relUrl": "/sk-rSK/user/units-and-locale.html#units-measurement--locale"
  },"5690": {
    "doc": "Units, Measurement & Locale",
    "title": "How It Works",
    "content": "Meshtastic radios always transmit data in metric units (meters, °C, m/s, hPa, etc.). When the app receives this data, it converts and displays 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. Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/units-and-locale.html#how-it-works",
    
    "relUrl": "/sk-rSK/user/units-and-locale.html#how-it-works"
  },"5691": {
    "doc": "Units, Measurement & Locale",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/sk-rSK/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"5692": {
    "doc": "Units, Measurement & Locale",
    "title": "Teplota",
    "content": "Temperature values from environment sensors are transmitted as °C and displayed based on your device’s temperature unit preference. | 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. Temperature follows your locale’s temperature preference, independent of the distance system. Locales that mix systems work correctly — a UK phone shows miles for distance but °C for temperature. On Android 14+, the Temperature regional preference (Settings → System → Languages → Regional preferences) overrides the locale default. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/units-and-locale.html#teplota",
    
    "relUrl": "/sk-rSK/user/units-and-locale.html#teplota"
  },"5693": {
    "doc": "Units, Measurement & Locale",
    "title": "Distance & Altitude",
    "content": "Distances between nodes and GPS altitudes are transmitted as meters and automatically scaled and converted. | Your Setting | Small Distance | Large Distance | Nadmorská výška | . | 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 kilometers 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 | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/units-and-locale.html#distance--altitude",
    
    "relUrl": "/sk-rSK/user/units-and-locale.html#distance--altitude"
  },"5694": {
    "doc": "Units, Measurement & Locale",
    "title": "Rýchlosť",
    "content": "GPS ground speed is displayed in your locale’s preferred speed unit. | Your Setting | You See | . | Metric | 12 km/h | . | Imperial (US) | 7 mph | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/units-and-locale.html#r%C3%BDchlos%C5%A5",
    
    "relUrl": "/sk-rSK/user/units-and-locale.html#rýchlosť"
  },"5695": {
    "doc": "Units, Measurement & Locale",
    "title": "Vietor",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | Your Setting | You See | . | Metric | 18.0 km/h | . | Imperial (US) | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/units-and-locale.html#vietor",
    
    "relUrl": "/sk-rSK/user/units-and-locale.html#vietor"
  },"5696": {
    "doc": "Units, Measurement & Locale",
    "title": "Hmotnosť",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | Your Setting | You See | . | Metric | 1.50 kg | . | Imperial (US) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/units-and-locale.html#hmotnos%C5%A5",
    
    "relUrl": "/sk-rSK/user/units-and-locale.html#hmotnosť"
  },"5697": {
    "doc": "Units, Measurement & Locale",
    "title": "Rainfall",
    "content": "Rainfall measurements (1-hour and 24-hour totals) are transmitted as mm and converted for display. | Your Setting | You See | . | Metric | 12.0 mm | . | Imperial (US) | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/units-and-locale.html#rainfall",
    
    "relUrl": "/sk-rSK/user/units-and-locale.html#rainfall"
  },"5698": {
    "doc": "Units, Measurement & Locale",
    "title": "Units That Never Change",
    "content": "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 | . | Radiácia | µR/h | Standard dosimetry unit | . | GPS coordinates | decimal degrees | Universal geographic standard | . | Humidity, battery, soil moisture | % | Universal | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/units-and-locale.html#units-that-never-change",
    
    "relUrl": "/sk-rSK/user/units-and-locale.html#units-that-never-change"
  },"5699": {
    "doc": "Units, Measurement & Locale",
    "title": "Date & Time",
    "content": "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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/units-and-locale.html#date--time",
    
    "relUrl": "/sk-rSK/user/units-and-locale.html#date--time"
  },"5700": {
    "doc": "Units, Measurement & Locale",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region | Return to Meshtastic — values update immediately | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/sk-rSK/user/units-and-locale.html#changing-your-measurement-system"
  },"5701": {
    "doc": "Units, Measurement & Locale",
    "title": "Related Topics",
    "content": ". | Node Metrics — where temperature, distance, and sensor values are displayed | Telemetry & Sensors — the sensors that produce these measurements | Measurement & Formatting — developer reference for the formatting utilities | Settings — Radio & User — region setting that drives unit selection | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/units-and-locale.html#related-topics",
    
    "relUrl": "/sk-rSK/user/units-and-locale.html#related-topics"
  },"5702": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": " ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/units-and-locale.html",
    
    "relUrl": "/sk-rSK/user/units-and-locale.html"
  },"5703": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/units-and-locale.html#units-measurement--locale",
    
    "relUrl": "/be-rBY/user/units-and-locale.html#units-measurement--locale"
  },"5704": {
    "doc": "Units, Measurement & Locale",
    "title": "How It Works",
    "content": "Meshtastic radios always transmit data in metric units (meters, °C, m/s, hPa, etc.). When the app receives this data, it converts and displays 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. Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/units-and-locale.html#how-it-works",
    
    "relUrl": "/be-rBY/user/units-and-locale.html#how-it-works"
  },"5705": {
    "doc": "Units, Measurement & Locale",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/be-rBY/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"5706": {
    "doc": "Units, Measurement & Locale",
    "title": "Тэмпература",
    "content": "Temperature values from environment sensors are transmitted as °C and displayed based on your device’s temperature unit preference. | 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. Temperature follows your locale’s temperature preference, independent of the distance system. Locales that mix systems work correctly — a UK phone shows miles for distance but °C for temperature. On Android 14+, the Temperature regional preference (Settings → System → Languages → Regional preferences) overrides the locale default. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/units-and-locale.html#%D1%82%D1%8D%D0%BC%D0%BF%D0%B5%D1%80%D0%B0%D1%82%D1%83%D1%80%D0%B0",
    
    "relUrl": "/be-rBY/user/units-and-locale.html#тэмпература"
  },"5707": {
    "doc": "Units, Measurement & Locale",
    "title": "Distance & Altitude",
    "content": "Distances between nodes and GPS altitudes are transmitted as meters and automatically scaled and converted. | 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 kilometers 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 | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/units-and-locale.html#distance--altitude",
    
    "relUrl": "/be-rBY/user/units-and-locale.html#distance--altitude"
  },"5708": {
    "doc": "Units, Measurement & Locale",
    "title": "Хуткасць",
    "content": "GPS ground speed is displayed in your locale’s preferred speed unit. | Your Setting | You See | . | Metric | 12 km/h | . | Imperial (US) | 7 mph | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/units-and-locale.html#%D1%85%D1%83%D1%82%D0%BA%D0%B0%D1%81%D1%86%D1%8C",
    
    "relUrl": "/be-rBY/user/units-and-locale.html#хуткасць"
  },"5709": {
    "doc": "Units, Measurement & Locale",
    "title": "Wind",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | Your Setting | You See | . | Metric | 18.0 km/h | . | Imperial (US) | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/units-and-locale.html#wind",
    
    "relUrl": "/be-rBY/user/units-and-locale.html#wind"
  },"5710": {
    "doc": "Units, Measurement & Locale",
    "title": "Weight",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | Your Setting | You See | . | Metric | 1.50 kg | . | Imperial (US) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/units-and-locale.html#weight",
    
    "relUrl": "/be-rBY/user/units-and-locale.html#weight"
  },"5711": {
    "doc": "Units, Measurement & Locale",
    "title": "Rainfall",
    "content": "Rainfall measurements (1-hour and 24-hour totals) are transmitted as mm and converted for display. | Your Setting | You See | . | Metric | 12.0 mm | . | Imperial (US) | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/units-and-locale.html#rainfall",
    
    "relUrl": "/be-rBY/user/units-and-locale.html#rainfall"
  },"5712": {
    "doc": "Units, Measurement & Locale",
    "title": "Units That Never Change",
    "content": "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/h | Standard dosimetry unit | . | GPS coordinates | decimal degrees | Universal geographic standard | . | Humidity, battery, soil moisture | % | Universal | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/units-and-locale.html#units-that-never-change",
    
    "relUrl": "/be-rBY/user/units-and-locale.html#units-that-never-change"
  },"5713": {
    "doc": "Units, Measurement & Locale",
    "title": "Date & Time",
    "content": "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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/units-and-locale.html#date--time",
    
    "relUrl": "/be-rBY/user/units-and-locale.html#date--time"
  },"5714": {
    "doc": "Units, Measurement & Locale",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region | Return to Meshtastic — values update immediately | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/be-rBY/user/units-and-locale.html#changing-your-measurement-system"
  },"5715": {
    "doc": "Units, Measurement & Locale",
    "title": "Related Topics",
    "content": ". | Node Metrics — where temperature, distance, and sensor values are displayed | Telemetry & Sensors — the sensors that produce these measurements | Measurement & Formatting — developer reference for the formatting utilities | Settings — Radio & User — region setting that drives unit selection | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/units-and-locale.html#related-topics",
    
    "relUrl": "/be-rBY/user/units-and-locale.html#related-topics"
  },"5716": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": " ",
    "url": "/Meshtastic-Android/main/be-rBY/user/units-and-locale.html",
    
    "relUrl": "/be-rBY/user/units-and-locale.html"
  },"5717": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/units-and-locale.html#units-measurement--locale",
    
    "relUrl": "/it-rIT/user/units-and-locale.html#units-measurement--locale"
  },"5718": {
    "doc": "Units, Measurement & Locale",
    "title": "Come funziona",
    "content": "Meshtastic radios always transmit data in metric units (meters, °C, m/s, hPa, etc.). When the app receives this data, it converts and displays 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. Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/units-and-locale.html#come-funziona",
    
    "relUrl": "/it-rIT/user/units-and-locale.html#come-funziona"
  },"5719": {
    "doc": "Units, Measurement & Locale",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/it-rIT/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"5720": {
    "doc": "Units, Measurement & Locale",
    "title": "Temperatura",
    "content": "Temperature values from environment sensors are transmitted as °C and displayed based on your device’s temperature unit preference. | 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. Temperature follows your locale’s temperature preference, independent of the distance system. Locales that mix systems work correctly — a UK phone shows miles for distance but °C for temperature. On Android 14+, the Temperature regional preference (Settings → System → Languages → Regional preferences) overrides the locale default. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/units-and-locale.html#temperatura",
    
    "relUrl": "/it-rIT/user/units-and-locale.html#temperatura"
  },"5721": {
    "doc": "Units, Measurement & Locale",
    "title": "Distance & Altitude",
    "content": "Distances between nodes and GPS altitudes are transmitted as meters and automatically scaled and converted. | Your Setting | Small Distance | Large Distance | Altitudine | . | Metrico | 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 kilometers 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 | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/units-and-locale.html#distance--altitude",
    
    "relUrl": "/it-rIT/user/units-and-locale.html#distance--altitude"
  },"5722": {
    "doc": "Units, Measurement & Locale",
    "title": "Velocità",
    "content": "GPS ground speed is displayed in your locale’s preferred speed unit. | Your Setting | You See | . | Metrico | 12 km/h | . | Imperial (US) | 7 mph | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/units-and-locale.html#velocit%C3%A0",
    
    "relUrl": "/it-rIT/user/units-and-locale.html#velocità"
  },"5723": {
    "doc": "Units, Measurement & Locale",
    "title": "Vento",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | Your Setting | You See | . | Metrico | 18.0 km/h | . | Imperial (US) | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/units-and-locale.html#vento",
    
    "relUrl": "/it-rIT/user/units-and-locale.html#vento"
  },"5724": {
    "doc": "Units, Measurement & Locale",
    "title": "Peso",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | Your Setting | You See | . | Metrico | 1.50 kg | . | Imperial (US) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/units-and-locale.html#peso",
    
    "relUrl": "/it-rIT/user/units-and-locale.html#peso"
  },"5725": {
    "doc": "Units, Measurement & Locale",
    "title": "Rainfall",
    "content": "Rainfall measurements (1-hour and 24-hour totals) are transmitted as mm and converted for display. | Your Setting | You See | . | Metrico | 12.0 mm | . | Imperial (US) | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/units-and-locale.html#rainfall",
    
    "relUrl": "/it-rIT/user/units-and-locale.html#rainfall"
  },"5726": {
    "doc": "Units, Measurement & Locale",
    "title": "Units That Never Change",
    "content": "Some units are international standards and are displayed the same way regardless of your locale: . | Measurement | Unit | Why | . | Pressione barometrica | hPa | International meteorological standard | . | Heading / bearing | ° (degrees) | Universal navigation convention | . | Radiazione | µR/h | Standard dosimetry unit | . | GPS coordinates | decimal degrees | Universal geographic standard | . | Humidity, battery, soil moisture | % | Universal | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/units-and-locale.html#units-that-never-change",
    
    "relUrl": "/it-rIT/user/units-and-locale.html#units-that-never-change"
  },"5727": {
    "doc": "Units, Measurement & Locale",
    "title": "Date & Time",
    "content": "All timestamps throughout the app — last heard, message times, telemetry logs, chart axes — follow your device’s date and time preferences. | Impostazione | What It Controls | Esempio | . | 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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/units-and-locale.html#date--time",
    
    "relUrl": "/it-rIT/user/units-and-locale.html#date--time"
  },"5728": {
    "doc": "Units, Measurement & Locale",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region | Return to Meshtastic — values update immediately | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/it-rIT/user/units-and-locale.html#changing-your-measurement-system"
  },"5729": {
    "doc": "Units, Measurement & Locale",
    "title": "Related Topics",
    "content": ". | Node Metrics — where temperature, distance, and sensor values are displayed | Telemetry & Sensors — the sensors that produce these measurements | Measurement & Formatting — developer reference for the formatting utilities | Settings — Radio & User — region setting that drives unit selection | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/units-and-locale.html#related-topics",
    
    "relUrl": "/it-rIT/user/units-and-locale.html#related-topics"
  },"5730": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": " ",
    "url": "/Meshtastic-Android/main/it-rIT/user/units-and-locale.html",
    
    "relUrl": "/it-rIT/user/units-and-locale.html"
  },"5731": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/es-rES/user/units-and-locale.html#units-measurement--locale",
    
    "relUrl": "/es-rES/user/units-and-locale.html#units-measurement--locale"
  },"5732": {
    "doc": "Units, Measurement & Locale",
    "title": "How It Works",
    "content": "Meshtastic radios always transmit data in metric units (meters, °C, m/s, hPa, etc.). When the app receives this data, it converts and displays 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. Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/es-rES/user/units-and-locale.html#how-it-works",
    
    "relUrl": "/es-rES/user/units-and-locale.html#how-it-works"
  },"5733": {
    "doc": "Units, Measurement & Locale",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/es-rES/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/es-rES/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"5734": {
    "doc": "Units, Measurement & Locale",
    "title": "Temperatura:",
    "content": "Temperature values from environment sensors are transmitted as °C and displayed based on your device’s temperature unit preference. | 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. Temperature follows your locale’s temperature preference, independent of the distance system. Locales that mix systems work correctly — a UK phone shows miles for distance but °C for temperature. On Android 14+, the Temperature regional preference (Settings → System → Languages → Regional preferences) overrides the locale default. ",
    "url": "/Meshtastic-Android/main/es-rES/user/units-and-locale.html#temperatura",
    
    "relUrl": "/es-rES/user/units-and-locale.html#temperatura"
  },"5735": {
    "doc": "Units, Measurement & Locale",
    "title": "Distance & Altitude",
    "content": "Distances between nodes and GPS altitudes are transmitted as meters and automatically scaled and converted. | Your Setting | Small Distance | Large Distance | Altitud | . | Métrico | 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 kilometers 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 | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/units-and-locale.html#distance--altitude",
    
    "relUrl": "/es-rES/user/units-and-locale.html#distance--altitude"
  },"5736": {
    "doc": "Units, Measurement & Locale",
    "title": "Velocidad",
    "content": "GPS ground speed is displayed in your locale’s preferred speed unit. | Your Setting | You See | . | Métrico | 12 km/h | . | Imperial (US) | 7 mph | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/units-and-locale.html#velocidad",
    
    "relUrl": "/es-rES/user/units-and-locale.html#velocidad"
  },"5737": {
    "doc": "Units, Measurement & Locale",
    "title": "Viento",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | Your Setting | You See | . | Métrico | 18.0 km/h | . | Imperial (US) | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/es-rES/user/units-and-locale.html#viento",
    
    "relUrl": "/es-rES/user/units-and-locale.html#viento"
  },"5738": {
    "doc": "Units, Measurement & Locale",
    "title": "Peso",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | Your Setting | You See | . | Métrico | 1.50 kg | . | Imperial (US) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/units-and-locale.html#peso",
    
    "relUrl": "/es-rES/user/units-and-locale.html#peso"
  },"5739": {
    "doc": "Units, Measurement & Locale",
    "title": "Rainfall",
    "content": "Rainfall measurements (1-hour and 24-hour totals) are transmitted as mm and converted for display. | Your Setting | You See | . | Métrico | 12.0 mm | . | Imperial (US) | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/units-and-locale.html#rainfall",
    
    "relUrl": "/es-rES/user/units-and-locale.html#rainfall"
  },"5740": {
    "doc": "Units, Measurement & Locale",
    "title": "Units That Never Change",
    "content": "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 | . | Radiación | µR/h | Standard dosimetry unit | . | GPS coordinates | decimal degrees | Universal geographic standard | . | Humidity, battery, soil moisture | % | Universal | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/units-and-locale.html#units-that-never-change",
    
    "relUrl": "/es-rES/user/units-and-locale.html#units-that-never-change"
  },"5741": {
    "doc": "Units, Measurement & Locale",
    "title": "Date & Time",
    "content": "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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/es-rES/user/units-and-locale.html#date--time",
    
    "relUrl": "/es-rES/user/units-and-locale.html#date--time"
  },"5742": {
    "doc": "Units, Measurement & Locale",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region | Return to Meshtastic — values update immediately | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/es-rES/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/es-rES/user/units-and-locale.html#changing-your-measurement-system"
  },"5743": {
    "doc": "Units, Measurement & Locale",
    "title": "Related Topics",
    "content": ". | Node Metrics — where temperature, distance, and sensor values are displayed | Telemetry & Sensors — the sensors that produce these measurements | Measurement & Formatting — developer reference for the formatting utilities | Settings — Radio & User — region setting that drives unit selection | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/units-and-locale.html#related-topics",
    
    "relUrl": "/es-rES/user/units-and-locale.html#related-topics"
  },"5744": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": " ",
    "url": "/Meshtastic-Android/main/es-rES/user/units-and-locale.html",
    
    "relUrl": "/es-rES/user/units-and-locale.html"
  },"5745": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/units-and-locale.html#units-measurement--locale",
    
    "relUrl": "/sl-rSI/user/units-and-locale.html#units-measurement--locale"
  },"5746": {
    "doc": "Units, Measurement & Locale",
    "title": "How It Works",
    "content": "Meshtastic radios always transmit data in metric units (meters, °C, m/s, hPa, etc.). When the app receives this data, it converts and displays 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. Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/units-and-locale.html#how-it-works",
    
    "relUrl": "/sl-rSI/user/units-and-locale.html#how-it-works"
  },"5747": {
    "doc": "Units, Measurement & Locale",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/sl-rSI/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"5748": {
    "doc": "Units, Measurement & Locale",
    "title": "Temperatura",
    "content": "Temperature values from environment sensors are transmitted as °C and displayed based on your device’s temperature unit preference. | 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. Temperature follows your locale’s temperature preference, independent of the distance system. Locales that mix systems work correctly — a UK phone shows miles for distance but °C for temperature. On Android 14+, the Temperature regional preference (Settings → System → Languages → Regional preferences) overrides the locale default. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/units-and-locale.html#temperatura",
    
    "relUrl": "/sl-rSI/user/units-and-locale.html#temperatura"
  },"5749": {
    "doc": "Units, Measurement & Locale",
    "title": "Distance & Altitude",
    "content": "Distances between nodes and GPS altitudes are transmitted as meters and automatically scaled and converted. | 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 kilometers 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 | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/units-and-locale.html#distance--altitude",
    
    "relUrl": "/sl-rSI/user/units-and-locale.html#distance--altitude"
  },"5750": {
    "doc": "Units, Measurement & Locale",
    "title": "Speed",
    "content": "GPS ground speed is displayed in your locale’s preferred speed unit. | Your Setting | You See | . | Metric | 12 km/h | . | Imperial (US) | 7 mph | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/units-and-locale.html#speed",
    
    "relUrl": "/sl-rSI/user/units-and-locale.html#speed"
  },"5751": {
    "doc": "Units, Measurement & Locale",
    "title": "Wind",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | Your Setting | You See | . | Metric | 18.0 km/h | . | Imperial (US) | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/units-and-locale.html#wind",
    
    "relUrl": "/sl-rSI/user/units-and-locale.html#wind"
  },"5752": {
    "doc": "Units, Measurement & Locale",
    "title": "Weight",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | Your Setting | You See | . | Metric | 1.50 kg | . | Imperial (US) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/units-and-locale.html#weight",
    
    "relUrl": "/sl-rSI/user/units-and-locale.html#weight"
  },"5753": {
    "doc": "Units, Measurement & Locale",
    "title": "Rainfall",
    "content": "Rainfall measurements (1-hour and 24-hour totals) are transmitted as mm and converted for display. | Your Setting | You See | . | Metric | 12.0 mm | . | Imperial (US) | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/units-and-locale.html#rainfall",
    
    "relUrl": "/sl-rSI/user/units-and-locale.html#rainfall"
  },"5754": {
    "doc": "Units, Measurement & Locale",
    "title": "Units That Never Change",
    "content": "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/h | Standard dosimetry unit | . | GPS coordinates | decimal degrees | Universal geographic standard | . | Humidity, battery, soil moisture | % | Universal | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/units-and-locale.html#units-that-never-change",
    
    "relUrl": "/sl-rSI/user/units-and-locale.html#units-that-never-change"
  },"5755": {
    "doc": "Units, Measurement & Locale",
    "title": "Date & Time",
    "content": "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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/units-and-locale.html#date--time",
    
    "relUrl": "/sl-rSI/user/units-and-locale.html#date--time"
  },"5756": {
    "doc": "Units, Measurement & Locale",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region | Return to Meshtastic — values update immediately | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/sl-rSI/user/units-and-locale.html#changing-your-measurement-system"
  },"5757": {
    "doc": "Units, Measurement & Locale",
    "title": "Related Topics",
    "content": ". | Node Metrics — where temperature, distance, and sensor values are displayed | Telemetry & Sensors — the sensors that produce these measurements | Measurement & Formatting — developer reference for the formatting utilities | Settings — Radio & User — region setting that drives unit selection | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/units-and-locale.html#related-topics",
    
    "relUrl": "/sl-rSI/user/units-and-locale.html#related-topics"
  },"5758": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": " ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/units-and-locale.html",
    
    "relUrl": "/sl-rSI/user/units-and-locale.html"
  },"5759": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/units-and-locale.html#units-measurement--locale",
    
    "relUrl": "/no-rNO/user/units-and-locale.html#units-measurement--locale"
  },"5760": {
    "doc": "Units, Measurement & Locale",
    "title": "How It Works",
    "content": "Meshtastic radios always transmit data in metric units (meters, °C, m/s, hPa, etc.). When the app receives this data, it converts and displays 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. Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/units-and-locale.html#how-it-works",
    
    "relUrl": "/no-rNO/user/units-and-locale.html#how-it-works"
  },"5761": {
    "doc": "Units, Measurement & Locale",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/no-rNO/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"5762": {
    "doc": "Units, Measurement & Locale",
    "title": "Temperatur",
    "content": "Temperature values from environment sensors are transmitted as °C and displayed based on your device’s temperature unit preference. | 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. Temperature follows your locale’s temperature preference, independent of the distance system. Locales that mix systems work correctly — a UK phone shows miles for distance but °C for temperature. On Android 14+, the Temperature regional preference (Settings → System → Languages → Regional preferences) overrides the locale default. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/units-and-locale.html#temperatur",
    
    "relUrl": "/no-rNO/user/units-and-locale.html#temperatur"
  },"5763": {
    "doc": "Units, Measurement & Locale",
    "title": "Distance & Altitude",
    "content": "Distances between nodes and GPS altitudes are transmitted as meters and automatically scaled and converted. | 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 kilometers 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 | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/units-and-locale.html#distance--altitude",
    
    "relUrl": "/no-rNO/user/units-and-locale.html#distance--altitude"
  },"5764": {
    "doc": "Units, Measurement & Locale",
    "title": "Speed",
    "content": "GPS ground speed is displayed in your locale’s preferred speed unit. | Your Setting | You See | . | Metric | 12 km/h | . | Imperial (US) | 7 mph | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/units-and-locale.html#speed",
    
    "relUrl": "/no-rNO/user/units-and-locale.html#speed"
  },"5765": {
    "doc": "Units, Measurement & Locale",
    "title": "Wind",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | Your Setting | You See | . | Metric | 18.0 km/h | . | Imperial (US) | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/units-and-locale.html#wind",
    
    "relUrl": "/no-rNO/user/units-and-locale.html#wind"
  },"5766": {
    "doc": "Units, Measurement & Locale",
    "title": "Weight",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | Your Setting | You See | . | Metric | 1.50 kg | . | Imperial (US) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/units-and-locale.html#weight",
    
    "relUrl": "/no-rNO/user/units-and-locale.html#weight"
  },"5767": {
    "doc": "Units, Measurement & Locale",
    "title": "Rainfall",
    "content": "Rainfall measurements (1-hour and 24-hour totals) are transmitted as mm and converted for display. | Your Setting | You See | . | Metric | 12.0 mm | . | Imperial (US) | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/units-and-locale.html#rainfall",
    
    "relUrl": "/no-rNO/user/units-and-locale.html#rainfall"
  },"5768": {
    "doc": "Units, Measurement & Locale",
    "title": "Units That Never Change",
    "content": "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/h | Standard dosimetry unit | . | GPS coordinates | decimal degrees | Universal geographic standard | . | Humidity, battery, soil moisture | % | Universal | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/units-and-locale.html#units-that-never-change",
    
    "relUrl": "/no-rNO/user/units-and-locale.html#units-that-never-change"
  },"5769": {
    "doc": "Units, Measurement & Locale",
    "title": "Date & Time",
    "content": "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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/units-and-locale.html#date--time",
    
    "relUrl": "/no-rNO/user/units-and-locale.html#date--time"
  },"5770": {
    "doc": "Units, Measurement & Locale",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region | Return to Meshtastic — values update immediately | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/no-rNO/user/units-and-locale.html#changing-your-measurement-system"
  },"5771": {
    "doc": "Units, Measurement & Locale",
    "title": "Related Topics",
    "content": ". | Node Metrics — where temperature, distance, and sensor values are displayed | Telemetry & Sensors — the sensors that produce these measurements | Measurement & Formatting — developer reference for the formatting utilities | Settings — Radio & User — region setting that drives unit selection | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/units-and-locale.html#related-topics",
    
    "relUrl": "/no-rNO/user/units-and-locale.html#related-topics"
  },"5772": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": " ",
    "url": "/Meshtastic-Android/main/no-rNO/user/units-and-locale.html",
    
    "relUrl": "/no-rNO/user/units-and-locale.html"
  },"5773": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/units-and-locale.html#units-measurement--locale",
    
    "relUrl": "/hu-rHU/user/units-and-locale.html#units-measurement--locale"
  },"5774": {
    "doc": "Units, Measurement & Locale",
    "title": "How It Works",
    "content": "Meshtastic radios always transmit data in metric units (meters, °C, m/s, hPa, etc.). When the app receives this data, it converts and displays 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. Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/units-and-locale.html#how-it-works",
    
    "relUrl": "/hu-rHU/user/units-and-locale.html#how-it-works"
  },"5775": {
    "doc": "Units, Measurement & Locale",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/hu-rHU/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"5776": {
    "doc": "Units, Measurement & Locale",
    "title": "Hőmérséklet",
    "content": "Temperature values from environment sensors are transmitted as °C and displayed based on your device’s temperature unit preference. | 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. Temperature follows your locale’s temperature preference, independent of the distance system. Locales that mix systems work correctly — a UK phone shows miles for distance but °C for temperature. On Android 14+, the Temperature regional preference (Settings → System → Languages → Regional preferences) overrides the locale default. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/units-and-locale.html#h%C5%91m%C3%A9rs%C3%A9klet",
    
    "relUrl": "/hu-rHU/user/units-and-locale.html#hőmérséklet"
  },"5777": {
    "doc": "Units, Measurement & Locale",
    "title": "Distance & Altitude",
    "content": "Distances between nodes and GPS altitudes are transmitted as meters and automatically scaled and converted. | Your Setting | Small Distance | Large Distance | Magasság | . | 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 kilometers 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 | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/units-and-locale.html#distance--altitude",
    
    "relUrl": "/hu-rHU/user/units-and-locale.html#distance--altitude"
  },"5778": {
    "doc": "Units, Measurement & Locale",
    "title": "Sebesség",
    "content": "GPS ground speed is displayed in your locale’s preferred speed unit. | Your Setting | You See | . | Metric | 12 km/h | . | Imperial (US) | 7 mph | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/units-and-locale.html#sebess%C3%A9g",
    
    "relUrl": "/hu-rHU/user/units-and-locale.html#sebesség"
  },"5779": {
    "doc": "Units, Measurement & Locale",
    "title": "Szél",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | Your Setting | You See | . | Metric | 18.0 km/h | . | Imperial (US) | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/units-and-locale.html#sz%C3%A9l",
    
    "relUrl": "/hu-rHU/user/units-and-locale.html#szél"
  },"5780": {
    "doc": "Units, Measurement & Locale",
    "title": "Súly",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | Your Setting | You See | . | Metric | 1.50 kg | . | Imperial (US) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/units-and-locale.html#s%C3%BAly",
    
    "relUrl": "/hu-rHU/user/units-and-locale.html#súly"
  },"5781": {
    "doc": "Units, Measurement & Locale",
    "title": "Rainfall",
    "content": "Rainfall measurements (1-hour and 24-hour totals) are transmitted as mm and converted for display. | Your Setting | You See | . | Metric | 12.0 mm | . | Imperial (US) | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/units-and-locale.html#rainfall",
    
    "relUrl": "/hu-rHU/user/units-and-locale.html#rainfall"
  },"5782": {
    "doc": "Units, Measurement & Locale",
    "title": "Units That Never Change",
    "content": "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 | . | Sugárzás | µR/h | Standard dosimetry unit | . | GPS coordinates | decimal degrees | Universal geographic standard | . | Humidity, battery, soil moisture | % | Universal | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/units-and-locale.html#units-that-never-change",
    
    "relUrl": "/hu-rHU/user/units-and-locale.html#units-that-never-change"
  },"5783": {
    "doc": "Units, Measurement & Locale",
    "title": "Date & Time",
    "content": "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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/units-and-locale.html#date--time",
    
    "relUrl": "/hu-rHU/user/units-and-locale.html#date--time"
  },"5784": {
    "doc": "Units, Measurement & Locale",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region | Return to Meshtastic — values update immediately | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/hu-rHU/user/units-and-locale.html#changing-your-measurement-system"
  },"5785": {
    "doc": "Units, Measurement & Locale",
    "title": "Related Topics",
    "content": ". | Node Metrics — where temperature, distance, and sensor values are displayed | Telemetry & Sensors — the sensors that produce these measurements | Measurement & Formatting — developer reference for the formatting utilities | Settings — Radio & User — region setting that drives unit selection | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/units-and-locale.html#related-topics",
    
    "relUrl": "/hu-rHU/user/units-and-locale.html#related-topics"
  },"5786": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": " ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/units-and-locale.html",
    
    "relUrl": "/hu-rHU/user/units-and-locale.html"
  },"5787": {
    "doc": "Единицы измерения и локаль",
    "title": "Единицы измерения и локаль",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/units-and-locale.html",
    
    "relUrl": "/ru-rRU/user/units-and-locale.html"
  },"5788": {
    "doc": "Единицы измерения и локаль",
    "title": "Как это работает",
    "content": "Радиостанции Meshtastic всегда передают данные в метрических единицах (метры, °C, м/с, гПа и т.д.). Когда приложение получает эти данные, оно преобразует их и показывает значения в той системе единиц, которую задает локаль устройства. На Android твои предпочтения единиц измерений определяются настройками системы Язык и регион. На настольном компьютере (JVM) приложение использует стандартную Locale JVM. Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/units-and-locale.html#%D0%BA%D0%B0%D0%BA-%D1%8D%D1%82%D0%BE-%D1%80%D0%B0%D0%B1%D0%BE%D1%82%D0%B0%D0%B5%D1%82",
    
    "relUrl": "/ru-rRU/user/units-and-locale.html#как-это-работает"
  },"5789": {
    "doc": "Единицы измерения и локаль",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/ru-rRU/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"5790": {
    "doc": "Единицы измерения и локаль",
    "title": "Температура",
    "content": "Значения температуры от датчиков окружающей среды передаются в °C и отображаются в соответствии с предпочтительным единицами температуры твоего устройства. | Твои настройки | Ты видишь | . | Цельсий | 22°C | . | Фаренгейт | 72°F | . Это влияет на все отображения температуры в приложении: телеметрия окружающей среды ноды, температура почвы, точка росы и оси диаграммы телеметрии. Температура следует вашим настройкам предпочитаемой шкалы температуры, независимо от системы измерения расстояния. Локали, где смешаны системы, работают корректно — телефон из Великобритании показывает мили для расстояния, но °C для температуры. На Android 14+ региональные настройки Температуры (Настройки → Система → Языки → Региональные предпочтения) заменяют значение по умолчанию для локали. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/units-and-locale.html#%D1%82%D0%B5%D0%BC%D0%BF%D0%B5%D1%80%D0%B0%D1%82%D1%83%D1%80%D0%B0",
    
    "relUrl": "/ru-rRU/user/units-and-locale.html#температура"
  },"5791": {
    "doc": "Единицы измерения и локаль",
    "title": "Расстояние и высота",
    "content": "Расстояния между нодами и высоты GPS передаются в метрах и автоматически масштабируются и преобразуются. | Твои настройки | Небольшое расстояние | Дальнее расстояние | Высота | . | Метрическая | 350 м | 2,5 км | 1200 м | . | Имперская | 1148 фт | 1,6 миль | 3937 фт | . The app uses natural scaling — short distances stay in meters or feet, while longer distances switch to kilometers or miles automatically. Где они появляются . | Список нод — расстояние и азимут до каждой ноды | Детали ноды — высота, расстояние от твоего положения | Карта — расстояния между путевыми точками, расстояния между хопами трассировки | Компас — расстояние до выбранной ноды | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/units-and-locale.html#%D1%80%D0%B0%D1%81%D1%81%D1%82%D0%BE%D1%8F%D0%BD%D0%B8%D0%B5-%D0%B8-%D0%B2%D1%8B%D1%81%D0%BE%D1%82%D0%B0",
    
    "relUrl": "/ru-rRU/user/units-and-locale.html#расстояние-и-высота"
  },"5792": {
    "doc": "Единицы измерения и локаль",
    "title": "Скорость",
    "content": "Наземная скорость GPS отображается в единицах скорости, предпочитаемых в твоем регионе. | Твоя настройка | Ты видишь | . | Метрическая | 12 км/ч | . | Имперская (США) | 7 миль/ч | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/units-and-locale.html#%D1%81%D0%BA%D0%BE%D1%80%D0%BE%D1%81%D1%82%D1%8C",
    
    "relUrl": "/ru-rRU/user/units-and-locale.html#скорость"
  },"5793": {
    "doc": "Единицы измерения и локаль",
    "title": "Ветер",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | Твоя настройка | Ты видишь | . | Метрическая | 18.0 km/h | . | Имперская (США) | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/units-and-locale.html#%D0%B2%D0%B5%D1%82%D0%B5%D1%80",
    
    "relUrl": "/ru-rRU/user/units-and-locale.html#ветер"
  },"5794": {
    "doc": "Единицы измерения и локаль",
    "title": "Вес",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | Твоя настройка | Ты видишь | . | Метрическая | 1.50 kg | . | Имперская (США) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/units-and-locale.html#%D0%B2%D0%B5%D1%81",
    
    "relUrl": "/ru-rRU/user/units-and-locale.html#вес"
  },"5795": {
    "doc": "Единицы измерения и локаль",
    "title": "Осадки",
    "content": "Измерения осадков (за 1 час и за 24 часа) передаются в мм и конвертируются для отображения. | Ваши настройки | Вы видите | . | Метрическая | 12.0 mm | . | Имперская (США) | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/units-and-locale.html#%D0%BE%D1%81%D0%B0%D0%B4%D0%BA%D0%B8",
    
    "relUrl": "/ru-rRU/user/units-and-locale.html#осадки"
  },"5796": {
    "doc": "Единицы измерения и локаль",
    "title": "Единицы, которые никогда не меняются",
    "content": "Некоторые единицы являются международными стандартами и отображаются одинаково независимо от вашего региона: . | Показатель | Единица | Почему | . | Барометрическое давление | гПа | Международный метеорологический стандарт | . | Курс / азимут | ° (градусы) | Универсальная навигационная конвенция | . | Радиация | µR/h | Стандартная единица дозиметрии | . | GPS координаты | десятичные градусы | Универсальный географический стандарт | . | Влажность, батарея, влажность почвы | % | Универсальный | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/units-and-locale.html#%D0%B5%D0%B4%D0%B8%D0%BD%D0%B8%D1%86%D1%8B-%D0%BA%D0%BE%D1%82%D0%BE%D1%80%D1%8B%D0%B5-%D0%BD%D0%B8%D0%BA%D0%BE%D0%B3%D0%B4%D0%B0-%D0%BD%D0%B5-%D0%BC%D0%B5%D0%BD%D1%8F%D1%8E%D1%82%D1%81%D1%8F",
    
    "relUrl": "/ru-rRU/user/units-and-locale.html#единицы-которые-никогда-не-меняются"
  },"5797": {
    "doc": "Единицы измерения и локаль",
    "title": "Дата и время",
    "content": "Все отметки времени в приложении — последняя активность, время сообщений, журналы телеметрии, оси графиков — следуют настройкам даты и времени вашего устройства. | Настройка | Что это контролирует | Пример | . | 24-часовой формат времени | Формат часов | 14:30 или 2:30 PM | . | Формат даты | Сортировка даты | 09/05/2026 или 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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/units-and-locale.html#%D0%B4%D0%B0%D1%82%D0%B0-%D0%B8-%D0%B2%D1%80%D0%B5%D0%BC%D1%8F",
    
    "relUrl": "/ru-rRU/user/units-and-locale.html#дата-и-время"
  },"5798": {
    "doc": "Единицы измерения и локаль",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | Откройте Настройки Android → Система → Язык и регион | Change your Region | Вернуться к Meshtastic — значения обновляются немедленно | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/ru-rRU/user/units-and-locale.html#changing-your-measurement-system"
  },"5799": {
    "doc": "Единицы измерения и локаль",
    "title": "Связанные темы",
    "content": ". | Метрики ноды — здесь отображаются температура, расстояние и значения датчиков | Телеметрия и датчики — датчики, производящие эти измерения | Измерение и форматирование — ссылка на разработчика утилит форматирования | Настройки — Радио и Пользователь — настройка региона, управляющая выбором единиц | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/units-and-locale.html#%D1%81%D0%B2%D1%8F%D0%B7%D0%B0%D0%BD%D0%BD%D1%8B%D0%B5-%D1%82%D0%B5%D0%BC%D1%8B",
    
    "relUrl": "/ru-rRU/user/units-and-locale.html#связанные-темы"
  },"5800": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/units-and-locale.html#units-measurement--locale",
    
    "relUrl": "/cs-rCZ/user/units-and-locale.html#units-measurement--locale"
  },"5801": {
    "doc": "Units, Measurement & Locale",
    "title": "How It Works",
    "content": "Meshtastic radios always transmit data in metric units (meters, °C, m/s, hPa, etc.). When the app receives this data, it converts and displays 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. Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/units-and-locale.html#how-it-works",
    
    "relUrl": "/cs-rCZ/user/units-and-locale.html#how-it-works"
  },"5802": {
    "doc": "Units, Measurement & Locale",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/cs-rCZ/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"5803": {
    "doc": "Units, Measurement & Locale",
    "title": "Teplota",
    "content": "Temperature values from environment sensors are transmitted as °C and displayed based on your device’s temperature unit preference. | 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. Temperature follows your locale’s temperature preference, independent of the distance system. Locales that mix systems work correctly — a UK phone shows miles for distance but °C for temperature. On Android 14+, the Temperature regional preference (Settings → System → Languages → Regional preferences) overrides the locale default. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/units-and-locale.html#teplota",
    
    "relUrl": "/cs-rCZ/user/units-and-locale.html#teplota"
  },"5804": {
    "doc": "Units, Measurement & Locale",
    "title": "Distance & Altitude",
    "content": "Distances between nodes and GPS altitudes are transmitted as meters and automatically scaled and converted. | Your Setting | Small Distance | Large Distance | Nadm. výška | . | Metrický | 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 kilometers 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 | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/units-and-locale.html#distance--altitude",
    
    "relUrl": "/cs-rCZ/user/units-and-locale.html#distance--altitude"
  },"5805": {
    "doc": "Units, Measurement & Locale",
    "title": "Rychlost",
    "content": "GPS ground speed is displayed in your locale’s preferred speed unit. | Your Setting | You See | . | Metrický | 12 km/h | . | Imperial (US) | 7 mph | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/units-and-locale.html#rychlost",
    
    "relUrl": "/cs-rCZ/user/units-and-locale.html#rychlost"
  },"5806": {
    "doc": "Units, Measurement & Locale",
    "title": "Vítr",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | Your Setting | You See | . | Metrický | 18.0 km/h | . | Imperial (US) | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/units-and-locale.html#v%C3%ADtr",
    
    "relUrl": "/cs-rCZ/user/units-and-locale.html#vítr"
  },"5807": {
    "doc": "Units, Measurement & Locale",
    "title": "Hmotnost",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | Your Setting | You See | . | Metrický | 1.50 kg | . | Imperial (US) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/units-and-locale.html#hmotnost",
    
    "relUrl": "/cs-rCZ/user/units-and-locale.html#hmotnost"
  },"5808": {
    "doc": "Units, Measurement & Locale",
    "title": "Rainfall",
    "content": "Rainfall measurements (1-hour and 24-hour totals) are transmitted as mm and converted for display. | Your Setting | You See | . | Metrický | 12.0 mm | . | Imperial (US) | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/units-and-locale.html#rainfall",
    
    "relUrl": "/cs-rCZ/user/units-and-locale.html#rainfall"
  },"5809": {
    "doc": "Units, Measurement & Locale",
    "title": "Units That Never Change",
    "content": "Some units are international standards and are displayed the same way regardless of your locale: . | Measurement | Unit | Why | . | Barometrický tlak | hPa | International meteorological standard | . | Heading / bearing | ° (degrees) | Universal navigation convention | . | Radiace | µR/h | Standard dosimetry unit | . | GPS coordinates | decimal degrees | Universal geographic standard | . | Humidity, battery, soil moisture | % | Universal | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/units-and-locale.html#units-that-never-change",
    
    "relUrl": "/cs-rCZ/user/units-and-locale.html#units-that-never-change"
  },"5810": {
    "doc": "Units, Measurement & Locale",
    "title": "Date & Time",
    "content": "All timestamps throughout the app — last heard, message times, telemetry logs, chart axes — follow your device’s date and time preferences. | Nastavení | 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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/units-and-locale.html#date--time",
    
    "relUrl": "/cs-rCZ/user/units-and-locale.html#date--time"
  },"5811": {
    "doc": "Units, Measurement & Locale",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region | Return to Meshtastic — values update immediately | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/cs-rCZ/user/units-and-locale.html#changing-your-measurement-system"
  },"5812": {
    "doc": "Units, Measurement & Locale",
    "title": "Related Topics",
    "content": ". | Node Metrics — where temperature, distance, and sensor values are displayed | Telemetry & Sensors — the sensors that produce these measurements | Measurement & Formatting — developer reference for the formatting utilities | Settings — Radio & User — region setting that drives unit selection | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/units-and-locale.html#related-topics",
    
    "relUrl": "/cs-rCZ/user/units-and-locale.html#related-topics"
  },"5813": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": " ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/units-and-locale.html",
    
    "relUrl": "/cs-rCZ/user/units-and-locale.html"
  },"5814": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/units-and-locale.html#units-measurement--locale",
    
    "relUrl": "/bg-rBG/user/units-and-locale.html#units-measurement--locale"
  },"5815": {
    "doc": "Units, Measurement & Locale",
    "title": "Как работи",
    "content": "Meshtastic radios always transmit data in metric units (meters, °C, m/s, hPa, etc.). When the app receives this data, it converts and displays 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. Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/units-and-locale.html#%D0%BA%D0%B0%D0%BA-%D1%80%D0%B0%D0%B1%D0%BE%D1%82%D0%B8",
    
    "relUrl": "/bg-rBG/user/units-and-locale.html#как-работи"
  },"5816": {
    "doc": "Units, Measurement & Locale",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/bg-rBG/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"5817": {
    "doc": "Units, Measurement & Locale",
    "title": "Температура",
    "content": "Temperature values from environment sensors are transmitted as °C and displayed based on your device’s temperature unit preference. | 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. Temperature follows your locale’s temperature preference, independent of the distance system. Locales that mix systems work correctly — a UK phone shows miles for distance but °C for temperature. On Android 14+, the Temperature regional preference (Settings → System → Languages → Regional preferences) overrides the locale default. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/units-and-locale.html#%D1%82%D0%B5%D0%BC%D0%BF%D0%B5%D1%80%D0%B0%D1%82%D1%83%D1%80%D0%B0",
    
    "relUrl": "/bg-rBG/user/units-and-locale.html#температура"
  },"5818": {
    "doc": "Units, Measurement & Locale",
    "title": "Distance & Altitude",
    "content": "Distances between nodes and GPS altitudes are transmitted as meters and automatically scaled and converted. | 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 kilometers 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 | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/units-and-locale.html#distance--altitude",
    
    "relUrl": "/bg-rBG/user/units-and-locale.html#distance--altitude"
  },"5819": {
    "doc": "Units, Measurement & Locale",
    "title": "Скорост",
    "content": "GPS ground speed is displayed in your locale’s preferred speed unit. | Your Setting | You See | . | Метрични | 12 km/h | . | Imperial (US) | 7 mph | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/units-and-locale.html#%D1%81%D0%BA%D0%BE%D1%80%D0%BE%D1%81%D1%82",
    
    "relUrl": "/bg-rBG/user/units-and-locale.html#скорост"
  },"5820": {
    "doc": "Units, Measurement & Locale",
    "title": "Вятър",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | Your Setting | You See | . | Метрични | 18.0 km/h | . | Imperial (US) | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/units-and-locale.html#%D0%B2%D1%8F%D1%82%D1%8A%D1%80",
    
    "relUrl": "/bg-rBG/user/units-and-locale.html#вятър"
  },"5821": {
    "doc": "Units, Measurement & Locale",
    "title": "Тегло",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | Your Setting | You See | . | Метрични | 1.50 kg | . | Imperial (US) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/units-and-locale.html#%D1%82%D0%B5%D0%B3%D0%BB%D0%BE",
    
    "relUrl": "/bg-rBG/user/units-and-locale.html#тегло"
  },"5822": {
    "doc": "Units, Measurement & Locale",
    "title": "Rainfall",
    "content": "Rainfall measurements (1-hour and 24-hour totals) are transmitted as mm and converted for display. | Your Setting | You See | . | Метрични | 12.0 mm | . | Imperial (US) | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/units-and-locale.html#rainfall",
    
    "relUrl": "/bg-rBG/user/units-and-locale.html#rainfall"
  },"5823": {
    "doc": "Units, Measurement & Locale",
    "title": "Units That Never Change",
    "content": "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/h | Standard dosimetry unit | . | GPS coordinates | decimal degrees | Universal geographic standard | . | Humidity, battery, soil moisture | % | Universal | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/units-and-locale.html#units-that-never-change",
    
    "relUrl": "/bg-rBG/user/units-and-locale.html#units-that-never-change"
  },"5824": {
    "doc": "Units, Measurement & Locale",
    "title": "Date & Time",
    "content": "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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/units-and-locale.html#date--time",
    
    "relUrl": "/bg-rBG/user/units-and-locale.html#date--time"
  },"5825": {
    "doc": "Units, Measurement & Locale",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region | Return to Meshtastic — values update immediately | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/bg-rBG/user/units-and-locale.html#changing-your-measurement-system"
  },"5826": {
    "doc": "Units, Measurement & Locale",
    "title": "Свързани теми",
    "content": ". | Node Metrics — where temperature, distance, and sensor values are displayed | Telemetry & Sensors — the sensors that produce these measurements | Measurement & Formatting — developer reference for the formatting utilities | Settings — Radio & User — region setting that drives unit selection | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/units-and-locale.html#%D1%81%D0%B2%D1%8A%D1%80%D0%B7%D0%B0%D0%BD%D0%B8-%D1%82%D0%B5%D0%BC%D0%B8",
    
    "relUrl": "/bg-rBG/user/units-and-locale.html#свързани-теми"
  },"5827": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": " ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/units-and-locale.html",
    
    "relUrl": "/bg-rBG/user/units-and-locale.html"
  },"5828": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/units-and-locale.html#units-measurement--locale",
    
    "relUrl": "/ga-rIE/user/units-and-locale.html#units-measurement--locale"
  },"5829": {
    "doc": "Units, Measurement & Locale",
    "title": "How It Works",
    "content": "Meshtastic radios always transmit data in metric units (meters, °C, m/s, hPa, etc.). When the app receives this data, it converts and displays 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. Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/units-and-locale.html#how-it-works",
    
    "relUrl": "/ga-rIE/user/units-and-locale.html#how-it-works"
  },"5830": {
    "doc": "Units, Measurement & Locale",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/ga-rIE/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"5831": {
    "doc": "Units, Measurement & Locale",
    "title": "Teocht",
    "content": "Temperature values from environment sensors are transmitted as °C and displayed based on your device’s temperature unit preference. | 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. Temperature follows your locale’s temperature preference, independent of the distance system. Locales that mix systems work correctly — a UK phone shows miles for distance but °C for temperature. On Android 14+, the Temperature regional preference (Settings → System → Languages → Regional preferences) overrides the locale default. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/units-and-locale.html#teocht",
    
    "relUrl": "/ga-rIE/user/units-and-locale.html#teocht"
  },"5832": {
    "doc": "Units, Measurement & Locale",
    "title": "Distance & Altitude",
    "content": "Distances between nodes and GPS altitudes are transmitted as meters and automatically scaled and converted. | 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 kilometers 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 | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/units-and-locale.html#distance--altitude",
    
    "relUrl": "/ga-rIE/user/units-and-locale.html#distance--altitude"
  },"5833": {
    "doc": "Units, Measurement & Locale",
    "title": "Speed",
    "content": "GPS ground speed is displayed in your locale’s preferred speed unit. | Your Setting | You See | . | Metric | 12 km/h | . | Imperial (US) | 7 mph | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/units-and-locale.html#speed",
    
    "relUrl": "/ga-rIE/user/units-and-locale.html#speed"
  },"5834": {
    "doc": "Units, Measurement & Locale",
    "title": "Wind",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | Your Setting | You See | . | Metric | 18.0 km/h | . | Imperial (US) | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/units-and-locale.html#wind",
    
    "relUrl": "/ga-rIE/user/units-and-locale.html#wind"
  },"5835": {
    "doc": "Units, Measurement & Locale",
    "title": "Weight",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | Your Setting | You See | . | Metric | 1.50 kg | . | Imperial (US) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/units-and-locale.html#weight",
    
    "relUrl": "/ga-rIE/user/units-and-locale.html#weight"
  },"5836": {
    "doc": "Units, Measurement & Locale",
    "title": "Rainfall",
    "content": "Rainfall measurements (1-hour and 24-hour totals) are transmitted as mm and converted for display. | Your Setting | You See | . | Metric | 12.0 mm | . | Imperial (US) | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/units-and-locale.html#rainfall",
    
    "relUrl": "/ga-rIE/user/units-and-locale.html#rainfall"
  },"5837": {
    "doc": "Units, Measurement & Locale",
    "title": "Units That Never Change",
    "content": "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/h | Standard dosimetry unit | . | GPS coordinates | decimal degrees | Universal geographic standard | . | Humidity, battery, soil moisture | % | Universal | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/units-and-locale.html#units-that-never-change",
    
    "relUrl": "/ga-rIE/user/units-and-locale.html#units-that-never-change"
  },"5838": {
    "doc": "Units, Measurement & Locale",
    "title": "Date & Time",
    "content": "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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/units-and-locale.html#date--time",
    
    "relUrl": "/ga-rIE/user/units-and-locale.html#date--time"
  },"5839": {
    "doc": "Units, Measurement & Locale",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region | Return to Meshtastic — values update immediately | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/ga-rIE/user/units-and-locale.html#changing-your-measurement-system"
  },"5840": {
    "doc": "Units, Measurement & Locale",
    "title": "Related Topics",
    "content": ". | Node Metrics — where temperature, distance, and sensor values are displayed | Telemetry & Sensors — the sensors that produce these measurements | Measurement & Formatting — developer reference for the formatting utilities | Settings — Radio & User — region setting that drives unit selection | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/units-and-locale.html#related-topics",
    
    "relUrl": "/ga-rIE/user/units-and-locale.html#related-topics"
  },"5841": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": " ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/units-and-locale.html",
    
    "relUrl": "/ga-rIE/user/units-and-locale.html"
  },"5842": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/units-and-locale.html#units-measurement--locale",
    
    "relUrl": "/fr-rCA/user/units-and-locale.html#units-measurement--locale"
  },"5843": {
    "doc": "Units, Measurement & Locale",
    "title": "Comment ça marche",
    "content": "Meshtastic radios always transmit data in metric units (meters, °C, m/s, hPa, etc.). When the app receives this data, it converts and displays values in whatever unit system your device’s locale specifies. Sur Android, vos préférences de mesure sont déterminées par les paramètres de Langue et Région de votre système. Sur l’application de bureau (JVM), la Locale par défaut de la JVM est utilisée. Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/units-and-locale.html#comment-%C3%A7a-marche",
    
    "relUrl": "/fr-rCA/user/units-and-locale.html#comment-ça-marche"
  },"5844": {
    "doc": "Units, Measurement & Locale",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/fr-rCA/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"5845": {
    "doc": "Units, Measurement & Locale",
    "title": "Température",
    "content": "Temperature values from environment sensors are transmitted as °C and displayed based on your device’s temperature unit preference. | 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. Temperature follows your locale’s temperature preference, independent of the distance system. Locales that mix systems work correctly — a UK phone shows miles for distance but °C for temperature. On Android 14+, the Temperature regional preference (Settings → System → Languages → Regional preferences) overrides the locale default. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/units-and-locale.html#temp%C3%A9rature",
    
    "relUrl": "/fr-rCA/user/units-and-locale.html#température"
  },"5846": {
    "doc": "Units, Measurement & Locale",
    "title": "Distance & Altitude",
    "content": "Distances between nodes and GPS altitudes are transmitted as meters and automatically scaled and converted. | 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 kilometers 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 | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/units-and-locale.html#distance--altitude",
    
    "relUrl": "/fr-rCA/user/units-and-locale.html#distance--altitude"
  },"5847": {
    "doc": "Units, Measurement & Locale",
    "title": "Vitesse",
    "content": "GPS ground speed is displayed in your locale’s preferred speed unit. | Your Setting | You See | . | Metric | 12 km/h | . | Imperial (US) | 7 mph | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/units-and-locale.html#vitesse",
    
    "relUrl": "/fr-rCA/user/units-and-locale.html#vitesse"
  },"5848": {
    "doc": "Units, Measurement & Locale",
    "title": "Vent",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | Your Setting | You See | . | Metric | 18.0 km/h | . | Imperial (US) | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/units-and-locale.html#vent",
    
    "relUrl": "/fr-rCA/user/units-and-locale.html#vent"
  },"5849": {
    "doc": "Units, Measurement & Locale",
    "title": "Poids",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | Your Setting | You See | . | Metric | 1.50 kg | . | Imperial (US) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/units-and-locale.html#poids",
    
    "relUrl": "/fr-rCA/user/units-and-locale.html#poids"
  },"5850": {
    "doc": "Units, Measurement & Locale",
    "title": "Rainfall",
    "content": "Rainfall measurements (1-hour and 24-hour totals) are transmitted as mm and converted for display. | Vos réglages | Vous voyez | . | Métrique | 12.0 mm | . | Impérial (États-Unis) | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/units-and-locale.html#rainfall",
    
    "relUrl": "/fr-rCA/user/units-and-locale.html#rainfall"
  },"5851": {
    "doc": "Units, Measurement & Locale",
    "title": "Units That Never Change",
    "content": "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/h | Standard dosimetry unit | . | GPS coordinates | decimal degrees | Universal geographic standard | . | Humidity, battery, soil moisture | % | Universal | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/units-and-locale.html#units-that-never-change",
    
    "relUrl": "/fr-rCA/user/units-and-locale.html#units-that-never-change"
  },"5852": {
    "doc": "Units, Measurement & Locale",
    "title": "Date & Time",
    "content": "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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/units-and-locale.html#date--time",
    
    "relUrl": "/fr-rCA/user/units-and-locale.html#date--time"
  },"5853": {
    "doc": "Units, Measurement & Locale",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region | Return to Meshtastic — values update immediately | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/fr-rCA/user/units-and-locale.html#changing-your-measurement-system"
  },"5854": {
    "doc": "Units, Measurement & Locale",
    "title": "Related Topics",
    "content": ". | Node Metrics — where temperature, distance, and sensor values are displayed | Telemetry & Sensors — the sensors that produce these measurements | Measurement & Formatting — developer reference for the formatting utilities | Settings — Radio & User — region setting that drives unit selection | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/units-and-locale.html#related-topics",
    
    "relUrl": "/fr-rCA/user/units-and-locale.html#related-topics"
  },"5855": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": " ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/units-and-locale.html",
    
    "relUrl": "/fr-rCA/user/units-and-locale.html"
  },"5856": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/srp/user/units-and-locale.html#units-measurement--locale",
    
    "relUrl": "/srp/user/units-and-locale.html#units-measurement--locale"
  },"5857": {
    "doc": "Units, Measurement & Locale",
    "title": "How It Works",
    "content": "Meshtastic radios always transmit data in metric units (meters, °C, m/s, hPa, etc.). When the app receives this data, it converts and displays 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. Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/srp/user/units-and-locale.html#how-it-works",
    
    "relUrl": "/srp/user/units-and-locale.html#how-it-works"
  },"5858": {
    "doc": "Units, Measurement & Locale",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/srp/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/srp/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"5859": {
    "doc": "Units, Measurement & Locale",
    "title": "Температура",
    "content": "Temperature values from environment sensors are transmitted as °C and displayed based on your device’s temperature unit preference. | 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. Temperature follows your locale’s temperature preference, independent of the distance system. Locales that mix systems work correctly — a UK phone shows miles for distance but °C for temperature. On Android 14+, the Temperature regional preference (Settings → System → Languages → Regional preferences) overrides the locale default. ",
    "url": "/Meshtastic-Android/main/srp/user/units-and-locale.html#%D1%82%D0%B5%D0%BC%D0%BF%D0%B5%D1%80%D0%B0%D1%82%D1%83%D1%80%D0%B0",
    
    "relUrl": "/srp/user/units-and-locale.html#температура"
  },"5860": {
    "doc": "Units, Measurement & Locale",
    "title": "Distance & Altitude",
    "content": "Distances between nodes and GPS altitudes are transmitted as meters and automatically scaled and converted. | 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 kilometers 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 | . ",
    "url": "/Meshtastic-Android/main/srp/user/units-and-locale.html#distance--altitude",
    
    "relUrl": "/srp/user/units-and-locale.html#distance--altitude"
  },"5861": {
    "doc": "Units, Measurement & Locale",
    "title": "Брзина",
    "content": "GPS ground speed is displayed in your locale’s preferred speed unit. | Your Setting | You See | . | Метрика | 12 km/h | . | Imperial (US) | 7 mph | . ",
    "url": "/Meshtastic-Android/main/srp/user/units-and-locale.html#%D0%B1%D1%80%D0%B7%D0%B8%D0%BD%D0%B0",
    
    "relUrl": "/srp/user/units-and-locale.html#брзина"
  },"5862": {
    "doc": "Units, Measurement & Locale",
    "title": "Wind",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | Your Setting | You See | . | Метрика | 18.0 km/h | . | Imperial (US) | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/srp/user/units-and-locale.html#wind",
    
    "relUrl": "/srp/user/units-and-locale.html#wind"
  },"5863": {
    "doc": "Units, Measurement & Locale",
    "title": "Weight",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | Your Setting | You See | . | Метрика | 1.50 kg | . | Imperial (US) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/srp/user/units-and-locale.html#weight",
    
    "relUrl": "/srp/user/units-and-locale.html#weight"
  },"5864": {
    "doc": "Units, Measurement & Locale",
    "title": "Rainfall",
    "content": "Rainfall measurements (1-hour and 24-hour totals) are transmitted as mm and converted for display. | Your Setting | You See | . | Метрика | 12.0 mm | . | Imperial (US) | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/srp/user/units-and-locale.html#rainfall",
    
    "relUrl": "/srp/user/units-and-locale.html#rainfall"
  },"5865": {
    "doc": "Units, Measurement & Locale",
    "title": "Units That Never Change",
    "content": "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/h | Standard dosimetry unit | . | GPS coordinates | decimal degrees | Universal geographic standard | . | Humidity, battery, soil moisture | % | Universal | . ",
    "url": "/Meshtastic-Android/main/srp/user/units-and-locale.html#units-that-never-change",
    
    "relUrl": "/srp/user/units-and-locale.html#units-that-never-change"
  },"5866": {
    "doc": "Units, Measurement & Locale",
    "title": "Date & Time",
    "content": "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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/srp/user/units-and-locale.html#date--time",
    
    "relUrl": "/srp/user/units-and-locale.html#date--time"
  },"5867": {
    "doc": "Units, Measurement & Locale",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region | Return to Meshtastic — values update immediately | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/srp/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/srp/user/units-and-locale.html#changing-your-measurement-system"
  },"5868": {
    "doc": "Units, Measurement & Locale",
    "title": "Related Topics",
    "content": ". | Node Metrics — where temperature, distance, and sensor values are displayed | Telemetry & Sensors — the sensors that produce these measurements | Measurement & Formatting — developer reference for the formatting utilities | Settings — Radio & User — region setting that drives unit selection | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/srp/user/units-and-locale.html#related-topics",
    
    "relUrl": "/srp/user/units-and-locale.html#related-topics"
  },"5869": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": " ",
    "url": "/Meshtastic-Android/main/srp/user/units-and-locale.html",
    
    "relUrl": "/srp/user/units-and-locale.html"
  },"5870": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/units-and-locale.html#units-measurement--locale",
    
    "relUrl": "/ca-rES/user/units-and-locale.html#units-measurement--locale"
  },"5871": {
    "doc": "Units, Measurement & Locale",
    "title": "How It Works",
    "content": "Meshtastic radios always transmit data in metric units (meters, °C, m/s, hPa, etc.). When the app receives this data, it converts and displays 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. Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/units-and-locale.html#how-it-works",
    
    "relUrl": "/ca-rES/user/units-and-locale.html#how-it-works"
  },"5872": {
    "doc": "Units, Measurement & Locale",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/ca-rES/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"5873": {
    "doc": "Units, Measurement & Locale",
    "title": "Temperature",
    "content": "Temperature values from environment sensors are transmitted as °C and displayed based on your device’s temperature unit preference. | 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. Temperature follows your locale’s temperature preference, independent of the distance system. Locales that mix systems work correctly — a UK phone shows miles for distance but °C for temperature. On Android 14+, the Temperature regional preference (Settings → System → Languages → Regional preferences) overrides the locale default. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/units-and-locale.html#temperature",
    
    "relUrl": "/ca-rES/user/units-and-locale.html#temperature"
  },"5874": {
    "doc": "Units, Measurement & Locale",
    "title": "Distance & Altitude",
    "content": "Distances between nodes and GPS altitudes are transmitted as meters and automatically scaled and converted. | 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 kilometers 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 | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/units-and-locale.html#distance--altitude",
    
    "relUrl": "/ca-rES/user/units-and-locale.html#distance--altitude"
  },"5875": {
    "doc": "Units, Measurement & Locale",
    "title": "Speed",
    "content": "GPS ground speed is displayed in your locale’s preferred speed unit. | Your Setting | You See | . | Metric | 12 km/h | . | Imperial (US) | 7 mph | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/units-and-locale.html#speed",
    
    "relUrl": "/ca-rES/user/units-and-locale.html#speed"
  },"5876": {
    "doc": "Units, Measurement & Locale",
    "title": "Wind",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | Your Setting | You See | . | Metric | 18.0 km/h | . | Imperial (US) | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/units-and-locale.html#wind",
    
    "relUrl": "/ca-rES/user/units-and-locale.html#wind"
  },"5877": {
    "doc": "Units, Measurement & Locale",
    "title": "Weight",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | Your Setting | You See | . | Metric | 1.50 kg | . | Imperial (US) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/units-and-locale.html#weight",
    
    "relUrl": "/ca-rES/user/units-and-locale.html#weight"
  },"5878": {
    "doc": "Units, Measurement & Locale",
    "title": "Rainfall",
    "content": "Rainfall measurements (1-hour and 24-hour totals) are transmitted as mm and converted for display. | Your Setting | You See | . | Metric | 12.0 mm | . | Imperial (US) | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/units-and-locale.html#rainfall",
    
    "relUrl": "/ca-rES/user/units-and-locale.html#rainfall"
  },"5879": {
    "doc": "Units, Measurement & Locale",
    "title": "Units That Never Change",
    "content": "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/h | Standard dosimetry unit | . | GPS coordinates | decimal degrees | Universal geographic standard | . | Humidity, battery, soil moisture | % | Universal | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/units-and-locale.html#units-that-never-change",
    
    "relUrl": "/ca-rES/user/units-and-locale.html#units-that-never-change"
  },"5880": {
    "doc": "Units, Measurement & Locale",
    "title": "Date & Time",
    "content": "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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/units-and-locale.html#date--time",
    
    "relUrl": "/ca-rES/user/units-and-locale.html#date--time"
  },"5881": {
    "doc": "Units, Measurement & Locale",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region | Return to Meshtastic — values update immediately | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/ca-rES/user/units-and-locale.html#changing-your-measurement-system"
  },"5882": {
    "doc": "Units, Measurement & Locale",
    "title": "Related Topics",
    "content": ". | Node Metrics — where temperature, distance, and sensor values are displayed | Telemetry & Sensors — the sensors that produce these measurements | Measurement & Formatting — developer reference for the formatting utilities | Settings — Radio & User — region setting that drives unit selection | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/units-and-locale.html#related-topics",
    
    "relUrl": "/ca-rES/user/units-and-locale.html#related-topics"
  },"5883": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": " ",
    "url": "/Meshtastic-Android/main/ca-rES/user/units-and-locale.html",
    
    "relUrl": "/ca-rES/user/units-and-locale.html"
  },"5884": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/units-and-locale.html#units-measurement--locale",
    
    "relUrl": "/ko-rKR/user/units-and-locale.html#units-measurement--locale"
  },"5885": {
    "doc": "Units, Measurement & Locale",
    "title": "How It Works",
    "content": "Meshtastic radios always transmit data in metric units (meters, °C, m/s, hPa, etc.). When the app receives this data, it converts and displays 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. Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/units-and-locale.html#how-it-works",
    
    "relUrl": "/ko-rKR/user/units-and-locale.html#how-it-works"
  },"5886": {
    "doc": "Units, Measurement & Locale",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/ko-rKR/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"5887": {
    "doc": "Units, Measurement & Locale",
    "title": "온도",
    "content": "Temperature values from environment sensors are transmitted as °C and displayed based on your device’s temperature unit preference. | 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. Temperature follows your locale’s temperature preference, independent of the distance system. Locales that mix systems work correctly — a UK phone shows miles for distance but °C for temperature. On Android 14+, the Temperature regional preference (Settings → System → Languages → Regional preferences) overrides the locale default. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/units-and-locale.html#%EC%98%A8%EB%8F%84",
    
    "relUrl": "/ko-rKR/user/units-and-locale.html#온도"
  },"5888": {
    "doc": "Units, Measurement & Locale",
    "title": "Distance & Altitude",
    "content": "Distances between nodes and GPS altitudes are transmitted as meters and automatically scaled and converted. | 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 kilometers 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 | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/units-and-locale.html#distance--altitude",
    
    "relUrl": "/ko-rKR/user/units-and-locale.html#distance--altitude"
  },"5889": {
    "doc": "Units, Measurement & Locale",
    "title": "Speed",
    "content": "GPS ground speed is displayed in your locale’s preferred speed unit. | Your Setting | You See | . | Metric | 12 km/h | . | Imperial (US) | 7 mph | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/units-and-locale.html#speed",
    
    "relUrl": "/ko-rKR/user/units-and-locale.html#speed"
  },"5890": {
    "doc": "Units, Measurement & Locale",
    "title": "바람",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | Your Setting | You See | . | Metric | 18.0 km/h | . | Imperial (US) | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/units-and-locale.html#%EB%B0%94%EB%9E%8C",
    
    "relUrl": "/ko-rKR/user/units-and-locale.html#바람"
  },"5891": {
    "doc": "Units, Measurement & Locale",
    "title": "무게",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | Your Setting | You See | . | Metric | 1.50 kg | . | Imperial (US) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/units-and-locale.html#%EB%AC%B4%EA%B2%8C",
    
    "relUrl": "/ko-rKR/user/units-and-locale.html#무게"
  },"5892": {
    "doc": "Units, Measurement & Locale",
    "title": "Rainfall",
    "content": "Rainfall measurements (1-hour and 24-hour totals) are transmitted as mm and converted for display. | Your Setting | You See | . | Metric | 12.0 mm | . | Imperial (US) | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/units-and-locale.html#rainfall",
    
    "relUrl": "/ko-rKR/user/units-and-locale.html#rainfall"
  },"5893": {
    "doc": "Units, Measurement & Locale",
    "title": "Units That Never Change",
    "content": "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/h | Standard dosimetry unit | . | GPS coordinates | decimal degrees | Universal geographic standard | . | Humidity, battery, soil moisture | % | Universal | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/units-and-locale.html#units-that-never-change",
    
    "relUrl": "/ko-rKR/user/units-and-locale.html#units-that-never-change"
  },"5894": {
    "doc": "Units, Measurement & Locale",
    "title": "Date & Time",
    "content": "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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/units-and-locale.html#date--time",
    
    "relUrl": "/ko-rKR/user/units-and-locale.html#date--time"
  },"5895": {
    "doc": "Units, Measurement & Locale",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region | Return to Meshtastic — values update immediately | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/ko-rKR/user/units-and-locale.html#changing-your-measurement-system"
  },"5896": {
    "doc": "Units, Measurement & Locale",
    "title": "Related Topics",
    "content": ". | Node Metrics — where temperature, distance, and sensor values are displayed | Telemetry & Sensors — the sensors that produce these measurements | Measurement & Formatting — developer reference for the formatting utilities | Settings — Radio & User — region setting that drives unit selection | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/units-and-locale.html#related-topics",
    
    "relUrl": "/ko-rKR/user/units-and-locale.html#related-topics"
  },"5897": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": " ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/units-and-locale.html",
    
    "relUrl": "/ko-rKR/user/units-and-locale.html"
  },"5898": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/units-and-locale.html#units-measurement--locale",
    
    "relUrl": "/sv-rSE/user/units-and-locale.html#units-measurement--locale"
  },"5899": {
    "doc": "Units, Measurement & Locale",
    "title": "How It Works",
    "content": "Meshtastic radios always transmit data in metric units (meters, °C, m/s, hPa, etc.). When the app receives this data, it converts and displays 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. Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/units-and-locale.html#how-it-works",
    
    "relUrl": "/sv-rSE/user/units-and-locale.html#how-it-works"
  },"5900": {
    "doc": "Units, Measurement & Locale",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/sv-rSE/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"5901": {
    "doc": "Units, Measurement & Locale",
    "title": "Temperatur",
    "content": "Temperature values from environment sensors are transmitted as °C and displayed based on your device’s temperature unit preference. | 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. Temperature follows your locale’s temperature preference, independent of the distance system. Locales that mix systems work correctly — a UK phone shows miles for distance but °C for temperature. On Android 14+, the Temperature regional preference (Settings → System → Languages → Regional preferences) overrides the locale default. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/units-and-locale.html#temperatur",
    
    "relUrl": "/sv-rSE/user/units-and-locale.html#temperatur"
  },"5902": {
    "doc": "Units, Measurement & Locale",
    "title": "Distance & Altitude",
    "content": "Distances between nodes and GPS altitudes are transmitted as meters and automatically scaled and converted. | Your Setting | Small Distance | Large Distance | Altitud | . | 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 kilometers 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 | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/units-and-locale.html#distance--altitude",
    
    "relUrl": "/sv-rSE/user/units-and-locale.html#distance--altitude"
  },"5903": {
    "doc": "Units, Measurement & Locale",
    "title": "Hastighet",
    "content": "GPS ground speed is displayed in your locale’s preferred speed unit. | Your Setting | You See | . | Metric | 12 km/h | . | Imperial (US) | 7 mph | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/units-and-locale.html#hastighet",
    
    "relUrl": "/sv-rSE/user/units-and-locale.html#hastighet"
  },"5904": {
    "doc": "Units, Measurement & Locale",
    "title": "Vind",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | Your Setting | You See | . | Metric | 18.0 km/h | . | Imperial (US) | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/units-and-locale.html#vind",
    
    "relUrl": "/sv-rSE/user/units-and-locale.html#vind"
  },"5905": {
    "doc": "Units, Measurement & Locale",
    "title": "Vikt",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | Your Setting | You See | . | Metric | 1.50 kg | . | Imperial (US) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/units-and-locale.html#vikt",
    
    "relUrl": "/sv-rSE/user/units-and-locale.html#vikt"
  },"5906": {
    "doc": "Units, Measurement & Locale",
    "title": "Rainfall",
    "content": "Rainfall measurements (1-hour and 24-hour totals) are transmitted as mm and converted for display. | Your Setting | You See | . | Metric | 12.0 mm | . | Imperial (US) | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/units-and-locale.html#rainfall",
    
    "relUrl": "/sv-rSE/user/units-and-locale.html#rainfall"
  },"5907": {
    "doc": "Units, Measurement & Locale",
    "title": "Units That Never Change",
    "content": "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 | . | Strålning | µR/h | Standard dosimetry unit | . | GPS coordinates | decimal degrees | Universal geographic standard | . | Humidity, battery, soil moisture | % | Universal | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/units-and-locale.html#units-that-never-change",
    
    "relUrl": "/sv-rSE/user/units-and-locale.html#units-that-never-change"
  },"5908": {
    "doc": "Units, Measurement & Locale",
    "title": "Date & Time",
    "content": "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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/units-and-locale.html#date--time",
    
    "relUrl": "/sv-rSE/user/units-and-locale.html#date--time"
  },"5909": {
    "doc": "Units, Measurement & Locale",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region | Return to Meshtastic — values update immediately | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/sv-rSE/user/units-and-locale.html#changing-your-measurement-system"
  },"5910": {
    "doc": "Units, Measurement & Locale",
    "title": "Related Topics",
    "content": ". | Node Metrics — where temperature, distance, and sensor values are displayed | Telemetry & Sensors — the sensors that produce these measurements | Measurement & Formatting — developer reference for the formatting utilities | Settings — Radio & User — region setting that drives unit selection | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/units-and-locale.html#related-topics",
    
    "relUrl": "/sv-rSE/user/units-and-locale.html#related-topics"
  },"5911": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": " ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/units-and-locale.html",
    
    "relUrl": "/sv-rSE/user/units-and-locale.html"
  },"5912": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/units-and-locale.html#units-measurement--locale",
    
    "relUrl": "/ht-rHT/user/units-and-locale.html#units-measurement--locale"
  },"5913": {
    "doc": "Units, Measurement & Locale",
    "title": "How It Works",
    "content": "Meshtastic radios always transmit data in metric units (meters, °C, m/s, hPa, etc.). When the app receives this data, it converts and displays 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. Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/units-and-locale.html#how-it-works",
    
    "relUrl": "/ht-rHT/user/units-and-locale.html#how-it-works"
  },"5914": {
    "doc": "Units, Measurement & Locale",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/ht-rHT/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"5915": {
    "doc": "Units, Measurement & Locale",
    "title": "Tanperati",
    "content": "Temperature values from environment sensors are transmitted as °C and displayed based on your device’s temperature unit preference. | 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. Temperature follows your locale’s temperature preference, independent of the distance system. Locales that mix systems work correctly — a UK phone shows miles for distance but °C for temperature. On Android 14+, the Temperature regional preference (Settings → System → Languages → Regional preferences) overrides the locale default. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/units-and-locale.html#tanperati",
    
    "relUrl": "/ht-rHT/user/units-and-locale.html#tanperati"
  },"5916": {
    "doc": "Units, Measurement & Locale",
    "title": "Distance & Altitude",
    "content": "Distances between nodes and GPS altitudes are transmitted as meters and automatically scaled and converted. | 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 kilometers 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 | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/units-and-locale.html#distance--altitude",
    
    "relUrl": "/ht-rHT/user/units-and-locale.html#distance--altitude"
  },"5917": {
    "doc": "Units, Measurement & Locale",
    "title": "Speed",
    "content": "GPS ground speed is displayed in your locale’s preferred speed unit. | Your Setting | You See | . | Metric | 12 km/h | . | Imperial (US) | 7 mph | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/units-and-locale.html#speed",
    
    "relUrl": "/ht-rHT/user/units-and-locale.html#speed"
  },"5918": {
    "doc": "Units, Measurement & Locale",
    "title": "Wind",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | Your Setting | You See | . | Metric | 18.0 km/h | . | Imperial (US) | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/units-and-locale.html#wind",
    
    "relUrl": "/ht-rHT/user/units-and-locale.html#wind"
  },"5919": {
    "doc": "Units, Measurement & Locale",
    "title": "Weight",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | Your Setting | You See | . | Metric | 1.50 kg | . | Imperial (US) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/units-and-locale.html#weight",
    
    "relUrl": "/ht-rHT/user/units-and-locale.html#weight"
  },"5920": {
    "doc": "Units, Measurement & Locale",
    "title": "Rainfall",
    "content": "Rainfall measurements (1-hour and 24-hour totals) are transmitted as mm and converted for display. | Your Setting | You See | . | Metric | 12.0 mm | . | Imperial (US) | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/units-and-locale.html#rainfall",
    
    "relUrl": "/ht-rHT/user/units-and-locale.html#rainfall"
  },"5921": {
    "doc": "Units, Measurement & Locale",
    "title": "Units That Never Change",
    "content": "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/h | Standard dosimetry unit | . | GPS coordinates | decimal degrees | Universal geographic standard | . | Humidity, battery, soil moisture | % | Universal | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/units-and-locale.html#units-that-never-change",
    
    "relUrl": "/ht-rHT/user/units-and-locale.html#units-that-never-change"
  },"5922": {
    "doc": "Units, Measurement & Locale",
    "title": "Date & Time",
    "content": "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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/units-and-locale.html#date--time",
    
    "relUrl": "/ht-rHT/user/units-and-locale.html#date--time"
  },"5923": {
    "doc": "Units, Measurement & Locale",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region | Return to Meshtastic — values update immediately | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/ht-rHT/user/units-and-locale.html#changing-your-measurement-system"
  },"5924": {
    "doc": "Units, Measurement & Locale",
    "title": "Related Topics",
    "content": ". | Node Metrics — where temperature, distance, and sensor values are displayed | Telemetry & Sensors — the sensors that produce these measurements | Measurement & Formatting — developer reference for the formatting utilities | Settings — Radio & User — region setting that drives unit selection | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/units-and-locale.html#related-topics",
    
    "relUrl": "/ht-rHT/user/units-and-locale.html#related-topics"
  },"5925": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": " ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/units-and-locale.html",
    
    "relUrl": "/ht-rHT/user/units-and-locale.html"
  },"5926": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/units-and-locale.html#units-measurement--locale",
    
    "relUrl": "/sr-rLatn/user/units-and-locale.html#units-measurement--locale"
  },"5927": {
    "doc": "Units, Measurement & Locale",
    "title": "How It Works",
    "content": "Meshtastic radios always transmit data in metric units (meters, °C, m/s, hPa, etc.). When the app receives this data, it converts and displays 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. Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/units-and-locale.html#how-it-works",
    
    "relUrl": "/sr-rLatn/user/units-and-locale.html#how-it-works"
  },"5928": {
    "doc": "Units, Measurement & Locale",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/sr-rLatn/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"5929": {
    "doc": "Units, Measurement & Locale",
    "title": "Температура",
    "content": "Temperature values from environment sensors are transmitted as °C and displayed based on your device’s temperature unit preference. | 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. Temperature follows your locale’s temperature preference, independent of the distance system. Locales that mix systems work correctly — a UK phone shows miles for distance but °C for temperature. On Android 14+, the Temperature regional preference (Settings → System → Languages → Regional preferences) overrides the locale default. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/units-and-locale.html#%D1%82%D0%B5%D0%BC%D0%BF%D0%B5%D1%80%D0%B0%D1%82%D1%83%D1%80%D0%B0",
    
    "relUrl": "/sr-rLatn/user/units-and-locale.html#температура"
  },"5930": {
    "doc": "Units, Measurement & Locale",
    "title": "Distance & Altitude",
    "content": "Distances between nodes and GPS altitudes are transmitted as meters and automatically scaled and converted. | 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 kilometers 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 | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/units-and-locale.html#distance--altitude",
    
    "relUrl": "/sr-rLatn/user/units-and-locale.html#distance--altitude"
  },"5931": {
    "doc": "Units, Measurement & Locale",
    "title": "Брзина",
    "content": "GPS ground speed is displayed in your locale’s preferred speed unit. | Your Setting | You See | . | Метрика | 12 km/h | . | Imperial (US) | 7 mph | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/units-and-locale.html#%D0%B1%D1%80%D0%B7%D0%B8%D0%BD%D0%B0",
    
    "relUrl": "/sr-rLatn/user/units-and-locale.html#брзина"
  },"5932": {
    "doc": "Units, Measurement & Locale",
    "title": "Wind",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | Your Setting | You See | . | Метрика | 18.0 km/h | . | Imperial (US) | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/units-and-locale.html#wind",
    
    "relUrl": "/sr-rLatn/user/units-and-locale.html#wind"
  },"5933": {
    "doc": "Units, Measurement & Locale",
    "title": "Weight",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | Your Setting | You See | . | Метрика | 1.50 kg | . | Imperial (US) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/units-and-locale.html#weight",
    
    "relUrl": "/sr-rLatn/user/units-and-locale.html#weight"
  },"5934": {
    "doc": "Units, Measurement & Locale",
    "title": "Rainfall",
    "content": "Rainfall measurements (1-hour and 24-hour totals) are transmitted as mm and converted for display. | Your Setting | You See | . | Метрика | 12.0 mm | . | Imperial (US) | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/units-and-locale.html#rainfall",
    
    "relUrl": "/sr-rLatn/user/units-and-locale.html#rainfall"
  },"5935": {
    "doc": "Units, Measurement & Locale",
    "title": "Units That Never Change",
    "content": "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/h | Standard dosimetry unit | . | GPS coordinates | decimal degrees | Universal geographic standard | . | Humidity, battery, soil moisture | % | Universal | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/units-and-locale.html#units-that-never-change",
    
    "relUrl": "/sr-rLatn/user/units-and-locale.html#units-that-never-change"
  },"5936": {
    "doc": "Units, Measurement & Locale",
    "title": "Date & Time",
    "content": "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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/units-and-locale.html#date--time",
    
    "relUrl": "/sr-rLatn/user/units-and-locale.html#date--time"
  },"5937": {
    "doc": "Units, Measurement & Locale",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region | Return to Meshtastic — values update immediately | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/sr-rLatn/user/units-and-locale.html#changing-your-measurement-system"
  },"5938": {
    "doc": "Units, Measurement & Locale",
    "title": "Related Topics",
    "content": ". | Node Metrics — where temperature, distance, and sensor values are displayed | Telemetry & Sensors — the sensors that produce these measurements | Measurement & Formatting — developer reference for the formatting utilities | Settings — Radio & User — region setting that drives unit selection | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/units-and-locale.html#related-topics",
    
    "relUrl": "/sr-rLatn/user/units-and-locale.html#related-topics"
  },"5939": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": " ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/units-and-locale.html",
    
    "relUrl": "/sr-rLatn/user/units-and-locale.html"
  },"5940": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/units-and-locale.html#units-measurement--locale",
    
    "relUrl": "/nl-rNL/user/units-and-locale.html#units-measurement--locale"
  },"5941": {
    "doc": "Units, Measurement & Locale",
    "title": "How It Works",
    "content": "Meshtastic radios always transmit data in metric units (meters, °C, m/s, hPa, etc.). When the app receives this data, it converts and displays 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. Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/units-and-locale.html#how-it-works",
    
    "relUrl": "/nl-rNL/user/units-and-locale.html#how-it-works"
  },"5942": {
    "doc": "Units, Measurement & Locale",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/nl-rNL/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"5943": {
    "doc": "Units, Measurement & Locale",
    "title": "Temperatuur",
    "content": "Temperature values from environment sensors are transmitted as °C and displayed based on your device’s temperature unit preference. | 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. Temperature follows your locale’s temperature preference, independent of the distance system. Locales that mix systems work correctly — a UK phone shows miles for distance but °C for temperature. On Android 14+, the Temperature regional preference (Settings → System → Languages → Regional preferences) overrides the locale default. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/units-and-locale.html#temperatuur",
    
    "relUrl": "/nl-rNL/user/units-and-locale.html#temperatuur"
  },"5944": {
    "doc": "Units, Measurement & Locale",
    "title": "Distance & Altitude",
    "content": "Distances between nodes and GPS altitudes are transmitted as meters and automatically scaled and converted. | 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 kilometers 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 | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/units-and-locale.html#distance--altitude",
    
    "relUrl": "/nl-rNL/user/units-and-locale.html#distance--altitude"
  },"5945": {
    "doc": "Units, Measurement & Locale",
    "title": "Speed",
    "content": "GPS ground speed is displayed in your locale’s preferred speed unit. | Your Setting | You See | . | Metric | 12 km/h | . | Imperial (US) | 7 mph | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/units-and-locale.html#speed",
    
    "relUrl": "/nl-rNL/user/units-and-locale.html#speed"
  },"5946": {
    "doc": "Units, Measurement & Locale",
    "title": "Wind",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | Your Setting | You See | . | Metric | 18.0 km/h | . | Imperial (US) | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/units-and-locale.html#wind",
    
    "relUrl": "/nl-rNL/user/units-and-locale.html#wind"
  },"5947": {
    "doc": "Units, Measurement & Locale",
    "title": "Gewicht",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | Your Setting | You See | . | Metric | 1.50 kg | . | Imperial (US) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/units-and-locale.html#gewicht",
    
    "relUrl": "/nl-rNL/user/units-and-locale.html#gewicht"
  },"5948": {
    "doc": "Units, Measurement & Locale",
    "title": "Rainfall",
    "content": "Rainfall measurements (1-hour and 24-hour totals) are transmitted as mm and converted for display. | Your Setting | You See | . | Metric | 12.0 mm | . | Imperial (US) | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/units-and-locale.html#rainfall",
    
    "relUrl": "/nl-rNL/user/units-and-locale.html#rainfall"
  },"5949": {
    "doc": "Units, Measurement & Locale",
    "title": "Units That Never Change",
    "content": "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 | . | Straling | µR/h | Standard dosimetry unit | . | GPS coordinates | decimal degrees | Universal geographic standard | . | Humidity, battery, soil moisture | % | Universal | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/units-and-locale.html#units-that-never-change",
    
    "relUrl": "/nl-rNL/user/units-and-locale.html#units-that-never-change"
  },"5950": {
    "doc": "Units, Measurement & Locale",
    "title": "Date & Time",
    "content": "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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/units-and-locale.html#date--time",
    
    "relUrl": "/nl-rNL/user/units-and-locale.html#date--time"
  },"5951": {
    "doc": "Units, Measurement & Locale",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region | Return to Meshtastic — values update immediately | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/nl-rNL/user/units-and-locale.html#changing-your-measurement-system"
  },"5952": {
    "doc": "Units, Measurement & Locale",
    "title": "Related Topics",
    "content": ". | Node Metrics — where temperature, distance, and sensor values are displayed | Telemetry & Sensors — the sensors that produce these measurements | Measurement & Formatting — developer reference for the formatting utilities | Settings — Radio & User — region setting that drives unit selection | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/units-and-locale.html#related-topics",
    
    "relUrl": "/nl-rNL/user/units-and-locale.html#related-topics"
  },"5953": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": " ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/units-and-locale.html",
    
    "relUrl": "/nl-rNL/user/units-and-locale.html"
  },"5954": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/units-and-locale.html#units-measurement--locale",
    
    "relUrl": "/uk-rUA/user/units-and-locale.html#units-measurement--locale"
  },"5955": {
    "doc": "Units, Measurement & Locale",
    "title": "How It Works",
    "content": "Meshtastic radios always transmit data in metric units (meters, °C, m/s, hPa, etc.). When the app receives this data, it converts and displays 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. Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/units-and-locale.html#how-it-works",
    
    "relUrl": "/uk-rUA/user/units-and-locale.html#how-it-works"
  },"5956": {
    "doc": "Units, Measurement & Locale",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/uk-rUA/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"5957": {
    "doc": "Units, Measurement & Locale",
    "title": "Температура",
    "content": "Temperature values from environment sensors are transmitted as °C and displayed based on your device’s temperature unit preference. | 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. Temperature follows your locale’s temperature preference, independent of the distance system. Locales that mix systems work correctly — a UK phone shows miles for distance but °C for temperature. On Android 14+, the Temperature regional preference (Settings → System → Languages → Regional preferences) overrides the locale default. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/units-and-locale.html#%D1%82%D0%B5%D0%BC%D0%BF%D0%B5%D1%80%D0%B0%D1%82%D1%83%D1%80%D0%B0",
    
    "relUrl": "/uk-rUA/user/units-and-locale.html#температура"
  },"5958": {
    "doc": "Units, Measurement & Locale",
    "title": "Distance & Altitude",
    "content": "Distances between nodes and GPS altitudes are transmitted as meters and automatically scaled and converted. | Your Setting | Small Distance | Large Distance | Висота | . | 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 kilometers 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 | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/units-and-locale.html#distance--altitude",
    
    "relUrl": "/uk-rUA/user/units-and-locale.html#distance--altitude"
  },"5959": {
    "doc": "Units, Measurement & Locale",
    "title": "Швидкість",
    "content": "GPS ground speed is displayed in your locale’s preferred speed unit. | Your Setting | You See | . | Metric | 12 km/h | . | Imperial (US) | 7 mph | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/units-and-locale.html#%D1%88%D0%B2%D0%B8%D0%B4%D0%BA%D1%96%D1%81%D1%82%D1%8C",
    
    "relUrl": "/uk-rUA/user/units-and-locale.html#швидкість"
  },"5960": {
    "doc": "Units, Measurement & Locale",
    "title": "Вітер",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | Your Setting | You See | . | Metric | 18.0 km/h | . | Imperial (US) | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/units-and-locale.html#%D0%B2%D1%96%D1%82%D0%B5%D1%80",
    
    "relUrl": "/uk-rUA/user/units-and-locale.html#вітер"
  },"5961": {
    "doc": "Units, Measurement & Locale",
    "title": "Вага",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | Your Setting | You See | . | Metric | 1.50 kg | . | Imperial (US) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/units-and-locale.html#%D0%B2%D0%B0%D0%B3%D0%B0",
    
    "relUrl": "/uk-rUA/user/units-and-locale.html#вага"
  },"5962": {
    "doc": "Units, Measurement & Locale",
    "title": "Rainfall",
    "content": "Rainfall measurements (1-hour and 24-hour totals) are transmitted as mm and converted for display. | Your Setting | You See | . | Metric | 12.0 mm | . | Imperial (US) | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/units-and-locale.html#rainfall",
    
    "relUrl": "/uk-rUA/user/units-and-locale.html#rainfall"
  },"5963": {
    "doc": "Units, Measurement & Locale",
    "title": "Units That Never Change",
    "content": "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/h | Standard dosimetry unit | . | GPS coordinates | decimal degrees | Universal geographic standard | . | Humidity, battery, soil moisture | % | Universal | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/units-and-locale.html#units-that-never-change",
    
    "relUrl": "/uk-rUA/user/units-and-locale.html#units-that-never-change"
  },"5964": {
    "doc": "Units, Measurement & Locale",
    "title": "Date & Time",
    "content": "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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/units-and-locale.html#date--time",
    
    "relUrl": "/uk-rUA/user/units-and-locale.html#date--time"
  },"5965": {
    "doc": "Units, Measurement & Locale",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region | Return to Meshtastic — values update immediately | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/uk-rUA/user/units-and-locale.html#changing-your-measurement-system"
  },"5966": {
    "doc": "Units, Measurement & Locale",
    "title": "Related Topics",
    "content": ". | Node Metrics — where temperature, distance, and sensor values are displayed | Telemetry & Sensors — the sensors that produce these measurements | Measurement & Formatting — developer reference for the formatting utilities | Settings — Radio & User — region setting that drives unit selection | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/units-and-locale.html#related-topics",
    
    "relUrl": "/uk-rUA/user/units-and-locale.html#related-topics"
  },"5967": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": " ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/units-and-locale.html",
    
    "relUrl": "/uk-rUA/user/units-and-locale.html"
  },"5968": {
    "doc": "Yksiköt, mittaus ja kieli- ja alueasetukset",
    "title": "Yksiköt, mittaus ja kieli- ja alueasetukset",
    "content": "Meshtastic-sovellus näyttää lämpötilat, etäisyydet, nopeudet ja ajat automaattisesti niissä yksiköissä, jotka laitteesi on määritetty käyttämään. Jos laitteesi asetukset eivät tarjoa haluamiasi yksiköitä, sovelluksen Yksiköt-asetus ohittaa ne. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/units-and-locale.html",
    
    "relUrl": "/fi-rFI/user/units-and-locale.html"
  },"5969": {
    "doc": "Yksiköt, mittaus ja kieli- ja alueasetukset",
    "title": "Kuinka se toimii",
    "content": "Meshtastic-radiot lähettävät tiedot aina metrisissä yksiköissä (metri, °C, m/s, hPa jne.). Kun sovellus vastaanottaa nämä tiedot, se muuntaa ja näyttää arvot laitteesi alueasetusten mukaisessa yksikköjärjestelmässä. Androidissa mittausasetukset määräytyvät järjestelmän Kieli ja alue -asetusten mukaan. Työpöytäversiossa (JVM) sovellus käyttää JVM:n oletus-Locale-asetusta. Yksiköt seuraavat laitteesi aluetta, ei näytön kieltä. Pelkkä kieli, kuten English, sovelluksen omasta Kieli-asetuksesta tai Androidin sovelluskohtaisesta kieliasetuksesta säilyttää laitteesi alueasetuksen. Kieli, jossa on oma alue, kuten English (Canada), ohittaa sen ja ottaa käyttöön kyseisen alueen yksiköt. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Vinkki: Oletusarvoisesti mitään ei tarvitse määrittää – muuta järjestelmän mittausjärjestelmäasetusta, niin kaikki Meshtasticin näkymät päivittyvät automaattisesti. Jos laitteesi ei tarjoa toimivaa alue- tai mittausjärjestelmäasetusta (joissakin valmistajien Android-versioissa näin on), määritä se sovelluksessa kohdassa Asetukset → Yksiköt. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/units-and-locale.html#kuinka-se-toimii",
    
    "relUrl": "/fi-rFI/user/units-and-locale.html#kuinka-se-toimii"
  },"5970": {
    "doc": "Yksiköt, mittaus ja kieli- ja alueasetukset",
    "title": "Radion oma näyttö käyttää omia asetuksiaan",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Radion asetusten muuttaminen ei koskaan vaikuta siihen, mitä sovellus näyttää. Katso laitteen asetuksia koskevat ohjeet Meshtasticin [Näytön asetukset] (https://meshtastic.org/docs/configuration/radio/display) -oppaasta. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/units-and-locale.html#radion-oma-n%C3%A4ytt%C3%B6-k%C3%A4ytt%C3%A4%C3%A4-omia-asetuksiaan",
    
    "relUrl": "/fi-rFI/user/units-and-locale.html#radion-oma-näyttö-käyttää-omia-asetuksiaan"
  },"5971": {
    "doc": "Yksiköt, mittaus ja kieli- ja alueasetukset",
    "title": "Lämpötila",
    "content": "Lämpötila-arvot ympäristösensoreista lähetetään muodossa °C ja näytetään laitteen lämpötila-asetusten mukaisesti. | Asetuksesi | Näet | . | Celsius | 22 °C | . | Fahrenheit | 72 °F | . Tämä vaikuttaa kaikkiin lämpötilanäyttöihin sovelluksessa: radion ympäristötelemetria, maaperän lämpötila, kastepiste ja telemetriakäyrien akselit. Lämpötila noudattaa alueesi lämpötila-asetusta riippumatta etäisyysjärjestelmästä. Alueet, joissa käytetään sekä metri- että brittiläisiä yksiköitä, toimivat oikein – esimerkiksi Isossa-Britanniassa etäisyydet näytetään maileina, mutta lämpötila °C-asteina. Android 14:ssä Lämpötila -alueasetus (Asetukset → Järjestelmä → Kielet → Alueasetukset) ohittaa alueen oletusasetuksen. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/units-and-locale.html#l%C3%A4mp%C3%B6tila",
    
    "relUrl": "/fi-rFI/user/units-and-locale.html#lämpötila"
  },"5972": {
    "doc": "Yksiköt, mittaus ja kieli- ja alueasetukset",
    "title": "Etäisyys ja korkeus",
    "content": "Radioiden väliset etäisyydet ja GPS-korkeudet lähetetään metreinä ja muunnetaan sekä skaalataan automaattisesti. | Asetuksesi | Pieni etäisyys | Suuri etäisyys | Korkeus | . | Metrijärjestelmä | 350 m | 2,5 km | 1 200 m | . | Imperiaalinen (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 kilometers or miles automatically. Missä nämä näkyvät . | Radiolista — etäisyys ja suunta jokaiseen radioon | Radion tiedot — korkeus ja etäisyys sijainnistasi | Kartta — reittipisteiden etäisyydet ja reitinselvityksen hyppy-etäisyydet | Kompassi — etäisyys valittuun radioon | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/units-and-locale.html#et%C3%A4isyys-ja-korkeus",
    
    "relUrl": "/fi-rFI/user/units-and-locale.html#etäisyys-ja-korkeus"
  },"5973": {
    "doc": "Yksiköt, mittaus ja kieli- ja alueasetukset",
    "title": "Nopeus",
    "content": "GPS-maanopeus näytetään laitteesi kieli- ja alueasetusten mukaisessa nopeusyksikössä. | Asetuksesi | Näet | . | Metrijärjestelmä | 12 km/h | . | Imperiaalinen (US) | 7 mph | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/units-and-locale.html#nopeus",
    
    "relUrl": "/fi-rFI/user/units-and-locale.html#nopeus"
  },"5974": {
    "doc": "Yksiköt, mittaus ja kieli- ja alueasetukset",
    "title": "Tuuli",
    "content": "Anturi lähettää tuulen nopeuden, puuskat ja tyynten jaksojen nopeuden yksikössä m/s, ja ne muunnetaan näyttöä varten — sovellus näyttää alueellasi käytettävän sääyksikön, ei anturin raakaa yksikköä. | Asetuksesi | Näet | . | Metrijärjestelmä | 18,0 km/h | . | Imperiaalinen (US) | 11.2 mph | . Kaikki kolme näytetään samassa yksikössä kaikkialla, missä ne esiintyvät: Radion tiedot -näkymän ympäristöosiossa, ympäristötelemetrian lokissa ja kaavioissa. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/units-and-locale.html#tuuli",
    
    "relUrl": "/fi-rFI/user/units-and-locale.html#tuuli"
  },"5975": {
    "doc": "Yksiköt, mittaus ja kieli- ja alueasetukset",
    "title": "Paino",
    "content": "Yhdistetyn vaa’an mittaustulokset lähetetään yksikössä kg ja muunnetaan näyttöä varten. | Asetuksesi | Näet | . | Metrijärjestelmä | 1,50 kg | . | Imperiaalinen (US) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/units-and-locale.html#paino",
    
    "relUrl": "/fi-rFI/user/units-and-locale.html#paino"
  },"5976": {
    "doc": "Yksiköt, mittaus ja kieli- ja alueasetukset",
    "title": "Sademäärä",
    "content": "Sademittaukset (1 tunnin ja 24 tunnin yhteismäärät) lähetetään muodossa mm ja muunnetaan näyttöä varten. | Asetuksesi | Näet | . | Metrijärjestelmä | 12,0 mm | . | Imperiaalinen (US) | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/units-and-locale.html#sadem%C3%A4%C3%A4r%C3%A4",
    
    "relUrl": "/fi-rFI/user/units-and-locale.html#sademäärä"
  },"5977": {
    "doc": "Yksiköt, mittaus ja kieli- ja alueasetukset",
    "title": "Yksiköt, jotka eivät muutu",
    "content": "Jotkin yksiköt ovat kansainvälisiä standardeja ja näkyvät samalla tavalla kieli- ja alueasetuksista riippumatta: . | Mittaus | Yksikkö | Miksi | . | Ilmanpaine | hPa | Kansainvälinen meteorologinen standardi | . | Suunta / suuntima | ° (astetta) | Universaali navigointikäytäntö | . | Säteily | µR/h | Standardi dosimetria-yksikkö | . | GPS-koordinaatit | desimaaliasteet | Kansainvälinen maantieteellinen standardi | . | Kosteus, akku ja maaperän kosteus | % | Yleinen | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/units-and-locale.html#yksik%C3%B6t-jotka-eiv%C3%A4t-muutu",
    
    "relUrl": "/fi-rFI/user/units-and-locale.html#yksiköt-jotka-eivät-muutu"
  },"5978": {
    "doc": "Yksiköt, mittaus ja kieli- ja alueasetukset",
    "title": "Päivämäärä ja aika",
    "content": "Kaikki aikaleimat koko sovelluksessa — viimeksi kuultu, viestien ajat, telemetrialokit, kaavioakselit — noudattavat laitteesi päivämäärä- ja aika-asetuksia. | Asetus | Mitä se ohjaa | Esimerkki | . | 24 tunnin aika | Aikamuoto | 14:30 vs 2:30 PM | . | Päivämäärämuoto | Päivämäärän järjestys | 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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/units-and-locale.html#p%C3%A4iv%C3%A4m%C3%A4%C3%A4r%C3%A4-ja-aika",
    
    "relUrl": "/fi-rFI/user/units-and-locale.html#päivämäärä-ja-aika"
  },"5979": {
    "doc": "Yksiköt, mittaus ja kieli- ja alueasetukset",
    "title": "Mittausjärjestelmän muuttaminen",
    "content": "Oletusarvoisesti sovellus käyttää laitteesi asetuksia, ja mittausjärjestelmä (metrinen tai imperiaalinen) määräytyy alueasetuksen mukaan: . | Avaa Asetukset → Järjestelmä → Kieli ja alue | Vaihda alueasetusta | Palaa Meshtasticiin — arvot päivittyvät välittömästi | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Kaikki englanninkieliset alueet eivät käytä täysin metristä järjestelmää. English (United Kingdom) käyttää etäisyyksissä maileja ja korkeuksissa jalkoja, joten radioluettelossa näkyvät mailit ja korkeus jaloissa. Jos haluat käyttää metrijärjestelmää, valitse sovelluksen Yksiköt-asetukseksi Metrinen (katso Yksiköiden ohittaminen sovelluksessa) tai valitse täysin metrijärjestelmää käyttävä alue, kuten English (Canada), English (Ireland) tai English (New Zealand). Joissakin puhelimissa Alueasetukset -valikkoa ei ole lainkaan, vaan tarjolla on vain English (United States). Näillä laitteilla käytä sovelluksen Yksiköt-asetusta (katso Yksiköiden ohittaminen sovelluksessa). Sovelluksen yksiköiden ohittaminen . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. Tällöin voit käyttää sovelluksen omaa asetusta: . | Avaa Meshtasticin asetukset → Yksiköt | Valitse Järjestelmän oletus, Metrinen tai Imperiaalinen | Kaikki näkymät päivittyvät heti – uudelleenkäynnistystä ei tarvita | . Järjestelmän oletus käyttää puhelimesi tai tietokoneesi alue- ja mittayksikköasetuksia. Metrinen- tai Imperiallinen-asetuksen pakottaminen koskee kaikkia yksiköitä, myös lämpötilaa (metrinen → °C, imperiaalinen → °F), vaikka järjestelmän omat alueasetukset määrittäisivät toisin. Asetus on käytettävissä sekä Android- että työpöytäversiossa. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/units-and-locale.html#mittausj%C3%A4rjestelm%C3%A4n-muuttaminen",
    
    "relUrl": "/fi-rFI/user/units-and-locale.html#mittausjärjestelmän-muuttaminen"
  },"5980": {
    "doc": "Yksiköt, mittaus ja kieli- ja alueasetukset",
    "title": "Aiheeseen liittyvät aiheet",
    "content": ". | Radion mittarit — missä lämpötila-, etäisyys- ja anturiarvot näytetään | Telemetria ja anturit — anturit, jotka tuottavat nämä mittaukset | Mittaus ja muotoilu — kehittäjien viite muotoiluapuohjelmista | Asetukset — Radio ja käyttäjä — alueasetus, joka määrittää käytettävät mittayksiköt | Näytön asetukset – radion oman näytön yksikkö-, kello- ja kompassiasetukset meshtastic.orgissa | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/units-and-locale.html#aiheeseen-liittyv%C3%A4t-aiheet",
    
    "relUrl": "/fi-rFI/user/units-and-locale.html#aiheeseen-liittyvät-aiheet"
  },"5981": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/units-and-locale.html#units-measurement--locale",
    
    "relUrl": "/is-rIS/user/units-and-locale.html#units-measurement--locale"
  },"5982": {
    "doc": "Units, Measurement & Locale",
    "title": "How It Works",
    "content": "Meshtastic radios always transmit data in metric units (meters, °C, m/s, hPa, etc.). When the app receives this data, it converts and displays 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. Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/units-and-locale.html#how-it-works",
    
    "relUrl": "/is-rIS/user/units-and-locale.html#how-it-works"
  },"5983": {
    "doc": "Units, Measurement & Locale",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/is-rIS/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"5984": {
    "doc": "Units, Measurement & Locale",
    "title": "Temperature",
    "content": "Temperature values from environment sensors are transmitted as °C and displayed based on your device’s temperature unit preference. | 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. Temperature follows your locale’s temperature preference, independent of the distance system. Locales that mix systems work correctly — a UK phone shows miles for distance but °C for temperature. On Android 14+, the Temperature regional preference (Settings → System → Languages → Regional preferences) overrides the locale default. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/units-and-locale.html#temperature",
    
    "relUrl": "/is-rIS/user/units-and-locale.html#temperature"
  },"5985": {
    "doc": "Units, Measurement & Locale",
    "title": "Distance & Altitude",
    "content": "Distances between nodes and GPS altitudes are transmitted as meters and automatically scaled and converted. | 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 kilometers 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 | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/units-and-locale.html#distance--altitude",
    
    "relUrl": "/is-rIS/user/units-and-locale.html#distance--altitude"
  },"5986": {
    "doc": "Units, Measurement & Locale",
    "title": "Speed",
    "content": "GPS ground speed is displayed in your locale’s preferred speed unit. | Your Setting | You See | . | Metric | 12 km/h | . | Imperial (US) | 7 mph | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/units-and-locale.html#speed",
    
    "relUrl": "/is-rIS/user/units-and-locale.html#speed"
  },"5987": {
    "doc": "Units, Measurement & Locale",
    "title": "Wind",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | Your Setting | You See | . | Metric | 18.0 km/h | . | Imperial (US) | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/units-and-locale.html#wind",
    
    "relUrl": "/is-rIS/user/units-and-locale.html#wind"
  },"5988": {
    "doc": "Units, Measurement & Locale",
    "title": "Weight",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | Your Setting | You See | . | Metric | 1.50 kg | . | Imperial (US) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/units-and-locale.html#weight",
    
    "relUrl": "/is-rIS/user/units-and-locale.html#weight"
  },"5989": {
    "doc": "Units, Measurement & Locale",
    "title": "Rainfall",
    "content": "Rainfall measurements (1-hour and 24-hour totals) are transmitted as mm and converted for display. | Your Setting | You See | . | Metric | 12.0 mm | . | Imperial (US) | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/units-and-locale.html#rainfall",
    
    "relUrl": "/is-rIS/user/units-and-locale.html#rainfall"
  },"5990": {
    "doc": "Units, Measurement & Locale",
    "title": "Units That Never Change",
    "content": "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/h | Standard dosimetry unit | . | GPS coordinates | decimal degrees | Universal geographic standard | . | Humidity, battery, soil moisture | % | Universal | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/units-and-locale.html#units-that-never-change",
    
    "relUrl": "/is-rIS/user/units-and-locale.html#units-that-never-change"
  },"5991": {
    "doc": "Units, Measurement & Locale",
    "title": "Date & Time",
    "content": "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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/units-and-locale.html#date--time",
    
    "relUrl": "/is-rIS/user/units-and-locale.html#date--time"
  },"5992": {
    "doc": "Units, Measurement & Locale",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region | Return to Meshtastic — values update immediately | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/is-rIS/user/units-and-locale.html#changing-your-measurement-system"
  },"5993": {
    "doc": "Units, Measurement & Locale",
    "title": "Related Topics",
    "content": ". | Node Metrics — where temperature, distance, and sensor values are displayed | Telemetry & Sensors — the sensors that produce these measurements | Measurement & Formatting — developer reference for the formatting utilities | Settings — Radio & User — region setting that drives unit selection | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/units-and-locale.html#related-topics",
    
    "relUrl": "/is-rIS/user/units-and-locale.html#related-topics"
  },"5994": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": " ",
    "url": "/Meshtastic-Android/main/is-rIS/user/units-and-locale.html",
    
    "relUrl": "/is-rIS/user/units-and-locale.html"
  },"5995": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/units-and-locale.html#units-measurement--locale",
    
    "relUrl": "/lt-rLT/user/units-and-locale.html#units-measurement--locale"
  },"5996": {
    "doc": "Units, Measurement & Locale",
    "title": "How It Works",
    "content": "Meshtastic radios always transmit data in metric units (meters, °C, m/s, hPa, etc.). When the app receives this data, it converts and displays 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. Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/units-and-locale.html#how-it-works",
    
    "relUrl": "/lt-rLT/user/units-and-locale.html#how-it-works"
  },"5997": {
    "doc": "Units, Measurement & Locale",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/lt-rLT/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"5998": {
    "doc": "Units, Measurement & Locale",
    "title": "Temperatūra",
    "content": "Temperature values from environment sensors are transmitted as °C and displayed based on your device’s temperature unit preference. | 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. Temperature follows your locale’s temperature preference, independent of the distance system. Locales that mix systems work correctly — a UK phone shows miles for distance but °C for temperature. On Android 14+, the Temperature regional preference (Settings → System → Languages → Regional preferences) overrides the locale default. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/units-and-locale.html#temperat%C5%ABra",
    
    "relUrl": "/lt-rLT/user/units-and-locale.html#temperatūra"
  },"5999": {
    "doc": "Units, Measurement & Locale",
    "title": "Distance & Altitude",
    "content": "Distances between nodes and GPS altitudes are transmitted as meters and automatically scaled and converted. | 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 kilometers 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 | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/units-and-locale.html#distance--altitude",
    
    "relUrl": "/lt-rLT/user/units-and-locale.html#distance--altitude"
  },"6000": {
    "doc": "Units, Measurement & Locale",
    "title": "Speed",
    "content": "GPS ground speed is displayed in your locale’s preferred speed unit. | Your Setting | You See | . | Metric | 12 km/h | . | Imperial (US) | 7 mph | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/units-and-locale.html#speed",
    
    "relUrl": "/lt-rLT/user/units-and-locale.html#speed"
  },"6001": {
    "doc": "Units, Measurement & Locale",
    "title": "Wind",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | Your Setting | You See | . | Metric | 18.0 km/h | . | Imperial (US) | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/units-and-locale.html#wind",
    
    "relUrl": "/lt-rLT/user/units-and-locale.html#wind"
  },"6002": {
    "doc": "Units, Measurement & Locale",
    "title": "Weight",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | Your Setting | You See | . | Metric | 1.50 kg | . | Imperial (US) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/units-and-locale.html#weight",
    
    "relUrl": "/lt-rLT/user/units-and-locale.html#weight"
  },"6003": {
    "doc": "Units, Measurement & Locale",
    "title": "Rainfall",
    "content": "Rainfall measurements (1-hour and 24-hour totals) are transmitted as mm and converted for display. | Your Setting | You See | . | Metric | 12.0 mm | . | Imperial (US) | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/units-and-locale.html#rainfall",
    
    "relUrl": "/lt-rLT/user/units-and-locale.html#rainfall"
  },"6004": {
    "doc": "Units, Measurement & Locale",
    "title": "Units That Never Change",
    "content": "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/h | Standard dosimetry unit | . | GPS coordinates | decimal degrees | Universal geographic standard | . | Humidity, battery, soil moisture | % | Universal | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/units-and-locale.html#units-that-never-change",
    
    "relUrl": "/lt-rLT/user/units-and-locale.html#units-that-never-change"
  },"6005": {
    "doc": "Units, Measurement & Locale",
    "title": "Date & Time",
    "content": "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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/units-and-locale.html#date--time",
    
    "relUrl": "/lt-rLT/user/units-and-locale.html#date--time"
  },"6006": {
    "doc": "Units, Measurement & Locale",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region | Return to Meshtastic — values update immediately | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/lt-rLT/user/units-and-locale.html#changing-your-measurement-system"
  },"6007": {
    "doc": "Units, Measurement & Locale",
    "title": "Related Topics",
    "content": ". | Node Metrics — where temperature, distance, and sensor values are displayed | Telemetry & Sensors — the sensors that produce these measurements | Measurement & Formatting — developer reference for the formatting utilities | Settings — Radio & User — region setting that drives unit selection | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/units-and-locale.html#related-topics",
    
    "relUrl": "/lt-rLT/user/units-and-locale.html#related-topics"
  },"6008": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": " ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/units-and-locale.html",
    
    "relUrl": "/lt-rLT/user/units-and-locale.html"
  },"6009": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/units-and-locale.html#units-measurement--locale",
    
    "relUrl": "/gl-rES/user/units-and-locale.html#units-measurement--locale"
  },"6010": {
    "doc": "Units, Measurement & Locale",
    "title": "How It Works",
    "content": "Meshtastic radios always transmit data in metric units (meters, °C, m/s, hPa, etc.). When the app receives this data, it converts and displays 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. Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/units-and-locale.html#how-it-works",
    
    "relUrl": "/gl-rES/user/units-and-locale.html#how-it-works"
  },"6011": {
    "doc": "Units, Measurement & Locale",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/gl-rES/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"6012": {
    "doc": "Units, Measurement & Locale",
    "title": "Temperature",
    "content": "Temperature values from environment sensors are transmitted as °C and displayed based on your device’s temperature unit preference. | 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. Temperature follows your locale’s temperature preference, independent of the distance system. Locales that mix systems work correctly — a UK phone shows miles for distance but °C for temperature. On Android 14+, the Temperature regional preference (Settings → System → Languages → Regional preferences) overrides the locale default. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/units-and-locale.html#temperature",
    
    "relUrl": "/gl-rES/user/units-and-locale.html#temperature"
  },"6013": {
    "doc": "Units, Measurement & Locale",
    "title": "Distance & Altitude",
    "content": "Distances between nodes and GPS altitudes are transmitted as meters and automatically scaled and converted. | 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 kilometers 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 | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/units-and-locale.html#distance--altitude",
    
    "relUrl": "/gl-rES/user/units-and-locale.html#distance--altitude"
  },"6014": {
    "doc": "Units, Measurement & Locale",
    "title": "Speed",
    "content": "GPS ground speed is displayed in your locale’s preferred speed unit. | Your Setting | You See | . | Metric | 12 km/h | . | Imperial (US) | 7 mph | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/units-and-locale.html#speed",
    
    "relUrl": "/gl-rES/user/units-and-locale.html#speed"
  },"6015": {
    "doc": "Units, Measurement & Locale",
    "title": "Wind",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | Your Setting | You See | . | Metric | 18.0 km/h | . | Imperial (US) | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/units-and-locale.html#wind",
    
    "relUrl": "/gl-rES/user/units-and-locale.html#wind"
  },"6016": {
    "doc": "Units, Measurement & Locale",
    "title": "Weight",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | Your Setting | You See | . | Metric | 1.50 kg | . | Imperial (US) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/units-and-locale.html#weight",
    
    "relUrl": "/gl-rES/user/units-and-locale.html#weight"
  },"6017": {
    "doc": "Units, Measurement & Locale",
    "title": "Rainfall",
    "content": "Rainfall measurements (1-hour and 24-hour totals) are transmitted as mm and converted for display. | Your Setting | You See | . | Metric | 12.0 mm | . | Imperial (US) | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/units-and-locale.html#rainfall",
    
    "relUrl": "/gl-rES/user/units-and-locale.html#rainfall"
  },"6018": {
    "doc": "Units, Measurement & Locale",
    "title": "Units That Never Change",
    "content": "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/h | Standard dosimetry unit | . | GPS coordinates | decimal degrees | Universal geographic standard | . | Humidity, battery, soil moisture | % | Universal | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/units-and-locale.html#units-that-never-change",
    
    "relUrl": "/gl-rES/user/units-and-locale.html#units-that-never-change"
  },"6019": {
    "doc": "Units, Measurement & Locale",
    "title": "Date & Time",
    "content": "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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/units-and-locale.html#date--time",
    
    "relUrl": "/gl-rES/user/units-and-locale.html#date--time"
  },"6020": {
    "doc": "Units, Measurement & Locale",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region | Return to Meshtastic — values update immediately | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/gl-rES/user/units-and-locale.html#changing-your-measurement-system"
  },"6021": {
    "doc": "Units, Measurement & Locale",
    "title": "Related Topics",
    "content": ". | Node Metrics — where temperature, distance, and sensor values are displayed | Telemetry & Sensors — the sensors that produce these measurements | Measurement & Formatting — developer reference for the formatting utilities | Settings — Radio & User — region setting that drives unit selection | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/units-and-locale.html#related-topics",
    
    "relUrl": "/gl-rES/user/units-and-locale.html#related-topics"
  },"6022": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": " ",
    "url": "/Meshtastic-Android/main/gl-rES/user/units-and-locale.html",
    
    "relUrl": "/gl-rES/user/units-and-locale.html"
  },"6023": {
    "doc": "単位・計測・ロケール",
    "title": "単位・計測・ロケール",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/units-and-locale.html",
    
    "relUrl": "/ja-rJP/user/units-and-locale.html"
  },"6024": {
    "doc": "単位・計測・ロケール",
    "title": "仕組み",
    "content": "Meshtastic の無線機は、常にメートル法の単位（メートル、°C、m/s、hPa など）でデータを送信します。アプリはこのデータを受信すると、デバイスのロケールで指定された単位系に変換して値を表示します。 . Android では、計測の設定はシステムの言語と地域の設定によって決まります。デスクトップ（JVM）では、アプリは JVM のデフォルトの Locale を使用します。 . Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/units-and-locale.html#%E4%BB%95%E7%B5%84%E3%81%BF",
    
    "relUrl": "/ja-rJP/user/units-and-locale.html#仕組み"
  },"6025": {
    "doc": "単位・計測・ロケール",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/ja-rJP/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"6026": {
    "doc": "単位・計測・ロケール",
    "title": "温度",
    "content": "環境センサーの温度値は °C で送信され、デバイスの温度単位の設定に基づいて表示されます。 . | あなたの設定 | 表示 | . | 摂氏 | 22°C | . | 華氏 | 72°F | . これは、アプリ全体のすべての温度表示に影響します：ノードの環境テレメトリ、土壌温度、露点、テレメトリグラフの軸。 . Temperature follows your locale’s temperature preference, independent of the distance system. Locales that mix systems work correctly — a UK phone shows miles for distance but °C for temperature. On Android 14+, the Temperature regional preference (Settings → System → Languages → Regional preferences) overrides the locale default. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/units-and-locale.html#%E6%B8%A9%E5%BA%A6",
    
    "relUrl": "/ja-rJP/user/units-and-locale.html#温度"
  },"6027": {
    "doc": "単位・計測・ロケール",
    "title": "距離と標高",
    "content": "ノード間の距離と GPS の標高はメートルで送信され、自動的にスケーリングされて変換されます。 . | あなたの設定 | 短い距離 | 長い距離 | 標高 | . | メートル法 | 350 m | 2.5 km | 1,200 m | . | ヤード・ポンド法（米国） | 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 kilometers or miles automatically. 表示される場所 . | ノードリスト：各ノードまでの距離と方位 | ノードの詳細：標高、自分の位置からの距離 | マップ：ウェイポイントまでの距離、ルート追跡のホップ距離 | コンパス：選択したノードまでの距離 | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/units-and-locale.html#%E8%B7%9D%E9%9B%A2%E3%81%A8%E6%A8%99%E9%AB%98",
    
    "relUrl": "/ja-rJP/user/units-and-locale.html#距離と標高"
  },"6028": {
    "doc": "単位・計測・ロケール",
    "title": "速度",
    "content": "GPS の対地速度は、ロケールで優先される速度単位で表示されます。 . | あなたの設定 | 表示 | . | メートル法 | 12 km/h | . | ヤード・ポンド法（米国） | 7 mph | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/units-and-locale.html#%E9%80%9F%E5%BA%A6",
    
    "relUrl": "/ja-rJP/user/units-and-locale.html#速度"
  },"6029": {
    "doc": "単位・計測・ロケール",
    "title": "風力",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | あなたの設定 | 表示 | . | メートル法 | 18.0 km/h | . | ヤード・ポンド法（米国） | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/units-and-locale.html#%E9%A2%A8%E5%8A%9B",
    
    "relUrl": "/ja-rJP/user/units-and-locale.html#風力"
  },"6030": {
    "doc": "単位・計測・ロケール",
    "title": "重さ",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | あなたの設定 | 表示 | . | メートル法 | 1.50 kg | . | ヤード・ポンド法（米国） | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/units-and-locale.html#%E9%87%8D%E3%81%95",
    
    "relUrl": "/ja-rJP/user/units-and-locale.html#重さ"
  },"6031": {
    "doc": "単位・計測・ロケール",
    "title": "降水量",
    "content": "降水量の測定値（1 時間および 24 時間の合計）は mm で送信され、表示用に変換されます。 . | あなたの設定 | 表示 | . | メートル法 | 12.0 mm | . | ヤード・ポンド法（米国） | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/units-and-locale.html#%E9%99%8D%E6%B0%B4%E9%87%8F",
    
    "relUrl": "/ja-rJP/user/units-and-locale.html#降水量"
  },"6032": {
    "doc": "単位・計測・ロケール",
    "title": "変わらない単位",
    "content": "一部の単位は国際標準であり、ロケールに関係なく同じように表示されます： . | 計測項目 | 単位 | 理由 | . | 大気圧 | hPa | 国際的な気象標準 | . | 方位／進行方向 | °（度） | 普遍的な航法の慣例 | . | 放射線 | µR/h | 標準的な線量測定の単位 | . | GPS 座標 | 十進法の度 | 普遍的な地理標準 | . | 湿度、バッテリー、土壌水分 | % | 普遍的 | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/units-and-locale.html#%E5%A4%89%E3%82%8F%E3%82%89%E3%81%AA%E3%81%84%E5%8D%98%E4%BD%8D",
    
    "relUrl": "/ja-rJP/user/units-and-locale.html#変わらない単位"
  },"6033": {
    "doc": "単位・計測・ロケール",
    "title": "日付と時刻",
    "content": "アプリ全体のすべてのタイムスタンプ（最後の通信、メッセージの時刻、テレメトリのログ、グラフの軸）は、デバイスの日付と時刻の設定に従います。 . | 設定 | 制御する内容 | 例 | . | 24 時間表示 | 時刻の形式 | 14:30 vs 2:30 PM | . | 日付形式 | 日付の並び順 | 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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/units-and-locale.html#%E6%97%A5%E4%BB%98%E3%81%A8%E6%99%82%E5%88%BB",
    
    "relUrl": "/ja-rJP/user/units-and-locale.html#日付と時刻"
  },"6034": {
    "doc": "単位・計測・ロケール",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | 「Android の設定 → システム → 言語と地域」を開きます | Change your Region | Meshtastic に戻ります。値がすぐに更新されます | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/ja-rJP/user/units-and-locale.html#changing-your-measurement-system"
  },"6035": {
    "doc": "単位・計測・ロケール",
    "title": "関連トピック",
    "content": ". | ノードメトリクス：温度・距離・センサー値が表示される場所 | テレメトリとセンサー：これらの計測値を生成するセンサー | 計測と書式：書式ユーティリティの開発者向けリファレンス | 設定：無線機とユーザー：単位の選択を決める地域設定 | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/units-and-locale.html#%E9%96%A2%E9%80%A3%E3%83%88%E3%83%94%E3%83%83%E3%82%AF",
    
    "relUrl": "/ja-rJP/user/units-and-locale.html#関連トピック"
  },"6036": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/units-and-locale.html#units-measurement--locale",
    
    "relUrl": "/de-rDE/user/units-and-locale.html#units-measurement--locale"
  },"6037": {
    "doc": "Units, Measurement & Locale",
    "title": "So funktioniert’s",
    "content": "Meshtastic radios always transmit data in metric units (meters, °C, m/s, hPa, etc.). When the app receives this data, it converts and displays 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. Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/units-and-locale.html#so-funktionierts",
    
    "relUrl": "/de-rDE/user/units-and-locale.html#so-funktionierts"
  },"6038": {
    "doc": "Units, Measurement & Locale",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/de-rDE/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"6039": {
    "doc": "Units, Measurement & Locale",
    "title": "Temperatur",
    "content": "Temperature values from environment sensors are transmitted as °C and displayed based on your device’s temperature unit preference. | 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. Temperature follows your locale’s temperature preference, independent of the distance system. Locales that mix systems work correctly — a UK phone shows miles for distance but °C for temperature. On Android 14+, the Temperature regional preference (Settings → System → Languages → Regional preferences) overrides the locale default. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/units-and-locale.html#temperatur",
    
    "relUrl": "/de-rDE/user/units-and-locale.html#temperatur"
  },"6040": {
    "doc": "Units, Measurement & Locale",
    "title": "Distance & Altitude",
    "content": "Distances between nodes and GPS altitudes are transmitted as meters and automatically scaled and converted. | Your Setting | Small Distance | Large Distance | Höhe | . | Metrisch | 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 kilometers 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 | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/units-and-locale.html#distance--altitude",
    
    "relUrl": "/de-rDE/user/units-and-locale.html#distance--altitude"
  },"6041": {
    "doc": "Units, Measurement & Locale",
    "title": "Geschwindigkeit",
    "content": "GPS ground speed is displayed in your locale’s preferred speed unit. | Your Setting | You See | . | Metrisch | 12 km/h | . | Imperial (US) | 7 mph | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/units-and-locale.html#geschwindigkeit",
    
    "relUrl": "/de-rDE/user/units-and-locale.html#geschwindigkeit"
  },"6042": {
    "doc": "Units, Measurement & Locale",
    "title": "Wind",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | Your Setting | You See | . | Metrisch | 18.0 km/h | . | Imperial (US) | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/units-and-locale.html#wind",
    
    "relUrl": "/de-rDE/user/units-and-locale.html#wind"
  },"6043": {
    "doc": "Units, Measurement & Locale",
    "title": "Gewicht",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | Your Setting | You See | . | Metrisch | 1.50 kg | . | Imperial (US) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/units-and-locale.html#gewicht",
    
    "relUrl": "/de-rDE/user/units-and-locale.html#gewicht"
  },"6044": {
    "doc": "Units, Measurement & Locale",
    "title": "Rainfall",
    "content": "Rainfall measurements (1-hour and 24-hour totals) are transmitted as mm and converted for display. | Your Setting | You See | . | Metrisch | 12.0 mm | . | Imperial (US) | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/units-and-locale.html#rainfall",
    
    "relUrl": "/de-rDE/user/units-and-locale.html#rainfall"
  },"6045": {
    "doc": "Units, Measurement & Locale",
    "title": "Units That Never Change",
    "content": "Some units are international standards and are displayed the same way regardless of your locale: . | Measurement | Einheit | Warum | . | Luftdruck | hPa | International meteorological standard | . | Heading / bearing | ° (degrees) | Universal navigation convention | . | Strahlung | µR/h | Standard dosimetry unit | . | GPS coordinates | decimal degrees | Universal geographic standard | . | Humidity, battery, soil moisture | % | Universal | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/units-and-locale.html#units-that-never-change",
    
    "relUrl": "/de-rDE/user/units-and-locale.html#units-that-never-change"
  },"6046": {
    "doc": "Units, Measurement & Locale",
    "title": "Date & Time",
    "content": "All timestamps throughout the app — last heard, message times, telemetry logs, chart axes — follow your device’s date and time preferences. | Einstellung | What It Controls | Beispiel | . | 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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/units-and-locale.html#date--time",
    
    "relUrl": "/de-rDE/user/units-and-locale.html#date--time"
  },"6047": {
    "doc": "Units, Measurement & Locale",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region | Return to Meshtastic — values update immediately | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/de-rDE/user/units-and-locale.html#changing-your-measurement-system"
  },"6048": {
    "doc": "Units, Measurement & Locale",
    "title": "Verwandte Themen",
    "content": ". | Node Metrics — where temperature, distance, and sensor values are displayed | Telemetry & Sensors — the sensors that produce these measurements | Measurement & Formatting — developer reference for the formatting utilities | Settings — Radio & User — region setting that drives unit selection | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/units-and-locale.html#verwandte-themen",
    
    "relUrl": "/de-rDE/user/units-and-locale.html#verwandte-themen"
  },"6049": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": " ",
    "url": "/Meshtastic-Android/main/de-rDE/user/units-and-locale.html",
    
    "relUrl": "/de-rDE/user/units-and-locale.html"
  },"6050": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/units-and-locale.html#units-measurement--locale",
    
    "relUrl": "/ar-rSA/user/units-and-locale.html#units-measurement--locale"
  },"6051": {
    "doc": "Units, Measurement & Locale",
    "title": "How It Works",
    "content": "Meshtastic radios always transmit data in metric units (meters, °C, m/s, hPa, etc.). When the app receives this data, it converts and displays 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. Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/units-and-locale.html#how-it-works",
    
    "relUrl": "/ar-rSA/user/units-and-locale.html#how-it-works"
  },"6052": {
    "doc": "Units, Measurement & Locale",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/ar-rSA/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"6053": {
    "doc": "Units, Measurement & Locale",
    "title": "الحرارة",
    "content": "Temperature values from environment sensors are transmitted as °C and displayed based on your device’s temperature unit preference. | 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. Temperature follows your locale’s temperature preference, independent of the distance system. Locales that mix systems work correctly — a UK phone shows miles for distance but °C for temperature. On Android 14+, the Temperature regional preference (Settings → System → Languages → Regional preferences) overrides the locale default. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/units-and-locale.html#%D8%A7%D9%84%D8%AD%D8%B1%D8%A7%D8%B1%D8%A9",
    
    "relUrl": "/ar-rSA/user/units-and-locale.html#الحرارة"
  },"6054": {
    "doc": "Units, Measurement & Locale",
    "title": "Distance & Altitude",
    "content": "Distances between nodes and GPS altitudes are transmitted as meters and automatically scaled and converted. | 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 kilometers 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 | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/units-and-locale.html#distance--altitude",
    
    "relUrl": "/ar-rSA/user/units-and-locale.html#distance--altitude"
  },"6055": {
    "doc": "Units, Measurement & Locale",
    "title": "Speed",
    "content": "GPS ground speed is displayed in your locale’s preferred speed unit. | Your Setting | You See | . | Metric | 12 km/h | . | Imperial (US) | 7 mph | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/units-and-locale.html#speed",
    
    "relUrl": "/ar-rSA/user/units-and-locale.html#speed"
  },"6056": {
    "doc": "Units, Measurement & Locale",
    "title": "Wind",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | Your Setting | You See | . | Metric | 18.0 km/h | . | Imperial (US) | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/units-and-locale.html#wind",
    
    "relUrl": "/ar-rSA/user/units-and-locale.html#wind"
  },"6057": {
    "doc": "Units, Measurement & Locale",
    "title": "Weight",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | Your Setting | You See | . | Metric | 1.50 kg | . | Imperial (US) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/units-and-locale.html#weight",
    
    "relUrl": "/ar-rSA/user/units-and-locale.html#weight"
  },"6058": {
    "doc": "Units, Measurement & Locale",
    "title": "Rainfall",
    "content": "Rainfall measurements (1-hour and 24-hour totals) are transmitted as mm and converted for display. | Your Setting | You See | . | Metric | 12.0 mm | . | Imperial (US) | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/units-and-locale.html#rainfall",
    
    "relUrl": "/ar-rSA/user/units-and-locale.html#rainfall"
  },"6059": {
    "doc": "Units, Measurement & Locale",
    "title": "Units That Never Change",
    "content": "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/h | Standard dosimetry unit | . | GPS coordinates | decimal degrees | Universal geographic standard | . | Humidity, battery, soil moisture | % | Universal | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/units-and-locale.html#units-that-never-change",
    
    "relUrl": "/ar-rSA/user/units-and-locale.html#units-that-never-change"
  },"6060": {
    "doc": "Units, Measurement & Locale",
    "title": "Date & Time",
    "content": "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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/units-and-locale.html#date--time",
    
    "relUrl": "/ar-rSA/user/units-and-locale.html#date--time"
  },"6061": {
    "doc": "Units, Measurement & Locale",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region | Return to Meshtastic — values update immediately | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/ar-rSA/user/units-and-locale.html#changing-your-measurement-system"
  },"6062": {
    "doc": "Units, Measurement & Locale",
    "title": "Related Topics",
    "content": ". | Node Metrics — where temperature, distance, and sensor values are displayed | Telemetry & Sensors — the sensors that produce these measurements | Measurement & Formatting — developer reference for the formatting utilities | Settings — Radio & User — region setting that drives unit selection | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/units-and-locale.html#related-topics",
    
    "relUrl": "/ar-rSA/user/units-and-locale.html#related-topics"
  },"6063": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": " ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/units-and-locale.html",
    
    "relUrl": "/ar-rSA/user/units-and-locale.html"
  },"6064": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/units-and-locale.html#units-measurement--locale",
    
    "relUrl": "/hr-rHR/user/units-and-locale.html#units-measurement--locale"
  },"6065": {
    "doc": "Units, Measurement & Locale",
    "title": "How It Works",
    "content": "Meshtastic radios always transmit data in metric units (meters, °C, m/s, hPa, etc.). When the app receives this data, it converts and displays 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. Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/units-and-locale.html#how-it-works",
    
    "relUrl": "/hr-rHR/user/units-and-locale.html#how-it-works"
  },"6066": {
    "doc": "Units, Measurement & Locale",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/hr-rHR/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"6067": {
    "doc": "Units, Measurement & Locale",
    "title": "Temperature",
    "content": "Temperature values from environment sensors are transmitted as °C and displayed based on your device’s temperature unit preference. | 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. Temperature follows your locale’s temperature preference, independent of the distance system. Locales that mix systems work correctly — a UK phone shows miles for distance but °C for temperature. On Android 14+, the Temperature regional preference (Settings → System → Languages → Regional preferences) overrides the locale default. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/units-and-locale.html#temperature",
    
    "relUrl": "/hr-rHR/user/units-and-locale.html#temperature"
  },"6068": {
    "doc": "Units, Measurement & Locale",
    "title": "Distance & Altitude",
    "content": "Distances between nodes and GPS altitudes are transmitted as meters and automatically scaled and converted. | 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 kilometers 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 | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/units-and-locale.html#distance--altitude",
    
    "relUrl": "/hr-rHR/user/units-and-locale.html#distance--altitude"
  },"6069": {
    "doc": "Units, Measurement & Locale",
    "title": "Speed",
    "content": "GPS ground speed is displayed in your locale’s preferred speed unit. | Your Setting | You See | . | Metric | 12 km/h | . | Imperial (US) | 7 mph | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/units-and-locale.html#speed",
    
    "relUrl": "/hr-rHR/user/units-and-locale.html#speed"
  },"6070": {
    "doc": "Units, Measurement & Locale",
    "title": "Wind",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | Your Setting | You See | . | Metric | 18.0 km/h | . | Imperial (US) | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/units-and-locale.html#wind",
    
    "relUrl": "/hr-rHR/user/units-and-locale.html#wind"
  },"6071": {
    "doc": "Units, Measurement & Locale",
    "title": "Weight",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | Your Setting | You See | . | Metric | 1.50 kg | . | Imperial (US) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/units-and-locale.html#weight",
    
    "relUrl": "/hr-rHR/user/units-and-locale.html#weight"
  },"6072": {
    "doc": "Units, Measurement & Locale",
    "title": "Rainfall",
    "content": "Rainfall measurements (1-hour and 24-hour totals) are transmitted as mm and converted for display. | Your Setting | You See | . | Metric | 12.0 mm | . | Imperial (US) | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/units-and-locale.html#rainfall",
    
    "relUrl": "/hr-rHR/user/units-and-locale.html#rainfall"
  },"6073": {
    "doc": "Units, Measurement & Locale",
    "title": "Units That Never Change",
    "content": "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/h | Standard dosimetry unit | . | GPS coordinates | decimal degrees | Universal geographic standard | . | Humidity, battery, soil moisture | % | Universal | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/units-and-locale.html#units-that-never-change",
    
    "relUrl": "/hr-rHR/user/units-and-locale.html#units-that-never-change"
  },"6074": {
    "doc": "Units, Measurement & Locale",
    "title": "Date & Time",
    "content": "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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/units-and-locale.html#date--time",
    
    "relUrl": "/hr-rHR/user/units-and-locale.html#date--time"
  },"6075": {
    "doc": "Units, Measurement & Locale",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region | Return to Meshtastic — values update immediately | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/hr-rHR/user/units-and-locale.html#changing-your-measurement-system"
  },"6076": {
    "doc": "Units, Measurement & Locale",
    "title": "Related Topics",
    "content": ". | Node Metrics — where temperature, distance, and sensor values are displayed | Telemetry & Sensors — the sensors that produce these measurements | Measurement & Formatting — developer reference for the formatting utilities | Settings — Radio & User — region setting that drives unit selection | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/units-and-locale.html#related-topics",
    
    "relUrl": "/hr-rHR/user/units-and-locale.html#related-topics"
  },"6077": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": " ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/units-and-locale.html",
    
    "relUrl": "/hr-rHR/user/units-and-locale.html"
  },"6078": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/units-and-locale.html#units-measurement--locale",
    
    "relUrl": "/pt-rPT/user/units-and-locale.html#units-measurement--locale"
  },"6079": {
    "doc": "Units, Measurement & Locale",
    "title": "How It Works",
    "content": "Meshtastic radios always transmit data in metric units (meters, °C, m/s, hPa, etc.). When the app receives this data, it converts and displays 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. Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/units-and-locale.html#how-it-works",
    
    "relUrl": "/pt-rPT/user/units-and-locale.html#how-it-works"
  },"6080": {
    "doc": "Units, Measurement & Locale",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/pt-rPT/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"6081": {
    "doc": "Units, Measurement & Locale",
    "title": "Temperatura",
    "content": "Temperature values from environment sensors are transmitted as °C and displayed based on your device’s temperature unit preference. | 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. Temperature follows your locale’s temperature preference, independent of the distance system. Locales that mix systems work correctly — a UK phone shows miles for distance but °C for temperature. On Android 14+, the Temperature regional preference (Settings → System → Languages → Regional preferences) overrides the locale default. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/units-and-locale.html#temperatura",
    
    "relUrl": "/pt-rPT/user/units-and-locale.html#temperatura"
  },"6082": {
    "doc": "Units, Measurement & Locale",
    "title": "Distance & Altitude",
    "content": "Distances between nodes and GPS altitudes are transmitted as meters and automatically scaled and converted. | 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 kilometers 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 | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/units-and-locale.html#distance--altitude",
    
    "relUrl": "/pt-rPT/user/units-and-locale.html#distance--altitude"
  },"6083": {
    "doc": "Units, Measurement & Locale",
    "title": "Speed",
    "content": "GPS ground speed is displayed in your locale’s preferred speed unit. | Your Setting | You See | . | Metric | 12 km/h | . | Imperial (US) | 7 mph | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/units-and-locale.html#speed",
    
    "relUrl": "/pt-rPT/user/units-and-locale.html#speed"
  },"6084": {
    "doc": "Units, Measurement & Locale",
    "title": "Vento",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | Your Setting | You See | . | Metric | 18.0 km/h | . | Imperial (US) | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/units-and-locale.html#vento",
    
    "relUrl": "/pt-rPT/user/units-and-locale.html#vento"
  },"6085": {
    "doc": "Units, Measurement & Locale",
    "title": "Peso",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | Your Setting | You See | . | Metric | 1.50 kg | . | Imperial (US) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/units-and-locale.html#peso",
    
    "relUrl": "/pt-rPT/user/units-and-locale.html#peso"
  },"6086": {
    "doc": "Units, Measurement & Locale",
    "title": "Rainfall",
    "content": "Rainfall measurements (1-hour and 24-hour totals) are transmitted as mm and converted for display. | Your Setting | You See | . | Metric | 12.0 mm | . | Imperial (US) | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/units-and-locale.html#rainfall",
    
    "relUrl": "/pt-rPT/user/units-and-locale.html#rainfall"
  },"6087": {
    "doc": "Units, Measurement & Locale",
    "title": "Units That Never Change",
    "content": "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 | . | Radiação | µR/h | Standard dosimetry unit | . | GPS coordinates | decimal degrees | Universal geographic standard | . | Humidity, battery, soil moisture | % | Universal | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/units-and-locale.html#units-that-never-change",
    
    "relUrl": "/pt-rPT/user/units-and-locale.html#units-that-never-change"
  },"6088": {
    "doc": "Units, Measurement & Locale",
    "title": "Date & Time",
    "content": "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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/units-and-locale.html#date--time",
    
    "relUrl": "/pt-rPT/user/units-and-locale.html#date--time"
  },"6089": {
    "doc": "Units, Measurement & Locale",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region | Return to Meshtastic — values update immediately | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/pt-rPT/user/units-and-locale.html#changing-your-measurement-system"
  },"6090": {
    "doc": "Units, Measurement & Locale",
    "title": "Related Topics",
    "content": ". | Node Metrics — where temperature, distance, and sensor values are displayed | Telemetry & Sensors — the sensors that produce these measurements | Measurement & Formatting — developer reference for the formatting utilities | Settings — Radio & User — region setting that drives unit selection | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/units-and-locale.html#related-topics",
    
    "relUrl": "/pt-rPT/user/units-and-locale.html#related-topics"
  },"6091": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": " ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/units-and-locale.html",
    
    "relUrl": "/pt-rPT/user/units-and-locale.html"
  },"6092": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/units-and-locale.html#units-measurement--locale",
    
    "relUrl": "/pl-rPL/user/units-and-locale.html#units-measurement--locale"
  },"6093": {
    "doc": "Units, Measurement & Locale",
    "title": "How It Works",
    "content": "Meshtastic radios always transmit data in metric units (meters, °C, m/s, hPa, etc.). When the app receives this data, it converts and displays 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. Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/units-and-locale.html#how-it-works",
    
    "relUrl": "/pl-rPL/user/units-and-locale.html#how-it-works"
  },"6094": {
    "doc": "Units, Measurement & Locale",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/pl-rPL/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"6095": {
    "doc": "Units, Measurement & Locale",
    "title": "Temperatura",
    "content": "Temperature values from environment sensors are transmitted as °C and displayed based on your device’s temperature unit preference. | 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. Temperature follows your locale’s temperature preference, independent of the distance system. Locales that mix systems work correctly — a UK phone shows miles for distance but °C for temperature. On Android 14+, the Temperature regional preference (Settings → System → Languages → Regional preferences) overrides the locale default. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/units-and-locale.html#temperatura",
    
    "relUrl": "/pl-rPL/user/units-and-locale.html#temperatura"
  },"6096": {
    "doc": "Units, Measurement & Locale",
    "title": "Distance & Altitude",
    "content": "Distances between nodes and GPS altitudes are transmitted as meters and automatically scaled and converted. | Your Setting | Small Distance | Large Distance | Wysokość | . | 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 kilometers 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 | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/units-and-locale.html#distance--altitude",
    
    "relUrl": "/pl-rPL/user/units-and-locale.html#distance--altitude"
  },"6097": {
    "doc": "Units, Measurement & Locale",
    "title": "Prędkość",
    "content": "GPS ground speed is displayed in your locale’s preferred speed unit. | Your Setting | You See | . | Metric | 12 km/h | . | Imperial (US) | 7 mph | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/units-and-locale.html#pr%C4%99dko%C5%9B%C4%87",
    
    "relUrl": "/pl-rPL/user/units-and-locale.html#prędkość"
  },"6098": {
    "doc": "Units, Measurement & Locale",
    "title": "Wiatr",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | Your Setting | You See | . | Metric | 18.0 km/h | . | Imperial (US) | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/units-and-locale.html#wiatr",
    
    "relUrl": "/pl-rPL/user/units-and-locale.html#wiatr"
  },"6099": {
    "doc": "Units, Measurement & Locale",
    "title": "Weight",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | Your Setting | You See | . | Metric | 1.50 kg | . | Imperial (US) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/units-and-locale.html#weight",
    
    "relUrl": "/pl-rPL/user/units-and-locale.html#weight"
  },"6100": {
    "doc": "Units, Measurement & Locale",
    "title": "Rainfall",
    "content": "Rainfall measurements (1-hour and 24-hour totals) are transmitted as mm and converted for display. | Your Setting | You See | . | Metric | 12.0 mm | . | Imperial (US) | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/units-and-locale.html#rainfall",
    
    "relUrl": "/pl-rPL/user/units-and-locale.html#rainfall"
  },"6101": {
    "doc": "Units, Measurement & Locale",
    "title": "Units That Never Change",
    "content": "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 | . | Promieniowanie | µR/h | Standard dosimetry unit | . | GPS coordinates | decimal degrees | Universal geographic standard | . | Humidity, battery, soil moisture | % | Universal | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/units-and-locale.html#units-that-never-change",
    
    "relUrl": "/pl-rPL/user/units-and-locale.html#units-that-never-change"
  },"6102": {
    "doc": "Units, Measurement & Locale",
    "title": "Date & Time",
    "content": "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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/units-and-locale.html#date--time",
    
    "relUrl": "/pl-rPL/user/units-and-locale.html#date--time"
  },"6103": {
    "doc": "Units, Measurement & Locale",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region | Return to Meshtastic — values update immediately | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/pl-rPL/user/units-and-locale.html#changing-your-measurement-system"
  },"6104": {
    "doc": "Units, Measurement & Locale",
    "title": "Related Topics",
    "content": ". | Node Metrics — where temperature, distance, and sensor values are displayed | Telemetry & Sensors — the sensors that produce these measurements | Measurement & Formatting — developer reference for the formatting utilities | Settings — Radio & User — region setting that drives unit selection | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/units-and-locale.html#related-topics",
    
    "relUrl": "/pl-rPL/user/units-and-locale.html#related-topics"
  },"6105": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": " ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/units-and-locale.html",
    
    "relUrl": "/pl-rPL/user/units-and-locale.html"
  },"6106": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/units-and-locale.html#units-measurement--locale",
    
    "relUrl": "/zh-rCN/user/units-and-locale.html#units-measurement--locale"
  },"6107": {
    "doc": "Units, Measurement & Locale",
    "title": "How It Works",
    "content": "Meshtastic radios always transmit data in metric units (meters, °C, m/s, hPa, etc.). When the app receives this data, it converts and displays 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. Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/units-and-locale.html#how-it-works",
    
    "relUrl": "/zh-rCN/user/units-and-locale.html#how-it-works"
  },"6108": {
    "doc": "Units, Measurement & Locale",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/zh-rCN/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"6109": {
    "doc": "Units, Measurement & Locale",
    "title": "温度",
    "content": "Temperature values from environment sensors are transmitted as °C and displayed based on your device’s temperature unit preference. | 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. Temperature follows your locale’s temperature preference, independent of the distance system. Locales that mix systems work correctly — a UK phone shows miles for distance but °C for temperature. On Android 14+, the Temperature regional preference (Settings → System → Languages → Regional preferences) overrides the locale default. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/units-and-locale.html#%E6%B8%A9%E5%BA%A6",
    
    "relUrl": "/zh-rCN/user/units-and-locale.html#温度"
  },"6110": {
    "doc": "Units, Measurement & Locale",
    "title": "Distance & Altitude",
    "content": "Distances between nodes and GPS altitudes are transmitted as meters and automatically scaled and converted. | 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 kilometers 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 | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/units-and-locale.html#distance--altitude",
    
    "relUrl": "/zh-rCN/user/units-and-locale.html#distance--altitude"
  },"6111": {
    "doc": "Units, Measurement & Locale",
    "title": "速度",
    "content": "GPS ground speed is displayed in your locale’s preferred speed unit. | Your Setting | You See | . | 公制 | 12 km/h | . | Imperial (US) | 7 mph | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/units-and-locale.html#%E9%80%9F%E5%BA%A6",
    
    "relUrl": "/zh-rCN/user/units-and-locale.html#速度"
  },"6112": {
    "doc": "Units, Measurement & Locale",
    "title": "风",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | Your Setting | You See | . | 公制 | 18.0 km/h | . | Imperial (US) | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/units-and-locale.html#%E9%A3%8E",
    
    "relUrl": "/zh-rCN/user/units-and-locale.html#风"
  },"6113": {
    "doc": "Units, Measurement & Locale",
    "title": "重量",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | Your Setting | You See | . | 公制 | 1.50 kg | . | Imperial (US) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/units-and-locale.html#%E9%87%8D%E9%87%8F",
    
    "relUrl": "/zh-rCN/user/units-and-locale.html#重量"
  },"6114": {
    "doc": "Units, Measurement & Locale",
    "title": "Rainfall",
    "content": "Rainfall measurements (1-hour and 24-hour totals) are transmitted as mm and converted for display. | Your Setting | You See | . | 公制 | 12.0 mm | . | Imperial (US) | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/units-and-locale.html#rainfall",
    
    "relUrl": "/zh-rCN/user/units-and-locale.html#rainfall"
  },"6115": {
    "doc": "Units, Measurement & Locale",
    "title": "Units That Never Change",
    "content": "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/h | Standard dosimetry unit | . | GPS coordinates | decimal degrees | Universal geographic standard | . | Humidity, battery, soil moisture | % | Universal | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/units-and-locale.html#units-that-never-change",
    
    "relUrl": "/zh-rCN/user/units-and-locale.html#units-that-never-change"
  },"6116": {
    "doc": "Units, Measurement & Locale",
    "title": "Date & Time",
    "content": "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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/units-and-locale.html#date--time",
    
    "relUrl": "/zh-rCN/user/units-and-locale.html#date--time"
  },"6117": {
    "doc": "Units, Measurement & Locale",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region | Return to Meshtastic — values update immediately | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/zh-rCN/user/units-and-locale.html#changing-your-measurement-system"
  },"6118": {
    "doc": "Units, Measurement & Locale",
    "title": "Related Topics",
    "content": ". | Node Metrics — where temperature, distance, and sensor values are displayed | Telemetry & Sensors — the sensors that produce these measurements | Measurement & Formatting — developer reference for the formatting utilities | Settings — Radio & User — region setting that drives unit selection | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/units-and-locale.html#related-topics",
    
    "relUrl": "/zh-rCN/user/units-and-locale.html#related-topics"
  },"6119": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": " ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/units-and-locale.html",
    
    "relUrl": "/zh-rCN/user/units-and-locale.html"
  },"6120": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/units-and-locale.html#units-measurement--locale",
    
    "relUrl": "/sq-rAL/user/units-and-locale.html#units-measurement--locale"
  },"6121": {
    "doc": "Units, Measurement & Locale",
    "title": "How It Works",
    "content": "Meshtastic radios always transmit data in metric units (meters, °C, m/s, hPa, etc.). When the app receives this data, it converts and displays 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. Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/units-and-locale.html#how-it-works",
    
    "relUrl": "/sq-rAL/user/units-and-locale.html#how-it-works"
  },"6122": {
    "doc": "Units, Measurement & Locale",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/sq-rAL/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"6123": {
    "doc": "Units, Measurement & Locale",
    "title": "Temperatura",
    "content": "Temperature values from environment sensors are transmitted as °C and displayed based on your device’s temperature unit preference. | 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. Temperature follows your locale’s temperature preference, independent of the distance system. Locales that mix systems work correctly — a UK phone shows miles for distance but °C for temperature. On Android 14+, the Temperature regional preference (Settings → System → Languages → Regional preferences) overrides the locale default. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/units-and-locale.html#temperatura",
    
    "relUrl": "/sq-rAL/user/units-and-locale.html#temperatura"
  },"6124": {
    "doc": "Units, Measurement & Locale",
    "title": "Distance & Altitude",
    "content": "Distances between nodes and GPS altitudes are transmitted as meters and automatically scaled and converted. | 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 kilometers 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 | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/units-and-locale.html#distance--altitude",
    
    "relUrl": "/sq-rAL/user/units-and-locale.html#distance--altitude"
  },"6125": {
    "doc": "Units, Measurement & Locale",
    "title": "Speed",
    "content": "GPS ground speed is displayed in your locale’s preferred speed unit. | Your Setting | You See | . | Metric | 12 km/h | . | Imperial (US) | 7 mph | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/units-and-locale.html#speed",
    
    "relUrl": "/sq-rAL/user/units-and-locale.html#speed"
  },"6126": {
    "doc": "Units, Measurement & Locale",
    "title": "Wind",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | Your Setting | You See | . | Metric | 18.0 km/h | . | Imperial (US) | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/units-and-locale.html#wind",
    
    "relUrl": "/sq-rAL/user/units-and-locale.html#wind"
  },"6127": {
    "doc": "Units, Measurement & Locale",
    "title": "Weight",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | Your Setting | You See | . | Metric | 1.50 kg | . | Imperial (US) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/units-and-locale.html#weight",
    
    "relUrl": "/sq-rAL/user/units-and-locale.html#weight"
  },"6128": {
    "doc": "Units, Measurement & Locale",
    "title": "Rainfall",
    "content": "Rainfall measurements (1-hour and 24-hour totals) are transmitted as mm and converted for display. | Your Setting | You See | . | Metric | 12.0 mm | . | Imperial (US) | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/units-and-locale.html#rainfall",
    
    "relUrl": "/sq-rAL/user/units-and-locale.html#rainfall"
  },"6129": {
    "doc": "Units, Measurement & Locale",
    "title": "Units That Never Change",
    "content": "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/h | Standard dosimetry unit | . | GPS coordinates | decimal degrees | Universal geographic standard | . | Humidity, battery, soil moisture | % | Universal | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/units-and-locale.html#units-that-never-change",
    
    "relUrl": "/sq-rAL/user/units-and-locale.html#units-that-never-change"
  },"6130": {
    "doc": "Units, Measurement & Locale",
    "title": "Date & Time",
    "content": "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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/units-and-locale.html#date--time",
    
    "relUrl": "/sq-rAL/user/units-and-locale.html#date--time"
  },"6131": {
    "doc": "Units, Measurement & Locale",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region | Return to Meshtastic — values update immediately | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/sq-rAL/user/units-and-locale.html#changing-your-measurement-system"
  },"6132": {
    "doc": "Units, Measurement & Locale",
    "title": "Related Topics",
    "content": ". | Node Metrics — where temperature, distance, and sensor values are displayed | Telemetry & Sensors — the sensors that produce these measurements | Measurement & Formatting — developer reference for the formatting utilities | Settings — Radio & User — region setting that drives unit selection | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/units-and-locale.html#related-topics",
    
    "relUrl": "/sq-rAL/user/units-and-locale.html#related-topics"
  },"6133": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": " ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/units-and-locale.html",
    
    "relUrl": "/sq-rAL/user/units-and-locale.html"
  },"6134": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/units-and-locale.html#units-measurement--locale",
    
    "relUrl": "/zh-rTW/user/units-and-locale.html#units-measurement--locale"
  },"6135": {
    "doc": "Units, Measurement & Locale",
    "title": "運作方式",
    "content": "Meshtastic radios always transmit data in metric units (meters, °C, m/s, hPa, etc.). When the app receives this data, it converts and displays values in whatever unit system your device’s locale specifies. 在 Android 上，量測單位偏好由系統的語言與地區設定決定。在桌面版（JVM）上，應用程式使用 JVM 的預設 Locale。 . Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/units-and-locale.html#%E9%81%8B%E4%BD%9C%E6%96%B9%E5%BC%8F",
    
    "relUrl": "/zh-rTW/user/units-and-locale.html#運作方式"
  },"6136": {
    "doc": "Units, Measurement & Locale",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/zh-rTW/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"6137": {
    "doc": "Units, Measurement & Locale",
    "title": "溫度",
    "content": "Temperature values from environment sensors are transmitted as °C and displayed based on your device’s temperature unit preference. | 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. Temperature follows your locale’s temperature preference, independent of the distance system. Locales that mix systems work correctly — a UK phone shows miles for distance but °C for temperature. On Android 14+, the Temperature regional preference (Settings → System → Languages → Regional preferences) overrides the locale default. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/units-and-locale.html#%E6%BA%AB%E5%BA%A6",
    
    "relUrl": "/zh-rTW/user/units-and-locale.html#溫度"
  },"6138": {
    "doc": "Units, Measurement & Locale",
    "title": "Distance & Altitude",
    "content": "Distances between nodes and GPS altitudes are transmitted as meters and automatically scaled and converted. | 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 kilometers 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 | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/units-and-locale.html#distance--altitude",
    
    "relUrl": "/zh-rTW/user/units-and-locale.html#distance--altitude"
  },"6139": {
    "doc": "Units, Measurement & Locale",
    "title": "速度",
    "content": "GPS ground speed is displayed in your locale’s preferred speed unit. | Your Setting | You See | . | 公制（公里/公尺） | 12 km/h | . | Imperial (US) | 7 mph | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/units-and-locale.html#%E9%80%9F%E5%BA%A6",
    
    "relUrl": "/zh-rTW/user/units-and-locale.html#速度"
  },"6140": {
    "doc": "Units, Measurement & Locale",
    "title": "風速",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | Your Setting | You See | . | 公制（公里/公尺） | 18.0 km/h | . | Imperial (US) | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/units-and-locale.html#%E9%A2%A8%E9%80%9F",
    
    "relUrl": "/zh-rTW/user/units-and-locale.html#風速"
  },"6141": {
    "doc": "Units, Measurement & Locale",
    "title": "重量",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | Your Setting | You See | . | 公制（公里/公尺） | 1.50 kg | . | Imperial (US) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/units-and-locale.html#%E9%87%8D%E9%87%8F",
    
    "relUrl": "/zh-rTW/user/units-and-locale.html#重量"
  },"6142": {
    "doc": "Units, Measurement & Locale",
    "title": "Rainfall",
    "content": "Rainfall measurements (1-hour and 24-hour totals) are transmitted as mm and converted for display. | 您的設定 | 顯示方式 | . | 公制（公里/公尺） | 12.0 mm | . | 英制（美國） | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/units-and-locale.html#rainfall",
    
    "relUrl": "/zh-rTW/user/units-and-locale.html#rainfall"
  },"6143": {
    "doc": "Units, Measurement & Locale",
    "title": "Units That Never Change",
    "content": "Some units are international standards and are displayed the same way regardless of your locale: . | Measurement | Unit | Why | . | 氣壓 | hPa | International meteorological standard | . | Heading / bearing | ° (degrees) | Universal navigation convention | . | 輻射 | µR/h | Standard dosimetry unit | . | GPS coordinates | decimal degrees | Universal geographic standard | . | Humidity, battery, soil moisture | % | Universal | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/units-and-locale.html#units-that-never-change",
    
    "relUrl": "/zh-rTW/user/units-and-locale.html#units-that-never-change"
  },"6144": {
    "doc": "Units, Measurement & Locale",
    "title": "Date & Time",
    "content": "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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/units-and-locale.html#date--time",
    
    "relUrl": "/zh-rTW/user/units-and-locale.html#date--time"
  },"6145": {
    "doc": "Units, Measurement & Locale",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region | Return to Meshtastic — values update immediately | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/zh-rTW/user/units-and-locale.html#changing-your-measurement-system"
  },"6146": {
    "doc": "Units, Measurement & Locale",
    "title": "相關主題",
    "content": ". | Node Metrics — where temperature, distance, and sensor values are displayed | Telemetry & Sensors — the sensors that produce these measurements | Measurement & Formatting — developer reference for the formatting utilities | Settings — Radio & User — region setting that drives unit selection | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/units-and-locale.html#%E7%9B%B8%E9%97%9C%E4%B8%BB%E9%A1%8C",
    
    "relUrl": "/zh-rTW/user/units-and-locale.html#相關主題"
  },"6147": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": " ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/units-and-locale.html",
    
    "relUrl": "/zh-rTW/user/units-and-locale.html"
  },"6148": {
    "doc": "Ühikud, mõõtühikud ja lokaat",
    "title": "Ühikud, mõõtühikud ja lokaat",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/units-and-locale.html",
    
    "relUrl": "/et-rEE/user/units-and-locale.html"
  },"6149": {
    "doc": "Ühikud, mõõtühikud ja lokaat",
    "title": "Kuidas see toimib",
    "content": "Meshtastic raadiod edastavad andmeid alati meetrilistes ühikutes (meetrites, °C, m/s, hPa jne). Kui rakendus need andmed vastu võtab, teisendab ja kuvab see väärtused seadme lokaadi määratud ühikutes. Androidis määravad mõõteseaded süsteemi Keel ja piirkond seaded. Töölaual (JVM) kasutab rakendus JVM-i vaikesätet „lokaat”. Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/units-and-locale.html#kuidas-see-toimib",
    
    "relUrl": "/et-rEE/user/units-and-locale.html#kuidas-see-toimib"
  },"6150": {
    "doc": "Ühikud, mõõtühikud ja lokaat",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/et-rEE/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"6151": {
    "doc": "Ühikud, mõõtühikud ja lokaat",
    "title": "Temperatuur",
    "content": "Temperature values from environment sensors are transmitted as °C and displayed based on your device’s temperature unit preference. | Sinu sätted | Teadmiseks | . | 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. Temperature follows your locale’s temperature preference, independent of the distance system. Locales that mix systems work correctly — a UK phone shows miles for distance but °C for temperature. Android 14+ puhul tühistab Temperatuuri piirkondlik eelistus (Seaded → Süsteem → Keeled → Piirkondlikud eelistused) lokaalse vaikesätte. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/units-and-locale.html#temperatuur",
    
    "relUrl": "/et-rEE/user/units-and-locale.html#temperatuur"
  },"6152": {
    "doc": "Ühikud, mõõtühikud ja lokaat",
    "title": "Distance & Altitude",
    "content": "Sõlmede vahelised kaugused ja GPS kõrgused edastatakse meetrites ning skaleeritakse ja teisendatakse automaatselt. | Sinu sätted | Small Distance | Large Distance | Kõrgus | . | Meetriline | 350 m | 2.5 km | 1200 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 kilometers or miles automatically. Where these appear . | Node list — distance and bearing to each node | Sõlme detail — kõrgus, kaugus asukohast | Kaart — teekonnapunktide vahemaad, traceroute’i hüppevahemaad | Kompass — kaugus valitud sõlmeni | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/units-and-locale.html#distance--altitude",
    
    "relUrl": "/et-rEE/user/units-and-locale.html#distance--altitude"
  },"6153": {
    "doc": "Ühikud, mõõtühikud ja lokaat",
    "title": "Kiirus",
    "content": "GPSi maapealne kiirus kuvatakse lokaadi eelistatud kiiruseühikus. | Sinu sätted | Teadmiseks | . | Meetriline | 12 km/h | . | Imperial (US) | 7 mph | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/units-and-locale.html#kiirus",
    
    "relUrl": "/et-rEE/user/units-and-locale.html#kiirus"
  },"6154": {
    "doc": "Ühikud, mõõtühikud ja lokaat",
    "title": "Tuul",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | Sinu sätted | Teadmiseks | . | Meetriline | 18.0 km/h | . | Imperial (US) | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/units-and-locale.html#tuul",
    
    "relUrl": "/et-rEE/user/units-and-locale.html#tuul"
  },"6155": {
    "doc": "Ühikud, mõõtühikud ja lokaat",
    "title": "Kaal",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | Sinu sätted | Teadmiseks | . | Meetriline | 1.50 kg | . | Imperial (US) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/units-and-locale.html#kaal",
    
    "relUrl": "/et-rEE/user/units-and-locale.html#kaal"
  },"6156": {
    "doc": "Ühikud, mõõtühikud ja lokaat",
    "title": "Rainfall",
    "content": "Rainfall measurements (1-hour and 24-hour totals) are transmitted as mm and converted for display. | Sinu sätted | Teadmiseks | . | Meetriline | 12.0 mm | . | Imperial (US) | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/units-and-locale.html#rainfall",
    
    "relUrl": "/et-rEE/user/units-and-locale.html#rainfall"
  },"6157": {
    "doc": "Ühikud, mõõtühikud ja lokaat",
    "title": "Units That Never Change",
    "content": "Mõned ühikud on rahvusvahelised standardid ja neid kuvatakse ühtemoodi olenemata lokaat: . | Measurement | Unit | Why | . | Baromeetrii rõhk | hPa | International meteorological standard | . | Heading / bearing | ° (degrees) | Universal navigation convention | . | Radiatsioon | µR/h | Standard dosimetry unit | . | GPS koordinaadid | decimal degrees | Universal geographic standard | . | Niiskus, aku, mulla niiskus | % | Universal | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/units-and-locale.html#units-that-never-change",
    
    "relUrl": "/et-rEE/user/units-and-locale.html#units-that-never-change"
  },"6158": {
    "doc": "Ühikud, mõõtühikud ja lokaat",
    "title": "Date & Time",
    "content": "All timestamps throughout the app — last heard, message times, telemetry logs, chart axes — follow your device’s date and time preferences. | Sätted | What It Controls | Example | . | 24 tunnine aeg | Kella vorming | 14:30 või 2:30 PM | . | Kuupäeva vorming | Date ordering | 09/05/2026 või 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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/units-and-locale.html#date--time",
    
    "relUrl": "/et-rEE/user/units-and-locale.html#date--time"
  },"6159": {
    "doc": "Ühikud, mõõtühikud ja lokaat",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | Ava Androidi seaded → Süsteem → Keel ja piirkond | Change your Region | Tagasi Meshtastic juurde — väärtused värskendatakse kohe | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/et-rEE/user/units-and-locale.html#changing-your-measurement-system"
  },"6160": {
    "doc": "Ühikud, mõõtühikud ja lokaat",
    "title": "Seotud teemad",
    "content": ". | Node Metrics — where temperature, distance, and sensor values are displayed | Telemeetia & Sensorid — andurid, mis neid mõõtmisi teevad | Measurement & Formatting — developer reference for the formatting utilities | Seaded — Raadio ja kasutaja — piirkonna säte, mis määrab üksuse valiku | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/units-and-locale.html#seotud-teemad",
    
    "relUrl": "/et-rEE/user/units-and-locale.html#seotud-teemad"
  },"6161": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/units-and-locale.html#units-measurement--locale",
    
    "relUrl": "/fr-rFR/user/units-and-locale.html#units-measurement--locale"
  },"6162": {
    "doc": "Units, Measurement & Locale",
    "title": "Comment ça marche",
    "content": "Meshtastic radios always transmit data in metric units (meters, °C, m/s, hPa, etc.). When the app receives this data, it converts and displays values in whatever unit system your device’s locale specifies. Sur Android, vos préférences de mesure sont déterminées par les paramètres de Langue et Région de votre système. Sur l’application de bureau (JVM), la Locale par défaut de la JVM est utilisée. Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/units-and-locale.html#comment-%C3%A7a-marche",
    
    "relUrl": "/fr-rFR/user/units-and-locale.html#comment-ça-marche"
  },"6163": {
    "doc": "Units, Measurement & Locale",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/fr-rFR/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"6164": {
    "doc": "Units, Measurement & Locale",
    "title": "Température",
    "content": "Temperature values from environment sensors are transmitted as °C and displayed based on your device’s temperature unit preference. | 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. Temperature follows your locale’s temperature preference, independent of the distance system. Locales that mix systems work correctly — a UK phone shows miles for distance but °C for temperature. On Android 14+, the Temperature regional preference (Settings → System → Languages → Regional preferences) overrides the locale default. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/units-and-locale.html#temp%C3%A9rature",
    
    "relUrl": "/fr-rFR/user/units-and-locale.html#température"
  },"6165": {
    "doc": "Units, Measurement & Locale",
    "title": "Distance & Altitude",
    "content": "Distances between nodes and GPS altitudes are transmitted as meters and automatically scaled and converted. | 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 kilometers 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 | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/units-and-locale.html#distance--altitude",
    
    "relUrl": "/fr-rFR/user/units-and-locale.html#distance--altitude"
  },"6166": {
    "doc": "Units, Measurement & Locale",
    "title": "Vitesse",
    "content": "GPS ground speed is displayed in your locale’s preferred speed unit. | Your Setting | You See | . | Metric | 12 km/h | . | Imperial (US) | 7 mph | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/units-and-locale.html#vitesse",
    
    "relUrl": "/fr-rFR/user/units-and-locale.html#vitesse"
  },"6167": {
    "doc": "Units, Measurement & Locale",
    "title": "Vent",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | Your Setting | You See | . | Metric | 18.0 km/h | . | Imperial (US) | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/units-and-locale.html#vent",
    
    "relUrl": "/fr-rFR/user/units-and-locale.html#vent"
  },"6168": {
    "doc": "Units, Measurement & Locale",
    "title": "Poids",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | Your Setting | You See | . | Metric | 1.50 kg | . | Imperial (US) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/units-and-locale.html#poids",
    
    "relUrl": "/fr-rFR/user/units-and-locale.html#poids"
  },"6169": {
    "doc": "Units, Measurement & Locale",
    "title": "Rainfall",
    "content": "Rainfall measurements (1-hour and 24-hour totals) are transmitted as mm and converted for display. | Vos réglages | Vous voyez | . | Métrique | 12.0 mm | . | Impérial (États-Unis) | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/units-and-locale.html#rainfall",
    
    "relUrl": "/fr-rFR/user/units-and-locale.html#rainfall"
  },"6170": {
    "doc": "Units, Measurement & Locale",
    "title": "Units That Never Change",
    "content": "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/h | Standard dosimetry unit | . | GPS coordinates | decimal degrees | Universal geographic standard | . | Humidity, battery, soil moisture | % | Universal | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/units-and-locale.html#units-that-never-change",
    
    "relUrl": "/fr-rFR/user/units-and-locale.html#units-that-never-change"
  },"6171": {
    "doc": "Units, Measurement & Locale",
    "title": "Date & Time",
    "content": "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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/units-and-locale.html#date--time",
    
    "relUrl": "/fr-rFR/user/units-and-locale.html#date--time"
  },"6172": {
    "doc": "Units, Measurement & Locale",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region | Return to Meshtastic — values update immediately | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/fr-rFR/user/units-and-locale.html#changing-your-measurement-system"
  },"6173": {
    "doc": "Units, Measurement & Locale",
    "title": "Related Topics",
    "content": ". | Node Metrics — where temperature, distance, and sensor values are displayed | Telemetry & Sensors — the sensors that produce these measurements | Measurement & Formatting — developer reference for the formatting utilities | Settings — Radio & User — region setting that drives unit selection | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/units-and-locale.html#related-topics",
    
    "relUrl": "/fr-rFR/user/units-and-locale.html#related-topics"
  },"6174": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": " ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/units-and-locale.html",
    
    "relUrl": "/fr-rFR/user/units-and-locale.html"
  },"6175": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/units-and-locale.html#units-measurement--locale",
    
    "relUrl": "/tr-rTR/user/units-and-locale.html#units-measurement--locale"
  },"6176": {
    "doc": "Units, Measurement & Locale",
    "title": "How It Works",
    "content": "Meshtastic radios always transmit data in metric units (meters, °C, m/s, hPa, etc.). When the app receives this data, it converts and displays 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. Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/units-and-locale.html#how-it-works",
    
    "relUrl": "/tr-rTR/user/units-and-locale.html#how-it-works"
  },"6177": {
    "doc": "Units, Measurement & Locale",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/tr-rTR/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"6178": {
    "doc": "Units, Measurement & Locale",
    "title": "Sıcaklık",
    "content": "Temperature values from environment sensors are transmitted as °C and displayed based on your device’s temperature unit preference. | 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. Temperature follows your locale’s temperature preference, independent of the distance system. Locales that mix systems work correctly — a UK phone shows miles for distance but °C for temperature. On Android 14+, the Temperature regional preference (Settings → System → Languages → Regional preferences) overrides the locale default. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/units-and-locale.html#s%C4%B1cakl%C4%B1k",
    
    "relUrl": "/tr-rTR/user/units-and-locale.html#sıcaklık"
  },"6179": {
    "doc": "Units, Measurement & Locale",
    "title": "Distance & Altitude",
    "content": "Distances between nodes and GPS altitudes are transmitted as meters and automatically scaled and converted. | Your Setting | Small Distance | Large Distance | Rakım | . | 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 kilometers 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 | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/units-and-locale.html#distance--altitude",
    
    "relUrl": "/tr-rTR/user/units-and-locale.html#distance--altitude"
  },"6180": {
    "doc": "Units, Measurement & Locale",
    "title": "Speed",
    "content": "GPS ground speed is displayed in your locale’s preferred speed unit. | Your Setting | You See | . | Metric | 12 km/h | . | Imperial (US) | 7 mph | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/units-and-locale.html#speed",
    
    "relUrl": "/tr-rTR/user/units-and-locale.html#speed"
  },"6181": {
    "doc": "Units, Measurement & Locale",
    "title": "Rüzgar",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | Your Setting | You See | . | Metric | 18.0 km/h | . | Imperial (US) | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/units-and-locale.html#r%C3%BCzgar",
    
    "relUrl": "/tr-rTR/user/units-and-locale.html#rüzgar"
  },"6182": {
    "doc": "Units, Measurement & Locale",
    "title": "Ağırlık",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | Your Setting | You See | . | Metric | 1.50 kg | . | Imperial (US) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/units-and-locale.html#a%C4%9F%C4%B1rl%C4%B1k",
    
    "relUrl": "/tr-rTR/user/units-and-locale.html#ağırlık"
  },"6183": {
    "doc": "Units, Measurement & Locale",
    "title": "Rainfall",
    "content": "Rainfall measurements (1-hour and 24-hour totals) are transmitted as mm and converted for display. | Your Setting | You See | . | Metric | 12.0 mm | . | Imperial (US) | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/units-and-locale.html#rainfall",
    
    "relUrl": "/tr-rTR/user/units-and-locale.html#rainfall"
  },"6184": {
    "doc": "Units, Measurement & Locale",
    "title": "Units That Never Change",
    "content": "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 | . | Radyasyon | µR/h | Standard dosimetry unit | . | GPS coordinates | decimal degrees | Universal geographic standard | . | Humidity, battery, soil moisture | % | Universal | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/units-and-locale.html#units-that-never-change",
    
    "relUrl": "/tr-rTR/user/units-and-locale.html#units-that-never-change"
  },"6185": {
    "doc": "Units, Measurement & Locale",
    "title": "Date & Time",
    "content": "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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/units-and-locale.html#date--time",
    
    "relUrl": "/tr-rTR/user/units-and-locale.html#date--time"
  },"6186": {
    "doc": "Units, Measurement & Locale",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region | Return to Meshtastic — values update immediately | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/tr-rTR/user/units-and-locale.html#changing-your-measurement-system"
  },"6187": {
    "doc": "Units, Measurement & Locale",
    "title": "Related Topics",
    "content": ". | Node Metrics — where temperature, distance, and sensor values are displayed | Telemetry & Sensors — the sensors that produce these measurements | Measurement & Formatting — developer reference for the formatting utilities | Settings — Radio & User — region setting that drives unit selection | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/units-and-locale.html#related-topics",
    
    "relUrl": "/tr-rTR/user/units-and-locale.html#related-topics"
  },"6188": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": " ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/units-and-locale.html",
    
    "relUrl": "/tr-rTR/user/units-and-locale.html"
  },"6189": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/units-and-locale.html#units-measurement--locale",
    
    "relUrl": "/el-rGR/user/units-and-locale.html#units-measurement--locale"
  },"6190": {
    "doc": "Units, Measurement & Locale",
    "title": "How It Works",
    "content": "Meshtastic radios always transmit data in metric units (meters, °C, m/s, hPa, etc.). When the app receives this data, it converts and displays 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. Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/units-and-locale.html#how-it-works",
    
    "relUrl": "/el-rGR/user/units-and-locale.html#how-it-works"
  },"6191": {
    "doc": "Units, Measurement & Locale",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/el-rGR/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"6192": {
    "doc": "Units, Measurement & Locale",
    "title": "Θερμοκρασία",
    "content": "Temperature values from environment sensors are transmitted as °C and displayed based on your device’s temperature unit preference. | 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. Temperature follows your locale’s temperature preference, independent of the distance system. Locales that mix systems work correctly — a UK phone shows miles for distance but °C for temperature. On Android 14+, the Temperature regional preference (Settings → System → Languages → Regional preferences) overrides the locale default. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/units-and-locale.html#%CE%B8%CE%B5%CF%81%CE%BC%CE%BF%CE%BA%CF%81%CE%B1%CF%83%CE%AF%CE%B1",
    
    "relUrl": "/el-rGR/user/units-and-locale.html#θερμοκρασία"
  },"6193": {
    "doc": "Units, Measurement & Locale",
    "title": "Distance & Altitude",
    "content": "Distances between nodes and GPS altitudes are transmitted as meters and automatically scaled and converted. | 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 kilometers 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 | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/units-and-locale.html#distance--altitude",
    
    "relUrl": "/el-rGR/user/units-and-locale.html#distance--altitude"
  },"6194": {
    "doc": "Units, Measurement & Locale",
    "title": "Speed",
    "content": "GPS ground speed is displayed in your locale’s preferred speed unit. | Your Setting | You See | . | Metric | 12 km/h | . | Imperial (US) | 7 mph | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/units-and-locale.html#speed",
    
    "relUrl": "/el-rGR/user/units-and-locale.html#speed"
  },"6195": {
    "doc": "Units, Measurement & Locale",
    "title": "Wind",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | Your Setting | You See | . | Metric | 18.0 km/h | . | Imperial (US) | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/units-and-locale.html#wind",
    
    "relUrl": "/el-rGR/user/units-and-locale.html#wind"
  },"6196": {
    "doc": "Units, Measurement & Locale",
    "title": "Βάρος",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | Your Setting | You See | . | Metric | 1.50 kg | . | Imperial (US) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/units-and-locale.html#%CE%B2%CE%AC%CF%81%CE%BF%CF%82",
    
    "relUrl": "/el-rGR/user/units-and-locale.html#βάρος"
  },"6197": {
    "doc": "Units, Measurement & Locale",
    "title": "Rainfall",
    "content": "Rainfall measurements (1-hour and 24-hour totals) are transmitted as mm and converted for display. | Your Setting | You See | . | Metric | 12.0 mm | . | Imperial (US) | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/units-and-locale.html#rainfall",
    
    "relUrl": "/el-rGR/user/units-and-locale.html#rainfall"
  },"6198": {
    "doc": "Units, Measurement & Locale",
    "title": "Units That Never Change",
    "content": "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/h | Standard dosimetry unit | . | GPS coordinates | decimal degrees | Universal geographic standard | . | Humidity, battery, soil moisture | % | Universal | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/units-and-locale.html#units-that-never-change",
    
    "relUrl": "/el-rGR/user/units-and-locale.html#units-that-never-change"
  },"6199": {
    "doc": "Units, Measurement & Locale",
    "title": "Date & Time",
    "content": "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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/units-and-locale.html#date--time",
    
    "relUrl": "/el-rGR/user/units-and-locale.html#date--time"
  },"6200": {
    "doc": "Units, Measurement & Locale",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region | Return to Meshtastic — values update immediately | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/el-rGR/user/units-and-locale.html#changing-your-measurement-system"
  },"6201": {
    "doc": "Units, Measurement & Locale",
    "title": "Related Topics",
    "content": ". | Node Metrics — where temperature, distance, and sensor values are displayed | Telemetry & Sensors — the sensors that produce these measurements | Measurement & Formatting — developer reference for the formatting utilities | Settings — Radio & User — region setting that drives unit selection | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/units-and-locale.html#related-topics",
    
    "relUrl": "/el-rGR/user/units-and-locale.html#related-topics"
  },"6202": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": " ",
    "url": "/Meshtastic-Android/main/el-rGR/user/units-and-locale.html",
    
    "relUrl": "/el-rGR/user/units-and-locale.html"
  },"6203": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/units-and-locale.html#units-measurement--locale",
    
    "relUrl": "/ro-rRO/user/units-and-locale.html#units-measurement--locale"
  },"6204": {
    "doc": "Units, Measurement & Locale",
    "title": "How It Works",
    "content": "Meshtastic radios always transmit data in metric units (meters, °C, m/s, hPa, etc.). When the app receives this data, it converts and displays 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. Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/units-and-locale.html#how-it-works",
    
    "relUrl": "/ro-rRO/user/units-and-locale.html#how-it-works"
  },"6205": {
    "doc": "Units, Measurement & Locale",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/ro-rRO/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"6206": {
    "doc": "Units, Measurement & Locale",
    "title": "Temperature",
    "content": "Temperature values from environment sensors are transmitted as °C and displayed based on your device’s temperature unit preference. | 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. Temperature follows your locale’s temperature preference, independent of the distance system. Locales that mix systems work correctly — a UK phone shows miles for distance but °C for temperature. On Android 14+, the Temperature regional preference (Settings → System → Languages → Regional preferences) overrides the locale default. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/units-and-locale.html#temperature",
    
    "relUrl": "/ro-rRO/user/units-and-locale.html#temperature"
  },"6207": {
    "doc": "Units, Measurement & Locale",
    "title": "Distance & Altitude",
    "content": "Distances between nodes and GPS altitudes are transmitted as meters and automatically scaled and converted. | Your Setting | Small Distance | Large Distance | Altitudine | . | 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 kilometers 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 | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/units-and-locale.html#distance--altitude",
    
    "relUrl": "/ro-rRO/user/units-and-locale.html#distance--altitude"
  },"6208": {
    "doc": "Units, Measurement & Locale",
    "title": "Viteza",
    "content": "GPS ground speed is displayed in your locale’s preferred speed unit. | Your Setting | You See | . | Metric | 12 km/h | . | Imperial (US) | 7 mph | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/units-and-locale.html#viteza",
    
    "relUrl": "/ro-rRO/user/units-and-locale.html#viteza"
  },"6209": {
    "doc": "Units, Measurement & Locale",
    "title": "Vânt",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | Your Setting | You See | . | Metric | 18.0 km/h | . | Imperial (US) | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/units-and-locale.html#v%C3%A2nt",
    
    "relUrl": "/ro-rRO/user/units-and-locale.html#vânt"
  },"6210": {
    "doc": "Units, Measurement & Locale",
    "title": "Greutate",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | Your Setting | You See | . | Metric | 1.50 kg | . | Imperial (US) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/units-and-locale.html#greutate",
    
    "relUrl": "/ro-rRO/user/units-and-locale.html#greutate"
  },"6211": {
    "doc": "Units, Measurement & Locale",
    "title": "Rainfall",
    "content": "Rainfall measurements (1-hour and 24-hour totals) are transmitted as mm and converted for display. | Your Setting | You See | . | Metric | 12.0 mm | . | Imperial (US) | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/units-and-locale.html#rainfall",
    
    "relUrl": "/ro-rRO/user/units-and-locale.html#rainfall"
  },"6212": {
    "doc": "Units, Measurement & Locale",
    "title": "Units That Never Change",
    "content": "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 | . | Radiație | µR/h | Standard dosimetry unit | . | GPS coordinates | decimal degrees | Universal geographic standard | . | Humidity, battery, soil moisture | % | Universal | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/units-and-locale.html#units-that-never-change",
    
    "relUrl": "/ro-rRO/user/units-and-locale.html#units-that-never-change"
  },"6213": {
    "doc": "Units, Measurement & Locale",
    "title": "Date & Time",
    "content": "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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/units-and-locale.html#date--time",
    
    "relUrl": "/ro-rRO/user/units-and-locale.html#date--time"
  },"6214": {
    "doc": "Units, Measurement & Locale",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region | Return to Meshtastic — values update immediately | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/ro-rRO/user/units-and-locale.html#changing-your-measurement-system"
  },"6215": {
    "doc": "Units, Measurement & Locale",
    "title": "Related Topics",
    "content": ". | Node Metrics — where temperature, distance, and sensor values are displayed | Telemetry & Sensors — the sensors that produce these measurements | Measurement & Formatting — developer reference for the formatting utilities | Settings — Radio & User — region setting that drives unit selection | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/units-and-locale.html#related-topics",
    
    "relUrl": "/ro-rRO/user/units-and-locale.html#related-topics"
  },"6216": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": " ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/units-and-locale.html",
    
    "relUrl": "/ro-rRO/user/units-and-locale.html"
  },"6217": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/units-and-locale.html#units-measurement--locale",
    
    "relUrl": "/iw-rIL/user/units-and-locale.html#units-measurement--locale"
  },"6218": {
    "doc": "Units, Measurement & Locale",
    "title": "How It Works",
    "content": "Meshtastic radios always transmit data in metric units (meters, °C, m/s, hPa, etc.). When the app receives this data, it converts and displays 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. Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/units-and-locale.html#how-it-works",
    
    "relUrl": "/iw-rIL/user/units-and-locale.html#how-it-works"
  },"6219": {
    "doc": "Units, Measurement & Locale",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/iw-rIL/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"6220": {
    "doc": "Units, Measurement & Locale",
    "title": "Temperature",
    "content": "Temperature values from environment sensors are transmitted as °C and displayed based on your device’s temperature unit preference. | 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. Temperature follows your locale’s temperature preference, independent of the distance system. Locales that mix systems work correctly — a UK phone shows miles for distance but °C for temperature. On Android 14+, the Temperature regional preference (Settings → System → Languages → Regional preferences) overrides the locale default. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/units-and-locale.html#temperature",
    
    "relUrl": "/iw-rIL/user/units-and-locale.html#temperature"
  },"6221": {
    "doc": "Units, Measurement & Locale",
    "title": "Distance & Altitude",
    "content": "Distances between nodes and GPS altitudes are transmitted as meters and automatically scaled and converted. | 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 kilometers 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 | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/units-and-locale.html#distance--altitude",
    
    "relUrl": "/iw-rIL/user/units-and-locale.html#distance--altitude"
  },"6222": {
    "doc": "Units, Measurement & Locale",
    "title": "Speed",
    "content": "GPS ground speed is displayed in your locale’s preferred speed unit. | Your Setting | You See | . | Metric | 12 km/h | . | Imperial (US) | 7 mph | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/units-and-locale.html#speed",
    
    "relUrl": "/iw-rIL/user/units-and-locale.html#speed"
  },"6223": {
    "doc": "Units, Measurement & Locale",
    "title": "Wind",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | Your Setting | You See | . | Metric | 18.0 km/h | . | Imperial (US) | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/units-and-locale.html#wind",
    
    "relUrl": "/iw-rIL/user/units-and-locale.html#wind"
  },"6224": {
    "doc": "Units, Measurement & Locale",
    "title": "Weight",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | Your Setting | You See | . | Metric | 1.50 kg | . | Imperial (US) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/units-and-locale.html#weight",
    
    "relUrl": "/iw-rIL/user/units-and-locale.html#weight"
  },"6225": {
    "doc": "Units, Measurement & Locale",
    "title": "Rainfall",
    "content": "Rainfall measurements (1-hour and 24-hour totals) are transmitted as mm and converted for display. | Your Setting | You See | . | Metric | 12.0 mm | . | Imperial (US) | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/units-and-locale.html#rainfall",
    
    "relUrl": "/iw-rIL/user/units-and-locale.html#rainfall"
  },"6226": {
    "doc": "Units, Measurement & Locale",
    "title": "Units That Never Change",
    "content": "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/h | Standard dosimetry unit | . | GPS coordinates | decimal degrees | Universal geographic standard | . | Humidity, battery, soil moisture | % | Universal | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/units-and-locale.html#units-that-never-change",
    
    "relUrl": "/iw-rIL/user/units-and-locale.html#units-that-never-change"
  },"6227": {
    "doc": "Units, Measurement & Locale",
    "title": "Date & Time",
    "content": "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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/units-and-locale.html#date--time",
    
    "relUrl": "/iw-rIL/user/units-and-locale.html#date--time"
  },"6228": {
    "doc": "Units, Measurement & Locale",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region | Return to Meshtastic — values update immediately | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/iw-rIL/user/units-and-locale.html#changing-your-measurement-system"
  },"6229": {
    "doc": "Units, Measurement & Locale",
    "title": "Related Topics",
    "content": ". | Node Metrics — where temperature, distance, and sensor values are displayed | Telemetry & Sensors — the sensors that produce these measurements | Measurement & Formatting — developer reference for the formatting utilities | Settings — Radio & User — region setting that drives unit selection | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/units-and-locale.html#related-topics",
    
    "relUrl": "/iw-rIL/user/units-and-locale.html#related-topics"
  },"6230": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": " ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/units-and-locale.html",
    
    "relUrl": "/iw-rIL/user/units-and-locale.html"
  },"6231": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/units-and-locale.html#units-measurement--locale",
    
    "relUrl": "/pt-rBR/user/units-and-locale.html#units-measurement--locale"
  },"6232": {
    "doc": "Units, Measurement & Locale",
    "title": "How It Works",
    "content": "Meshtastic radios always transmit data in metric units (meters, °C, m/s, hPa, etc.). When the app receives this data, it converts and displays 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. Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/units-and-locale.html#how-it-works",
    
    "relUrl": "/pt-rBR/user/units-and-locale.html#how-it-works"
  },"6233": {
    "doc": "Units, Measurement & Locale",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/pt-rBR/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"6234": {
    "doc": "Units, Measurement & Locale",
    "title": "Temperatura",
    "content": "Temperature values from environment sensors are transmitted as °C and displayed based on your device’s temperature unit preference. | 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. Temperature follows your locale’s temperature preference, independent of the distance system. Locales that mix systems work correctly — a UK phone shows miles for distance but °C for temperature. On Android 14+, the Temperature regional preference (Settings → System → Languages → Regional preferences) overrides the locale default. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/units-and-locale.html#temperatura",
    
    "relUrl": "/pt-rBR/user/units-and-locale.html#temperatura"
  },"6235": {
    "doc": "Units, Measurement & Locale",
    "title": "Distance & Altitude",
    "content": "Distances between nodes and GPS altitudes are transmitted as meters and automatically scaled and converted. | 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 kilometers 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 | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/units-and-locale.html#distance--altitude",
    
    "relUrl": "/pt-rBR/user/units-and-locale.html#distance--altitude"
  },"6236": {
    "doc": "Units, Measurement & Locale",
    "title": "Velocidade",
    "content": "GPS ground speed is displayed in your locale’s preferred speed unit. | Your Setting | You See | . | Metric | 12 km/h | . | Imperial (US) | 7 mph | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/units-and-locale.html#velocidade",
    
    "relUrl": "/pt-rBR/user/units-and-locale.html#velocidade"
  },"6237": {
    "doc": "Units, Measurement & Locale",
    "title": "Vento",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | Your Setting | You See | . | Metric | 18.0 km/h | . | Imperial (US) | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/units-and-locale.html#vento",
    
    "relUrl": "/pt-rBR/user/units-and-locale.html#vento"
  },"6238": {
    "doc": "Units, Measurement & Locale",
    "title": "Peso",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | Your Setting | You See | . | Metric | 1.50 kg | . | Imperial (US) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/units-and-locale.html#peso",
    
    "relUrl": "/pt-rBR/user/units-and-locale.html#peso"
  },"6239": {
    "doc": "Units, Measurement & Locale",
    "title": "Rainfall",
    "content": "Rainfall measurements (1-hour and 24-hour totals) are transmitted as mm and converted for display. | Your Setting | You See | . | Metric | 12.0 mm | . | Imperial (US) | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/units-and-locale.html#rainfall",
    
    "relUrl": "/pt-rBR/user/units-and-locale.html#rainfall"
  },"6240": {
    "doc": "Units, Measurement & Locale",
    "title": "Units That Never Change",
    "content": "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 | . | Radiação | µR/h | Standard dosimetry unit | . | GPS coordinates | decimal degrees | Universal geographic standard | . | Humidity, battery, soil moisture | % | Universal | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/units-and-locale.html#units-that-never-change",
    
    "relUrl": "/pt-rBR/user/units-and-locale.html#units-that-never-change"
  },"6241": {
    "doc": "Units, Measurement & Locale",
    "title": "Date & Time",
    "content": "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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/units-and-locale.html#date--time",
    
    "relUrl": "/pt-rBR/user/units-and-locale.html#date--time"
  },"6242": {
    "doc": "Units, Measurement & Locale",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region | Return to Meshtastic — values update immediately | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/pt-rBR/user/units-and-locale.html#changing-your-measurement-system"
  },"6243": {
    "doc": "Units, Measurement & Locale",
    "title": "Related Topics",
    "content": ". | Node Metrics — where temperature, distance, and sensor values are displayed | Telemetry & Sensors — the sensors that produce these measurements | Measurement & Formatting — developer reference for the formatting utilities | Settings — Radio & User — region setting that drives unit selection | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/units-and-locale.html#related-topics",
    
    "relUrl": "/pt-rBR/user/units-and-locale.html#related-topics"
  },"6244": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": " ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/units-and-locale.html",
    
    "relUrl": "/pt-rBR/user/units-and-locale.html"
  },"6245": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": "The Meshtastic app automatically displays temperatures, distances, speeds, and times in the units your device is configured to use. If your device’s settings can’t express the units you want, an in-app Units setting overrides them. ",
    "url": "/Meshtastic-Android/main/en/user/units-and-locale.html#units-measurement--locale",
    
    "relUrl": "/en/user/units-and-locale.html#units-measurement--locale"
  },"6246": {
    "doc": "Units, Measurement & Locale",
    "title": "How It Works",
    "content": "Meshtastic radios always transmit data in metric units (meters, °C, m/s, hPa, etc.). When the app receives this data, it converts and displays 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. Units follow your device’s region, not the display language. Plain languages — like English in the app’s own Language setting or Android’s per-app language — keep the region your device is set to. A choice that names a region of its own, like English (Canada), overrides it and brings that region’s units with it. On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature, which keeps following the region. 💡 Tip: By default there is nothing to configure — change your system measurement preferences and every screen in Meshtastic updates automatically. If your device offers no working region or measurement setting (some manufacturer builds don’t), set Settings → Units in the app instead. ",
    "url": "/Meshtastic-Android/main/en/user/units-and-locale.html#how-it-works",
    
    "relUrl": "/en/user/units-and-locale.html#how-it-works"
  },"6247": {
    "doc": "Units, Measurement & Locale",
    "title": "The Radio’s Own Screen Is Separate",
    "content": "Settings → Device configuration → Display → Display units configures the screen on the radio, not the app. The Use 12h clock format and Always point north settings do too — all three apply to the radio’s display only. Temperature on that screen has its own setting, Environment metrics use Fahrenheit, on the radio’s Telemetry module — see the Telemetry module reference on meshtastic.org. If your node list shows miles while the radio’s screen shows kilometers, this is why: the two are set in different places. Changing the radio’s setting never alters what the app displays. See the Display Config guide on meshtastic.org for the device-side options. ",
    "url": "/Meshtastic-Android/main/en/user/units-and-locale.html#the-radios-own-screen-is-separate",
    
    "relUrl": "/en/user/units-and-locale.html#the-radios-own-screen-is-separate"
  },"6248": {
    "doc": "Units, Measurement & Locale",
    "title": "Temperature",
    "content": "Temperature values from environment sensors are transmitted as °C and displayed based on your device’s temperature unit preference. | 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. Temperature follows your locale’s temperature preference, independent of the distance system. Locales that mix systems work correctly — a UK phone shows miles for distance but °C for temperature. On Android 14+, the Temperature regional preference (Settings → System → Languages → Regional preferences) overrides the locale default. ",
    "url": "/Meshtastic-Android/main/en/user/units-and-locale.html#temperature",
    
    "relUrl": "/en/user/units-and-locale.html#temperature"
  },"6249": {
    "doc": "Units, Measurement & Locale",
    "title": "Distance & Altitude",
    "content": "Distances between nodes and GPS altitudes are transmitted as meters and automatically scaled and converted. | 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 kilometers 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 | . ",
    "url": "/Meshtastic-Android/main/en/user/units-and-locale.html#distance--altitude",
    
    "relUrl": "/en/user/units-and-locale.html#distance--altitude"
  },"6250": {
    "doc": "Units, Measurement & Locale",
    "title": "Speed",
    "content": "GPS ground speed is displayed in your locale’s preferred speed unit. | Your Setting | You See | . | Metric | 12 km/h | . | Imperial (US) | 7 mph | . ",
    "url": "/Meshtastic-Android/main/en/user/units-and-locale.html#speed",
    
    "relUrl": "/en/user/units-and-locale.html#speed"
  },"6251": {
    "doc": "Units, Measurement & Locale",
    "title": "Wind",
    "content": "Wind speed, gust and lull are transmitted by the sensor as m/s and converted for display — the app shows the unit weather forecasts use in your region, not the raw sensor unit. | Your Setting | You See | . | Metric | 18.0 km/h | . | Imperial (US) | 11.2 mph | . All three read in the same unit wherever they appear: the Node Detail environment section, the Environment Telemetry log, and the charts. ",
    "url": "/Meshtastic-Android/main/en/user/units-and-locale.html#wind",
    
    "relUrl": "/en/user/units-and-locale.html#wind"
  },"6252": {
    "doc": "Units, Measurement & Locale",
    "title": "Weight",
    "content": "Readings from a connected scale are transmitted in kg and converted for display. | Your Setting | You See | . | Metric | 1.50 kg | . | Imperial (US) | 3.31 lb | . ",
    "url": "/Meshtastic-Android/main/en/user/units-and-locale.html#weight",
    
    "relUrl": "/en/user/units-and-locale.html#weight"
  },"6253": {
    "doc": "Units, Measurement & Locale",
    "title": "Rainfall",
    "content": "Rainfall measurements (1-hour and 24-hour totals) are transmitted as mm and converted for display. | Your Setting | You See | . | Metric | 12.0 mm | . | Imperial (US) | 0.47 in | . ",
    "url": "/Meshtastic-Android/main/en/user/units-and-locale.html#rainfall",
    
    "relUrl": "/en/user/units-and-locale.html#rainfall"
  },"6254": {
    "doc": "Units, Measurement & Locale",
    "title": "Units That Never Change",
    "content": "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/h | Standard dosimetry unit | . | GPS coordinates | decimal degrees | Universal geographic standard | . | Humidity, battery, soil moisture | % | Universal | . ",
    "url": "/Meshtastic-Android/main/en/user/units-and-locale.html#units-that-never-change",
    
    "relUrl": "/en/user/units-and-locale.html#units-that-never-change"
  },"6255": {
    "doc": "Units, Measurement & Locale",
    "title": "Date & Time",
    "content": "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 localized into your device language. ",
    "url": "/Meshtastic-Android/main/en/user/units-and-locale.html#date--time",
    
    "relUrl": "/en/user/units-and-locale.html#date--time"
  },"6256": {
    "doc": "Units, Measurement & Locale",
    "title": "Changing Your Measurement System",
    "content": "By default the app follows your device, and your measurement system (metric vs imperial) is tied to your region setting: . | Open Android Settings → System → Language & Region | Change your Region | Return to Meshtastic — values update immediately | . On Android 16+, the system-wide Measurement system preference overrides the region for distance, speed, and the other measurements — but not for temperature. Temperature is resolved separately, and on Android 14+ you override it on its own under Regional preferences → Temperature. Not every English region is fully metric. English (United Kingdom) uses miles and feet for distance, so the node list shows miles and altitude in feet. For metric distances, set the app’s Units setting to Metric (see Overriding the Units in the App), or choose a fully metric region such as English (Canada), English (Ireland), or English (New Zealand). Some phones do not offer the Regional preferences menu at all and list only English (United States). On those devices, use the app’s Units setting (see Overriding the Units in the App). Overriding the units in the app . Not every device can express every preference — some manufacturer builds ship no regional preferences at all, some offer only one English variant, and UK regions are imperial for distance even if you’d rather read altitude in meters. For those cases the app has its own switch: . | Open Meshtastic Settings → Units | Choose System default, Metric, or Imperial | Every screen updates immediately — no restart needed | . System default follows your phone’s or computer’s region and measurement settings. Forcing Metric or Imperial applies to everything, temperature included (metric → °C, imperial → °F), even where the system’s own regional preferences say otherwise. The setting exists on Android and Desktop alike. ",
    "url": "/Meshtastic-Android/main/en/user/units-and-locale.html#changing-your-measurement-system",
    
    "relUrl": "/en/user/units-and-locale.html#changing-your-measurement-system"
  },"6257": {
    "doc": "Units, Measurement & Locale",
    "title": "Related Topics",
    "content": ". | Node Metrics — where temperature, distance, and sensor values are displayed | Telemetry & Sensors — the sensors that produce these measurements | Measurement & Formatting — developer reference for the formatting utilities | Settings — Radio & User — region setting that drives unit selection | Display Config — units, clock, and compass settings for the radio’s own screen, on meshtastic.org | . ",
    "url": "/Meshtastic-Android/main/en/user/units-and-locale.html#related-topics",
    
    "relUrl": "/en/user/units-and-locale.html#related-topics"
  },"6258": {
    "doc": "Units, Measurement & Locale",
    "title": "Units, Measurement & Locale",
    "content": " ",
    "url": "/Meshtastic-Android/main/en/user/units-and-locale.html",
    
    "relUrl": "/en/user/units-and-locale.html"
  },"6259": {
    "doc": "User Guide",
    "title": "User Guide",
    "content": "Documentation for using the Meshtastic Android and Desktop app. ",
    "url": "/Meshtastic-Android/main/en/user.html",
    
    "relUrl": "/en/user.html"
  },"6260": {
    "doc": "User Guide",
    "title": "What’s New in the Docs",
    "content": "September 2026 — Nodes — Nodes your node has not heard since its LoRa settings changed now carry an orange marker, a Hide unheard nodes filter, and a banner whose Remove action deletes them in bulk. September 2026 — Settings — Radio & User — Lockdown’s debug-port lock is not reversible from the app, Managed Mode locks the whole configuration list, and the preset list is filtered to what your region permits. September 2026 — Local Mesh Discovery — Signal colours are relative to the preset’s demodulation floor rather than fixed thresholds, and a beacon’s broadcast targets always hold at least one row. September 2026 — Nodes — Nodes on firmware 2.8 show signed and verified identity icons in place of the PKI lock, and Signed only and Encrypted only filters join the node list and the map. September 2026 — Map & Waypoints — Offline terrain (hillshade and contours) can be downloaded on Google Play, F-Droid, and Desktop. August 2026 — Local Mesh Discovery — Mesh Beacon advertises the region and preset your radio actually uses, requires a region and a standard modem preset before it will broadcast, and hides invitations to channels your radio already has. August 2026 — Map & Waypoints — Filter the map by node role and by how a node was heard, from a new filter sheet. August 2026 — Map & Waypoints — Every map layer and overlay now has its own opacity slider. ",
    "url": "/Meshtastic-Android/main/en/user.html#whats-new-in-the-docs",
    
    "relUrl": "/en/user.html#whats-new-in-the-docs"
  },"6261": {
    "doc": "Home Screen Widget",
    "title": "Home Screen Widget",
    "content": "On Android, Meshtastic provides a home screen widget that shows live local statistics from your connected radio at a glance — no need to open the app. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/widget.html",
    
    "relUrl": "/sk-rSK/user/widget.html"
  },"6262": {
    "doc": "Home Screen Widget",
    "title": "What It Shows",
    "content": "The widget displays the connected radio’s current local stats: . | A node chip across the top, carrying the radio’s short name in its own colors | Battery — the radio’s battery level, or Powered when running on external power | ChUtil — channel utilization (how busy the LoRa channel is, as a percentage) | AirUtil — airtime utilization (how much of the duty cycle your radio is transmitting) | Traffic — packets transmitted / received, and duplicates seen | Relays — packets relayed and relay cancellations (shown when the radio is relaying) | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Heap — free versus total memory on the radio, drawn as a bar | Nodes — how many nodes are online, out of the total known | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . Tap the widget to open the app, or use its refresh control to request fresh stats. ℹ️ Note: The values reflect the connected radio. If the radio disconnects, the widget replaces the stats with a status line — Disconnected, Connecting, or Device sleeping. It does not keep the last-known numbers on screen. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/widget.html#what-it-shows",
    
    "relUrl": "/sk-rSK/user/widget.html#what-it-shows"
  },"6263": {
    "doc": "Home Screen Widget",
    "title": "Adding the Widget",
    "content": ". | Touch & hold an empty area of your Android home screen. | Tap Widgets. | Drag the Meshtastic widget to your home screen. The app ships one widget, so the picker entry is just the app name. | Resize it as needed — the layout adapts to the available space. | . ℹ️ Note: The widget is Android-only. It is not available on the Desktop or iOS builds. ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/widget.html#adding-the-widget",
    
    "relUrl": "/sk-rSK/user/widget.html#adding-the-widget"
  },"6264": {
    "doc": "Home Screen Widget",
    "title": "Related Topics",
    "content": ". | Node Metrics — the full Signal Quality and Local Stats history inside the app | Connections — connect to a radio so the widget has stats to show | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/sk-rSK/user/widget.html#related-topics",
    
    "relUrl": "/sk-rSK/user/widget.html#related-topics"
  },"6265": {
    "doc": "Home Screen Widget",
    "title": "Home Screen Widget",
    "content": "On Android, Meshtastic provides a home screen widget that shows live local statistics from your connected radio at a glance — no need to open the app. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/widget.html",
    
    "relUrl": "/be-rBY/user/widget.html"
  },"6266": {
    "doc": "Home Screen Widget",
    "title": "What It Shows",
    "content": "The widget displays the connected radio’s current local stats: . | A node chip across the top, carrying the radio’s short name in its own colors | Battery — the radio’s battery level, or Powered when running on external power | ChUtil — channel utilization (how busy the LoRa channel is, as a percentage) | AirUtil — airtime utilization (how much of the duty cycle your radio is transmitting) | Traffic — packets transmitted / received, and duplicates seen | Relays — packets relayed and relay cancellations (shown when the radio is relaying) | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Heap — free versus total memory on the radio, drawn as a bar | Nodes — how many nodes are online, out of the total known | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . Tap the widget to open the app, or use its refresh control to request fresh stats. ℹ️ Note: The values reflect the connected radio. If the radio disconnects, the widget replaces the stats with a status line — Disconnected, Connecting, or Device sleeping. It does not keep the last-known numbers on screen. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/widget.html#what-it-shows",
    
    "relUrl": "/be-rBY/user/widget.html#what-it-shows"
  },"6267": {
    "doc": "Home Screen Widget",
    "title": "Adding the Widget",
    "content": ". | Touch & hold an empty area of your Android home screen. | Tap Widgets. | Drag the Meshtastic widget to your home screen. The app ships one widget, so the picker entry is just the app name. | Resize it as needed — the layout adapts to the available space. | . ℹ️ Note: The widget is Android-only. It is not available on the Desktop or iOS builds. ",
    "url": "/Meshtastic-Android/main/be-rBY/user/widget.html#adding-the-widget",
    
    "relUrl": "/be-rBY/user/widget.html#adding-the-widget"
  },"6268": {
    "doc": "Home Screen Widget",
    "title": "Related Topics",
    "content": ". | Node Metrics — the full Signal Quality and Local Stats history inside the app | Connections — connect to a radio so the widget has stats to show | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/be-rBY/user/widget.html#related-topics",
    
    "relUrl": "/be-rBY/user/widget.html#related-topics"
  },"6269": {
    "doc": "Home Screen Widget",
    "title": "Home Screen Widget",
    "content": "On Android, Meshtastic provides a home screen widget that shows live local statistics from your connected radio at a glance — no need to open the app. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/widget.html",
    
    "relUrl": "/it-rIT/user/widget.html"
  },"6270": {
    "doc": "Home Screen Widget",
    "title": "What It Shows",
    "content": "The widget displays the connected radio’s current local stats: . | A node chip across the top, carrying the radio’s short name in its own colors | Battery — the radio’s battery level, or Powered when running on external power | ChUtil — channel utilization (how busy the LoRa channel is, as a percentage) | AirUtil — airtime utilization (how much of the duty cycle your radio is transmitting) | Traffic — packets transmitted / received, and duplicates seen | Relays — packets relayed and relay cancellations (shown when the radio is relaying) | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Heap — free versus total memory on the radio, drawn as a bar | Nodes — how many nodes are online, out of the total known | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . Tap the widget to open the app, or use its refresh control to request fresh stats. ℹ️ Note: The values reflect the connected radio. If the radio disconnects, the widget replaces the stats with a status line — Disconnected, Connecting, or Device sleeping. It does not keep the last-known numbers on screen. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/widget.html#what-it-shows",
    
    "relUrl": "/it-rIT/user/widget.html#what-it-shows"
  },"6271": {
    "doc": "Home Screen Widget",
    "title": "Adding the Widget",
    "content": ". | Touch & hold an empty area of your Android home screen. | Tap Widgets. | Drag the Meshtastic widget to your home screen. The app ships one widget, so the picker entry is just the app name. | Resize it as needed — the layout adapts to the available space. | . ℹ️ Note: The widget is Android-only. It is not available on the Desktop or iOS builds. ",
    "url": "/Meshtastic-Android/main/it-rIT/user/widget.html#adding-the-widget",
    
    "relUrl": "/it-rIT/user/widget.html#adding-the-widget"
  },"6272": {
    "doc": "Home Screen Widget",
    "title": "Related Topics",
    "content": ". | Node Metrics — the full Signal Quality and Local Stats history inside the app | Connections — connect to a radio so the widget has stats to show | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/it-rIT/user/widget.html#related-topics",
    
    "relUrl": "/it-rIT/user/widget.html#related-topics"
  },"6273": {
    "doc": "Home Screen Widget",
    "title": "Home Screen Widget",
    "content": "On Android, Meshtastic provides a home screen widget that shows live local statistics from your connected radio at a glance — no need to open the app. ",
    "url": "/Meshtastic-Android/main/es-rES/user/widget.html",
    
    "relUrl": "/es-rES/user/widget.html"
  },"6274": {
    "doc": "Home Screen Widget",
    "title": "What It Shows",
    "content": "The widget displays the connected radio’s current local stats: . | A node chip across the top, carrying the radio’s short name in its own colors | Battery — the radio’s battery level, or Powered when running on external power | ChUtil — channel utilization (how busy the LoRa channel is, as a percentage) | AirUtil — airtime utilization (how much of the duty cycle your radio is transmitting) | Traffic — packets transmitted / received, and duplicates seen | Relays — packets relayed and relay cancellations (shown when the radio is relaying) | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Heap — free versus total memory on the radio, drawn as a bar | Nodes — how many nodes are online, out of the total known | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . Tap the widget to open the app, or use its refresh control to request fresh stats. ℹ️ Note: The values reflect the connected radio. If the radio disconnects, the widget replaces the stats with a status line — Disconnected, Connecting, or Device sleeping. It does not keep the last-known numbers on screen. ",
    "url": "/Meshtastic-Android/main/es-rES/user/widget.html#what-it-shows",
    
    "relUrl": "/es-rES/user/widget.html#what-it-shows"
  },"6275": {
    "doc": "Home Screen Widget",
    "title": "Adding the Widget",
    "content": ". | Touch & hold an empty area of your Android home screen. | Tap Widgets. | Drag the Meshtastic widget to your home screen. The app ships one widget, so the picker entry is just the app name. | Resize it as needed — the layout adapts to the available space. | . ℹ️ Note: The widget is Android-only. It is not available on the Desktop or iOS builds. ",
    "url": "/Meshtastic-Android/main/es-rES/user/widget.html#adding-the-widget",
    
    "relUrl": "/es-rES/user/widget.html#adding-the-widget"
  },"6276": {
    "doc": "Home Screen Widget",
    "title": "Related Topics",
    "content": ". | Node Metrics — the full Signal Quality and Local Stats history inside the app | Connections — connect to a radio so the widget has stats to show | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/es-rES/user/widget.html#related-topics",
    
    "relUrl": "/es-rES/user/widget.html#related-topics"
  },"6277": {
    "doc": "Home Screen Widget",
    "title": "Home Screen Widget",
    "content": "On Android, Meshtastic provides a home screen widget that shows live local statistics from your connected radio at a glance — no need to open the app. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/widget.html",
    
    "relUrl": "/sl-rSI/user/widget.html"
  },"6278": {
    "doc": "Home Screen Widget",
    "title": "What It Shows",
    "content": "The widget displays the connected radio’s current local stats: . | A node chip across the top, carrying the radio’s short name in its own colors | Battery — the radio’s battery level, or Powered when running on external power | ChUtil — channel utilization (how busy the LoRa channel is, as a percentage) | AirUtil — airtime utilization (how much of the duty cycle your radio is transmitting) | Traffic — packets transmitted / received, and duplicates seen | Relays — packets relayed and relay cancellations (shown when the radio is relaying) | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Heap — free versus total memory on the radio, drawn as a bar | Nodes — how many nodes are online, out of the total known | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . Tap the widget to open the app, or use its refresh control to request fresh stats. ℹ️ Note: The values reflect the connected radio. If the radio disconnects, the widget replaces the stats with a status line — Disconnected, Connecting, or Device sleeping. It does not keep the last-known numbers on screen. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/widget.html#what-it-shows",
    
    "relUrl": "/sl-rSI/user/widget.html#what-it-shows"
  },"6279": {
    "doc": "Home Screen Widget",
    "title": "Adding the Widget",
    "content": ". | Touch & hold an empty area of your Android home screen. | Tap Widgets. | Drag the Meshtastic widget to your home screen. The app ships one widget, so the picker entry is just the app name. | Resize it as needed — the layout adapts to the available space. | . ℹ️ Note: The widget is Android-only. It is not available on the Desktop or iOS builds. ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/widget.html#adding-the-widget",
    
    "relUrl": "/sl-rSI/user/widget.html#adding-the-widget"
  },"6280": {
    "doc": "Home Screen Widget",
    "title": "Related Topics",
    "content": ". | Node Metrics — the full Signal Quality and Local Stats history inside the app | Connections — connect to a radio so the widget has stats to show | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/sl-rSI/user/widget.html#related-topics",
    
    "relUrl": "/sl-rSI/user/widget.html#related-topics"
  },"6281": {
    "doc": "Home Screen Widget",
    "title": "Home Screen Widget",
    "content": "On Android, Meshtastic provides a home screen widget that shows live local statistics from your connected radio at a glance — no need to open the app. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/widget.html",
    
    "relUrl": "/no-rNO/user/widget.html"
  },"6282": {
    "doc": "Home Screen Widget",
    "title": "What It Shows",
    "content": "The widget displays the connected radio’s current local stats: . | A node chip across the top, carrying the radio’s short name in its own colors | Battery — the radio’s battery level, or Powered when running on external power | ChUtil — channel utilization (how busy the LoRa channel is, as a percentage) | AirUtil — airtime utilization (how much of the duty cycle your radio is transmitting) | Traffic — packets transmitted / received, and duplicates seen | Relays — packets relayed and relay cancellations (shown when the radio is relaying) | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Heap — free versus total memory on the radio, drawn as a bar | Nodes — how many nodes are online, out of the total known | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . Tap the widget to open the app, or use its refresh control to request fresh stats. ℹ️ Note: The values reflect the connected radio. If the radio disconnects, the widget replaces the stats with a status line — Disconnected, Connecting, or Device sleeping. It does not keep the last-known numbers on screen. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/widget.html#what-it-shows",
    
    "relUrl": "/no-rNO/user/widget.html#what-it-shows"
  },"6283": {
    "doc": "Home Screen Widget",
    "title": "Adding the Widget",
    "content": ". | Touch & hold an empty area of your Android home screen. | Tap Widgets. | Drag the Meshtastic widget to your home screen. The app ships one widget, so the picker entry is just the app name. | Resize it as needed — the layout adapts to the available space. | . ℹ️ Note: The widget is Android-only. It is not available on the Desktop or iOS builds. ",
    "url": "/Meshtastic-Android/main/no-rNO/user/widget.html#adding-the-widget",
    
    "relUrl": "/no-rNO/user/widget.html#adding-the-widget"
  },"6284": {
    "doc": "Home Screen Widget",
    "title": "Related Topics",
    "content": ". | Node Metrics — the full Signal Quality and Local Stats history inside the app | Connections — connect to a radio so the widget has stats to show | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/no-rNO/user/widget.html#related-topics",
    
    "relUrl": "/no-rNO/user/widget.html#related-topics"
  },"6285": {
    "doc": "Home Screen Widget",
    "title": "Home Screen Widget",
    "content": "On Android, Meshtastic provides a home screen widget that shows live local statistics from your connected radio at a glance — no need to open the app. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/widget.html",
    
    "relUrl": "/hu-rHU/user/widget.html"
  },"6286": {
    "doc": "Home Screen Widget",
    "title": "What It Shows",
    "content": "The widget displays the connected radio’s current local stats: . | A node chip across the top, carrying the radio’s short name in its own colors | Battery — the radio’s battery level, or Powered when running on external power | ChUtil — channel utilization (how busy the LoRa channel is, as a percentage) | AirUtil — airtime utilization (how much of the duty cycle your radio is transmitting) | Traffic — packets transmitted / received, and duplicates seen | Relays — packets relayed and relay cancellations (shown when the radio is relaying) | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Heap — free versus total memory on the radio, drawn as a bar | Nodes — how many nodes are online, out of the total known | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . Tap the widget to open the app, or use its refresh control to request fresh stats. ℹ️ Note: The values reflect the connected radio. If the radio disconnects, the widget replaces the stats with a status line — Disconnected, Connecting, or Device sleeping. It does not keep the last-known numbers on screen. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/widget.html#what-it-shows",
    
    "relUrl": "/hu-rHU/user/widget.html#what-it-shows"
  },"6287": {
    "doc": "Home Screen Widget",
    "title": "Adding the Widget",
    "content": ". | Touch & hold an empty area of your Android home screen. | Tap Widgets. | Drag the Meshtastic widget to your home screen. The app ships one widget, so the picker entry is just the app name. | Resize it as needed — the layout adapts to the available space. | . ℹ️ Note: The widget is Android-only. It is not available on the Desktop or iOS builds. ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/widget.html#adding-the-widget",
    
    "relUrl": "/hu-rHU/user/widget.html#adding-the-widget"
  },"6288": {
    "doc": "Home Screen Widget",
    "title": "Related Topics",
    "content": ". | Node Metrics — the full Signal Quality and Local Stats history inside the app | Connections — connect to a radio so the widget has stats to show | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/hu-rHU/user/widget.html#related-topics",
    
    "relUrl": "/hu-rHU/user/widget.html#related-topics"
  },"6289": {
    "doc": "Виджет на главный экран",
    "title": "Виджет на главный экран",
    "content": "На Android, Meshtastic предоставляет виджет главного экрана, который показывает статистику по живым локальным каналам с подключенного устройства без необходимости открывать приложение. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/widget.html",
    
    "relUrl": "/ru-rRU/user/widget.html"
  },"6290": {
    "doc": "Виджет на главный экран",
    "title": "Что он покажет",
    "content": "Виджет показывает текущую локальную статистику подключённого радиоустройства: . | A node chip across the top, carrying the radio’s short name in its own colors | Батарея — уровень заряда батареи радиоустройства или Питание от сети, когда работает от внешнего источника | ChUtil — использование канала (насколько занят канал LoRa, в процентах) | AirUtil — использование времени передачи (сколько рабочих циклов передаёт вашего радиоустройство) | Трафик — пакеты, переданные / полученные, и дубликаты | Relays — пересылаемые пакеты и отмены пересылки (показаны, когда радио действует как ретранслятор) | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Heap — free versus total memory on the radio, drawn as a bar | Nodes — how many nodes are online, out of the total known | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . Нажми на виджет, чтобы открыть приложение, или используй его кнопку обновления для запроса свежей статистики. ℹ️ Note: The values reflect the connected radio. If the radio disconnects, the widget replaces the stats with a status line — Disconnected, Connecting, or Device sleeping. It does not keep the last-known numbers on screen. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/widget.html#%D1%87%D1%82%D0%BE-%D0%BE%D0%BD-%D0%BF%D0%BE%D0%BA%D0%B0%D0%B6%D0%B5%D1%82",
    
    "relUrl": "/ru-rRU/user/widget.html#что-он-покажет"
  },"6291": {
    "doc": "Виджет на главный экран",
    "title": "Добавление виджета",
    "content": ". | Touch & hold an empty area of your Android home screen. | Нажми Виджет. | Drag the Meshtastic widget to your home screen. The app ships one widget, so the picker entry is just the app name. | Изменение размера по мере необходимости — макет адаптируется к доступному пространству. | . ℹ️ Note: The widget is Android-only. Он недоступен для ПК или сборках для iOS. ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/widget.html#%D0%B4%D0%BE%D0%B1%D0%B0%D0%B2%D0%BB%D0%B5%D0%BD%D0%B8%D0%B5-%D0%B2%D0%B8%D0%B4%D0%B6%D0%B5%D1%82%D0%B0",
    
    "relUrl": "/ru-rRU/user/widget.html#добавление-виджета"
  },"6292": {
    "doc": "Виджет на главный экран",
    "title": "Связанные темы",
    "content": ". | Метрики нод — полная статистика сигнала и локальная статистика внутри приложения | Подключения — подключиться к радиоустройству, чтобы виджет показывал статистику | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/ru-rRU/user/widget.html#%D1%81%D0%B2%D1%8F%D0%B7%D0%B0%D0%BD%D0%BD%D1%8B%D0%B5-%D1%82%D0%B5%D0%BC%D1%8B",
    
    "relUrl": "/ru-rRU/user/widget.html#связанные-темы"
  },"6293": {
    "doc": "Widget na domovské obrazovce",
    "title": "Widget na domovské obrazovce",
    "content": "V systému Android nabízí Meshtastic widget na domovskou obrazovku, který na první pohled zobrazuje aktuální místní statistiky připojeného rádia – bez nutnosti otevírat aplikaci. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/widget.html",
    
    "relUrl": "/cs-rCZ/user/widget.html"
  },"6294": {
    "doc": "Widget na domovské obrazovce",
    "title": "Co zobrazuje",
    "content": "Widget zobrazuje aktuální místní statistiky připojeného rádia: . | Nahoře je štítek uzlu s krátkým názvem rádia v jeho vlastních barvách | Baterie – úroveň nabití baterie rádia, nebo Napájeno při napájení z externího zdroje | ChUtil — využití kanálu (jak je kanál LoRa vytížený, v procentech) | AirUtil — využití vysílacího času (jakou část povoleného vysílacího cyklu rádio využívá k vysílání) | Provoz – pakety odeslané / přijaté a zaznamenané duplikáty | Přeposláno – přeposlané pakety a zrušení přeposílání (zobrazuje se, když rádio přeposílá pakety) | Diagnostiky – společný řádek s údaji Šum (úroveň okolního šumu v dBm), Poškozené (přijaté poškozené pakety) a Zahozené (pakety, které rádio zahodilo). Poškozené a zahozené pakety se zobrazí až při hodnotě vyšší než nula, takže u rádia bez provozu se může zobrazovat pouze hodnota šumu | Halda — volná a celková paměť rádia, znázorněná pomocí pruhu | Uzly — počet uzlů online z celkového počtu známých uzlů | Doba provozu — doba provozu rádia od posledního restartu, zobrazená vedle položky Uzly | Aktualizováno – čas poslední aktualizace statistik, zobrazený v dolní části widgetu | . Klepnutím na widget otevřete aplikaci nebo pomocí tlačítka obnovení vyžádejte aktuální statistiky. ℹ️ Poznámka: Hodnoty se vztahují k připojenému rádiu. Pokud se rádio odpojí, widget nahradí statistiky stavovým řádkem – Odpojeno, Připojování nebo Zařízení spí. Nezobrazuje poslední známé hodnoty. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/widget.html#co-zobrazuje",
    
    "relUrl": "/cs-rCZ/user/widget.html#co-zobrazuje"
  },"6295": {
    "doc": "Widget na domovské obrazovce",
    "title": "Přidání widgetu",
    "content": ". | Dotkněte se prázdného místa na domovské obrazovce Androidu a podržte jej. | Klepněte na položku Widgety. | Přetáhněte widget Meshtastic na domovskou obrazovku. Aplikace obsahuje jeden widget, takže v nabídce widgetů se zobrazuje pouze název aplikace. | Podle potřeby změňte jeho velikost – rozložení se přizpůsobí dostupnému prostoru. | . ℹ️ Poznámka: Widget je k dispozici pouze pro Android. Není k dispozici ve verzích pro Desktop ani iOS. ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/widget.html#p%C5%99id%C3%A1n%C3%AD-widgetu",
    
    "relUrl": "/cs-rCZ/user/widget.html#přidání-widgetu"
  },"6296": {
    "doc": "Widget na domovské obrazovce",
    "title": "Související témata",
    "content": ". | Metriky uzlu — kompletní historie kvality signálu a místních statistik přímo v aplikaci | Připojení — připojte se k rádiu, aby widget mohl zobrazovat statistiky | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/cs-rCZ/user/widget.html#souvisej%C3%ADc%C3%AD-t%C3%A9mata",
    
    "relUrl": "/cs-rCZ/user/widget.html#související-témata"
  },"6297": {
    "doc": "Home Screen Widget",
    "title": "Home Screen Widget",
    "content": "On Android, Meshtastic provides a home screen widget that shows live local statistics from your connected radio at a glance — no need to open the app. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/widget.html",
    
    "relUrl": "/bg-rBG/user/widget.html"
  },"6298": {
    "doc": "Home Screen Widget",
    "title": "What It Shows",
    "content": "The widget displays the connected radio’s current local stats: . | A node chip across the top, carrying the radio’s short name in its own colors | Battery — the radio’s battery level, or Powered when running on external power | ChUtil — channel utilization (how busy the LoRa channel is, as a percentage) | AirUtil — airtime utilization (how much of the duty cycle your radio is transmitting) | Traffic — packets transmitted / received, and duplicates seen | Relays — packets relayed and relay cancellations (shown when the radio is relaying) | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Heap — free versus total memory on the radio, drawn as a bar | Nodes — how many nodes are online, out of the total known | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . Tap the widget to open the app, or use its refresh control to request fresh stats. ℹ️ Note: The values reflect the connected radio. If the radio disconnects, the widget replaces the stats with a status line — Disconnected, Connecting, or Device sleeping. It does not keep the last-known numbers on screen. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/widget.html#what-it-shows",
    
    "relUrl": "/bg-rBG/user/widget.html#what-it-shows"
  },"6299": {
    "doc": "Home Screen Widget",
    "title": "Adding the Widget",
    "content": ". | Touch & hold an empty area of your Android home screen. | Tap Widgets. | Drag the Meshtastic widget to your home screen. The app ships one widget, so the picker entry is just the app name. | Resize it as needed — the layout adapts to the available space. | . ℹ️ Note: The widget is Android-only. It is not available on the Desktop or iOS builds. ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/widget.html#adding-the-widget",
    
    "relUrl": "/bg-rBG/user/widget.html#adding-the-widget"
  },"6300": {
    "doc": "Home Screen Widget",
    "title": "Related Topics",
    "content": ". | Node Metrics — the full Signal Quality and Local Stats history inside the app | Connections — connect to a radio so the widget has stats to show | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/bg-rBG/user/widget.html#related-topics",
    
    "relUrl": "/bg-rBG/user/widget.html#related-topics"
  },"6301": {
    "doc": "Home Screen Widget",
    "title": "Home Screen Widget",
    "content": "On Android, Meshtastic provides a home screen widget that shows live local statistics from your connected radio at a glance — no need to open the app. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/widget.html",
    
    "relUrl": "/ga-rIE/user/widget.html"
  },"6302": {
    "doc": "Home Screen Widget",
    "title": "What It Shows",
    "content": "The widget displays the connected radio’s current local stats: . | A node chip across the top, carrying the radio’s short name in its own colors | Battery — the radio’s battery level, or Powered when running on external power | ChUtil — channel utilization (how busy the LoRa channel is, as a percentage) | AirUtil — airtime utilization (how much of the duty cycle your radio is transmitting) | Traffic — packets transmitted / received, and duplicates seen | Relays — packets relayed and relay cancellations (shown when the radio is relaying) | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Heap — free versus total memory on the radio, drawn as a bar | Nodes — how many nodes are online, out of the total known | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . Tap the widget to open the app, or use its refresh control to request fresh stats. ℹ️ Note: The values reflect the connected radio. If the radio disconnects, the widget replaces the stats with a status line — Disconnected, Connecting, or Device sleeping. It does not keep the last-known numbers on screen. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/widget.html#what-it-shows",
    
    "relUrl": "/ga-rIE/user/widget.html#what-it-shows"
  },"6303": {
    "doc": "Home Screen Widget",
    "title": "Adding the Widget",
    "content": ". | Touch & hold an empty area of your Android home screen. | Tap Widgets. | Drag the Meshtastic widget to your home screen. The app ships one widget, so the picker entry is just the app name. | Resize it as needed — the layout adapts to the available space. | . ℹ️ Note: The widget is Android-only. It is not available on the Desktop or iOS builds. ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/widget.html#adding-the-widget",
    
    "relUrl": "/ga-rIE/user/widget.html#adding-the-widget"
  },"6304": {
    "doc": "Home Screen Widget",
    "title": "Related Topics",
    "content": ". | Node Metrics — the full Signal Quality and Local Stats history inside the app | Connections — connect to a radio so the widget has stats to show | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/ga-rIE/user/widget.html#related-topics",
    
    "relUrl": "/ga-rIE/user/widget.html#related-topics"
  },"6305": {
    "doc": "Home Screen Widget",
    "title": "Home Screen Widget",
    "content": "On Android, Meshtastic provides a home screen widget that shows live local statistics from your connected radio at a glance — no need to open the app. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/widget.html",
    
    "relUrl": "/fr-rCA/user/widget.html"
  },"6306": {
    "doc": "Home Screen Widget",
    "title": "What It Shows",
    "content": "The widget displays the connected radio’s current local stats: . | A node chip across the top, carrying the radio’s short name in its own colors | Battery — the radio’s battery level, or Powered when running on external power | ChUtil — channel utilization (how busy the LoRa channel is, as a percentage) | AirUtil — airtime utilization (how much of the duty cycle your radio is transmitting) | Traffic — packets transmitted / received, and duplicates seen | Relays — packets relayed and relay cancellations (shown when the radio is relaying) | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Heap — free versus total memory on the radio, drawn as a bar | Nodes — how many nodes are online, out of the total known | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . Tap the widget to open the app, or use its refresh control to request fresh stats. ℹ️ Note: The values reflect the connected radio. If the radio disconnects, the widget replaces the stats with a status line — Disconnected, Connecting, or Device sleeping. It does not keep the last-known numbers on screen. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/widget.html#what-it-shows",
    
    "relUrl": "/fr-rCA/user/widget.html#what-it-shows"
  },"6307": {
    "doc": "Home Screen Widget",
    "title": "Adding the Widget",
    "content": ". | Touch & hold an empty area of your Android home screen. | Tap Widgets. | Drag the Meshtastic widget to your home screen. The app ships one widget, so the picker entry is just the app name. | Resize it as needed — the layout adapts to the available space. | . ℹ️ Note: The widget is Android-only. It is not available on the Desktop or iOS builds. ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/widget.html#adding-the-widget",
    
    "relUrl": "/fr-rCA/user/widget.html#adding-the-widget"
  },"6308": {
    "doc": "Home Screen Widget",
    "title": "Related Topics",
    "content": ". | Node Metrics — the full Signal Quality and Local Stats history inside the app | Connections — connect to a radio so the widget has stats to show | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/fr-rCA/user/widget.html#related-topics",
    
    "relUrl": "/fr-rCA/user/widget.html#related-topics"
  },"6309": {
    "doc": "Home Screen Widget",
    "title": "Home Screen Widget",
    "content": "On Android, Meshtastic provides a home screen widget that shows live local statistics from your connected radio at a glance — no need to open the app. ",
    "url": "/Meshtastic-Android/main/srp/user/widget.html",
    
    "relUrl": "/srp/user/widget.html"
  },"6310": {
    "doc": "Home Screen Widget",
    "title": "What It Shows",
    "content": "The widget displays the connected radio’s current local stats: . | A node chip across the top, carrying the radio’s short name in its own colors | Battery — the radio’s battery level, or Powered when running on external power | ChUtil — channel utilization (how busy the LoRa channel is, as a percentage) | AirUtil — airtime utilization (how much of the duty cycle your radio is transmitting) | Traffic — packets transmitted / received, and duplicates seen | Relays — packets relayed and relay cancellations (shown when the radio is relaying) | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Heap — free versus total memory on the radio, drawn as a bar | Nodes — how many nodes are online, out of the total known | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . Tap the widget to open the app, or use its refresh control to request fresh stats. ℹ️ Note: The values reflect the connected radio. If the radio disconnects, the widget replaces the stats with a status line — Disconnected, Connecting, or Device sleeping. It does not keep the last-known numbers on screen. ",
    "url": "/Meshtastic-Android/main/srp/user/widget.html#what-it-shows",
    
    "relUrl": "/srp/user/widget.html#what-it-shows"
  },"6311": {
    "doc": "Home Screen Widget",
    "title": "Adding the Widget",
    "content": ". | Touch & hold an empty area of your Android home screen. | Tap Widgets. | Drag the Meshtastic widget to your home screen. The app ships one widget, so the picker entry is just the app name. | Resize it as needed — the layout adapts to the available space. | . ℹ️ Note: The widget is Android-only. It is not available on the Desktop or iOS builds. ",
    "url": "/Meshtastic-Android/main/srp/user/widget.html#adding-the-widget",
    
    "relUrl": "/srp/user/widget.html#adding-the-widget"
  },"6312": {
    "doc": "Home Screen Widget",
    "title": "Related Topics",
    "content": ". | Node Metrics — the full Signal Quality and Local Stats history inside the app | Connections — connect to a radio so the widget has stats to show | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/srp/user/widget.html#related-topics",
    
    "relUrl": "/srp/user/widget.html#related-topics"
  },"6313": {
    "doc": "Home Screen Widget",
    "title": "Home Screen Widget",
    "content": "On Android, Meshtastic provides a home screen widget that shows live local statistics from your connected radio at a glance — no need to open the app. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/widget.html",
    
    "relUrl": "/ca-rES/user/widget.html"
  },"6314": {
    "doc": "Home Screen Widget",
    "title": "What It Shows",
    "content": "The widget displays the connected radio’s current local stats: . | A node chip across the top, carrying the radio’s short name in its own colors | Battery — the radio’s battery level, or Powered when running on external power | ChUtil — channel utilization (how busy the LoRa channel is, as a percentage) | AirUtil — airtime utilization (how much of the duty cycle your radio is transmitting) | Traffic — packets transmitted / received, and duplicates seen | Relays — packets relayed and relay cancellations (shown when the radio is relaying) | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Heap — free versus total memory on the radio, drawn as a bar | Nodes — how many nodes are online, out of the total known | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . Tap the widget to open the app, or use its refresh control to request fresh stats. ℹ️ Note: The values reflect the connected radio. If the radio disconnects, the widget replaces the stats with a status line — Disconnected, Connecting, or Device sleeping. It does not keep the last-known numbers on screen. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/widget.html#what-it-shows",
    
    "relUrl": "/ca-rES/user/widget.html#what-it-shows"
  },"6315": {
    "doc": "Home Screen Widget",
    "title": "Adding the Widget",
    "content": ". | Touch & hold an empty area of your Android home screen. | Tap Widgets. | Drag the Meshtastic widget to your home screen. The app ships one widget, so the picker entry is just the app name. | Resize it as needed — the layout adapts to the available space. | . ℹ️ Note: The widget is Android-only. It is not available on the Desktop or iOS builds. ",
    "url": "/Meshtastic-Android/main/ca-rES/user/widget.html#adding-the-widget",
    
    "relUrl": "/ca-rES/user/widget.html#adding-the-widget"
  },"6316": {
    "doc": "Home Screen Widget",
    "title": "Related Topics",
    "content": ". | Node Metrics — the full Signal Quality and Local Stats history inside the app | Connections — connect to a radio so the widget has stats to show | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/ca-rES/user/widget.html#related-topics",
    
    "relUrl": "/ca-rES/user/widget.html#related-topics"
  },"6317": {
    "doc": "Home Screen Widget",
    "title": "Home Screen Widget",
    "content": "On Android, Meshtastic provides a home screen widget that shows live local statistics from your connected radio at a glance — no need to open the app. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/widget.html",
    
    "relUrl": "/ko-rKR/user/widget.html"
  },"6318": {
    "doc": "Home Screen Widget",
    "title": "What It Shows",
    "content": "The widget displays the connected radio’s current local stats: . | A node chip across the top, carrying the radio’s short name in its own colors | Battery — the radio’s battery level, or Powered when running on external power | ChUtil — channel utilization (how busy the LoRa channel is, as a percentage) | AirUtil — airtime utilization (how much of the duty cycle your radio is transmitting) | Traffic — packets transmitted / received, and duplicates seen | Relays — packets relayed and relay cancellations (shown when the radio is relaying) | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Heap — free versus total memory on the radio, drawn as a bar | Nodes — how many nodes are online, out of the total known | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . Tap the widget to open the app, or use its refresh control to request fresh stats. ℹ️ Note: The values reflect the connected radio. If the radio disconnects, the widget replaces the stats with a status line — Disconnected, Connecting, or Device sleeping. It does not keep the last-known numbers on screen. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/widget.html#what-it-shows",
    
    "relUrl": "/ko-rKR/user/widget.html#what-it-shows"
  },"6319": {
    "doc": "Home Screen Widget",
    "title": "Adding the Widget",
    "content": ". | Touch & hold an empty area of your Android home screen. | Tap Widgets. | Drag the Meshtastic widget to your home screen. The app ships one widget, so the picker entry is just the app name. | Resize it as needed — the layout adapts to the available space. | . ℹ️ Note: The widget is Android-only. It is not available on the Desktop or iOS builds. ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/widget.html#adding-the-widget",
    
    "relUrl": "/ko-rKR/user/widget.html#adding-the-widget"
  },"6320": {
    "doc": "Home Screen Widget",
    "title": "Related Topics",
    "content": ". | Node Metrics — the full Signal Quality and Local Stats history inside the app | Connections — connect to a radio so the widget has stats to show | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/ko-rKR/user/widget.html#related-topics",
    
    "relUrl": "/ko-rKR/user/widget.html#related-topics"
  },"6321": {
    "doc": "Home Screen Widget",
    "title": "Home Screen Widget",
    "content": "On Android, Meshtastic provides a home screen widget that shows live local statistics from your connected radio at a glance — no need to open the app. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/widget.html",
    
    "relUrl": "/sv-rSE/user/widget.html"
  },"6322": {
    "doc": "Home Screen Widget",
    "title": "What It Shows",
    "content": "The widget displays the connected radio’s current local stats: . | A node chip across the top, carrying the radio’s short name in its own colors | Battery — the radio’s battery level, or Powered when running on external power | ChUtil — channel utilization (how busy the LoRa channel is, as a percentage) | AirUtil — airtime utilization (how much of the duty cycle your radio is transmitting) | Traffic — packets transmitted / received, and duplicates seen | Relays — packets relayed and relay cancellations (shown when the radio is relaying) | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Heap — free versus total memory on the radio, drawn as a bar | Nodes — how many nodes are online, out of the total known | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . Tap the widget to open the app, or use its refresh control to request fresh stats. ℹ️ Note: The values reflect the connected radio. If the radio disconnects, the widget replaces the stats with a status line — Disconnected, Connecting, or Device sleeping. It does not keep the last-known numbers on screen. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/widget.html#what-it-shows",
    
    "relUrl": "/sv-rSE/user/widget.html#what-it-shows"
  },"6323": {
    "doc": "Home Screen Widget",
    "title": "Adding the Widget",
    "content": ". | Touch & hold an empty area of your Android home screen. | Tap Widgets. | Drag the Meshtastic widget to your home screen. The app ships one widget, so the picker entry is just the app name. | Resize it as needed — the layout adapts to the available space. | . ℹ️ Note: The widget is Android-only. It is not available on the Desktop or iOS builds. ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/widget.html#adding-the-widget",
    
    "relUrl": "/sv-rSE/user/widget.html#adding-the-widget"
  },"6324": {
    "doc": "Home Screen Widget",
    "title": "Related Topics",
    "content": ". | Node Metrics — the full Signal Quality and Local Stats history inside the app | Connections — connect to a radio so the widget has stats to show | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/sv-rSE/user/widget.html#related-topics",
    
    "relUrl": "/sv-rSE/user/widget.html#related-topics"
  },"6325": {
    "doc": "Home Screen Widget",
    "title": "Home Screen Widget",
    "content": "On Android, Meshtastic provides a home screen widget that shows live local statistics from your connected radio at a glance — no need to open the app. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/widget.html",
    
    "relUrl": "/ht-rHT/user/widget.html"
  },"6326": {
    "doc": "Home Screen Widget",
    "title": "What It Shows",
    "content": "The widget displays the connected radio’s current local stats: . | A node chip across the top, carrying the radio’s short name in its own colors | Battery — the radio’s battery level, or Powered when running on external power | ChUtil — channel utilization (how busy the LoRa channel is, as a percentage) | AirUtil — airtime utilization (how much of the duty cycle your radio is transmitting) | Traffic — packets transmitted / received, and duplicates seen | Relays — packets relayed and relay cancellations (shown when the radio is relaying) | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Heap — free versus total memory on the radio, drawn as a bar | Nodes — how many nodes are online, out of the total known | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . Tap the widget to open the app, or use its refresh control to request fresh stats. ℹ️ Note: The values reflect the connected radio. If the radio disconnects, the widget replaces the stats with a status line — Disconnected, Connecting, or Device sleeping. It does not keep the last-known numbers on screen. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/widget.html#what-it-shows",
    
    "relUrl": "/ht-rHT/user/widget.html#what-it-shows"
  },"6327": {
    "doc": "Home Screen Widget",
    "title": "Adding the Widget",
    "content": ". | Touch & hold an empty area of your Android home screen. | Tap Widgets. | Drag the Meshtastic widget to your home screen. The app ships one widget, so the picker entry is just the app name. | Resize it as needed — the layout adapts to the available space. | . ℹ️ Note: The widget is Android-only. It is not available on the Desktop or iOS builds. ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/widget.html#adding-the-widget",
    
    "relUrl": "/ht-rHT/user/widget.html#adding-the-widget"
  },"6328": {
    "doc": "Home Screen Widget",
    "title": "Related Topics",
    "content": ". | Node Metrics — the full Signal Quality and Local Stats history inside the app | Connections — connect to a radio so the widget has stats to show | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/ht-rHT/user/widget.html#related-topics",
    
    "relUrl": "/ht-rHT/user/widget.html#related-topics"
  },"6329": {
    "doc": "Home Screen Widget",
    "title": "Home Screen Widget",
    "content": "On Android, Meshtastic provides a home screen widget that shows live local statistics from your connected radio at a glance — no need to open the app. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/widget.html",
    
    "relUrl": "/sr-rLatn/user/widget.html"
  },"6330": {
    "doc": "Home Screen Widget",
    "title": "What It Shows",
    "content": "The widget displays the connected radio’s current local stats: . | A node chip across the top, carrying the radio’s short name in its own colors | Battery — the radio’s battery level, or Powered when running on external power | ChUtil — channel utilization (how busy the LoRa channel is, as a percentage) | AirUtil — airtime utilization (how much of the duty cycle your radio is transmitting) | Traffic — packets transmitted / received, and duplicates seen | Relays — packets relayed and relay cancellations (shown when the radio is relaying) | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Heap — free versus total memory on the radio, drawn as a bar | Nodes — how many nodes are online, out of the total known | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . Tap the widget to open the app, or use its refresh control to request fresh stats. ℹ️ Note: The values reflect the connected radio. If the radio disconnects, the widget replaces the stats with a status line — Disconnected, Connecting, or Device sleeping. It does not keep the last-known numbers on screen. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/widget.html#what-it-shows",
    
    "relUrl": "/sr-rLatn/user/widget.html#what-it-shows"
  },"6331": {
    "doc": "Home Screen Widget",
    "title": "Adding the Widget",
    "content": ". | Touch & hold an empty area of your Android home screen. | Tap Widgets. | Drag the Meshtastic widget to your home screen. The app ships one widget, so the picker entry is just the app name. | Resize it as needed — the layout adapts to the available space. | . ℹ️ Note: The widget is Android-only. It is not available on the Desktop or iOS builds. ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/widget.html#adding-the-widget",
    
    "relUrl": "/sr-rLatn/user/widget.html#adding-the-widget"
  },"6332": {
    "doc": "Home Screen Widget",
    "title": "Related Topics",
    "content": ". | Node Metrics — the full Signal Quality and Local Stats history inside the app | Connections — connect to a radio so the widget has stats to show | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/sr-rLatn/user/widget.html#related-topics",
    
    "relUrl": "/sr-rLatn/user/widget.html#related-topics"
  },"6333": {
    "doc": "Home Screen Widget",
    "title": "Home Screen Widget",
    "content": "On Android, Meshtastic provides a home screen widget that shows live local statistics from your connected radio at a glance — no need to open the app. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/widget.html",
    
    "relUrl": "/nl-rNL/user/widget.html"
  },"6334": {
    "doc": "Home Screen Widget",
    "title": "What It Shows",
    "content": "The widget displays the connected radio’s current local stats: . | A node chip across the top, carrying the radio’s short name in its own colors | Battery — the radio’s battery level, or Powered when running on external power | ChUtil — channel utilization (how busy the LoRa channel is, as a percentage) | AirUtil — airtime utilization (how much of the duty cycle your radio is transmitting) | Traffic — packets transmitted / received, and duplicates seen | Relays — packets relayed and relay cancellations (shown when the radio is relaying) | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Heap — free versus total memory on the radio, drawn as a bar | Nodes — how many nodes are online, out of the total known | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . Tap the widget to open the app, or use its refresh control to request fresh stats. ℹ️ Note: The values reflect the connected radio. If the radio disconnects, the widget replaces the stats with a status line — Disconnected, Connecting, or Device sleeping. It does not keep the last-known numbers on screen. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/widget.html#what-it-shows",
    
    "relUrl": "/nl-rNL/user/widget.html#what-it-shows"
  },"6335": {
    "doc": "Home Screen Widget",
    "title": "Adding the Widget",
    "content": ". | Touch & hold an empty area of your Android home screen. | Tap Widgets. | Drag the Meshtastic widget to your home screen. The app ships one widget, so the picker entry is just the app name. | Resize it as needed — the layout adapts to the available space. | . ℹ️ Note: The widget is Android-only. It is not available on the Desktop or iOS builds. ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/widget.html#adding-the-widget",
    
    "relUrl": "/nl-rNL/user/widget.html#adding-the-widget"
  },"6336": {
    "doc": "Home Screen Widget",
    "title": "Related Topics",
    "content": ". | Node Metrics — the full Signal Quality and Local Stats history inside the app | Connections — connect to a radio so the widget has stats to show | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/nl-rNL/user/widget.html#related-topics",
    
    "relUrl": "/nl-rNL/user/widget.html#related-topics"
  },"6337": {
    "doc": "Home Screen Widget",
    "title": "Home Screen Widget",
    "content": "On Android, Meshtastic provides a home screen widget that shows live local statistics from your connected radio at a glance — no need to open the app. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/widget.html",
    
    "relUrl": "/uk-rUA/user/widget.html"
  },"6338": {
    "doc": "Home Screen Widget",
    "title": "What It Shows",
    "content": "The widget displays the connected radio’s current local stats: . | A node chip across the top, carrying the radio’s short name in its own colors | Battery — the radio’s battery level, or Powered when running on external power | ChUtil — channel utilization (how busy the LoRa channel is, as a percentage) | AirUtil — airtime utilization (how much of the duty cycle your radio is transmitting) | Traffic — packets transmitted / received, and duplicates seen | Relays — packets relayed and relay cancellations (shown when the radio is relaying) | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Heap — free versus total memory on the radio, drawn as a bar | Nodes — how many nodes are online, out of the total known | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . Tap the widget to open the app, or use its refresh control to request fresh stats. ℹ️ Note: The values reflect the connected radio. If the radio disconnects, the widget replaces the stats with a status line — Disconnected, Connecting, or Device sleeping. It does not keep the last-known numbers on screen. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/widget.html#what-it-shows",
    
    "relUrl": "/uk-rUA/user/widget.html#what-it-shows"
  },"6339": {
    "doc": "Home Screen Widget",
    "title": "Adding the Widget",
    "content": ". | Touch & hold an empty area of your Android home screen. | Tap Widgets. | Drag the Meshtastic widget to your home screen. The app ships one widget, so the picker entry is just the app name. | Resize it as needed — the layout adapts to the available space. | . ℹ️ Note: The widget is Android-only. It is not available on the Desktop or iOS builds. ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/widget.html#adding-the-widget",
    
    "relUrl": "/uk-rUA/user/widget.html#adding-the-widget"
  },"6340": {
    "doc": "Home Screen Widget",
    "title": "Related Topics",
    "content": ". | Node Metrics — the full Signal Quality and Local Stats history inside the app | Connections — connect to a radio so the widget has stats to show | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/uk-rUA/user/widget.html#related-topics",
    
    "relUrl": "/uk-rUA/user/widget.html#related-topics"
  },"6341": {
    "doc": "Aloitusnäytön widget",
    "title": "Aloitusnäytön widget",
    "content": "Androidissa Meshtastic tarjoaa aloitusnäytölle widgetin, joka näyttää yhdistetyn radiosi paikalliset tilastot yhdellä silmäyksellä — sovellusta ei tarvitse avata. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/widget.html",
    
    "relUrl": "/fi-rFI/user/widget.html"
  },"6342": {
    "doc": "Aloitusnäytön widget",
    "title": "Mitä se näyttää",
    "content": "Widget näyttää yhdistetyn radion tämänhetkiset paikalliset tilastot: . | A node chip across the top, carrying the radio’s short name in its own colors | Akun varaustaso — radion akun varaustaso tai Verkkovirta, jos radio käyttää ulkoista virtalähdettä | ChUtil — kanavan käyttöaste (kuinka kuormitettu LoRa-kanava on prosentteina) | AirUtil — lähetysajan käyttöaste (kuinka suuren osan lähetysajasta radiosi käyttää) | Liikenne — lähetetyt ja vastaanotetut paketit sekä havaitut kaksoiskappaleet | Välitykset — välitetyt paketit ja välityksen peruutukset (näytetään, kun radio toimii välittäjänä) | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Muistin käyttö — radion vapaa ja kokonaismuisti palkkina esitettynä | Radiot — kuinka monta radiota on verkossa tunnetusta kokonaismäärästä | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . Avaa sovellus napauttamalla widgetiä tai pyydä uudet tilastot sen päivityspainikkeella. ℹ️ Huomautus: Arvot vastaavat yhdistettyä radiota. Jos yhteys radioon katkeaa, pienoissovellus korvaa tilastot tilarivillä — Yhteys katkaistu, Yhdistetään tai Laite lepotilassa. Se ei säilytä viimeisimpiä arvoja näytöllä. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/widget.html#mit%C3%A4-se-n%C3%A4ytt%C3%A4%C3%A4",
    
    "relUrl": "/fi-rFI/user/widget.html#mitä-se-näyttää"
  },"6343": {
    "doc": "Aloitusnäytön widget",
    "title": "Widgetin lisääminen",
    "content": ". | Kosketa Androidin aloitusnäytön tyhjää aluetta pitkään. | Napauta Widgetit. | Vedä Meshtastic-pienoissovellus aloitusnäyttöön. Sovelluksessa on vain yksi pienoissovellus, joten valitsimessa näkyy vain sovelluksen nimi. | Muuta widgetin kokoa tarvittaessa — asettelu mukautuu käytettävissä olevaan tilaan. | . ℹ️ Huomautus: Pienoissovellus on käytettävissä vain Androidissa. Se ei ole käytettävissä Desktop- tai iOS-versioissa. ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/widget.html#widgetin-lis%C3%A4%C3%A4minen",
    
    "relUrl": "/fi-rFI/user/widget.html#widgetin-lisääminen"
  },"6344": {
    "doc": "Aloitusnäytön widget",
    "title": "Aiheeseen liittyvät aiheet",
    "content": ". | Radion mittarit — täydellinen signaalin laatu- ja paikalliset tilastot -historia sovelluksessa | Yhteydet — yhdistä radioon, jotta widgetillä on näytettäviä tilastoja | Paikallinen mesh-verkon etsintä — kanavan ja lähetysajan käyttö koko mesh-verkossa | . ",
    "url": "/Meshtastic-Android/main/fi-rFI/user/widget.html#aiheeseen-liittyv%C3%A4t-aiheet",
    
    "relUrl": "/fi-rFI/user/widget.html#aiheeseen-liittyvät-aiheet"
  },"6345": {
    "doc": "Home Screen Widget",
    "title": "Home Screen Widget",
    "content": "On Android, Meshtastic provides a home screen widget that shows live local statistics from your connected radio at a glance — no need to open the app. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/widget.html",
    
    "relUrl": "/is-rIS/user/widget.html"
  },"6346": {
    "doc": "Home Screen Widget",
    "title": "What It Shows",
    "content": "The widget displays the connected radio’s current local stats: . | A node chip across the top, carrying the radio’s short name in its own colors | Battery — the radio’s battery level, or Powered when running on external power | ChUtil — channel utilization (how busy the LoRa channel is, as a percentage) | AirUtil — airtime utilization (how much of the duty cycle your radio is transmitting) | Traffic — packets transmitted / received, and duplicates seen | Relays — packets relayed and relay cancellations (shown when the radio is relaying) | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Heap — free versus total memory on the radio, drawn as a bar | Nodes — how many nodes are online, out of the total known | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . Tap the widget to open the app, or use its refresh control to request fresh stats. ℹ️ Note: The values reflect the connected radio. If the radio disconnects, the widget replaces the stats with a status line — Disconnected, Connecting, or Device sleeping. It does not keep the last-known numbers on screen. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/widget.html#what-it-shows",
    
    "relUrl": "/is-rIS/user/widget.html#what-it-shows"
  },"6347": {
    "doc": "Home Screen Widget",
    "title": "Adding the Widget",
    "content": ". | Touch & hold an empty area of your Android home screen. | Tap Widgets. | Drag the Meshtastic widget to your home screen. The app ships one widget, so the picker entry is just the app name. | Resize it as needed — the layout adapts to the available space. | . ℹ️ Note: The widget is Android-only. It is not available on the Desktop or iOS builds. ",
    "url": "/Meshtastic-Android/main/is-rIS/user/widget.html#adding-the-widget",
    
    "relUrl": "/is-rIS/user/widget.html#adding-the-widget"
  },"6348": {
    "doc": "Home Screen Widget",
    "title": "Related Topics",
    "content": ". | Node Metrics — the full Signal Quality and Local Stats history inside the app | Connections — connect to a radio so the widget has stats to show | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/is-rIS/user/widget.html#related-topics",
    
    "relUrl": "/is-rIS/user/widget.html#related-topics"
  },"6349": {
    "doc": "Home Screen Widget",
    "title": "Home Screen Widget",
    "content": "On Android, Meshtastic provides a home screen widget that shows live local statistics from your connected radio at a glance — no need to open the app. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/widget.html",
    
    "relUrl": "/lt-rLT/user/widget.html"
  },"6350": {
    "doc": "Home Screen Widget",
    "title": "What It Shows",
    "content": "The widget displays the connected radio’s current local stats: . | A node chip across the top, carrying the radio’s short name in its own colors | Battery — the radio’s battery level, or Powered when running on external power | ChUtil — channel utilization (how busy the LoRa channel is, as a percentage) | AirUtil — airtime utilization (how much of the duty cycle your radio is transmitting) | Traffic — packets transmitted / received, and duplicates seen | Relays — packets relayed and relay cancellations (shown when the radio is relaying) | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Heap — free versus total memory on the radio, drawn as a bar | Nodes — how many nodes are online, out of the total known | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . Tap the widget to open the app, or use its refresh control to request fresh stats. ℹ️ Note: The values reflect the connected radio. If the radio disconnects, the widget replaces the stats with a status line — Disconnected, Connecting, or Device sleeping. It does not keep the last-known numbers on screen. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/widget.html#what-it-shows",
    
    "relUrl": "/lt-rLT/user/widget.html#what-it-shows"
  },"6351": {
    "doc": "Home Screen Widget",
    "title": "Adding the Widget",
    "content": ". | Touch & hold an empty area of your Android home screen. | Tap Widgets. | Drag the Meshtastic widget to your home screen. The app ships one widget, so the picker entry is just the app name. | Resize it as needed — the layout adapts to the available space. | . ℹ️ Note: The widget is Android-only. It is not available on the Desktop or iOS builds. ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/widget.html#adding-the-widget",
    
    "relUrl": "/lt-rLT/user/widget.html#adding-the-widget"
  },"6352": {
    "doc": "Home Screen Widget",
    "title": "Related Topics",
    "content": ". | Node Metrics — the full Signal Quality and Local Stats history inside the app | Connections — connect to a radio so the widget has stats to show | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/lt-rLT/user/widget.html#related-topics",
    
    "relUrl": "/lt-rLT/user/widget.html#related-topics"
  },"6353": {
    "doc": "Home Screen Widget",
    "title": "Home Screen Widget",
    "content": "On Android, Meshtastic provides a home screen widget that shows live local statistics from your connected radio at a glance — no need to open the app. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/widget.html",
    
    "relUrl": "/gl-rES/user/widget.html"
  },"6354": {
    "doc": "Home Screen Widget",
    "title": "What It Shows",
    "content": "The widget displays the connected radio’s current local stats: . | A node chip across the top, carrying the radio’s short name in its own colors | Battery — the radio’s battery level, or Powered when running on external power | ChUtil — channel utilization (how busy the LoRa channel is, as a percentage) | AirUtil — airtime utilization (how much of the duty cycle your radio is transmitting) | Traffic — packets transmitted / received, and duplicates seen | Relays — packets relayed and relay cancellations (shown when the radio is relaying) | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Heap — free versus total memory on the radio, drawn as a bar | Nodes — how many nodes are online, out of the total known | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . Tap the widget to open the app, or use its refresh control to request fresh stats. ℹ️ Note: The values reflect the connected radio. If the radio disconnects, the widget replaces the stats with a status line — Disconnected, Connecting, or Device sleeping. It does not keep the last-known numbers on screen. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/widget.html#what-it-shows",
    
    "relUrl": "/gl-rES/user/widget.html#what-it-shows"
  },"6355": {
    "doc": "Home Screen Widget",
    "title": "Adding the Widget",
    "content": ". | Touch & hold an empty area of your Android home screen. | Tap Widgets. | Drag the Meshtastic widget to your home screen. The app ships one widget, so the picker entry is just the app name. | Resize it as needed — the layout adapts to the available space. | . ℹ️ Note: The widget is Android-only. It is not available on the Desktop or iOS builds. ",
    "url": "/Meshtastic-Android/main/gl-rES/user/widget.html#adding-the-widget",
    
    "relUrl": "/gl-rES/user/widget.html#adding-the-widget"
  },"6356": {
    "doc": "Home Screen Widget",
    "title": "Related Topics",
    "content": ". | Node Metrics — the full Signal Quality and Local Stats history inside the app | Connections — connect to a radio so the widget has stats to show | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/gl-rES/user/widget.html#related-topics",
    
    "relUrl": "/gl-rES/user/widget.html#related-topics"
  },"6357": {
    "doc": "ホーム画面ウィジェット",
    "title": "ホーム画面ウィジェット",
    "content": "Android では、Meshtastic はホーム画面のウィジェットを提供しており、接続中の無線機のライブなローカル統計をひと目で確認できます。アプリを開く必要はありません。 . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/widget.html",
    
    "relUrl": "/ja-rJP/user/widget.html"
  },"6358": {
    "doc": "ホーム画面ウィジェット",
    "title": "表示される内容",
    "content": "ウィジェットは、接続中の無線機の現在のローカル統計を表示します： . | A node chip across the top, carrying the radio’s short name in its own colors | Battery：無線機のバッテリー残量。外部電源で動作している場合は Powered（給電中） | ChUtil：チャンネル利用率（LoRa チャンネルがどれだけ混雑しているかを割合で表示） | AirUtil：電波利用率（無線機がデューティサイクルのうちどれだけ送信しているか） | Traffic：送受信したパケットと、検出した重複 | Relays：中継したパケットと、中継のキャンセル（無線機が中継しているときに表示） | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Heap — free versus total memory on the radio, drawn as a bar | Nodes — how many nodes are online, out of the total known | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . ウィジェットをタップするとアプリが開きます。更新コントロールを使うと、最新の統計を要求できます。 . ℹ️ Note: The values reflect the connected radio. If the radio disconnects, the widget replaces the stats with a status line — Disconnected, Connecting, or Device sleeping. It does not keep the last-known numbers on screen. ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/widget.html#%E8%A1%A8%E7%A4%BA%E3%81%95%E3%82%8C%E3%82%8B%E5%86%85%E5%AE%B9",
    
    "relUrl": "/ja-rJP/user/widget.html#表示される内容"
  },"6359": {
    "doc": "ホーム画面ウィジェット",
    "title": "ウィジェットを追加する",
    "content": ". | Touch & hold an empty area of your Android home screen. | 「ウィジェット」をタップします。 | Drag the Meshtastic widget to your home screen. The app ships one widget, so the picker entry is just the app name. | 必要に応じてサイズを変更します。レイアウトは利用可能なスペースに合わせて調整されます。 | . ℹ️ Note: The widget is Android-only. デスクトップ版や iOS 版では利用できません。 . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/widget.html#%E3%82%A6%E3%82%A3%E3%82%B8%E3%82%A7%E3%83%83%E3%83%88%E3%82%92%E8%BF%BD%E5%8A%A0%E3%81%99%E3%82%8B",
    
    "relUrl": "/ja-rJP/user/widget.html#ウィジェットを追加する"
  },"6360": {
    "doc": "ホーム画面ウィジェット",
    "title": "関連トピック",
    "content": ". | ノードメトリクス：アプリ内の完全な信号品質とローカル統計の履歴 | コネクション：ウィジェットに表示する統計が得られるよう、無線機に接続する | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/ja-rJP/user/widget.html#%E9%96%A2%E9%80%A3%E3%83%88%E3%83%94%E3%83%83%E3%82%AF",
    
    "relUrl": "/ja-rJP/user/widget.html#関連トピック"
  },"6361": {
    "doc": "Home Screen Widget",
    "title": "Home Screen Widget",
    "content": "On Android, Meshtastic provides a home screen widget that shows live local statistics from your connected radio at a glance — no need to open the app. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/widget.html",
    
    "relUrl": "/de-rDE/user/widget.html"
  },"6362": {
    "doc": "Home Screen Widget",
    "title": "What It Shows",
    "content": "The widget displays the connected radio’s current local stats: . | A node chip across the top, carrying the radio’s short name in its own colors | Battery — the radio’s battery level, or Powered when running on external power | ChUtil — channel utilization (how busy the LoRa channel is, as a percentage) | AirUtil — airtime utilization (how much of the duty cycle your radio is transmitting) | Traffic — packets transmitted / received, and duplicates seen | Relays — packets relayed and relay cancellations (shown when the radio is relaying) | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Heap — free versus total memory on the radio, drawn as a bar | Nodes — how many nodes are online, out of the total known | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . Tap the widget to open the app, or use its refresh control to request fresh stats. ℹ️ Note: The values reflect the connected radio. If the radio disconnects, the widget replaces the stats with a status line — Disconnected, Connecting, or Device sleeping. It does not keep the last-known numbers on screen. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/widget.html#what-it-shows",
    
    "relUrl": "/de-rDE/user/widget.html#what-it-shows"
  },"6363": {
    "doc": "Home Screen Widget",
    "title": "Adding the Widget",
    "content": ". | Touch & hold an empty area of your Android home screen. | Tap Widgets. | Drag the Meshtastic widget to your home screen. The app ships one widget, so the picker entry is just the app name. | Resize it as needed — the layout adapts to the available space. | . ℹ️ Note: The widget is Android-only. It is not available on the Desktop or iOS builds. ",
    "url": "/Meshtastic-Android/main/de-rDE/user/widget.html#adding-the-widget",
    
    "relUrl": "/de-rDE/user/widget.html#adding-the-widget"
  },"6364": {
    "doc": "Home Screen Widget",
    "title": "Related Topics",
    "content": ". | Node Metrics — the full Signal Quality and Local Stats history inside the app | Connections — connect to a radio so the widget has stats to show | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/de-rDE/user/widget.html#related-topics",
    
    "relUrl": "/de-rDE/user/widget.html#related-topics"
  },"6365": {
    "doc": "Home Screen Widget",
    "title": "Home Screen Widget",
    "content": "On Android, Meshtastic provides a home screen widget that shows live local statistics from your connected radio at a glance — no need to open the app. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/widget.html",
    
    "relUrl": "/ar-rSA/user/widget.html"
  },"6366": {
    "doc": "Home Screen Widget",
    "title": "What It Shows",
    "content": "The widget displays the connected radio’s current local stats: . | A node chip across the top, carrying the radio’s short name in its own colors | Battery — the radio’s battery level, or Powered when running on external power | ChUtil — channel utilization (how busy the LoRa channel is, as a percentage) | AirUtil — airtime utilization (how much of the duty cycle your radio is transmitting) | Traffic — packets transmitted / received, and duplicates seen | Relays — packets relayed and relay cancellations (shown when the radio is relaying) | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Heap — free versus total memory on the radio, drawn as a bar | Nodes — how many nodes are online, out of the total known | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . Tap the widget to open the app, or use its refresh control to request fresh stats. ℹ️ Note: The values reflect the connected radio. If the radio disconnects, the widget replaces the stats with a status line — Disconnected, Connecting, or Device sleeping. It does not keep the last-known numbers on screen. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/widget.html#what-it-shows",
    
    "relUrl": "/ar-rSA/user/widget.html#what-it-shows"
  },"6367": {
    "doc": "Home Screen Widget",
    "title": "Adding the Widget",
    "content": ". | Touch & hold an empty area of your Android home screen. | Tap Widgets. | Drag the Meshtastic widget to your home screen. The app ships one widget, so the picker entry is just the app name. | Resize it as needed — the layout adapts to the available space. | . ℹ️ Note: The widget is Android-only. It is not available on the Desktop or iOS builds. ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/widget.html#adding-the-widget",
    
    "relUrl": "/ar-rSA/user/widget.html#adding-the-widget"
  },"6368": {
    "doc": "Home Screen Widget",
    "title": "Related Topics",
    "content": ". | Node Metrics — the full Signal Quality and Local Stats history inside the app | Connections — connect to a radio so the widget has stats to show | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/ar-rSA/user/widget.html#related-topics",
    
    "relUrl": "/ar-rSA/user/widget.html#related-topics"
  },"6369": {
    "doc": "Home Screen Widget",
    "title": "Home Screen Widget",
    "content": "On Android, Meshtastic provides a home screen widget that shows live local statistics from your connected radio at a glance — no need to open the app. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/widget.html",
    
    "relUrl": "/hr-rHR/user/widget.html"
  },"6370": {
    "doc": "Home Screen Widget",
    "title": "What It Shows",
    "content": "The widget displays the connected radio’s current local stats: . | A node chip across the top, carrying the radio’s short name in its own colors | Battery — the radio’s battery level, or Powered when running on external power | ChUtil — channel utilization (how busy the LoRa channel is, as a percentage) | AirUtil — airtime utilization (how much of the duty cycle your radio is transmitting) | Traffic — packets transmitted / received, and duplicates seen | Relays — packets relayed and relay cancellations (shown when the radio is relaying) | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Heap — free versus total memory on the radio, drawn as a bar | Nodes — how many nodes are online, out of the total known | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . Tap the widget to open the app, or use its refresh control to request fresh stats. ℹ️ Note: The values reflect the connected radio. If the radio disconnects, the widget replaces the stats with a status line — Disconnected, Connecting, or Device sleeping. It does not keep the last-known numbers on screen. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/widget.html#what-it-shows",
    
    "relUrl": "/hr-rHR/user/widget.html#what-it-shows"
  },"6371": {
    "doc": "Home Screen Widget",
    "title": "Adding the Widget",
    "content": ". | Touch & hold an empty area of your Android home screen. | Tap Widgets. | Drag the Meshtastic widget to your home screen. The app ships one widget, so the picker entry is just the app name. | Resize it as needed — the layout adapts to the available space. | . ℹ️ Note: The widget is Android-only. It is not available on the Desktop or iOS builds. ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/widget.html#adding-the-widget",
    
    "relUrl": "/hr-rHR/user/widget.html#adding-the-widget"
  },"6372": {
    "doc": "Home Screen Widget",
    "title": "Related Topics",
    "content": ". | Node Metrics — the full Signal Quality and Local Stats history inside the app | Connections — connect to a radio so the widget has stats to show | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/hr-rHR/user/widget.html#related-topics",
    
    "relUrl": "/hr-rHR/user/widget.html#related-topics"
  },"6373": {
    "doc": "Home Screen Widget",
    "title": "Home Screen Widget",
    "content": "On Android, Meshtastic provides a home screen widget that shows live local statistics from your connected radio at a glance — no need to open the app. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/widget.html",
    
    "relUrl": "/pt-rPT/user/widget.html"
  },"6374": {
    "doc": "Home Screen Widget",
    "title": "What It Shows",
    "content": "The widget displays the connected radio’s current local stats: . | A node chip across the top, carrying the radio’s short name in its own colors | Battery — the radio’s battery level, or Powered when running on external power | ChUtil — channel utilization (how busy the LoRa channel is, as a percentage) | AirUtil — airtime utilization (how much of the duty cycle your radio is transmitting) | Traffic — packets transmitted / received, and duplicates seen | Relays — packets relayed and relay cancellations (shown when the radio is relaying) | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Heap — free versus total memory on the radio, drawn as a bar | Nodes — how many nodes are online, out of the total known | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . Tap the widget to open the app, or use its refresh control to request fresh stats. ℹ️ Note: The values reflect the connected radio. If the radio disconnects, the widget replaces the stats with a status line — Disconnected, Connecting, or Device sleeping. It does not keep the last-known numbers on screen. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/widget.html#what-it-shows",
    
    "relUrl": "/pt-rPT/user/widget.html#what-it-shows"
  },"6375": {
    "doc": "Home Screen Widget",
    "title": "Adding the Widget",
    "content": ". | Touch & hold an empty area of your Android home screen. | Tap Widgets. | Drag the Meshtastic widget to your home screen. The app ships one widget, so the picker entry is just the app name. | Resize it as needed — the layout adapts to the available space. | . ℹ️ Note: The widget is Android-only. It is not available on the Desktop or iOS builds. ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/widget.html#adding-the-widget",
    
    "relUrl": "/pt-rPT/user/widget.html#adding-the-widget"
  },"6376": {
    "doc": "Home Screen Widget",
    "title": "Related Topics",
    "content": ". | Node Metrics — the full Signal Quality and Local Stats history inside the app | Connections — connect to a radio so the widget has stats to show | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/pt-rPT/user/widget.html#related-topics",
    
    "relUrl": "/pt-rPT/user/widget.html#related-topics"
  },"6377": {
    "doc": "Home Screen Widget",
    "title": "Home Screen Widget",
    "content": "On Android, Meshtastic provides a home screen widget that shows live local statistics from your connected radio at a glance — no need to open the app. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/widget.html",
    
    "relUrl": "/pl-rPL/user/widget.html"
  },"6378": {
    "doc": "Home Screen Widget",
    "title": "What It Shows",
    "content": "The widget displays the connected radio’s current local stats: . | A node chip across the top, carrying the radio’s short name in its own colors | Battery — the radio’s battery level, or Powered when running on external power | ChUtil — channel utilization (how busy the LoRa channel is, as a percentage) | AirUtil — airtime utilization (how much of the duty cycle your radio is transmitting) | Traffic — packets transmitted / received, and duplicates seen | Relays — packets relayed and relay cancellations (shown when the radio is relaying) | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Heap — free versus total memory on the radio, drawn as a bar | Nodes — how many nodes are online, out of the total known | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . Tap the widget to open the app, or use its refresh control to request fresh stats. ℹ️ Note: The values reflect the connected radio. If the radio disconnects, the widget replaces the stats with a status line — Disconnected, Connecting, or Device sleeping. It does not keep the last-known numbers on screen. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/widget.html#what-it-shows",
    
    "relUrl": "/pl-rPL/user/widget.html#what-it-shows"
  },"6379": {
    "doc": "Home Screen Widget",
    "title": "Adding the Widget",
    "content": ". | Touch & hold an empty area of your Android home screen. | Tap Widgets. | Drag the Meshtastic widget to your home screen. The app ships one widget, so the picker entry is just the app name. | Resize it as needed — the layout adapts to the available space. | . ℹ️ Note: The widget is Android-only. It is not available on the Desktop or iOS builds. ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/widget.html#adding-the-widget",
    
    "relUrl": "/pl-rPL/user/widget.html#adding-the-widget"
  },"6380": {
    "doc": "Home Screen Widget",
    "title": "Related Topics",
    "content": ". | Node Metrics — the full Signal Quality and Local Stats history inside the app | Connections — connect to a radio so the widget has stats to show | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/pl-rPL/user/widget.html#related-topics",
    
    "relUrl": "/pl-rPL/user/widget.html#related-topics"
  },"6381": {
    "doc": "Home Screen Widget",
    "title": "Home Screen Widget",
    "content": "On Android, Meshtastic provides a home screen widget that shows live local statistics from your connected radio at a glance — no need to open the app. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/widget.html",
    
    "relUrl": "/zh-rCN/user/widget.html"
  },"6382": {
    "doc": "Home Screen Widget",
    "title": "What It Shows",
    "content": "The widget displays the connected radio’s current local stats: . | A node chip across the top, carrying the radio’s short name in its own colors | Battery — the radio’s battery level, or Powered when running on external power | ChUtil — channel utilization (how busy the LoRa channel is, as a percentage) | AirUtil — airtime utilization (how much of the duty cycle your radio is transmitting) | Traffic — packets transmitted / received, and duplicates seen | Relays — packets relayed and relay cancellations (shown when the radio is relaying) | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Heap — free versus total memory on the radio, drawn as a bar | Nodes — how many nodes are online, out of the total known | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . Tap the widget to open the app, or use its refresh control to request fresh stats. ℹ️ Note: The values reflect the connected radio. If the radio disconnects, the widget replaces the stats with a status line — Disconnected, Connecting, or Device sleeping. It does not keep the last-known numbers on screen. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/widget.html#what-it-shows",
    
    "relUrl": "/zh-rCN/user/widget.html#what-it-shows"
  },"6383": {
    "doc": "Home Screen Widget",
    "title": "Adding the Widget",
    "content": ". | Touch & hold an empty area of your Android home screen. | Tap Widgets. | Drag the Meshtastic widget to your home screen. The app ships one widget, so the picker entry is just the app name. | Resize it as needed — the layout adapts to the available space. | . ℹ️ Note: The widget is Android-only. It is not available on the Desktop or iOS builds. ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/widget.html#adding-the-widget",
    
    "relUrl": "/zh-rCN/user/widget.html#adding-the-widget"
  },"6384": {
    "doc": "Home Screen Widget",
    "title": "Related Topics",
    "content": ". | Node Metrics — the full Signal Quality and Local Stats history inside the app | Connections — connect to a radio so the widget has stats to show | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/zh-rCN/user/widget.html#related-topics",
    
    "relUrl": "/zh-rCN/user/widget.html#related-topics"
  },"6385": {
    "doc": "Home Screen Widget",
    "title": "Home Screen Widget",
    "content": "On Android, Meshtastic provides a home screen widget that shows live local statistics from your connected radio at a glance — no need to open the app. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/widget.html",
    
    "relUrl": "/sq-rAL/user/widget.html"
  },"6386": {
    "doc": "Home Screen Widget",
    "title": "What It Shows",
    "content": "The widget displays the connected radio’s current local stats: . | A node chip across the top, carrying the radio’s short name in its own colors | Battery — the radio’s battery level, or Powered when running on external power | ChUtil — channel utilization (how busy the LoRa channel is, as a percentage) | AirUtil — airtime utilization (how much of the duty cycle your radio is transmitting) | Traffic — packets transmitted / received, and duplicates seen | Relays — packets relayed and relay cancellations (shown when the radio is relaying) | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Heap — free versus total memory on the radio, drawn as a bar | Nodes — how many nodes are online, out of the total known | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . Tap the widget to open the app, or use its refresh control to request fresh stats. ℹ️ Note: The values reflect the connected radio. If the radio disconnects, the widget replaces the stats with a status line — Disconnected, Connecting, or Device sleeping. It does not keep the last-known numbers on screen. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/widget.html#what-it-shows",
    
    "relUrl": "/sq-rAL/user/widget.html#what-it-shows"
  },"6387": {
    "doc": "Home Screen Widget",
    "title": "Adding the Widget",
    "content": ". | Touch & hold an empty area of your Android home screen. | Tap Widgets. | Drag the Meshtastic widget to your home screen. The app ships one widget, so the picker entry is just the app name. | Resize it as needed — the layout adapts to the available space. | . ℹ️ Note: The widget is Android-only. It is not available on the Desktop or iOS builds. ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/widget.html#adding-the-widget",
    
    "relUrl": "/sq-rAL/user/widget.html#adding-the-widget"
  },"6388": {
    "doc": "Home Screen Widget",
    "title": "Related Topics",
    "content": ". | Node Metrics — the full Signal Quality and Local Stats history inside the app | Connections — connect to a radio so the widget has stats to show | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/sq-rAL/user/widget.html#related-topics",
    
    "relUrl": "/sq-rAL/user/widget.html#related-topics"
  },"6389": {
    "doc": "Home Screen Widget",
    "title": "Home Screen Widget",
    "content": "On Android, Meshtastic provides a home screen widget that shows live local statistics from your connected radio at a glance — no need to open the app. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/widget.html",
    
    "relUrl": "/zh-rTW/user/widget.html"
  },"6390": {
    "doc": "Home Screen Widget",
    "title": "What It Shows",
    "content": "The widget displays the connected radio’s current local stats: . | A node chip across the top, carrying the radio’s short name in its own colors | Battery — the radio’s battery level, or Powered when running on external power | ChUtil — channel utilization (how busy the LoRa channel is, as a percentage) | AirUtil — airtime utilization (how much of the duty cycle your radio is transmitting) | Traffic — packets transmitted / received, and duplicates seen | Relays — packets relayed and relay cancellations (shown when the radio is relaying) | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Heap — free versus total memory on the radio, drawn as a bar | Nodes — how many nodes are online, out of the total known | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . Tap the widget to open the app, or use its refresh control to request fresh stats. ℹ️ Note: The values reflect the connected radio. If the radio disconnects, the widget replaces the stats with a status line — Disconnected, Connecting, or Device sleeping. It does not keep the last-known numbers on screen. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/widget.html#what-it-shows",
    
    "relUrl": "/zh-rTW/user/widget.html#what-it-shows"
  },"6391": {
    "doc": "Home Screen Widget",
    "title": "Adding the Widget",
    "content": ". | Touch & hold an empty area of your Android home screen. | Tap Widgets. | Drag the Meshtastic widget to your home screen. The app ships one widget, so the picker entry is just the app name. | Resize it as needed — the layout adapts to the available space. | . ℹ️ Note: The widget is Android-only. It is not available on the Desktop or iOS builds. ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/widget.html#adding-the-widget",
    
    "relUrl": "/zh-rTW/user/widget.html#adding-the-widget"
  },"6392": {
    "doc": "Home Screen Widget",
    "title": "相關主題",
    "content": ". | Node Metrics — the full Signal Quality and Local Stats history inside the app | Connections — connect to a radio so the widget has stats to show | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/zh-rTW/user/widget.html#%E7%9B%B8%E9%97%9C%E4%B8%BB%E9%A1%8C",
    
    "relUrl": "/zh-rTW/user/widget.html#相關主題"
  },"6393": {
    "doc": "Home Screen Widget",
    "title": "Home Screen Widget",
    "content": "Androidis pakub Meshtastic avakuva vidinat, mis näitab ühendatud raadio reaalajas kohalikku statistikat – rakendust pole vaja avada. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/widget.html",
    
    "relUrl": "/et-rEE/user/widget.html"
  },"6394": {
    "doc": "Home Screen Widget",
    "title": "Mida see näitab",
    "content": "The widget displays the connected radio’s current local stats: . | A node chip across the top, carrying the radio’s short name in its own colors | Aku – raadio aku tase või Toitel, kui see töötab välise toiteallikaga | ChUtil — kanali kasutus (kui hõivatud on LoRa kanal protsentides) | AirUtil — eetriaega (kui suurt osa töötsüklist raadio edastab) | Liiklus — edastatud/vastuvõetud paketid ja nähtud duplikaadid | Vahendajad — edastatud paketid ja edastuste tühistamised (kuvatakse raadio vahendusprotsessi ajal) | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Heap — free versus total memory on the radio, drawn as a bar | Nodes — how many nodes are online, out of the total known | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . Tap the widget to open the app, or use its refresh control to request fresh stats. ℹ️ Note: The values reflect the connected radio. If the radio disconnects, the widget replaces the stats with a status line — Disconnected, Connecting, or Device sleeping. It does not keep the last-known numbers on screen. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/widget.html#mida-see-n%C3%A4itab",
    
    "relUrl": "/et-rEE/user/widget.html#mida-see-näitab"
  },"6395": {
    "doc": "Home Screen Widget",
    "title": "Adding the Widget",
    "content": ". | Touch & hold an empty area of your Android home screen. | Tap Widgets. | Drag the Meshtastic widget to your home screen. The app ships one widget, so the picker entry is just the app name. | Resize it as needed — the layout adapts to the available space. | . ℹ️ Note: The widget is Android-only. It is not available on the Desktop or iOS builds. ",
    "url": "/Meshtastic-Android/main/et-rEE/user/widget.html#adding-the-widget",
    
    "relUrl": "/et-rEE/user/widget.html#adding-the-widget"
  },"6396": {
    "doc": "Home Screen Widget",
    "title": "Seotud teemad",
    "content": ". | Node Metrics — the full Signal Quality and Local Stats history inside the app | Ühendused — loo ühendus raadioga, et vidinal oleks statistikat kuvada | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/et-rEE/user/widget.html#seotud-teemad",
    
    "relUrl": "/et-rEE/user/widget.html#seotud-teemad"
  },"6397": {
    "doc": "Home Screen Widget",
    "title": "Home Screen Widget",
    "content": "On Android, Meshtastic provides a home screen widget that shows live local statistics from your connected radio at a glance — no need to open the app. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/widget.html",
    
    "relUrl": "/fr-rFR/user/widget.html"
  },"6398": {
    "doc": "Home Screen Widget",
    "title": "What It Shows",
    "content": "The widget displays the connected radio’s current local stats: . | A node chip across the top, carrying the radio’s short name in its own colors | Battery — the radio’s battery level, or Powered when running on external power | ChUtil — channel utilization (how busy the LoRa channel is, as a percentage) | AirUtil — airtime utilization (how much of the duty cycle your radio is transmitting) | Traffic — packets transmitted / received, and duplicates seen | Relays — packets relayed and relay cancellations (shown when the radio is relaying) | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Heap — free versus total memory on the radio, drawn as a bar | Nodes — how many nodes are online, out of the total known | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . Tap the widget to open the app, or use its refresh control to request fresh stats. ℹ️ Note: The values reflect the connected radio. If the radio disconnects, the widget replaces the stats with a status line — Disconnected, Connecting, or Device sleeping. It does not keep the last-known numbers on screen. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/widget.html#what-it-shows",
    
    "relUrl": "/fr-rFR/user/widget.html#what-it-shows"
  },"6399": {
    "doc": "Home Screen Widget",
    "title": "Adding the Widget",
    "content": ". | Touch & hold an empty area of your Android home screen. | Tap Widgets. | Drag the Meshtastic widget to your home screen. The app ships one widget, so the picker entry is just the app name. | Resize it as needed — the layout adapts to the available space. | . ℹ️ Note: The widget is Android-only. It is not available on the Desktop or iOS builds. ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/widget.html#adding-the-widget",
    
    "relUrl": "/fr-rFR/user/widget.html#adding-the-widget"
  },"6400": {
    "doc": "Home Screen Widget",
    "title": "Related Topics",
    "content": ". | Node Metrics — the full Signal Quality and Local Stats history inside the app | Connections — connect to a radio so the widget has stats to show | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/fr-rFR/user/widget.html#related-topics",
    
    "relUrl": "/fr-rFR/user/widget.html#related-topics"
  },"6401": {
    "doc": "Home Screen Widget",
    "title": "Home Screen Widget",
    "content": "On Android, Meshtastic provides a home screen widget that shows live local statistics from your connected radio at a glance — no need to open the app. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/widget.html",
    
    "relUrl": "/tr-rTR/user/widget.html"
  },"6402": {
    "doc": "Home Screen Widget",
    "title": "What It Shows",
    "content": "The widget displays the connected radio’s current local stats: . | A node chip across the top, carrying the radio’s short name in its own colors | Battery — the radio’s battery level, or Powered when running on external power | ChUtil — channel utilization (how busy the LoRa channel is, as a percentage) | AirUtil — airtime utilization (how much of the duty cycle your radio is transmitting) | Traffic — packets transmitted / received, and duplicates seen | Relays — packets relayed and relay cancellations (shown when the radio is relaying) | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Heap — free versus total memory on the radio, drawn as a bar | Nodes — how many nodes are online, out of the total known | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . Tap the widget to open the app, or use its refresh control to request fresh stats. ℹ️ Note: The values reflect the connected radio. If the radio disconnects, the widget replaces the stats with a status line — Disconnected, Connecting, or Device sleeping. It does not keep the last-known numbers on screen. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/widget.html#what-it-shows",
    
    "relUrl": "/tr-rTR/user/widget.html#what-it-shows"
  },"6403": {
    "doc": "Home Screen Widget",
    "title": "Adding the Widget",
    "content": ". | Touch & hold an empty area of your Android home screen. | Tap Widgets. | Drag the Meshtastic widget to your home screen. The app ships one widget, so the picker entry is just the app name. | Resize it as needed — the layout adapts to the available space. | . ℹ️ Note: The widget is Android-only. It is not available on the Desktop or iOS builds. ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/widget.html#adding-the-widget",
    
    "relUrl": "/tr-rTR/user/widget.html#adding-the-widget"
  },"6404": {
    "doc": "Home Screen Widget",
    "title": "Related Topics",
    "content": ". | Node Metrics — the full Signal Quality and Local Stats history inside the app | Connections — connect to a radio so the widget has stats to show | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/tr-rTR/user/widget.html#related-topics",
    
    "relUrl": "/tr-rTR/user/widget.html#related-topics"
  },"6405": {
    "doc": "Home Screen Widget",
    "title": "Home Screen Widget",
    "content": "On Android, Meshtastic provides a home screen widget that shows live local statistics from your connected radio at a glance — no need to open the app. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/widget.html",
    
    "relUrl": "/el-rGR/user/widget.html"
  },"6406": {
    "doc": "Home Screen Widget",
    "title": "What It Shows",
    "content": "The widget displays the connected radio’s current local stats: . | A node chip across the top, carrying the radio’s short name in its own colors | Battery — the radio’s battery level, or Powered when running on external power | ChUtil — channel utilization (how busy the LoRa channel is, as a percentage) | AirUtil — airtime utilization (how much of the duty cycle your radio is transmitting) | Traffic — packets transmitted / received, and duplicates seen | Relays — packets relayed and relay cancellations (shown when the radio is relaying) | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Heap — free versus total memory on the radio, drawn as a bar | Nodes — how many nodes are online, out of the total known | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . Tap the widget to open the app, or use its refresh control to request fresh stats. ℹ️ Note: The values reflect the connected radio. If the radio disconnects, the widget replaces the stats with a status line — Disconnected, Connecting, or Device sleeping. It does not keep the last-known numbers on screen. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/widget.html#what-it-shows",
    
    "relUrl": "/el-rGR/user/widget.html#what-it-shows"
  },"6407": {
    "doc": "Home Screen Widget",
    "title": "Adding the Widget",
    "content": ". | Touch & hold an empty area of your Android home screen. | Tap Widgets. | Drag the Meshtastic widget to your home screen. The app ships one widget, so the picker entry is just the app name. | Resize it as needed — the layout adapts to the available space. | . ℹ️ Note: The widget is Android-only. It is not available on the Desktop or iOS builds. ",
    "url": "/Meshtastic-Android/main/el-rGR/user/widget.html#adding-the-widget",
    
    "relUrl": "/el-rGR/user/widget.html#adding-the-widget"
  },"6408": {
    "doc": "Home Screen Widget",
    "title": "Related Topics",
    "content": ". | Node Metrics — the full Signal Quality and Local Stats history inside the app | Connections — connect to a radio so the widget has stats to show | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/el-rGR/user/widget.html#related-topics",
    
    "relUrl": "/el-rGR/user/widget.html#related-topics"
  },"6409": {
    "doc": "Home Screen Widget",
    "title": "Home Screen Widget",
    "content": "On Android, Meshtastic provides a home screen widget that shows live local statistics from your connected radio at a glance — no need to open the app. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/widget.html",
    
    "relUrl": "/ro-rRO/user/widget.html"
  },"6410": {
    "doc": "Home Screen Widget",
    "title": "What It Shows",
    "content": "The widget displays the connected radio’s current local stats: . | A node chip across the top, carrying the radio’s short name in its own colors | Battery — the radio’s battery level, or Powered when running on external power | ChUtil — channel utilization (how busy the LoRa channel is, as a percentage) | AirUtil — airtime utilization (how much of the duty cycle your radio is transmitting) | Traffic — packets transmitted / received, and duplicates seen | Relays — packets relayed and relay cancellations (shown when the radio is relaying) | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Heap — free versus total memory on the radio, drawn as a bar | Nodes — how many nodes are online, out of the total known | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . Tap the widget to open the app, or use its refresh control to request fresh stats. ℹ️ Note: The values reflect the connected radio. If the radio disconnects, the widget replaces the stats with a status line — Disconnected, Connecting, or Device sleeping. It does not keep the last-known numbers on screen. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/widget.html#what-it-shows",
    
    "relUrl": "/ro-rRO/user/widget.html#what-it-shows"
  },"6411": {
    "doc": "Home Screen Widget",
    "title": "Adding the Widget",
    "content": ". | Touch & hold an empty area of your Android home screen. | Tap Widgets. | Drag the Meshtastic widget to your home screen. The app ships one widget, so the picker entry is just the app name. | Resize it as needed — the layout adapts to the available space. | . ℹ️ Note: The widget is Android-only. It is not available on the Desktop or iOS builds. ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/widget.html#adding-the-widget",
    
    "relUrl": "/ro-rRO/user/widget.html#adding-the-widget"
  },"6412": {
    "doc": "Home Screen Widget",
    "title": "Related Topics",
    "content": ". | Node Metrics — the full Signal Quality and Local Stats history inside the app | Connections — connect to a radio so the widget has stats to show | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/ro-rRO/user/widget.html#related-topics",
    
    "relUrl": "/ro-rRO/user/widget.html#related-topics"
  },"6413": {
    "doc": "Home Screen Widget",
    "title": "Home Screen Widget",
    "content": "On Android, Meshtastic provides a home screen widget that shows live local statistics from your connected radio at a glance — no need to open the app. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/widget.html",
    
    "relUrl": "/iw-rIL/user/widget.html"
  },"6414": {
    "doc": "Home Screen Widget",
    "title": "What It Shows",
    "content": "The widget displays the connected radio’s current local stats: . | A node chip across the top, carrying the radio’s short name in its own colors | Battery — the radio’s battery level, or Powered when running on external power | ChUtil — channel utilization (how busy the LoRa channel is, as a percentage) | AirUtil — airtime utilization (how much of the duty cycle your radio is transmitting) | Traffic — packets transmitted / received, and duplicates seen | Relays — packets relayed and relay cancellations (shown when the radio is relaying) | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Heap — free versus total memory on the radio, drawn as a bar | Nodes — how many nodes are online, out of the total known | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . Tap the widget to open the app, or use its refresh control to request fresh stats. ℹ️ Note: The values reflect the connected radio. If the radio disconnects, the widget replaces the stats with a status line — Disconnected, Connecting, or Device sleeping. It does not keep the last-known numbers on screen. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/widget.html#what-it-shows",
    
    "relUrl": "/iw-rIL/user/widget.html#what-it-shows"
  },"6415": {
    "doc": "Home Screen Widget",
    "title": "Adding the Widget",
    "content": ". | Touch & hold an empty area of your Android home screen. | Tap Widgets. | Drag the Meshtastic widget to your home screen. The app ships one widget, so the picker entry is just the app name. | Resize it as needed — the layout adapts to the available space. | . ℹ️ Note: The widget is Android-only. It is not available on the Desktop or iOS builds. ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/widget.html#adding-the-widget",
    
    "relUrl": "/iw-rIL/user/widget.html#adding-the-widget"
  },"6416": {
    "doc": "Home Screen Widget",
    "title": "Related Topics",
    "content": ". | Node Metrics — the full Signal Quality and Local Stats history inside the app | Connections — connect to a radio so the widget has stats to show | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/iw-rIL/user/widget.html#related-topics",
    
    "relUrl": "/iw-rIL/user/widget.html#related-topics"
  },"6417": {
    "doc": "Home Screen Widget",
    "title": "Home Screen Widget",
    "content": "On Android, Meshtastic provides a home screen widget that shows live local statistics from your connected radio at a glance — no need to open the app. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/widget.html",
    
    "relUrl": "/pt-rBR/user/widget.html"
  },"6418": {
    "doc": "Home Screen Widget",
    "title": "What It Shows",
    "content": "The widget displays the connected radio’s current local stats: . | A node chip across the top, carrying the radio’s short name in its own colors | Battery — the radio’s battery level, or Powered when running on external power | ChUtil — channel utilization (how busy the LoRa channel is, as a percentage) | AirUtil — airtime utilization (how much of the duty cycle your radio is transmitting) | Traffic — packets transmitted / received, and duplicates seen | Relays — packets relayed and relay cancellations (shown when the radio is relaying) | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Heap — free versus total memory on the radio, drawn as a bar | Nodes — how many nodes are online, out of the total known | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . Tap the widget to open the app, or use its refresh control to request fresh stats. ℹ️ Note: The values reflect the connected radio. If the radio disconnects, the widget replaces the stats with a status line — Disconnected, Connecting, or Device sleeping. It does not keep the last-known numbers on screen. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/widget.html#what-it-shows",
    
    "relUrl": "/pt-rBR/user/widget.html#what-it-shows"
  },"6419": {
    "doc": "Home Screen Widget",
    "title": "Adding the Widget",
    "content": ". | Touch & hold an empty area of your Android home screen. | Tap Widgets. | Drag the Meshtastic widget to your home screen. The app ships one widget, so the picker entry is just the app name. | Resize it as needed — the layout adapts to the available space. | . ℹ️ Note: The widget is Android-only. It is not available on the Desktop or iOS builds. ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/widget.html#adding-the-widget",
    
    "relUrl": "/pt-rBR/user/widget.html#adding-the-widget"
  },"6420": {
    "doc": "Home Screen Widget",
    "title": "Related Topics",
    "content": ". | Node Metrics — the full Signal Quality and Local Stats history inside the app | Connections — connect to a radio so the widget has stats to show | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/pt-rBR/user/widget.html#related-topics",
    
    "relUrl": "/pt-rBR/user/widget.html#related-topics"
  },"6421": {
    "doc": "Home Screen Widget",
    "title": "Home Screen Widget",
    "content": "On Android, Meshtastic provides a home screen widget that shows live local statistics from your connected radio at a glance — no need to open the app. ",
    "url": "/Meshtastic-Android/main/en/user/widget.html",
    
    "relUrl": "/en/user/widget.html"
  },"6422": {
    "doc": "Home Screen Widget",
    "title": "What It Shows",
    "content": "The widget displays the connected radio’s current local stats: . | A node chip across the top, carrying the radio’s short name in its own colors | Battery — the radio’s battery level, or Powered when running on external power | ChUtil — channel utilization (how busy the LoRa channel is, as a percentage) | AirUtil — airtime utilization (how much of the duty cycle your radio is transmitting) | Traffic — packets transmitted / received, and duplicates seen | Relays — packets relayed and relay cancellations (shown when the radio is relaying) | Diagnostics — a combined line carrying Noise (the background noise level in dBm), Bad (corrupt packets received), and Dropped (packets the radio discarded). Bad and Dropped appear only once they are above zero, so a quiet radio may show the noise reading alone | Heap — free versus total memory on the radio, drawn as a bar | Nodes — how many nodes are online, out of the total known | Uptime — how long the radio has been running since its last reboot, shown beside Nodes | Updated — the time the stats last refreshed, along the foot of the widget | . Tap the widget to open the app, or use its refresh control to request fresh stats. ℹ️ Note: The values reflect the connected radio. If the radio disconnects, the widget replaces the stats with a status line — Disconnected, Connecting, or Device sleeping. It does not keep the last-known numbers on screen. ",
    "url": "/Meshtastic-Android/main/en/user/widget.html#what-it-shows",
    
    "relUrl": "/en/user/widget.html#what-it-shows"
  },"6423": {
    "doc": "Home Screen Widget",
    "title": "Adding the Widget",
    "content": ". | Touch & hold an empty area of your Android home screen. | Tap Widgets. | Drag the Meshtastic widget to your home screen. The app ships one widget, so the picker entry is just the app name. | Resize it as needed — the layout adapts to the available space. | . ℹ️ Note: The widget is Android-only. It is not available on the Desktop or iOS builds. ",
    "url": "/Meshtastic-Android/main/en/user/widget.html#adding-the-widget",
    
    "relUrl": "/en/user/widget.html#adding-the-widget"
  },"6424": {
    "doc": "Home Screen Widget",
    "title": "Related Topics",
    "content": ". | Node Metrics — the full Signal Quality and Local Stats history inside the app | Connections — connect to a radio so the widget has stats to show | Local Mesh Discovery — channel and airtime utilization across the mesh | . ",
    "url": "/Meshtastic-Android/main/en/user/widget.html#related-topics",
    
    "relUrl": "/en/user/widget.html#related-topics"
  }
}